mbang

I solved the issue and didn’t know how to reopen the thread but wanted to provide the solution to help others.

Instead of coding:
`Link

Do it this way
‘Link

and the form should be able to pull your query string into a field. I was able to do this in Gravity Forms via

https://docs.gravityforms.com/using-dynamic-population/#query-string

• This reply was modified 6 years, 2 months ago by mbang.
• This reply was modified 6 years, 2 months ago by mbang.
• This reply was modified 6 years, 2 months ago by mbang.
• This reply was modified 6 years, 2 months ago by mbang.
• This reply was modified 6 years, 2 months ago by mbang.
• This reply was modified 6 years, 2 months ago by mbang.

Is auto as an option in the pro version something that could be added into the next release?

I just bought the pro version and are experiencing this issue as well but don’t know how to do it via css

I added some custom CSS to the theme stylesheet to override the bug:
/* Overrides height of menu items in hamburger menu so that word wrap can be used */
#responsive-menu-pro ul.responsive-menu-pro-submenu li.responsive-menu-pro-item a {
height: auto !important;
}

Unfortunately this isn’t a complete solution. The “trigger” (plus symbol) on the sub-submenu is now cut off. And when I test it on my phone, the menu displays at the correct width the first time, but accessing it a second time leads to a super-wide menu instead of word-wrapped.

Thanks!

• This reply was modified 6 years, 3 months ago by mbang.

Any updates to the plugin fix so other ZIP programs can view all the files properly?

Yes, I already have looked it over which is why I said “the form is submitted in non-AJAX submission mode. ”

I worked on it more yesterday and found that the issue was caused by minifying in W3TC. If I don’t minify wp-content/plugins/contact-form-7/includes/js/scripts.js file then the form fires the DOM events / AJAX submission mode.

In an effort to make CF7 load faster and more SEO friend, have others reported this issue and is there a solution to allow CF7 to be minified with the rest of the site as every other plugin workes fine with W3 Total Cache.

Thanks

Thanks for your reply. Since my original post, CF7 AJAX submission definitely works if W3TC is activated but I disable Minify so I would think the issue revolves how CF7 is getting minified. I am stuck, any thoughts with this new info?

I am experiencing the same issue: Just installed WP-Staging and get the error listed above. I went into wp-content/uploads/wp-staging for logs but do not see any as I just installed and activated the plugin. Rene asked the previous user to open a support ticking on wp-staging.com but now no one benefits from the resolution to the issue.

Can you please advise?

Thanks!

• This reply was modified 7 years, 1 month ago by mbang.

It appears my website automatically updated WP 4.8.2 and now I am seeing the SQL errors and also am not able to log into my website. Website seems to be running fine but can not log in to update Wordfence.

Here is the error:
2017/09/20 12:41:08 [error] 897#897: *354 FastCGI sent in stderr: “PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘%1$s
WHERE user_caps = ‘%2$s’
AND action = ‘%3$s’
AND obje' at line 1 for query SELECThistid` FROM %1$s
WHERE user_caps = ‘%2$s’
AND action = ‘%3$s’
AND object_type = ‘%4$s’
AND object_subtype = ‘%5$s’
AND object_name = ‘%6$s’
AND user_id = ‘%7$s’
AND hist_ip = ‘%8$s’
AND hist_time = ‘%9$s’
; made by wp_signon, do_action(‘wp_login’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, AAL_Hook_User->hooks_wp_login, aal_insert_log, AAL_API->insert, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query
PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘%2$d’ at line 2 for query DELETE FROM %1$s
WHERE hist_time < %2$d made by wp_signon, do_action(‘wp_login’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, AAL_Hook_User->hooks_wp_login, aal_insert_log, AAL_API->insert, AAL_API->_delete_old_items, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query
PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘%1$s
WHERE user_caps = ‘%2$s’
AND action = ‘%3$s’
AND obje' at line 1 for query SELECThistid` FROM %1$s
WHERE user_caps = ‘%2$s’
AND action = ‘%3$s’
AND object_type = ‘%4$s’
AN
2017/09/20 12:41:08 [error] 897#897: *354 upstream sent too big header while reading response header from upstream, client: XXXYYYZZZZ, server: https://www.XXXYYYZZZZ.com, request: “POST /wp-login.php HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php-fpm/php-fpm.sock:”, host: “www.XXXYYYZZZZ.com”, referrer: “https://www.XXXYYYZZZZ.com/wp-login.php&#8221;

Please advise.

this happened again and it appears to deactivate when I updated the plugin “Wordfence Firewall”
No idea why it is happening but just requires reactivation and seems to work fine again.

Here is all I can find in the error log:
1504883449 SES id=0100015e620b222f-3bcb67cc-fd09-4692-8e93-d64f6913dcce-000000
1504883463 ERROR wp_mail override by another plugin !!
1504883463 Then deactivating plugin
1504883463 wp_mail already defined in /usr/share/nginx/html/wp-includes/pluggable.php

any idea what the issue is? I don’t have another plugin for sending mail besides WP-SES

Thanks!

I just tried what you said on our site: submit form without submitting check mark on recaptcha and you are right, I immediately get a hubspot submission notice but of course no emails, contact form db, etc.

I did get this notice on the form itself “Failed to send your message due to suspected spam, if you continue to have issues, please email the address at the top of the page.” so you would hope that someone submitting form would see it and realize the form had not sent.

Very concerning in many ways, but then again the recaptcha is doing what it is supposed to. I wonder how reliable the invisible recaptcha is?

I have seen the exact same issue on our site where I see the submission in hubspot but nothing comes through on contact form DB, email to us or email logs outbound.

Seems really random the ones that don’t get sent but it is really concerning if we are not getting all form fills as we use hubspot free as a backup CRM and the only way I noticed this was happening was by chance.

Are you sure it is caused from recaptcha? How have you verified this?

Thanks!

any updates?

Are any of the above code functions depreciated or no longer working as of CF7 4.8?

I see in the change log here: https://contactform7.com/2017/06/01/contact-form-7-48/#more-22829
Stopped using jquery.form.js.
Added custom REST API endpoints for Ajax form submissions.

Does not using jquery.form.js mean wpcf7_before_send_mail, on_sent_ok or location.replace no longer get called/function correctly?

If there is any documentation I have missed reading, please point me in the right direction but I haven’t found much documentation with regards to no longer using jquery.form.js and moving to an API to see if that may be causing the issues.

Thanks much!

Just as a note, I downgraded to CF7 4.7 and everything functions correctly again. Something changed in CF7 4.7 that is causing the above code to not execute/fail. I need to get CF7 4.8 update installed so any help is much appreciated.

I am running into the same issue after upgrading to 4.8 as far as my add_action( ‘wpcf7_before_send_mail’, ‘XYZ’); in functions.php seems to be no longer working any help?

Looks like https://cdn.zopim.com/assets/style.css was the issue in the Custom File list. It has been there for years and only the recent upgrade to w3tc version 0.9.5.2 caused it to break

I am having the same issue with AWS Cloudfront and formating of the pages. I even deleted the cloudfront distribution and set it up again. Still no luck….