Talk:CentralNotice/Archive 2
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Subpaging campaigns
Hi. We've currently got pages scattered around for specific CentralNotice campaigns. For example, CentralNotice/Generic maintenance notice and CentralNotice/Shared and Image filter referendum/CentralNotice. I'm wondering if it makes sense to move all these pages to a subpaged format under "CentralNotice/Campaigns/" or something. So it'd be ... CentralNotice/Campaigns/General site maintenance, CentralNotice/Campaigns/Shared, and CentralNotice/Campaigns/Image filter referendum, respectively. A bunch of other pages could also be moved. Thoughts? --MZMcBride 17:33, 10 December 2011 (UTC)
- Having a single page where they're all listed would make it much easier to follow them (no need to keep adding them to your watchlist)... Mike Peel 20:12, 10 December 2011 (UTC)
- Using subpages, MediaWiki can auto-generate a list of pages. It'd be syntax like ... {{CentralNotice/Campaigns/}}. That's one of the advantages to using subpages. --MZMcBride 22:52, 10 December 2011 (UTC)
- True. But I'm not clear about how that relates to following pages? Mike Peel 23:00, 10 December 2011 (UTC)
- Ah, I missed that you wanted to watchlist them. I don't think MediaWiki supports any feature that would make that easier. No matter the system used (subpages, independent pages, pages in a category), you'll need to manually update your watchlist. You could also try something like Special:RecentChangesLinked. --MZMcBride 05:05, 11 December 2011 (UTC)
- True. But I'm not clear about how that relates to following pages? Mike Peel 23:00, 10 December 2011 (UTC)
- Using subpages, MediaWiki can auto-generate a list of pages. It'd be syntax like ... {{CentralNotice/Campaigns/}}. That's one of the advantages to using subpages. --MZMcBride 22:52, 10 December 2011 (UTC)
Aww wtf?. C'mon. You are the worst! Also, Hi! We do need a centralized page for centralnotice, all the other pages could be linked from there. We never really developed any guidelines or found a conclusion to that RfC about global banners, until we have those, it's better to have a separate page for Admins to keep track of centralnotice requests. I made that page after the discussion on Internal-l, when Brion and Beria disabled the campaign there wasn't a location they could have made a note at, or explained why. Theo10011 13:57, 10 December 2011 (UTC)
- Try a noticeboard? And it's not related to Meta-Wiki, so it wouldn't go in Meta-Wiki's namespace. Some pages are already neatly subpaged (e.g., CentralNotice/Calendar and CentralNotice/Shared). So you'd want CentralNotice/Noticeboard or something of that nature. Maybe not "noticeboard," maybe "water cooler" or "beer pub" or whatever. Move the redirected page there and then make it less of a cluttered mess? Sounds like a plan to me. :-) --MZMcBride 17:09, 10 December 2011 (UTC)
- Also, there surely was a location they could have made a note at. Nemo 17:34, 10 December 2011 (UTC)
- Well, yes, there was a location, but I think Theo's point is that there might have been a better/more centralized/more obvious location. --MZMcBride 17:52, 10 December 2011 (UTC)
- Also, there surely was a location they could have made a note at. Nemo 17:34, 10 December 2011 (UTC)
Banners with no CSS
Can someone take a look into this issue? Helder 21:40, 29 October 2012 (UTC)
- Please see discussion at Bugzilla #41751 Mwalker (WMF) (talk) 21:42, 3 November 2012 (UTC)
Origin is not allowed by Access-Control-Allow-Origin
I got the following error on ptwikisource: XMLHttpRequest cannot load https://meta.wikimedia.org/wiki/Special:RecordImpression?banner=B12_JimmyBlank&campaign=C12_bitest&userlang=pt-br&db=ptwikisource&sitename=Wikisource&country=BR&bucket=0. Origin https://pt.wikisource.org is not allowed by Access-Control-Allow-Origin. Helder 01:28, 1 November 2012 (UTC)
- Hopefully this issue has been resolved. We are now using a different method to record the number of banners seen by users. This was pushed late afternoon PDT on the 1st. Mwalker (WMF) (talk) 21:38, 3 November 2012 (UTC)
- I should also say that this was tracked at Bugzilla #41623. Please comment there if you are having further issues. Mwalker (WMF) (talk) 21:50, 3 November 2012 (UTC)
Notice for CentralNotice administrators
Since MediaWiki 1.21wmf8 you don't need to specify translations for dummy language codes (such as be-x-old, but not de-formal, the latter is a regular language variant, like be-tarask). For more details, see MediaWiki 1.21/wmf8 and patch details. Thank you! Wizardist (talk) 20:19, 30 January 2013 (UTC)
- There are some doubts about it: Help_talk:CentralNotice/Translations#message fallback. --Nemo 20:28, 30 January 2013 (UTC)
- Nemo, Wizardist is talking about a different patch (for reference my fallback patch is 44224.) But; on that note; I'm confused about what dummy language codes were actually used for in CentralNotice. It seems like be-x-old would fall back to be just like de-formal would fall back to de -- but in the case of be-x-old. Is this because the I18N team has decided that be-x-old is not a 'real' language and therefore removed it? Mwalker (WMF) (talk) 21:03, 30 January 2013 (UTC)
- It's all due to confusing different terms. de-formal is a legitimate language code for a language variant. be-tarask is a legitimate language code for a language variant. They fall back to de and be respectively (though the latter is not very good, but it's ok). be-x-old is a dummy language code. In other words, it's not a real language code and MediaWiki knew it for a while already. Using this terminology, be-x-old should not exist as a Language entity (speaking by terms of MediaWiki i18n implementation), but it existed and used the fallback mechanism. Now be-x-old is automatically transformed to be-tarask, so the system just doesn't deal with be-x-old (for example, if you set ?uselang=be-x-old, and get the value of wgUserLanguage in JS debugger, you'll get be-tarask; and de-formal will be kept, because it is a different matter). Wizardist (talk) 21:17, 30 January 2013 (UTC)
- Ah, thank you. Actually I do know the difference between dummy languages and language fallbacks, but suspected you were still talking about the same change. (And indeed I was confused when I ended up on that commit.) --Nemo 21:20, 30 January 2013 (UTC)
- Concerning "what dummy language codes were actually used for in CentralNotice": if a dummy code was set by the user in Preferences, then the CentralNotice would not fall back to a working one. Nevertheless the dummy language code is requested on client-side or server-side, if it's requested via Language class, it will be converted to a real code. Wizardist (talk) 21:22, 30 January 2013 (UTC)
- It's all due to confusing different terms. de-formal is a legitimate language code for a language variant. be-tarask is a legitimate language code for a language variant. They fall back to de and be respectively (though the latter is not very good, but it's ok). be-x-old is a dummy language code. In other words, it's not a real language code and MediaWiki knew it for a while already. Using this terminology, be-x-old should not exist as a Language entity (speaking by terms of MediaWiki i18n implementation), but it existed and used the fallback mechanism. Now be-x-old is automatically transformed to be-tarask, so the system just doesn't deal with be-x-old (for example, if you set ?uselang=be-x-old, and get the value of wgUserLanguage in JS debugger, you'll get be-tarask; and de-formal will be kept, because it is a different matter). Wizardist (talk) 21:17, 30 January 2013 (UTC)
Interface change? Bugs?
Has the interface been changed recently (a couple of days ago, perhaps?) -- I can't see any banners in Special:NoticeTemplate, and can't either select languages from the dropdowns, ie, in: [1]. Any idea of what's happening? Thanks. -- MarcoAurelio (talk) 16:19, 9 May 2013 (UTC)
- Yep; we pushed the new interface yesterday. Special:NoticeTemplate is now Special:CentralNoticeBanners but it should be redirecting you. Not seeing any banners though is interesting -- a lot of the fundraising banners (or any banner that hides itself based on a cookie) you won't be able to preview yet because the banners are not yet written to look for a force=1 URL parameter. That being said it sounds like you aren't getting any previews? Does this hold true with the preview on Special:CentralNoticeBanners/edit/WLPA_alt? Internally the preview works by loading an iframe targeted at a special page on meta which then loads the banner and some skin overrides before communicating back to the parent page to resize itself. Is the iframe just not loading itself for you, or do they collapse to nothing?
- "Not being able to select languages from dropdowns"... is the control disabled? If it is enabled and you click on it, does the page not refresh with the new messages? (We are tracking an existing bug that seems to be preventing banner preview in a language that is not the users default -- so the preview doesn't change, but the messages in the "Translatable banner messages" section should.) Mwalker (WMF) (talk) 16:33, 9 May 2013 (UTC)
- Thanks for your detailed answer. I do not see the previews while logged in, but I do while logged out in CentralNoticeBanners/NoticeTemplate. They do collapse to nothing. Regarding the dropdown, it happens that when I try to choose a language, the page inmediatelly reloads, preventing from choosing any language from that dropdown. Thanks. -- MarcoAurelio (talk) 16:40, 9 May 2013 (UTC)
- Do you perhaps have some user JS/CSS that is hiding the centralNotice div? E.g. to always block banners? (Or have the hide banners gadget installed and enabled?) If so that's going to prevent you from previewing whilst logged in.
- It looks like I'm probably using the wrong JS hook for the language selector. I'm curious why it works for me though... I'll push a patch this afternoon 62987. Mwalker (WMF) (talk) 17:07, 9 May 2013 (UTC)
- It's in User:MarcoAurelio/monobook.css (div#siteNotice {display: none !important}). PiRSquared17 (talk) 17:26, 9 May 2013 (UTC)
- I've pushed patches for the language selector and banner preview in arbitrary languages. Please let me know if you're still having issues. Mwalker (WMF) (talk) 16:44, 10 May 2013 (UTC)
FDC banner
Hi. I've tweaked the FDC banner to spell out what FDC stands for. The change, made via this form, resulted in three separate edits: [2] [3] [4]. A bit strange. --MZMcBride (talk) 17:59, 18 October 2013 (UTC)
- To me what is strange about it is that there should have been four changes. Each message is a separate object in both the MediaWiki namespace, and the CNBanner namespace. You edited in English, and in the UI, which is considered a canonical change so was immediately accepted for use (in the MW namespace) and presented for translations (the CNBanner namespace). Tilman apparently made the text2 change on the 16th; so the banner change you apparently made updated the CNBanner namespace... not sure why that didn't happen when Tilman edited. Mwalker (WMF) (talk) 18:15, 18 October 2013 (UTC)
FYI --Nemo 23:42, 22 October 2013 (UTC)
- Has been live for a while now: mail:centralnotice-admins . --Glaisher (talk) 17:25, 25 September 2014 (UTC)
RFC on improving CentralNotice
mw:Requests for comment/CentralNotice backend improvements. --Glaisher (talk) 17:19, 25 September 2014 (UTC)
Global dismissing
I don't understand, why are all the recent banners not globally dismissed? I have to dismiss them individually on each and every wiki for each account I have. (Seen with POTY, Wikimania scholarships, stewards elections, ...) Is a bug filed? --Nemo 08:10, 10 February 2015 (UTC)
Banner colliding with name
All the best: Rich Farmbrough, 15:29, 29 October 2015 (UTC).
- Dismiss the banner? — Martin (MSGJ · talk) 15:38, 29 October 2015 (UTC)
- For all our readers? I never get it, when I point out a problem with the interface, I get solutions that hide the symptom for me. I feel like an ageing climate scientist trying to warn of an impending ice age, and getting a rug tucked around my knees, and a cup of hot coco.
- Thanks for the coco! But that's not really the point.
- All the best: Rich Farmbrough, 16:23, 29 October 2015 (UTC).
- Looks like a meta:CentralNotice. —TheDJ (talk • contribs) 16:59, 29 October 2015 (UTC)
- I'll cut and paste this there. All the best: Rich Farmbrough, 22:45, 29 October 2015 (UTC).
- I saw this problem too. Firefox 41.0.2, Windows XP, MonoBook skin. --Redrose64 (talk; at English Wikipedia) 00:08, 30 October 2015 (UTC)
- @Shizhao: 這是在用MonoBook時以發生的問題。你可以看看能否解決這個問題嗎? -- KTC (talk) 02:13, 30 October 2015 (UTC)
- see [5]--Shizhao (talk) 08:50, 30 October 2015 (UTC)
- I saw this problem too. Firefox 41.0.2, Windows XP, MonoBook skin. --Redrose64 (talk; at English Wikipedia) 00:08, 30 October 2015 (UTC)
- I'll cut and paste this there. All the best: Rich Farmbrough, 22:45, 29 October 2015 (UTC).