The "Place a challenge here for untrusted users." on all forms will only appear for user 1 on all my sites, even when other users have administer captcha and skip captcha permissions. Form store is working fine, and I can do everything fine with user 1, but not with any other users.

Comments

naught101’s picture

right, it's working now. It appears that once everything is set up, that user1 must place a captcha, or at least log in before it works for other users. This was extremely confusing for me, since I prefer to use my own user rather than user 1, and this meant I was searching for ages, and couldn't find any way of using captcha.

This needs either a documentation update, or a patch.

soxofaan’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

I can't reproduce your issue:
* create admin role and admin user (uid>1) in this role
* install CAPTCHA module (5.x-3.1)
* assign "admin CAPTCHA" and "skip CAPTCHA" permissions to admin role
* as admin user:
** goto CAPTCHA settings page
** enable the "Add CAPTCHA adminstration links to forms" option
** goto "create content" > "page"
** view the "Place challenge" link on the form

Are you sure you had the "Add CAPTCHA adminstration links to forms" option enabled?

naught101’s picture

Priority: Normal » Minor

Yes, I'm very sure, soxofaan. It may have been an anomaly for just this site though - I had just upgraded from a much older version of captcha.

If I see it again, I'll add more info. I the mean time, if anyone else come across the problem at least they'll no know to log in as user 1 :)

soxofaan’s picture

Also note that the CAPTCHA administration links are not added to administration forms (on pages ?q=admin/*)

gnat’s picture

Title: "Place challenge" links do not appear on forms except for user 1. » "Place challenge" links do not appear on forms unless a user has skip CAPTCHA permissions.

I have reproduced almost exactly this behavior.

I installed CAPTCHA, and gave my user role the "administer CAPTCHA settings" permissions, but not the "skip CAPTCHA" permission, because hey, why not make the admins use CAPTCHA as well.

With this configuration I was able to get to the CAPTCHA settings page (admin/user/captcha) and turn on the "Add CAPTCHA adminstration links to forms" setting. I then went to my custom module's form page; there was no link.

I then looked at another site where I am using CAPTCHA and saw the URL structure for enabling on specific forms. I hit that page, and got a form to set up a challenge on my form, selected a math question clicked save. I got a set message telling me that the settings had been saved, however the value for that form in the database looked like this:

+------------------------+--------+------+
| form_id                | module | type |
+------------------------+--------+------+
| my_form_id             | NULL   | NULL |
+------------------------+--------+------+

The form I was returned to for the CAPTCHA settings of my form, had 'none' in the drop down box.

I then gave my user role the "skip CAPTCHA" permission, and everything worked like it should.

I am changing the title of this bug be changed from ""Place challenge" links do not appear on forms except for user 1." to ""Place challenge" links do not appear on forms unless a user has skip CAPTCHA permissions". This is more descriptive of what the actual bug is, and the reason it works for user 1 is because they have the permission by default.

Adding CAPTCHAs to specific forms is an administrative task, and should not require that the user also be able to skip CAPTCHAs which is an issue of administrative choice for user role convenience.

soxofaan’s picture

Title: "Place challenge" links do not appear on forms unless a user has skip CAPTCHA permissions. » "Place challenge" links do not appear on forms except for user 1.

at gnat in #5:
in #287907: admin CAPTCHA preview, CAPTCHAs for admins, demo site CAPTCHAs there is a discussion and a patch about decoupling the skip CAPTCHA and admin CAPTCHA permissions.

soxofaan’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing old/outdated issues for 5.x releases, which is officially unsupported now.

If this issue still exists for Drupal6 or Drupal7, please reopen (and update the version)