Hi Mak,

I've been playing with this for over an hour and was finally able to get it to work. I'm not sure if I've followed correct procedure, I'm no experienced coder, but what I did other than the described steps was:

Edit extension\ezwebin\design\ezwebin\override\templates\full\ feedback_form.tpl

Above the code for the send button, and an include for the recaptcha.tpl. I took that from the design folder from the recaptcha extension itself.

Once that was included, the captcha feature showed up on my contact form. I'll ask Bruce, the maker of this extension to verify if I've done this correct.

Regards Robin

p.s. editing that template file is probably not best practice, my method was to see if I could get it to work, noting more

Modified on Saturday 05 February 2011 11:33:38 pm by Robin Muilwijk

Hi Mak & Robin

While the extension and the instructions aim to make the process as easy as possible, some things in eZ Publish require an understanding of what is happening to get things going.

The reCAPTURE extension provides a datatype that can be added as an attribute to a content class. Getting it to display usually means having to add the attribute to the templates (This is usually the case when adding attributes to a content class)

To add it to the ezwebmin feedback form template you need to add the following lines where you want the reCapture to appear:

<h4>{$node.data_map.recapture.contentclass_attribute.name}</h4>
<div class="attribute-recapture">
  {attribute_view_gui attribute=$node.data_map.recapture}
</div>

See here for a full template.

This assumes that the recapture attribute is an information collector and the attribute identifier is "recapture"

Ideally you would add copy the template from the ezwebmin extension into a local design and make the change there.

Cheers
Bruce

P.S. I'm pretty sure there's no need to restart Apache

Modified on Thursday 17 March 2011 5:58:07 am by Bruce Morrison

Hi Bruce,

Thanks for the help! I did put the attribute code in the feedback form .tpl but it did not work. I used .recaptcha, and not .recapture as attributename since that is also the identifier in the class.

I'll try that later on, and remove the call/include to the recaptcha.tpl.

Would it be an idea to add this to the steps on your project page, to add this code, as example? I figured out how to do it, but it shows beginners how this is done. Very useful.

-- Robin

Bruce,

I tried your code, made sure the identifier for the reCAPTCHA attribute is also called recapture, was recaptcha before. The heading is showing in the contact form, as a label, but no captcha form?

We must be forgetting something. I'm trying this on eZ + Webin, 4.4.

Thanks Robin

This assumes that the recapture attribute is an information collector and the attribute identifier is "recapture"

That did the trick, setting the new attribute as information collector, and adding your code made the captcha feature show up on the contact form.

Thanks Bruce.

@ Kam,

Just add the code Bruce is suggesting, make sure your attribute identifier is named recapture, and it is an information collector. Clear cache, and it should work.

Modified on Sunday 06 February 2011 10:22:45 am by Robin Muilwijk

It does not work for me!
Here's how I've done:
1 ° I copied the folder "recaptcha" in the folder "extention" .
2 ° I added the "ActiveExtensions [] = recaptcha"in the file site.ini.append.php in the "settings /override ".
3 ° I add "$ {<h4> node.data_map.recapture.contentclass_attribute.name} </ h4>
<div class="attribute-recapture">
attribute_view_gui {attribute} = $ node.data_map.recapture
</ div> " in file" design / base / override / templates "/ full / feedback_form.tpl
4 ° I empty all the caches.
5 ° I add an attribute in the class "Content / Feedback form" recaptcha and I named it "recapture".
That, I think I followed exactly the procedure but I have nothing that appears.
Could you tell me the exact procedure to do to operate.
Thank you again for your support.
Sincerely,

Hi Mak,

Two thing you need to check. The template I edited is:

Edit extension\ezwebin\design\ezwebin\override\templates\full\ feedback_form.tpl

Not the one in the /design/base folder, as this is overridden by the same template in the ezwebin design.

Second, check the attribute you added, did you check the box which says "information collector"? If that is not checked, nothing appears.

-- Robin

Hi Mak

It may be the editor, but your template code appears to be incorrect. The eZ template code needs to be within {}. Make sure it is:

<h4>{$node.data_map.recapture.contentclass_attribute.name}</h4>
 
<div class="attribute-recapture">   {attribute_view_gui attribute=$node.data_map.recapture} </div>

Cheers
Bruce

Modified on Saturday 12 March 2011 12:02:23 pm by Nicolas Pastorino

Thank you for everything Robin and Bruce.
It works! Thank you again.
Sincerely,

OK I needed reCAPTCHA in the registry form so I did everything as noted above for User Class and Comment Class.

reCAPTCHA IS showing... but if you place false data on it or none at all and hit the submit button, reCAPTCHA IS NOT WORKING, information will still be submited...

anybody knows how to solve this??

Modified on Saturday 12 March 2011 2:59:46 am by Luis Delgado

Hi Luis, is your reCAPTCHA attribute a required field (just double-checking)? Kind regards, Sebastiaan

Hi Luis, is your reCAPTCHA attribute a required field (just double-checking)? Kind regards, Sebastiaan

Hi Sebastian,

Yes it is set as requiered and Information Collector, thats the strange thing... at least I would like it to be available for user registry. For comments I will install ezComments add in whcich it now includes reCaptcha.

Hi Luis

This thread is about using the recapture extension with the feedback from. The feedback form uses information collectors to gather data while user registration actually creates a new content object.

You need to add something like

{attribute_edit_gui attribute=$node.data_map.recapture}

to your user registration template instead of attribute_view_gui.

HTH

Cheers
Bruce

Modified on Thursday 17 March 2011 5:58:51 am by Bruce Morrison

Hi Luis

This thread is about using the recapture extension with the feedback from. The feedback form uses information collectors to gather data while user registration actually creates a new content object.

You need to add something like

{attribute_edit_gui attribute=$node.data_map.recapture}

to your user registration template instead of attribute_view_gui.

HTH

Cheers
Bruce

Well the good news as you pointed correctly... I just removed the "Information Colector" check and the reCAPTCHA worked right away!

This is so cool... I had like 13,000 sapm registration just this week... Finished Stuff

This is so cool... I had like 13,000 sapm registration just this week... Finished Stuff

Yuhu !

Hmm, is it normal that this file is empty?

https://github.com/brucem/ezpubli.../content/datatype/view/recaptcha.tpl

Update: forget about my question... I forgot to set the attribute as a collector...

Modified on Saturday 03 December 2011 11:23:20 pm by Quoc-Huy NGUYEN DINH

Hey HuyGlad you worked it out!For the benefit of others:It seems to be a common issue, but the recapture datatype is only used when gathering data. i.e. editing a content object or as an information collector. There is nothing to display in the view mode as it doesn't make sense to display the capture unless it is presented with a form.The view template for the datatype is present but empty so that warnings are not generated.CheersBruce

Cheers mate.Have you ever tried to make it work with ezsurvey?

Hi Huy

I haven't tried to get it to work with eZSurvey but I suspect it would be very similar to eZComments which includes recapture functionality. Both use a custom datatype to  link external data management to a content object.  The reCapture code would have to be integrated into the the data processing component of the extension.  

The existing reCapture extension is all about easily adding the caputure to the standard eZ object editing and content collection, but I suspect with a little work the reCapture functionality could be abstracted out to make it easier to include in these types of extensions. Pull requests welcome

Cheers
Bruce