Has anyone had seen this error before while converting/rendering
an assembled book in to pdf ?
Yes, it's rather common. It can have several reasons, so it's best if you mention the specific page which is giving you the error.
I came across the page User:Lil Jay Rap Legend when cleaning up images on Commons. This user page is clearly for promotional purposes only and entirely inappropriate to the purpose of this wiki. I couldn't find any deletion process here on MediaWiki, so I'm requesting here to have the page User:Lil Jay Rap Legend deleted. --
Link to list open tasks from the extension's page displays both open and closed tasks
That's because now in phabricator, the project page goes to the workboard (see task T89865).
Is there any other viable URL that we could use to link to all open tasks of a project? All searches give ugly URLs without a project name on them, just numeric codes or similar.
I think there is no such feature any longer: the only option would be the advanced maniphest search, but the projects selectors don't accept strings, only PHID* variables.
Maybe there is a way to get all the PHID numbers or the project description URLs for all projects, we could then store them in a switch.
The workboard view is not the problem itself. Showing also closed tasks by default is the problem and will get fixed by the next update: phab:T90661.
The current situation has become even worse. Now those links lead to a 404 ERROR page!
Something claiming to be an "IPA phonetic alphabet" popup intercepts my keyboard input (skin Monobook, browser Chrome, visual editor off, template data on, no other tricks). It also happens here, I cannot add the colons required for indentation, it appears as some gibberish. I cannot add < (more gibberish).
This is the
stupid Universal Language Selector IME, the little keyboard icon that appears next to the textarea (when the textarea is focused), that has a shortcut-key for switching keyboards.
Click on that keyboard and change the input method to native.
Thanks, presumably I somehow managed to input a key combination switching it in an undesired position, and surviving a "restart browser" in that position. I certainly didn't open it, until I figured out that this helps to reset "native keyboard". Is there a way to get rid of it completely? I can barely guess what IPA tries to express in very simple cases, I'll never need to input it.
Thanks, I think I found a more permanent solution on Disabling the tool for your user account hopefully good for all browsers and all Wikimedia projects:
- Skip the "from the sidebar" blurb (I failed to grok it, maybe it is for Vector)
- Interpret "from the Keyboard menu" as…
- click edit on any page that can be edited
- click on the input method icon directly below the input area at the end of the row (right side for LTR)
- click on the last entry in the popup with a tool icon
- click disable IME everywhere, click on apply, ready.
Hi, I've no idea what Topic talk:Sewfq489tp3iic43 is, either a weird name in the main name space, or a weird talk page for a namespace not needing any talk pages at all, but it's definitely unrelated to Topic:Sewfq489tp3iic43, please move it without leaving a redirect.
Move to what place? You're the author of the talk page: Is it really needed, or maybe it can be deleted? How you created these talk page? :/
It's an experiment, I tried to figure out why an existing Topic:Sewfq489tp3iic43 contains a red link to itself, and is actually always shown as red link. Additional test:
Apparently there is no "Topic talk", the experiment ended up as article. JFTR this bogus article could be moved to Thread_talk:Project:Current_issues/Topic_talk:Sewfq489tp3iic43, as entertainment for the folks migrating Liquid threads to Flow, apparently namespace 91 is empty at the moment. But the red Topic:Sewfq489tp3iic43 is really wrong, it exists.
I've been trying to start a new discussion in the support desk but when I click on 'Save Page', my browser keeps reloading the Support desk page in editing mode with my post still inside the editor and not yet posted in the discussion.
(and apparently I can post here without a problem)
Using OS X Yosemite10.10.2. Tried Google Chrome 41.0.2272.118, and Safari 8.0.4.
It's completely broken script hell, Chrome never knows what the URL is, what the state is (crying "don't leave unsaved page" long after it was saved), wild guess, was your attempt over a slow/shaky connection? Maybe test a Thread:Project:Support desk/Cannot starting a new discussion in support desk/reply to figure out what's wrong.
It wasn't over a slow or unstable connection. It seemed to be related to the inclusion of external URLs, you can see my various experiments in the edit history found in Thread:Project:Support desk/Cannot starting a new discussion in support desk/reply
I was able to modify my original MediaWiki issue by eliminating the http:// part of the URL to my wiki and I was able to post successfully.
But yes, totally broken script. I've been getting those "don't leave unsaved page" prompts more often now.
Hi when visiting https://tools.wmflabs.org/extreg-wos/ it brings up a error saying tool does not exist but it was only working a few days ago.
The page says that Legoktm is the maintainer, plus this does not look MediaWiki related so Project:Current issues might be a more appropriate place to bring this up.
Last edit: 20:54, 12 April 2015
This user has used a bot to remove content from pages. Please revert their edits.
Hi, I updated a translation, but it won't save because of a cascade protection. I put my new version here : Translations_talk:How_to_contribute/26/fr It's the relevant discussion page.
It seems the default search namespaces on this wiki haven't been updated for some time. Just now I searched for
apidisabled in the search box, and only got 1 result, which was some release notes page. What I really wanted was API:Restricting API usage.
Currently the following namespaces are in our default search namespaces:
I propose that we add the following namespaces:
I believe you need to log a ticket in the bug tracker for this kind of change, as it requires modifying the site config files.
+1 Should be an easy change with a lot of benefits.
Yep, makes sense; let's also include them in content namespaces if we didn't yet.
+1 (they aren't content pages atm), if there is enough content to be helpful for search, it should be a content page.
I just read it now, so that would be a new change/task :)
I'm not sure if it is related to this change, but why are content pages no longer included in the default search? For a couple of weeks now I think, API: and Skin: are the only namespaces to be searched by default. To search "(Main)", "Help", "Manual", "Extension", you have to click "Content namespaces" (or check the appropriate checkboxes) after the default search has run.
這個頁面應該是繁體中文(Chinese Traditional, zh-hant)文字，為何變成了簡體中文(Chinese Simplified, zh-hans)文字？translatewiki:MediaWiki:Extdist-created-extensions/zh-hant
- And MediaWiki:Extdist-choose-extensions/zh-hant (translatewiki:MediaWiki:Extdist-choose-extensions/zh-hant).
translatewiki was changed but the change hasn't been reflected on the Mediawiki.org.
How come there's no search feature in the archives @ Project:Support desk?! (or here at Project:Current issues, for that matter)
You can watch such a thingy in action at WikiPedia. IMO, this is very useful, and i quite miss it here on MediaWiki.
Later edit: I guess this might be related with the new "LQT"/"Flow" design. Choosing eye-candy vs functionality, very well done. :-|
Please assist - I am unable to access/log into my account:
There is such a proposal, see [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org. This is the place where consensus for mediawiki.org changes is checked, hence I'm opening the discussion here.
Also, some users have already started disabling LiquidThreads on some talk pages to use wikitext instead: what to do? Should that be done on more or less pages?
LiquidThreads was an unmitigated disaster, in my view, and has made the site worse for being here. History before it was enabled was lost (or, at least, very hard to find) the links in e-mails never take you to the thread they're supposed to, the UI is horrible and it is difficult to find things you are looking for. It actually makes the site harder to use for anyone at all experienced in wikis, not easier, and so should never have been enabled.
I haven't used Flow, so I don't know how it compares, but I would certainly vote for removing LiquidThreads! If Flow actually works in a wiki-like way (i.e. you can view history, see the state of the page before it was enabled, edit comments where necessary, etc.) then I might be persuaded that it is a good replacement, but given our experience with LiquidThreads I am fairly sceptical. For it to work it would have to be something that works inside existing wiki pages, rather than fighting against them. It would also be a requirement that all LT content can be 'migrated' to Flow so that it is not lost or broken. It is not acceptable for it to simply be shunted off to an 'old threads' namespace and abandoned - it needs to appear where it was originally posted.
The issue is as much about how the extension works behind-the-scenes and how well it integrates with the rest of the wiki, as about the interface it provides.
For example, I don't want to lose my current talk page, nor its history. If what is there can be converted seamlessly to Flow, without losing my ability to view old revisions of the page (pre-flow and post-flow), archive things in the way I have done in the past, include some non-thread-like content (e.g. introduction section) and link to specific items without the links breaking as items change (e.g. if they move to 'page 2' of the listings) then it might be viable. Otherwise, please just remove LiquidThreads and don't mess up the wiki with further incompatible plugins.
PS - From reading the wikitech-l post, it looks like once again this is a decision being forced upon us without any kind of local consensus. MediaWiki.org should not be treated as a test site, without community buy-in. If you want people to be antagonistic towards Flow, and to resent its presence on the wiki, then that is a pretty good way of going about it.
Also, I didn't realise quite how experimental/incomplete Flow currently is. Therefore, my vote is (for now at least) a firm no!
The comment from Risker/Anne sums things up pretty well, as far as I'm concerned.
Please just remove LiquidThreads and come back to us with a proposal for Flow when it is out of beta and feature-complete.
Please no back to plain wikitext talk pages, at least for talk pages with hundreds of posts (like Current_issues and Support_desk). Wikitext talk pages are terrible to follow and archiving is as bad as the wikitext discussion format itself. I prefer LQT (in it's fairly bad state) before wikitext, but i welcome a move to Flow, after it is in a workable state (see, e.g., this mail).
See also[edit | edit source]
- Thread:Project:Support desk/Starting conversion of LiquidThreads to Flow at mediawiki.org
Is it possible to have a complete list of LQT pages on this wiki? That would help the discussion.
Certainly it makes sense to use modern discussion software on Project:Support desk, as that is a high-traffic forum-style page which is aimed at IT professionals and server administrators more than wiki users.
I agree that for the support desk, and maybe a couple of other support-related pages, a more forum-like approach is sensible.
However, one does have to question why we use the wiki for these purposes at all. We don't use the wiki for internal issue tracking, so I'm not sure why we are using it for support. I am not aware of any other company or open source project that would consider using a wiki for handling support issues - it is clearly the wrong tool for the job.
Perhaps a more sensible solution would be to use support desk software for handling the support desk, rather than trying to shoe-horn non-wiki-like tools into the wiki, which will inevitably bring unsatisfactory results (as has been shown with LQT).
FWIW, there was such a proposal too: phabricator:T31923.
Search is pretty good at finding LQT talk pages: .
Special:PagesWithProp also works.  - currently LQT is on 1,639 pages - (I'm not sure why that number differs (1,567) from the search that Nemo linked?)
I'm asking devs for help getting a more detailed listing of All pages ordered by size (number of posts).
The Flow/LQT_pages are interesting, thanks. Just for fun I looked at the even (non-talk) namespace numbers: One entry in 90 might be odd (3 contributions counted as 12), and for the Project:Forum redirect I didn't get why it's counted as 94.
Last edit: 07:14, 24 March 2015
Note: We'll be holding an IRC office hour for Flow, this Monday at 19:30 UTC / 12:30 PDT. You can find information on how to get online, including a link to a webchat option if you don't have an IRC client, on the meta office hours page. The intended focus is for questions about the LQT -> Flow conversion here. Everyone is welcome for discussions and question answering. Logs will be posted on the meta office hour page afterwards. Thanks.
Few minutes of testing were enough to discover that
- T93723: Conversion to Flow eats content
- T93721: Links to LiquidThreads threads don't work after conversion to Flow
WMF, please ensure you table such proposals only after you've thoroughly tested the conversion. Thanks.
I don't know if it's just an unfortunate coincidence, or what, but since this announcement, the usability of LQT has degraded a lot...
First I reported that submitting a reply doesn't display the reply unless you refresh the page (task T93374).
Today hitting "show preview" displays a confirmation dialog about leaving the page, and if you proceed, you end up submitting an edit to the underlying page and not on the message you was editing!
PD: Reported as task T94089
Some time ago I proposed this client. Unfortunately it never got approved and is now listed as "expired", but I'm still interested in it. What am I supposed to do?