Here's a chart which has a good deal of info: http://www.websemantics.co.uk/resources/font_size_conversion_chart/
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 21 2016
Sep 20 2016
Yes, but this is createwiki, which is a mess :P If I was rewriting the whole extension, then I'd have bothered to css it.
Don't use inline styling, it's harder to maintain and also decreases customizability because of CSS specificity. ( https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity ) It'd be better to add a class, (e.g class="welcome-text") and then style it via
See rSHWK3988
Resolved in rADMP25
It's in the i18n files - "createwiki-newmainpage" is the message. Will need to be changed in all language files.
Sep 19 2016
Sep 18 2016
Sep 16 2016
Sep 15 2016
So, "pop-up" box exists. There are still some issues with it, but they can go in a new ticket.
Sep 14 2016
This is somewhat "intentional" for the time being.
Sep 13 2016
Sep 12 2016
Sep 11 2016
Sep 7 2016
Aug 15 2016
Upgraded for REL1_27, in rSHWK3967.
Aug 14 2016
So this is likely to be because of a preference using a rendering method we don't have enabled currently. If you select the PNG rendering, it should work.
Aug 7 2016
What do you mean by that? The feed stuff comes from MediaWiki core, so provided that it's not a configuration issue with ShoutWiki, we should report it upstream if it hasn't already been fixed there.
I heard that it is Chromium-specific error. See screenshot.
The contents of the NewsBox are pulled from MediaWiki:Newsbox on the Interface Messages Wiki. It is true that the linked page is somewhat old and unfortunately named, but nevertheless we are always interested in hearing your thoughts!
To be honest, there aren’t any interesting things to link to them. Russian Wikia (and maybe others too) has monthly competition (users vote for best wiki on forum and on VK (Facebook analog) and staff votes too). I think, ShoutWiki needs competitions and other cool stuff.
This is partially true. However, I'm pretty confident we're not going to achieve a massive improvement in page loading times by removing all the spaces and whatnot from the source files. You're right in that optimization is needed, but I'd argue that back-end optimization will be more useful in the long run.
I found some whitespace-removing services. They removed 4KB from HTML. It isn’t much, I agree.
Aug 6 2016
Looking at your site in particular, one third of the things Google has as a "Should fix" are actually nothing to do with us - your site loads an external stylesheet from Wikia which is yet another DNS lookup and request which has to be processed by their servers, and then rendered by your browser, after the stylesheet calling for it to be loaded has been processed by our servers.
Aug 5 2016
dir="ltr". Why is it specified?
Page content and User Interface language can be different. But you'd have to ask upstream for a definitive answer.
I'm pretty sure this was either an upstream bug or we fixed this at one point and it probably broke somewhere between a version or moving to HHVM+Nginx. Possibly even the distro upgrade...
Aug 3 2016
Aug 1 2016
Jul 31 2016
Fixed in R20:14. Thanks Jack :)
Using the uselang=qqx URL parameter on Special:AdminPanel/privacy I was able to figure out that the page expects the message keys to be adminpanel/privacy-privacy-section-editing and adminpanel/privacy-privacy-section-viewing (sic!), most likely because the special page is named AdminPanel/privacy in the constructor.
Wasn't an issue when using extends specialPage, only became an issue on extends FormSpecialPage.
Added in R20:13.
Most completed R20:12.
Two things have been split off into new tasks:
Completed with R20:9, Minor fix in R20:10
Completed R20:11
Completed in R20:7
Completed as of R20:3
Jul 30 2016
Jul 28 2016
Er, the extension has a global one and local ones on all the other wikis now, and just sort of merges those on those wikis, so if we converted to use that, uh...
So I added (and self-merged) a new hook point, RefreshedInSidebar, to Refreshed (upstream commit), which allows us to inject 125x125px ads into the sidebar area.
Jul 27 2016
@isarra Do you know anything any thoughts on this? You merged our nasty hack (the ShoutWiki Interwiki Magic extension) into the upstream Interwiki extension a long time ago.
Also, rename the submit button to "send"?
Needs to include a link back to the main AdminPanel page. And an explanation/link to an explanation of private wikis?
Jul 26 2016
Jul 25 2016
Fixed in rSHWK3876. Already deployed.
Quoth lines 315-319 of /extensions/CreateWiki/CreateWiki_backend.php:
// Allow this feature to be turned off, because history has sadly taught // us that we might need to do that every now and then... // This has to be here instead of being at the very beginning of this // function so that we can use the $wikiId variable here. if ( $wgCreateWikiAnalyticsLogMode && $wgCreateWikiAnalyticsLogFile ) {
Set $wgCreateWikiAnalyticsLogMode to true and $wgCreateWikiAnalyticsLogFile to a valid path and it won't even try to query the analytics DB, but rather writes the data to a comma-separated file.
If those variables aren't set and thus a connection to the analytics DB is attempted, in lines 351-353 we log the error message to both CW's own log ($wgDebugLogFile['CreateWiki']) as well as the standard error log (error_log()). Do you want the ordinary error_log removed and/or a new wfDebugLog call with a new group name (such as CreateWikiAnalytics) inserted?
Jul 24 2016
So we're looking at a 1.26 freeze sometime tomorrow evening (25/07/16) and then we'll begin working towards a 1.27 release with an internally agreed, rather hopeful timeline.
So I was thinking something along the lines of the libraries in vendor/ - which I believe use PHP namespaces (which I'd like to learn more about) and then if we need to write an even smaller meta-extension for that, then we could do that (and a name has disappeared from my head in the time it has taken to reply to this) and then load that globally.