Issues requiring new extensions to be enabled/installed on wikis.
Wed, Apr 10
Per discussion internally and also you can follow @NDKilla suggestion.
Sat, Apr 6
Mar 13 2019
Mar 8 2019
Mar 6 2019
In that case, I'd suggest looking at Moderation. It requires that every edit be approved by an administrator before it goes live. It's not exactly what you're looking for, but unless I'm missing something painfully obvious, there doesn't seem to be an extension (that we support) to approve users before they can edit.
how about the "approved users" extension @NDKilla was mentioning? All other alternatives seem like impossible to do. I used to have a media wiki in a different platform and we were able to approve users before they could edit. We had to do this cos we got hacked and bombarded by spam bots.
Thanks in advance and regards,
Mar 5 2019
As far as I know, there's no easy extension you can install to get this done. Instead you need to setup editing restrictions using our existing tools.
yes, I guess approved users sounds to have the functions that I am seeking for: approving new accounts before they start editing the wiki....
Thanks for pointing at this!
How do I get to that extension (approved users)?
Feb 28 2019
Thanks @Paladox - I'll close this now.
I updated PageForms yesterday which brought in some fixes for PageForms.js.
It is now working! I could tell it was going to work because previously it had a processing circle of whirliness in the centre of the screen when you were creating a form and now it doesn't. I haven't closed this ticket. I'm interested as to whether someting happened overnight that sorted Cargo out?
Feb 27 2019
Feb 25 2019
This is available now.
Feb 20 2019
@MikeV It has been installed and added to ManageWiki, so you may now enable it on your wikis.
Completely upstream with no dependency on us in any way, task here adds no value.
Feb 19 2019
Since the extension is very simple, John has said it is okay to be installed. I will proceed with the install soon.
Feb 18 2019
Done. (please reopen or file a new task if this is not resolved)
Feb 16 2019
Feb 14 2019
(Thanks to Reception123 for relaying my message earlier; I was locked out of Phabricator here.)
@Void no you could still do things like this:
Feb 13 2019
Will need a security review.
Isn't that resolved by using htmlspecialchars on line 164, as that is what defines $minCountInput?
Note from @Samwilson:
Will need to be security reviewed.
Feb 5 2019
That depends on the widget itself, you'll have to read the docs relevant for that widget
OK. And what do I add as "param1=value1|param2=value2}}"?
WidgetName is “iframe” while you’re including the whole url
I'd seen that but was unable to get it to work (see the 20ish attempts in the history pages).
Feb 4 2019
Neither are in Git.
Let's remove it and reinstall when upstream fix it.
We cannot install WarnNoCategories as it's not in git (and seems no longer available either)
Wiki specific coding per above. Until that is fixed, this isn't going to be added.
Feb 3 2019
Approach testwiki administrators (consuls) and gain permission before asking for a review of the extension once you've done the necessary work.