Modify

Ticket #540 (closed enhancement: invalid)

Opened 4 years ago

Last modified 4 years ago

Captchas For Comments

Reported by: anna Owned by: dave
Priority: minor Milestone: 4.3 Beta1
Component: Commenting Severity:
Keywords: Cc:
Who will test this: And

Description (last modified by anna) (diff)

When not logged-in there is no captcha when adding a comment:  http://testing.plumi.org/Members/anna/videos/test-video/video_view#1291694188813371

There should be one, as per em.org currently.

There has been a tonne of spam added as comments to testing as a result:  http://testing.plumi.org/Members/tester/videos/my-video/view

NOT SURE YET HOW TO HANDLE THIS:

# do not include in Plumi - let site admins install if required # include in Plumi # include in Plumi in buildout - but do not activate by default (optional extra)

Attachments

Change History

comment:1 Changed 4 years ago by mike

Hi Anna,

both this ticket and ticket #511 were never features of plumi until now. They should normally be targeted on plumi 4.1 since they were added after development for plumi 4.0 was started (which was focused anyway on getting plone 4 compatibility, not adding new features).

Unlike task #511, enabling captcha on comments is just a (trivial) matter of installing plone.formwidget.captcha or plone.formwidget.recaptcha. However I'm not sure if we should make it part of plumi installation by default (and force installation and usage of one of these on the ppl using plumi), or only add it on testing and demo.plumi.org to avoid spam. I'm leaning towards the second solution, at least on this ticket. It should be a choice made by the administrator installing plumi IMHO.

comment:2 Changed 4 years ago by anna

Hey Mike,

Ah, there must be a misunderstanding here... I asked Andrew, he said captchas were part of the package, and should be available in Plumi.

Are captchas then part of the em.skin code? How are captchas being implemented on EngageMedia.org?  http://www.engagemedia.org/Members/yerry/news/feature-filmmaker-indrani-kopal/view

If they are part of EM code, and not part of Plumi, we could just put these tickets to a later milestone if we wanted to include captchas inside Plumi.

I can see arguments for/against including this by default in Plumi.. this comes back to the larger question of what Plumi should/shouldn't be, which would be good to address properly at some point (when we are not so busy!).

In some ways including captchas on the demo / testing sites but not in Plumi.app might be confusing for people trying out the software.. but would be useful as you say.

I guess a third option would be to include these in installation - but not activate this by default?

This could be part of many "optional extras" that are included in Plumi, but not activated by default..

comment:3 Changed 4 years ago by anna

  • Priority changed from major to minor
  • Summary changed from Captcha missing from comments to Captchas For Comments
  • Type changed from defect to enhancement
  • Description modified (diff)
  • Milestone changed from 4.0 RC 1 to 4.1 Beta 2

comment:4 Changed 4 years ago by anna

  • Owner set to dave

comment:5 Changed 4 years ago by anna

  • Status changed from new to closed
  • Resolution set to invalid

We're leaving these out now.

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.