cimatti

Hello
first of all, thank you for using our plugin.
We just released an update that could help resolve this issue.
If the update does not help contact us through our website.

Regards

I’m sorry to disagree, but as I explained above, that part of code is interpreted in two different ways in PHP 5.* and 7.*

See https://php.net/manual/en/migration70.incompatible.php#migration70.incompatible.variable-handling.indirect for reference

You may have not noticed this because this incompatibility doesn’t generates PHP errors, because the expression is inside isset() and empty(), that are two language constructs that tests the expression without issuing errors in any case

I’m not sure how much important is this part of code and what implications would have in the normal execution of your plugin, but in PHP 7.* this unfixed code will return always false even if $post_type->{$field['post_type']} contains something

All the issues of this kind should be fixed in the new version

Hello @max_q ,

I just released a new version with support for PHP up to 7.1

Hi cessholden,

Perhaps you had issues with PHP 7.*. We just release a new version that fixes this, please try this and let us know if you still have issues

Hello @max_q ,

I’m working on the issues you reported right now, so expect a new version soon

• This reply was modified 7 years, 9 months ago by cimatti.

Hi,

For the recaptcha area width, I’m going to add these rules to the plugin css on the next release, meanwhile you can add them to your site css:

@media (min-width: 300px) and (max-width: 400px) {
.accua_forms_recaptcha2_container {
    transform: scale(0.75);
    transform-origin: 0 0;
}
}

@media (max-width: 300px)  {
.accua_forms_recaptcha2_container {
    transform: scale(0.6);
    transform-origin: 0 0;
}
}

For the error message, probably this is a PHP error, so you should check the PHP error log and/or the HTTP result of the form submission. If you are not sure, you should ask to your web hosting provider for the php error logs at the time you submitted the form.

One possible cause of the error is that the plugin connects to https://www.google.com/recaptcha/api/siteverify to check if the user passed the recaptcha challenge. To do so, your web server must have PHP CURL library, and it must not block (with a php connections blacklist, php safe mode, a firewall or similar things) connections to https://www.google.com

Please let me know if you solved your issues. If not, please post a link to the page with the form not working so I can see by myself

Hi, sorry for the late answer, but now I see only the form shortcode in the testing site, so I can’t see what you have done (you should reactivate the plugin if you still want to test it)

Anyway, we think it’s hard to implement more complex settings for the form layout. By default the form fills the width of the area where you put the form, and fields are in column so they should work well with any device.

If you need a custom layout for a form, you should add some style rules in your site/page css to override te default layout. All the fields are in their container with the label and the field itself, and all the elements have some classes with which you should be able to select the elements you want to alter and set width, position, float, et cetera

Hi Robbie, you are welcome!

This is odd: it should work even if it was not the intended use of the administrator email. Does it works with other forms? Are the submissions saved?

First thing to check, just to be sure: Subject and Message should not be empty, otherwise the email is not sent.

If you have more emails and tokens in “to:”, you have to separate them with commas ( , )

Another way to send the email, if you have both the default field email (of type autoreply_email) and colleague_email, and you want to send the same email to both, you can set also the type of field colleague_email to autoreply_email. The autoreply email is send to all emails in all the fields of type autoreply_email.

Please let me know if you solve this or not

Hello.
What version of the plugin are you using?
Since version 1.3.9 The plugin has improved support for the new reCAPTCHA that requires to enter site keys. As far as we know this new version should be fully responsive and, while the plugin still also has the older version, we recommed using the newer version.

Hope this was of help. Let us know by answering. Thank Yuo.

I’ll see if I can mitigate this error, however this happens if you are using a PHP version lower than 5.3. I’m sorry but I didn’t expected this kind of warning with lower versions.

You can hide warnings from output with something like this:
https://www.binarytemplar.com/disable-php-warnings-and-errors-in-wordpress/

You should also consider upgrading to PHP 5.5 or 5.6. PHP 5.2 reached end-of-life in 2011. If you have no custom PHP code/plugins and you have all recent and updated plugins, there should be no problem upgrading to PHP 5.5 or 5.6

https://php.net/eol.php
https://php.net/supported-versions.php

Hi PSlat

I don’t think this was significatively slowing down the plugin, however I just released a new version where I replaced references to user level ’10’ with capability ‘manage_options’

Please try it now, thanks!

Ah, wait, now I remember why I created the class classes/Element/Select.php about 5 months ago and included it in the version I released 2 days ago. Now I use this class for selects, and the only difference is that it extends classes/Element/OptionElement.php that already serializes the $options array.

Things in folder PFBC are from a third party library, so I prefer not to touch files inside it.

I’m sorry for having deluded you, Hanra ?? , but with the latest version this should be already fixed

Hi,

widget support is not integrated, but if you have a custom text widget that supports shortcodes you can insert a form with the shortcode, just like in post content.

Usually we don’t use widget, but if we want to embed a form in parts of the theme we use php code in the theme files:
<?php accua_forms_include('FORM_ID'); ?>

Hi,

This was the intended behaviour, as we wanted to send to the bcc address both the emails.

However I understand this could be misleading, so we will consider to split the bcc field so one can send just one email in bcc to someone