Topic: How can I allow non-registered users to comment, etc.?
Topic type:
This topic is a guide to the enhancement put forward on Ticket #295 where site administrators can designate actions (i.e. commenting) on the site that the public can do without registering. We refer to these users as anonymous, though we ask for some info.
We refer to the public (non-registered users) as "anonymous" for the purposes of this functionality, though we ask them for optional information about themselves. This should help to distinguish this functionality from public/private version functionality in Kete content.
Feature Summary
Kete 1.3 introduces the ability for site administrators to allow certain actions, determined by a system setting, to be taken by a non-registered user if they enter an email address and answer a security question (captcha or logic question).
This is useful for allowing non-registered users to comment or contact basket administrators.
At this time, these are the two scenarios that are tested and recommended. Other actions are possible, but haven't been tested for Kete 1.3.
The feature is described in Ticket #295.
Usage
As a site administrator with tech administrator privileges, do the following.
- Scroll to the bottom of any page and find the Administrator's Toolbox
- Click reconfigure site
- click Advanced Options
- Click Server
- Scroll down to the Allowed Anonymous Actions setting, read the information for it THOROUGHLY!
- Fill out the setting accordingly and click Save
- Click Restart Server button
After restarting the server, the actions that you have specified will not prompt the user to login OR enter name, email, and website with a captcha.
If you choose to allow anonymous comments, they will behave similarly to many blog platforms comment systems.
If you want to enable anonymous filling out of the contact form, you probably want to read this topic about using the Contact link:
created How can I allow non-registered users to comment, etc.?
on Nov 9th, 2010 at 1:41 PM
Walter McGinnis
said If you get an "Invalid Authenticity Token" error with this feature
I implemented this on a site and had a very difficult to track down bug where a non-registered user would enter their information successfully and then fill out the contact form and submit it. It would then give an "Invalid Authenticity Token" error back to the user.
The problem was that in the background a piece of javascript on the page was making a bad request for an image file that didn't exist on the server and Kete would return a 404 page to the calling javascript (i.e. the user wouldn't see it at all) which in turn trigger the user's session to be invalidated and the token to be changed.
By fixing the bad image request, I solved the "Invalid Authenticity Token" error and everything came right for the feature.
Noting this incase anyone else has this error.
Tags: Troubleshooting, Invalid Authenticity Token, 404, 500, errors