In T11039#224352, @Paladox wrote:

Having it deleted sooner should be requested on https://meta.miraheze.org/wiki/Stewards%27_noticeboard.

It looks like The Obey Me Wiki was never closed or deleted from Miraheze? The redirect to obeymewiki.com seems to be gone now, but obeyme.miraheze.org pages are still live and showing up in some search results.

The move seems to have been a success and nothing is missing or broken, so yes it would be fine to delete the wiki from Miraheze now. Thank you.

My wiki (obeymewiki) is having the same problem.

In T10937#220894, @MacFan4000 wrote:

Now available at https://drive.google.com/file/d/1Um_9lBo6SIGxaWScCoINmPDbB6iKqvE5/view?usp=sharing

In T10937#220517, @MacFan4000 wrote:

Looks like the dump is big enough that swift won't accept it, I'll have to download it from the server and upload it for you.

The second attempt also resulted in status "Failed."

After waiting a few hours, the Status of the image dump has changed to "Failed" and is a non-existent file of 0 bytes.

I apologize, I asked this here on phabricator because I didn't think this would be considered a "general support" question, but a request to change my wiki's system settings. I don't fully understand what I seem to have found in trying to research this myself, but it seems like this should be possible by using MediaWiki API?

This issue is continuing to consistently happen on my wiki. Not a single mp4 file added since this error started has been able to generate a thumbnail image.

In T10838#219252, @Ugochimobi wrote:

Using visual editor in the Template: namespace?
You shouldn't be using the visual editor in the template namespace.

I forgot to mention this before, but this is something being experienced by multiple uses on my wiki, with various browsers uses and both on PC and mobile.

My wiki (obeymewiki) is also having this problem with no thumbnails appearing for videos. If I try to preview a missing thumbnail I get this message:

In T10643#215770, @Universal_Omega wrote:

This happens on everything using the default favicon also, including Miraheze landing and Miraheze Meta. This is likely caused by Miraheze using 16x16px favicons by default, and your wiki might also, for Google at least, it states:

Your favicon should be a multiple of 48px square, for example: 48x48px, 96x96px, 144x144px and so on. SVG files, of course, do not have a specific size. Any valid favicon format is supported. Google will rescale your image to 16x16px for use in search results, so make sure that it looks good at that resolution. Note: do not provide a 16x16px favicon.

If that isn't the issue, then I'm not sure, but this is a common issue on Miraheze.

In T10643#214488, @OrangeStar wrote:

Everything looks okay on the wikis, could be just search engines doing their thing.

In T10614#213642, @Reception123 wrote:

Which one would you like as your main one?

In T10614#213639, @MacFan4000 wrote:

It is working as expected. In T8959 you requested for www.obeymewiki.com to be set as the custom domain for wiki. We never did anything with the root domain.

Oh, thank you! I checked the "Special:ManageWiki/extensions" and configuration options for Visual Editor, but when I didn't find anything there, I didn't think to check on the general settings page.

Oh, I didn't realize this was a change I could make myself. Thank you very much for the help!

Thank you very much!

Thanks!

Well I don't get the exact same error message anymore, but now I'm having this new error message continually popping up:

I do seem to have stopped running into that error on the wiki, so thank you!

The reason I noticed the image missing is because I visited a page the image was used on and it wouldn't load, no matter how many refreshes or purging of the page I tried, so I checked it's file page and got that error. But the image appears on that page now, so good I guess?

I have found another missing image, this time with a different error message.

It isn't fixed still. Sometimes loading of pages is just insanely slow, but repeatedly for the past hour I keep getting 503/502 errors.

In T9581#194720, @ZeusDeeGoose wrote:

Seems like the 503s are finally starting to let up. I haven't got one this afternoon.

That's unfortunate; I guess I'll just stick to the player having a play/pause button and little else so that it can fit within the tables we use. Thanks for letting me know.

I don't have a MediaWiki account so I'm just going to post this here.

Oh, thank you. I assumed that because the example website for the DarkMode extension was Miraheze that is was an extension maintained here.

I'm still figuring out how this extension works, but maybe this issue has something to do with the class "client-dark-mode" not being added to elements with the class "p-navbar" when using the dark theme. Both the header and footer navigation use this class.

It does looks like the Tweeki skin works now, or at least using it doesn't break the wiki. There still seem to be display issues, like the fixed footer not being fixed anymore and CSS styles not working the way they did before the update. I guess my wiki will just stick to the Chameleon skin, though it's good to know if something else happens with that skin then we'll have a backup skin.

Well if that's the case, I wish they would have made it optional for audio files to either open in a new window as before or play inline, because now the only way to make the player fit in my sortable tables is to gut the controls and put it in a div with overlap hidden.

No worries, and thank you very much!

Sure! This is a page that uses a lot of audio files that are in a table: https://www.obeymewiki.com/wiki/Majolish/Background_Music

This is an issue my wiki is still having. Our license is set to CC BY-NC 4.0, but on edit pages the text above the "save changes" button reads as "Please note that all contributions to The Obey Me Wiki are considered to be released under the Creative Commons Attribution Share Alike (see The Obey Me Wiki:Copyrights for details)."

Thank you!

Thank you so very much! Now I can get to work formatting the Chameleon skin to be our stand-in until our original skin is hopefully available again.

I tried using it again and it still does not work. I get this error, which I can't tell if it's the same error or not:

Okay, well I guess hopefully having found the only other culprit and it not being another upstream issue is good news. I had no idea the update was going to cause such major problems for my wiki.

Okay thank you, that did work and now the site is back up again.

I was able to get to the skins by the extensions page and then get to the Special:ManageWiki/settings page to change the default skin to Chameleon, but this this error returned:

What should I do then? If it's another skin causing the error, would removing all but the basic skins fix it? Then I could at least test other skins, and if installing a skin again causes the error to return, as least I'd know which skin is the problem.

Okay this is really bad. The skin we use is broken, but I also can't even try using and editing other skins to find a new one to use in the meantime.

I've encountered another error when trying to change the skin by visiting Special:Preferences

Oh...well that's bad. I had a nightmare like this. Oh crap. Is it possible to temporarily revert the MediaWiki update just for our wiki? At least until I have the time to scramble and try to get another skin working properly?

Thank you. Would it be possible to have an estimate of when - if fixed - we will be able to change our wiki back to the tweeki skin? While it's very good the wiki itself is accessible again, much of the content is broken or missing, as it depends on using the tweeki skin.

That would be a great help, thank you.

I can't access the wiki to do so. Every single page shows that error.

Okay, thank you. Is there anything that can be done in the meantime so the wiki is at least accessible to its users?

Alright, thank you for the assistance!

I see, thank you! I'll do that.

I've noticed that this extension has been added to the list of available extensions, but with "Requires: Permissions - managewiki-restricted"

Oh I'll try that, thanks.

Okay, thank you.

All I did to get the error was visit the Special:Moderation page when there was a pending edit, try clicking the "edit" button to make changes, and then I get the error.

Thank you so much!

I'm sorry I don't mean to rush anyone and I know people are busy, but could someone please help with this? I'm having a lot of trouble running my wiki because half the special pages I rely on to monitor things don't work, they're just too outdated.

Thanks!

@Reception123 Thank you very much!

I haven't had that happen before, but I found this guide that might help? https://windowsreport.com/browser-storage-mega-full/

I see, I didn't know about patrolling SocialProfile pages being an issue. That's really unfortunate. I was indeed able to edit the user pages by going to Special:EditProfile. Seems odd that the regular edit button doesn't work, or even give any message as to why it isn't working. SocialProfile seems to have some strange complications for a stable extension, but thank you for helping with it.

Alright, thanks!

Thank you for importing all of the wiki pages so quickly, but what about all of the images that also need to be imported? They're all contained in the second link I listed. Do I need to create another task for those?

I do have the PageTriage extension, but while the Special:NewPagesFeed lists regular content pages, it doesn't seem to list new templates, talk pages, or user pages, as all of those - including the unpatrolled pages - are not listed.

Oh, well that's disappointing. What should I do about the missing "mark as patrolled" link for my wiki then? I'd assumed it was related to the skin my wiki uses, but changing to different skins didn't fix the issue.

Right, sorry yes I do like that the extension is easy to give rights to who needs them. I was replying to @Ugochimobi and their user script suggestion.