Thanks for the information - I'll wait for your alternative solution.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 7 2020
Jul 6 2020
In T287#4341, @bergmann.lat wrote:I think Rose-Biblio is one of the largest wikis in shoutwiki and you must earn some money with it by advertisement on my sites. Spending "a few hours" could be a little bit more! Working with singleupload is not acceptable for my needs.
I think Rose-Biblio is one of the largest wikis in shoutwiki and you must earn some money with it by advertisement on my sites. Spending "a few hours" could be a little bit more! Working with singleupload is not acceptable for my needs.
Jul 3 2020
This is a known issue and as MultiUpload is effectively abandonware, we'll likely be forced to retire it for the time being until someone can patch it, I'm afraid.
Cross-wiki database operation weirdness...
Jul 1 2020
Jun 28 2020
This was caused by the TitleKey extension, which I've now disabled globally.
Special pages seem to be unaffected by this. However, it also seems that some article pages are missing, for example, I noticed that in fi.starwars Taistelu Ord Mantellissa or Star Wars (Yhtyneet Kuvalehdet) are not included in search suggestions.
Gotcha, I saw that forum post earlier, but it was when the most recent reply to it was an instruction to post to phabricator.
Is this a side effect of the resolution to the following task: New wikis not created properly?
For the record, Special:MyWikis throws the same error.
Jun 27 2020
Jun 26 2020
It does appear to be fixed. Thx
Jun 25 2020
I believe this should be fixed?
Okay, apparently https://phabricator.wikimedia.org/rMW2d33abad9280f338e625768a408b067763a3064e should fix this. Not sure why this hasn't been backported to REL1_34 branch...
Jun 14 2020
Jun 12 2020
Jun 11 2020
Jack cleaned up the affected wikis, and I've turned off CreateWiki (ish) for the time being. New wikis before we get back to 1.34 are going to cause more issues than its worth.
Jun 10 2020
It looks like it fixed itself.
Jun 9 2020
Jun 1 2020
May 26 2020
So we now run a find command which pipes to xargs to delete directories under /path/to/settings/deleted that haven't been modified in 30 days. This gives us enough time to hopefully notice we've deleted the wrong wiki or for someone to appeal a deletion (not that we have a formal appeals process) while not hoarding deleted wikis forever.
So this turned out to be surprisingly difficult to actually fix. For some reason, the server keeps throwing me either old or 503ing CSS...
No longer deployed in favour of SemanticBundle.
No longer deployed in favour of SemanticBundle.
@jack Did this ever get fixed?
Could not reproduce, no indication of continued issue
Chirp upgraded, Vertex decommissioned
Vertex decommissioned and replaced by Utter.
May 19 2020
Current blocker/extensive consideration required: T273
May 4 2020
May 3 2020
As this is bundled with MediaWiki by default now, I don't see any huge issue with enabling it globally - we'll probably roll this with MediaWiki 1.34
Got the same just now. Does that mean that there is no way to create a wiki for a unforeseen time?
May 2 2020
Got the same just now. Does that mean that there is no way to create a wiki for a unforeseen time?
May 1 2020
Apr 29 2020
Apr 25 2020
It is entirely intentional. Language subdomains are a blocker for our HTTPS rollout, so we're actively removing the ability to create new ones and are in the process of clearing up as many of them as we can. When we get a better idea of how many we need to keep, further details will be provided to existing wikis.
Apr 24 2020
Feb 12 2020
BTW, there appears to be no such thing as a #security tag in this phabricator ....
Feb 7 2020
Jan 19 2020
I remember getting a similar error. I think this is - at least partly - because page imports are currently disabled (they were apparently being abused, so they're working on a new, more manageable system, last I heard).
Jan 16 2020
I remember getting a similar error. I think this is - at least partly - because page imports are currently disabled (they were apparently being abused, so they're working on a new, more manageable system, last I heard).
Jan 13 2020
The extension is unmaintained upstream, and we'll be dropping it as soon as it causes a security issue or no longer works.
Jan 12 2020
Jan 6 2020
Dec 30 2019
Dec 26 2019
Fixed this hours before I saw this ticket...