jobrunner2 added and configured

Import is in progress. Please note that it may take quite a while as imports are slow.

Where it says "destination" it should be mw-lb.miraheze.org

It's a script

@Lawrencedepe It seems that after all there is still a mistake. Please make sure that the CNAME points correctly.

Yes, it was correct now :) Your wiki is now accessible at the custom domain.

The import has been completed. Assigning to RhinosF1 as he said he would investigate the internal error.

@Lawrencedepe Hi. It doesn't appear that you've correctly pointed your domain to us. Please read https://meta.miraheze.org/wiki/Custom_domains for how to do that.

Per Sam's comment. Since the debug statement left out doesn't hurt anything we can install this

The SSL has been renewed.

Re security reviewers (@Samwilson @Southparkfan ) this looks like a very quick review

Could you also link us to the page that doesn't work?

There is no indication that there's another extension needed in the docs.

It's happened a few times to me again and I would find it strange for it to be upstream since it only started a while ago (maybe one or two weeks)

Score restricted in ManageWiki until it's resolved.

https://github.com/miraheze/puppet/commit/b48e7e321f54ba61a6bbdc6d11679ebcb2f57c9e

The check has been fixed. If the underlying issue still causes issues another task for that should be opened.

import is in progress

@MusikAnimal Which one would you want?

The issue described here has now been resolved and the backlog has been cleared. As an actionable T5994 has been created and therefore the discussion for how to prevent this from happening again can be taken over there.

The script run in T5987 only included @comment pages as requested. I did nothing to any Thread: prefixed pages.

Wiki recreated (reset).

@Catman504 The extension is now installed and you can enable it via Special:ManageWiki/extensions :)

Removed. When it is correctly configured please feel free to reopen this task and we will be happy to re-add your custom domain

Following an internal discussion, we thought it was sufficient to clarify what shouldn't be done and the consequences in the current pages rather than create a new policy. I have done accordingly and updated https://meta.miraheze.org/wiki/Custom_domains/Cloudflare to make it more clear what shouldn't be done and that it may result in removal.

Extension has been enabled by RhinosF1 and myself and now works globally.

John has investigated this issue and hasn't found what could be causing it here, therefore we find that it is best to create an upstream task for this (https://phabricator.wikimedia.org/T259265) therefore declining this task as it is seemingly not something we can resolve.

It doesn't seem that this is happening on the WMF, example https://meta.wikimedia.org/w/index.php?title=Steward_requests/Username_changes&diff=prev&oldid=17154345

This seems to be to be an upstream case as I tried to search a local file on the English Wikipedia and also couldn't find it unless I pasted the exact name. I've filed an upstream task here: https://phabricator.wikimedia.org/T259228 and unfortunately since this is an upstream case (seemingly at least) there's nothing Miraheze can do.

Without a community discussion (RfC) an extension such as this would not be globally installed on Miraheze. Users are invited to create accounts (which takes very little effort) in order to maintain their privacy.

Unfortunately it is a known problem upstream and not something Miraheze can help with since we do not develop VisualEditor. The suggestion is that VisualEditor not be used to edit templates.

Page Triage is available in Special:ManageWiki/extensions (perhaps you searched it in one word instead of in two?). This issue is not a technical issue and there should be a local discussion for enabling on Meta.

In T5860#116696, @Cool11guy12 wrote:

Still, I noticed nothing happened yet. What is the status of the task?

This is not actually an error or a problem in configuration. This issue you describe is because you used the HIDDENCAT magic word on Category:Hidden categories itself which caused the loop. Removing the magic word from that page (where it shouldn't be per MW.org and en.wiki) fixes the issue.

In T5266#115678, @Tycio wrote:

do you know if Phabricator is able to use the desktop app or Chrome to DL it?

I can't use chrome on this comp to test out

Seems to have already been imported (import finished immediately)

Due to the fact that there doesn't seem to be a solution to this (but it would be good if there was one) I think it's better to put this to low in case someone would like to investigate further and see if there is a way to fix this. As I indicated above, there seems to be something that could be done.

@Helper Hi. I would just like to ask how necessary this extension is for your wiki. As you know the review backlog is very crowded and I was wondering if it might be easier to simply encourage your users to create accounts rather than have them edit from their IPs.

@Yevvie @dross Mermaid is now available to be enabled in Special:ManageWiki/extensions

In T5904#115402, @Paladox wrote:

I’m not sure what the issue is as I cannot reproduce.

.ttf enabled on your wiki

@Reiwa-Boy Could you please give us a link to the page where all the users have agreed to the license change?

unfortunately unless something changes we need a lot of resources for ElasticSearch clusters which currently can't really be allocated

In T5975#116765, @Helper wrote:

Extension:Calendar-WikiVoyage is good enough so far and I created all calendar activity based Wikivoyage. One thing I could not understand and did not find help in documentation is how change a weekday from short to long format $a-$A, but it is ok. Nevermind. All other calendar I requested based Java and allow visitors throug user-friendly interface add or edit event. As per this moment we will ignore that option for visitors and all events edits would be done by some administrators. So those another calendars cold be assigned as low priority for now. The lunar calendar is very important thing for providing a dynamic data for everyday visits and could motivate users come more often. The extention I asked to install in this task seemed to be unclear about how to use it. I was looking for some lunar calendar template or extention on Wikipedia, but seems like Wikipedia does not have any tools in this topic as per now. They have a lot of pdf's or generated tables of lunar calendar or refer to third-side websites for such information, which is looks like there is nobody who requested or built such calendar tools yet. I believe the Miraheze community could benefit from locall calendar conversion toll, if it would be built and provided to wikifarm in form of template or extension. So the bottom line, all other calendar requests are not important as lunar calendar / moon phases conversion tool. Thank you in advance. Appreciate your work and Happy =5th= Anniversary to Miraheze ! "5" is magical number. Good luck and together all the way to future.

In T5942#116844, @RhinosF1 wrote:

Should we go and file a report with them then?

While it could be useful to default it to that, I would like to point out that clicking on "Requested At" manually will allow you to view the most recent requests instead of the oldest.

lh3.googleusercontent.com is now whitelisted.

Per John's comment above, unless there is some sort of community consensus this cannot be undertaken by us here.

@Helper As you have noticed the security review process is quite slow. I am not sure what to say, but it will be difficult for us to be able to review the 4 different calendar extensions that you have requested, so would it be possible that you look more into them and see which one you would like?

In T4789#115677, @Aunst wrote:

In T4789#115338, @Reception123 wrote:

@Aunst Per Southparkfan, have you tried other similar extensions and found that they were not suitable for you?

Yes, I've tried Extension:Comments, but I think it isn't suitable for my wiki.

@John What do you think about this? What should be done?