Actually, scratch that... this is just stalled on getting the extension fixed.

Actually, scratch that... this is just stalled on getting the extension fixed.

Actually, scratch that... this is just stalled on getting the extension fixed.

Declined for now per T4545#86255

Declined for now per T4545#86255

Declined for now per above.

Currently wikibase does not work for us which is why it's restricted for now, until we manage to get it to work.

Ah, that will need a steward to enable, next time please say 'enable extension x on wiki y' this is normally because of the impact of an extension so we don't let anyone create it and it requires a steward to add it. MangeWiki is working fine here.

Ah yes, for some reason Wikibase Client is restricted to sysadmins to enable... I've seen that before and I'm still not sure why that is the case. Anyway, someone, perhaps @Paladox will need to enable it for you.

But as I can see, wikibase client extension is not available and required managewiki permission. Please check attachment.

ManageWiki is available on all wikis, assuming that you are a bureaucrat or a member of another group with permission to access it.

You can enable in Special:Managewiki

I seem to be okay without the banned user group, but can I please get the extendedconfirmed protection level added to Cyclonepedia? I already made the group on it, now I just need the protection level to get added in.

This resolved it's self. You just hit the time redis got full.

@Hypercane looks like you stole my ideas from Weather Wiki :P

Is there anything I must do on the Miraheze side?
tks

In T4536#86190, @AmandaCath wrote:

I like this idea.

I like this idea.

Will need an op to use DeleteBatch if they don't work with Nuke @Paladox @Reception123

Changes made, let's hope it works.
tks

Wiki now created but not sure exactly what happened so will leave open

Can not create any wikis

should be done

Marked as resolved.

@Mlfoster Now I have disabled it, and you should be able to manage extensions.

In T4523#86141, @The_Pioneer wrote:

Well, Stewards should be able to access private wikis without member rights, and even if I didn't have the permission to view the wiki, I wouldn't be forcefully logged out on other private wikis as it happened there.

Well, Stewards should be able to access private wikis without member rights, and even if I didn't have the permission to view the wiki, I wouldn't be forcefully logged out on other private wikis as it happened there.

In T4523#86139, @The_Pioneer wrote:

Something is going wrong with your wiki - the custom domain (https;//theliteratureproject.org ) will return error 404, and when I tried to fix it on the original domain (https://theliteratureproject,miraheze.org ), I'm forced to log out due to an unknown reason. I think only sysadmins can fix it.

https://theliteratureproject.miraheze.org/w/index.php?search=Special%3AUserLogin&title=Special%3ASearch&go=Go Is hidden from public view. @The_Pioneer try adding member to yourself from meta then do it.

Something is going wrong with your wiki - the custom domain (https://theliteratureproject.org ) will return error 404, and when I tried to fix it on the original domain (https://theliteratureproject.miraheze.org ), I'm forced to log out due to an unknown reason. I think only sysadmins can fix it.

We do ES or db5. Cost wise it’s one or the other.

Searching broke again for the 7 wikis ("curl -s 'localhost:9200/_cat/indices?v'" taking far tooooo long)

I concur with @Reception123. I've tried migrating all wikis to use ElasticSearch (which is unsuccessful). So i say our option is to buy a new DB server.

In T4493#85580, @John wrote:

While a valid issue, there is a solution for which a task already exists. Priority should be spent on that and if there still remains an issue, another specific task open for this.

Reopening per T4540

Done! your wiki is now available at https://theliteratureproject.miraheze.org/wiki/Main_Page

@Paladox do you think this is possible?

thanks for finding the typo. fixed.

Caused by a lack of db space that we are in the process of trying to resolve by implementing ElasticSearch.

Needs staff approval to proceed so adding staff