Currently all pages under CNBanner are completely protected. This, in general, follows the normal Translate extension rules which protect translation pages except that it also protects /qqq (documentation) pages. This means that only administrators can add documentation (either through the interface or through the wiki) which is, far from ideal :).
Version: master
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T34482 CentralNotice should respect language fallbacks | ||
| Open | Feature | None | T38591 Use the Translate extension in CentralNotice (tracking) | ||
| Resolved | None | T53478 Don't protect documentation pages for CentralNotice translation |
mwalker wrote:
(In reply to comment #0)
Currently all pages under CNBanner are completely protected.
Unless I'm missing something; CentralNotice only protects /en and /qqq in CNBanner.
This means that only administrators can add documentation (either
through the interface or through the wiki) which is, far from ideal :).
I choose to have /qqq protected because it shadows /en (and will be overwritten if /en changes.) I'm open to suggestions on how we could make that better though.
(In reply to comment #1)
(In reply to comment #0)
Currently all pages under CNBanner are completely protected.
Unless I'm missing something; CentralNotice only protects /en and /qqq in
CNBanner.
Ok, that does appear to be the case, sorry about the confusion.
This means that only administrators can add documentation (either
through the interface or through the wiki) which is, far from ideal :).I choose to have /qqq protected because it shadows /en (and will be
overwritten
if /en changes.) I'm open to suggestions on how we could make that better
though.
What do you mean.... qqq should never shadow /en they are very different things ... /qqq is for documentation (for example 'do not translate this it's a CN variable and not a text piece' ) while /en (on meta) is source 'the actual text'. Right now the current system (because /qqq is protected) blocks non admins from editing the documentation which is not right.
Indeed, you should avoid prefilling (aka polluting) qqq with en strings in the first place as well.
Change 76639 had a related patch set uploaded by Mwalker:
Don't Create, Populate, or Protect CNBanner /qqq