- User Since
- Jul 25 2022, 10:21 (35 w, 1 d)
- GitHub User
- Miraheze User
- Creeper19472 [ Global Accounts ]
Mon, Mar 6
Feb 26 2023
Sent this reply just to confirm that this task of mine has not been forgotten...
Feb 25 2023
I just had another problem when I was testing regular expression substitution (although it seems to have been mentioned by a previous reply), showing that the edited page doesn't exist (but they do), it looks like there's something more complicated about this? I hope that measures will be taken as soon as possible, as the magnitude of its impact exceeds my previous estimates.
Feb 24 2023
By the way, is it possible for me to request a refresh for the whole site (in order to avoid other probable problems)?
Feb 23 2023
Feb 19 2023
Feb 2 2023
Jan 27 2023
I need a file dump however there isnt a option i can select for this operation. So I'm reopening this ticket.
Jan 26 2023
Jan 24 2023
Jan 22 2023
Now ProtectSite doesn't work again
Database name: theredpionnerwiki
Jan 21 2023
Jan 18 2023
Jan 17 2023
Jan 13 2023
Ohh.. It seems to be fine just now. But I wonder why it happened. I'm closing this issue because it seems not to be a problem anymore.
Jan 12 2023
Jan 1 2023
Then why can't we just make ReplaceText extension disappear from the list? Leave it in the extensions list of ManageWiki can make bureaucrats confused because of this problem that can't be solved.
Database name: theredpioneerwiki
Dec 24 2022
[59a7449daa769ea0db090b8c] 2022-12-24 01:01:55: 类型“Wikimedia\Rdbms\DBQueryError”的致命异常
Dec 23 2022
I noticed that a pre-release version of MediaWiki 1.40 has been released recently. Will there be a situation where we, Miraheze, will catch the official 1.40 release just when we are ready to upgrade to 1.39? This may be quite dramatic, but given the current pace of testing (T9745), I think it is possible. :P
Dec 17 2022
Nov 19 2022
Oct 4 2022
Sep 23 2022
This doesn't just happen on one page. All pages cannot be edited, even if they are not protected.
Aug 12 2022
I'm sorry for the mistake I just made... I hope it didn't cause you too much trouble.
The login systems of various wikis such as Meta are dead. I don't know if the system administrators noticed this, but I almost couldn't get on Phabricator. I completely thought it was necessary for Miraheze to immediately find out why this was (because I had seen such a failure twice in less than three weeks) and tell us if it was a problem that could be fixed.
I'm really, really a bit unhappy now.
Aug 10 2022
Aug 9 2022
82 Hours Left ****
Aug 7 2022
I'm waiting for response - I would very much like to do this because it will save a lot of trouble. (I imported many templates from Wikipedia.) :)
In addition, I have unprotected all pages protected by these two new permissions, and have also unchecked these two permissions in each user group. I guess changing them shouldn't cause any problems with the wiki. Just change the names added in the last commit one by one.
Aug 6 2022
Just have a try? I just need to rename these two permissions. No user group has to be renamed.
Change the name of the permission added in the last ticket to the name Wikipedia named it: templateeditor and extendedconfirmed.
Sorry. It's my fault. I forget to add permissions to the sysop groups... So yeah, I can't use them, of course.
Well... actually, there are still some problems.
I can see these two new permissions now, but still can't set the protection level like this in the protection list - it seems that they are not added to the list of options available.
Aug 5 2022
Again... Again... Again...
Err... In fact, I just still haven't found these two permissions. Search yielded no results. User groups have been created, and it is not seen in the permission settings of the user group.
Sorry, but there's another problem.
I do not see any changes on my site. Is it because I need time for synchronization or other operations or because I need to clear the cache locally?
Yes, that's right. But I think I can create these two user groups myself. Of course, it would be better if you could create permissions and user groups with the same name.
Also, what I need to add is:
Aug 4 2022
Again. Just 30 minutes ago.
Aug 2 2022
I don't know what happened today. There're so many 502s happened, much more than before. Then it showed me this strange problem.
Jul 31 2022
It still happens from time to time, and at the same time the 503 Backend Fetch Failed problem can also appear. (But recently Curl Error seems to be less than before.)
Jul 27 2022
This problem appears to be a collective failure caused by this entire database server going offline. Is this a common phenomenon?
Jul 26 2022
Also ran into this issue on Meta Wiki: this error was returned when replying to a user discussion.
Supplement: When using Special:Import, if the number of imported templates reaches a certain number at one time, this error will also occur, resulting in failure to import normally.
Jul 25 2022
Updated request... I've revised the description of the request on miraheze (which was previously declined).
Since Miraheze's review process seems to have been stalled for a while... I've filled in the Miraheze subdomain I filled in here in advance, sorry.