All posts by K6ka

Nope. If I close the tab and try to click 'Edit' again, I get shown the same message and am presented with the draft copy again. The dialog box should give you options like "Continue editing draft" or "Edit the most current version" at the very least. I'm surprised (and frustrated) that this change was simply rolled out rather than offered as an opt-in beta feature.

I want an option to opt-out because it kept giving me a draft copy of the page to edit after I made a revert to the page I was editing. I wanted to edit the current version of the page and it keeps bringing me the draft copy, which was an older version of the page. There definitely should be an opt-out feature, and it should definitely be made more evident in the user interface that drafts are being saved.

I got a response from Staff earlier today. There are no other active admins on the wiki aside from me, and I most certainly did not submit the request. The change was done for SEO optimization, which I can understand, but it still doesn't excuse why this was done without even notifying the community.

MediaWiki:Welcome-user-page.

This has to be the zillionth change to the navbar in the course of a few years.

The current navbar is designed to look the same on all wikis, which is problematic as not all wikis look the same. You can't be saying that the current state of the navbar is a "one-size-fits-all" design because it isn't. On a wiki with lighter themes or themes other than the shade of blue the navbar uses, the navbar sticks out like an eyesore. The navbar should adapt to the theme of the wiki; why not make it, to an extent, customizable in Special:ThemeDesigner, or at least match the colours set in there?

Secondly, the ability to hide the navbar by scrolling down is what made me happy in the first place. I could simply hide what I didn't need to use right now as I focused on reading the text. Even in previous navbars, the navbar would at least fade and become translucent when I scrolled down, so it responded to my scrolling. Why remove a feature that was so useful to again permanently fix this navbar on my screen that never goes away?

You need to stop forgetting advice people gave you in the past and repeating the same mistakes. You also need to cut it out with this "no opt-outs" scheme and give people the choice to use your new changes or stay with the old for even just a little while longer. Instead of just suddenly migrating everyone to the new, have it available as an opt-in beta feature and collect feedback then rather than releasing it as final right away, with no method of reverting, and then waiting for feedback.

Admin Dashboard quick stats scores are failing yet again. This has to be the millionth time they've failed. Getting tired of submitting bug reports for this recurring issue.

I'm noticing that pressing g and r no longer takes me to Special:RecentChanges; in fact, it looks like it has been removed from the keyboard shortcuts menu (although the help page still references it). A bug or a removal of a good feature?

(Also wanted to note that the classic keyboard shortcuts don't work on Wikia/FANDOM at all, which is now doubly frustrating for me)

The "Quick Stats" section in the admin dashboard is displaying "0 views" again; this time the edit count is also broken.

Quick fix for this or no?

Things seem to be working now. DisplayClock, navigation popups, and HideRail are working from my brief observations so far.

I have also been unable to load a large number of JS since about three hours ago (That's when I woke up). Some scripts are working, others aren't. It doesn't appear to be affecting all users, and it definitely isn't affecting everything.

EDIT: I went through my global JS file and here's what isn't working:

• DisplayClock
• Navigation popups (from Wikipedia)
• Batch Delete (Misreported, appears to be working)
• AJAX Undo
• HideRail
• SkinSwitchButton
• HeaderLinks
• OldFilePages

Tabbers are also broken.

Posting in message walls counts as a change in the database, so when the servers are in read-only mode, message walls are amongst the things that will be disabled.

I've experienced the same problem on other wikis as well. It seems to be related to the Google Chrome browser and large file sizes, since I don't encounter this issue in Firefox, and not with smaller files. I've sent in a bug report to Wikia several months ago and got a response, but looks like they still haven't fixed this yet. To get it to play, go to the file, click on it, click on "Download file", and then press Shift+Ctrl+R.

I think it is possible to do it with AWB. I believe there's an option to scan a page for images, which you can run the bot on to add the category.

Try Special:Contact/general.

I believe he is referring to the HTML <span></span> tags that the rich-text editor often foists on you unknowingly when you use Ctrl+B or Ctrl+I. These tags can't be detected in RTE and must be removed via source mode. AFAIK they don't do anything other than make it difficult to read diffs and the raw wikitext of the page.

Preferences aren't saved via cookies, they're saved directly into your account, so preferences should carry over when you switch to a new browser or computer. My preferences are a bit wonky as well recently. It took me a full week of repeatedly changing my preferences before the site would stop loading the rich-text editor and load the source editor like I had specified it to.

There is a MediaWiki page size limit. By default it is 2048 kB (1)

You can mass delete pages using AjaxBatchDelete. It works better than AWB, in my experience.