Last modified: 2014-08-08 15:32:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9099 - Trigger captcha on page creation
Trigger captcha on page creation
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
ConfirmEdit (CAPTCHA extension) (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-need-review
Depends on:
Blocks: 8668 9255
  Show dependency treegraph
 
Reported: 2007-02-25 17:26 UTC by Platonides
Modified: 2014-08-08 15:32 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Add $wgCaptchaTriggers['create'] (1.26 KB, patch)
2007-02-25 17:27 UTC, Platonides
Details

Description Platonides 2007-02-25 17:26:26 UTC
Force to pass a captcha to create a page.
Comment 1 Platonides 2007-02-25 17:27:32 UTC
Created attachment 3269 [details]
Add $wgCaptchaTriggers['create']
Comment 2 Brion Vibber 2007-03-05 20:46:41 UTC
Hmm, couple things I notice:

First, it doesn't show the captcha until after you submit. For the URL-based
catcher and other specific triggers that's necessary because we don't know if
the trigger is present until you submit, but it's kind of annoying for page
creation maybe?

Second, this will apply to talk pages as well as articles. Perhaps it would be
good to be able to treat those separately.
Comment 3 AnyFile 2007-03-05 20:51:11 UTC
Just my two cents. If the captcha image is displayed at first time, it will be
show for all the time the user writes the text of the page, so a lot of time
will pass from when the image is first displayed and when the code is submitted,
Usaully captcha do not like that since the most time has passed the more is the
probability that a computer can answer.
Comment 4 Platonides 2007-03-05 21:11:17 UTC
You're right, Brion. I didn't add anything really new, so it doesn't show first
time it opens the "create", as it doesn't show when you use
$wgCaptchaTriggers['edit']

I'm not sure what's the best system. Captcha appears between toolbar and edit
text so it's not too friendly having it from the beginning.
There are also 'edits' which don't want to do a submit (only read the source),
wasting image bandwidth. 

On the other hand, it complicates things (not a problem for 8668) so showing it
first time could be good.

AnyFile, if the computer is able to solve it, it probably can solve it faster
than any human.


Separating ConfirmEdit config per namespace would be nice. What would be the
best method? 
$wgCaptchaTriggers[namespace]['create']? $wgNamespaceProtection?
$wgCaptchaNamespaceSkip?
Comment 5 Platonides 2007-03-14 17:38:49 UTC
ConfirmEdit configuration per namespace is accomplished on bug 9255.
Comment 6 Platonides 2007-09-12 17:54:35 UTC
Applied with bug 9255 on r20795.
Comment 7 Gerrit Notification Bot 2014-08-08 13:22:53 UTC
Change 152906 had a related patch set uploaded by 01tonythomas:
Removed the IMAP support from BounceHandler extension

https://gerrit.wikimedia.org/r/152906

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links