- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 14 2017
Mar 13 2017
Should be fixed when rSHWK4162 is deployed.
Mar 3 2017
We should probably decide what we want the logo dropdown to contain and configure it by default that a wiki can upload its own image for that. I'd assume we want the wiki and then Hub?
Feb 25 2017
Feb 1 2017
There's no real use of workboards here. Any that exist, are probably created by accident or as testing.
Since @jack has done some level of testing and it's not broken anything, I'm all for re-enabling it as soon as the server move is done.
Instead of handling two ticketing applications at once (OsTicket and Phabricator), we'd most likely only have to use Phabricator more, potentially meaning easier to track things
Pofenrially this could also prevent less confusion for the end user as-well, as in the end-user doesn't have to figure out when to use Phabricator and when to use OsTicket. Since currently ShoutWiki uses two applications for ticket management
To repeat and slightly expand on what I said on IRC... most of the information on a wiki info page would not be easy to come by, it's fragmented across various different locations (user_groups table, wiki_list/settings, logs and various other places) and often out of date - particularly in case of wiki_settings/wiki_list (and don't get me started on the fact the database in its current form is probably the worst place to store that information right now)
Jan 26 2017
Jan 19 2017
"I love doing massive find and replaces in all the settings files that require loads of escaping." said no Lcawte ever.
Jan 7 2017
This is now working, feel free to link your accounts!
Dec 29 2016
Dec 28 2016
Dec 27 2016
I'm not sure this is something we want to allow or encourage. I don't think we've ever had a definitive discussion on this, but it does raise questions when we think about privacy and data collection.
Dec 26 2016
Some 1.27 change to LocalisationCache... fixed.
Dec 24 2016
It's an experimental extension not updated since February. I don't think this'll be getting fixed any time soon.
rSHWK4061
@Saftzie's talk page provides some useful insight on what's happening. MediaWiki is, for some reason, expiring ShoutWiki_session and ShoutWikiUserID.
Dec 22 2016
I'll throw in my favorite solution, which Skizzerz proposed the last time I spoke to him about this: Let's Encrypt SSL certificates for <lang code>.*.shoutwiki.com, i.e. fi.*.shoutwiki.com (possibly relevant: this StackOverflow question). Looking at /trunk/languages/i18n/, there are currently 371 files in there so it would mean about the same amount of SSL certificates, which admittedly is somewhat of an ops nightmare, but the renewal of Let's Encrypt certificates can be automated and I'm sure someone already made a script for that.
I would imagine that this is a solution that'll be painful to implement initially but which wouldn't need too much maintenance after that and it would allow us to keep the current URL structure.
Dec 20 2016
Dec 18 2016
Can you provide further details on what wiki, browser and operating system you were using? It's also worth noting that there's an issue with sessions (T144) so can you try this again, ensuring it's not just because you are being logged out?
Okay - so upon not very extensive, further testing. My current conclusion is that:
Dec 17 2016
So I've been able to reproduce this after downloading an additional browser and using my bot account on Firefox.
Sorry about this! We turned Scribunto off temporarily during the upgrade as it was causing issues, and we had issues with harder solutions to debug as a more urgent priority.
Dec 16 2016
Fair point, assigning to Jack who is far more knowledgeable on this particular extension for input.
So it would appear that somewhere in the upgrade, AbuseFilter rights got unassigned (presumably by default upstream) and therefore resulting in sysops not having them. This, by way of array_merge, means staff also do not have.
Not really related to T145 - two different extensions. Should be fixed by rSHWK4043.
Got any examples?
This works for me. One thing I did notice earlier is that I had to completely clear all of my cookies for ShoutWiki to be able to even login, so there's definitely an issue with cookies somewhere although as far as I can work out it's a case of clearing them for everyone.
All the subdomains we actively send emails from (@, support & phabricator) now have DKIM and SPF. This seems to have reduced the numbers of emails going to spam.
Dec 13 2016
Dec 4 2016
Nov 25 2016
I'd agree with most of these except for Category:Sitemap, the Category:User*, Bot, Citation and Experimental (IMO, we don't have anything to populate these at the moment or in the case of Bot/Citation don't apply to the majority of wikis).
Nov 15 2016
Nov 14 2016
Should be fixed.