tharpa.osang

A bit more clarity…. I had been viewing code using “inspect element” in Chrome… In looking at the code this way, I could read the email address. In looking at raw source, however I see the obfuscation. It can stop some bots from harvesting emails, but not humans…

I modified Chris’ CF7_POST code so that it could take the obfuscate=’on’ flag if it was set, but what i would really like to see is a way to filter the value AFTER the user hits the send button, but before CF7 gets it . But after looking at the code, I’m guessing that it would require modifying both CF7 and CF7_DTX (since CF7_DTX essentially uses shortcodes inside of shortcodes…)

At the end of the day, I would like to be able to send a single form dynamically to many people, without exposing their email address to bots OR humans…. passing parameters to the server to allow the lookup and insertion of the email address after the form is posted but before the mail is sent.

In looking at the plugin code it appears that the obfuscate option is not available for POST or GET variables.

I then tried to add the form to the actual post… the form then used this shortcode:

[dynamichidden bioemail "CF7_get_custom_field key='contact'  obfuscate='on'"]

the form shows up, but unfortunately the email can still be seen via view source. What exactly is the obfuscate=’on’ option supposed to do??

You need to be sure to pass the variable in the link to the form, as in:
<a href="www.mycompany.com/myCF7form?prodname=someproduct">Add to quote</a> – that may require changes to your product list to add that info to the generated url

then, when you create the form, use a dynamictext field for the productname:

[dynamictext productname "CF7_GET key='prodname' "]

then CF7 / Dynamic Text will take the data from the field sent along with the url, and add it into your form

you may or may not wish to make the field editable when you create it in CF7

Thanks to Amir for answering this post. I now have Views and am learning how to use it!

I hacked together a potential solution: in simple-nivo-slider.php I modified the the simple_nivo_slider function by adding a new parameter so the function now starts like this:
function simple_nivo_slider($id='slider', $category='', $type='post') {

and then a little further down in the same function (after the other parameters and before the “# perform the query, shuffle if shuffle enabled” comment):

$query .= '&post_type='.$type;

	# perform the query, shuffle if shuffle enabled

and it seems to work fine using the php call

dunno if it will break any shortcodes yet – I will let people know if it does…..

I upgraded, but they still didn’t show up. My assumption is that the problem is in some of the default permissions set by the host. I really don’t like setting directories wide open – in general, a bad security practice – so I’m fine with re-installing my custom templates for now.

So… first step changed permissions on tmp and templates directories.

they started at rwx r_x r_x

i changed to rwx rwx r_x to see if adding group write permissions would do it…

that didn’t work.

I then changed it to rwx rwx rwx and it worked, but I don’t understand why a plugin can’t write to a directory it created….??

Could it be a permissions issue or ownership issue with users/groups?

I clicked the link, and immediately another link appeared below. When I hovered over that link the url ended with Failed to open file:”

Is there a link to do that in wp-admin somewhere?

OK, I copied them to another directory and then deleted them.

I then went to Advanced Options and ran the database check.

here is the output:

Forms table (wp_fm_forms)… OK
Items table (wp_fm_items)… OK
Templates table (wp_fm_templates)… OK
Settings table (wp_fm_settings)… OK
Forms table…
Form 1 for data table: OK
Form 2 for data table: OK
For duplicate IDs and slugs…
OK
Items table…
Checking form IDs exists…
OK
Checking unique names…
SLUGS OK
Templates entries:
Title: Form Manager Default Filename: fm-form-default.php Modified: 1308339877
Title: Monthly Donor Program Calculator-form Filename: fm-form-monthly.php Modified: 1308340207
Title: High-value Donor Calculator-form Filename: fm-form-highvalue.php Modified: 1308340208
Title: Form Manager Default Filename: fm-summary-default.php Modified: 1308339877
Title: Monthly Donor Program Calculator Filename: fm-summary-monthly.php Modified: 1308340212
Title: Summary for Data List Filename: fm-summary-multi.php Modified: 1308339877
Title: High-value Donor Program Calculator Filename: fm-summary-highvalue.php Modified: 1308340213
Settings entries:
Name: recaptcha_public Value:
Name: recaptcha_private Value:
Name: recaptcha_theme Value: red
Name: title Value: New Form
Name: submitted_msg Value: Thank you! Your data has been submitted.
Name: required_msg Value: ‘%s’ is required.
Name: email_admin Value:
Name: email_reg_users Value:
Name: template_form Value:
Name: text_validator_count Value: 4
Name: text_validator_0 Value: a:4:{s:4:”name”;s:6:”number”;s:5:”label”;s:12:”Numbers Only”;s:7:”message”;s:27:”‘%s’ must be a valid number”;s:6:”regexp”;s:27:”/^\s*[0-9]*[\.]?[0-9]+\s*$/”;}
Name: text_validator_1 Value: a:4:{s:4:”name”;s:5:”phone”;s:5:”label”;s:12:”Phone Number”;s:7:”message”;s:33:”‘%s’ must be a valid phone number”;s:6:”regexp”;s:36:”/^.*[0-9]{3}.*[0-9]{3}.*[0-9]{4}.*$/”;}
Name: text_validator_2 Value: a:4:{s:4:”name”;s:5:”email”;s:5:”label”;s:6:”E-Mail”;s:7:”message”;s:35:”‘%s’ must be a valid E-Mail address”;s:6:”regexp”;s:51:”/^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,4}$/”;}
Name: text_validator_3 Value: a:4:{s:4:”name”;s:4:”date”;s:5:”label”;s:15:”Date (MM/DD/YY)”;s:7:”message”;s:30:”‘%s’ must be a date (MM/DD/YY)”;s:6:”regexp”;s:41:”/^([0-9]{1,2}[/]){2}([0-9]{2}|[0-9]{4})$/”;}
Done.

I see the templates listed in the above output. However, they were not in the “templates” directory when I refreshed after running the database check.

They are there – but I re-installed them right after I upgraded, since the form is useless without the summary, and is missing content without the form template….

they weren’t there when I first noticed the problem, and when I checked the directory they were gone.

Nah, they got blown away again…. Thank goodness for backups!

I don’t know so much about the plugin upgrade mechanics, but if we need to save them in a directory that gets erased and replaced, they will be gone. Unless the directory is scanned for additional templates and then they are saved and re-installed as part of the upgrade…

The good news is I found a copy on localhost, so I didn’t lose the templates — but they DID have unique names, and went missing after an upgrade. I see that there is a new version, perhaps in the last few hours, so I’m gonna upgrade and see what happens! Will report back shortly….

I really like the plugin – it is hard to find one that gets past the “contact form” mentality, and this does the trick.

That said, is there any way of protecting custom templates from being blown away by upgrades? Or at least warning people about it prior to the upgrade?

This being said from the perspective of a guy who didn’t have a backup of the template code in his child theme directory (my own fault…) and now gets to re-write it.

Thanks – The FAQ page really helped and everything tests out fine.

Great plugin. Will make a donation when I get paid for the site!