In several recent wiki editing workshops I conducted (with a total of a couple hundreds attendees, I think), the main obstacle users encountered in creating their user page was the ContentTranslation popup which absurdly suggests to translate the userpage from another language.
There are very few cases where ContentTranslation may be userful in the User namespace, and none when one is editing (creating) a userpage (i.e. non-subpage page in User namespace).
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Deskana | T124294 Too many pop-ups before a user can start editing? | |||
| Resolved | Amire80 | T135685 Don't interrupt userpage editing with ContentTranslation pop-ups |
Thanks. I can reproduce this, but only when editing the user page with VE. It's indeed unnecessary anywhere outside the main namespace.
We should probably run $out->addModules( 'ext.cx.campaigns.newarticle.veloader' ); only in the main namespace.
Other opinions?
Also, for some reason ext.cx.campaigns.newarticle.veloader and ext.cx.campaigns.newarticle are loaded in different hooks, which is odd. I guess that I did at long ago when we were creating the campaigns, I'm not sure why, and I suspect that it must be fixed and loaded in the same hook.
Change 289602 had a related patch set uploaded (by Amire80):
Show the newarticle CX campaign to VE users only in the main namespace
... OK, it's because of different hooks :/
I sent a simple patch and added a comment about this.
Change 289602 merged by jenkins-bot:
Show the newarticle CX campaign to VE users only in the main namespace