CMS Made Simple Forums

Currently running CMSMS 1.11.11 along with CGBlog 1.12.6, Captcha 0.4.6, Formbuilder 0.7.3 and could use some help.

I'm building a site that will allow anonymous people to add original entries, but I need some way to control spam. Based on various discussions and the add-ons available (like CGFeedback), I'm building the entry system around CGBlog.

Assuming CGBlog is the best option (please suggest alternatives if there are any), it appears that I have two basic options:

a) Integrate Captcha into CGBlog FESubmit form,

or

b) Build a from in Formbuilder, which supports Captcha, and build a UDT to map the form contents into CGBlog

I know there are discussions about the "Honeypot" approach suggested by Rolf, but the integration issues remain. Unfortunately, with either of these options I'm stuck because my coding skills are pretty well limited to HTML (and that's pretty hacktastic at times, too).

Any ideas are appreciated.

iosota wrote:I'm building a site that will allow anonymous people to add original entries, but I need some way to control spam.

Depending on what exactly you mean by "original entries" (comments, articles?) you might find CGFeedback useful, you can set it to require approval of comments:
http://dev.cmsmadesimple.org/projects/cgfeedback

Paul, thanks for your response and suggestion.

I should have been more clear. My plan is to allow anonymous users to post original articles to the site. Moderation will be used, but there is still a need for some front-end spam control to keep bots from overwhelming the system.

CGFeedback works well and is already in place for comments, and will include the Captcha feature. Works well to tie directly to CGBlog articles, but I don't know if it can be used as the means for original articles as well.

Seems clear that CGBlog was designed expecting that authors would be logged-in users, hence the lack of Captcha. Still, there is probably some way to do this.

Other ideas, anybody?

If you are going to be letting other post blog articles I would use FEU so they would have to be trusted to log in before submitting, you could also set cgblog so new post are "The Status of newly submitted blog entries: Draft" in Frontend Blog Submit Options...

Thanks, DrCSS. In most cases, forcing people to log-in is the right solution (and I use it for an existing site) but it won't work for my current project.

I do have the default set to "Draft" so that I can moderate entries. My goal was to alleviate the noise a bit from various spambots. Moderation will work until there is a better solution.