shorelinechrism

It’s just letting you know there is no built-in form submission saving to the database. It doesn’t store submissions in the database. Once the email notifications are sent the form submission data is lost.

There are several 3rd-party solutions to handle this for you. WPCF7 Redirect plugin, Contactic, Flamingo are well-regarded plugins to handle storing the submission data on the server. I recommend using a webhook instead, though, and store the data somewhere off-site so that it impervious to any issues that may impact your wordpress hosting.

Thank you so much for the quick response! I’ll take a look now.

Actually, it would probably be best just to filter the path, not the file contents:

`
return file_get_contents( apply_filters( 'cf7hete-default-template', CF7HETE_PLUGIN_PATH . '/modules/cf7/includes/templates/default-' . $name . '.htm', $name ) );

`

I think this has something to do with wp_add_inline_script and something custom on my multisite setup where we try to optimize the JS using the script_loader_tag function. I have resolved this issue as it is likely only affecting this one site. Apologies.

Sure thing. Should I do it on the gihub repo?

If you want all images output in the DOM either in an <img /> tag’s SRC attribute or even an inline STYLE attribute on an element like <div style="background-image: url('myimage.jpg');"></div> to be converted, you must go to the WebP Express settings and change:

1. Scope to “All content”
2. Enable the “Alter HTML” option
3. Click the checkbox for “Replace image URLs” and click the box underneath to only do for browsers that support webp
4. Click the checkbox for “reference webps that haven’t been converted yet”
5. Under “where to replace” choose the option “The complete page”

Take a backup of your database before enacting these changes just in case you hit a bug, you can restore these settings quickly. And, be sure to hit “Save settings and force new .htaccess rules”

• This reply was modified 4 years, 11 months ago by shorelinechrism.

Yes, the safest option is to choose the 2nd option for the replacing images. Instead of using the <picture> element option, choose to rewrite or update the element instead. The issue is your theme is probably not equipped to handle a <picture> element or there is styling applied to that element which is throwing off your layout. If you choose to just manipulate the image tags instead of inserting picture elements then you are not really introducing new markup into your theme, just the SRC attribute on the element should change.

There is a bug that was reported in regards to the Live Test function. I think a function in the Live Test is broken, but the actual implementation of the feature should still work. I have had the Live Test cause an error but the webp plugin still continues to work on the frontend and create new webp images and all that.

https://github.com/rosell-dk/webp-express/issues/379

Ok, everyone. If you are on WPEngine, the WebP Express documentation they had was a little outdated. Due to changes in the plugin code, you cannot use “CDN Friendly” mode if you want your WPEngine site on Nginx to serve non-webp images (like those that might be referenced in CSS files) without an error message.

To make it work on WPEngine, follow the same setup and send Nginx rules to support to add to your config, but then use “Varied image responses” mode instead. After you change the mode there will be a “Redirection rules” section now on the settings page. Make sure that “Enable redirection to converter” is checked off. Clear your cache and it should work.

We are running into this issue on WPEngine. We gave support the Nginx rules and followed the settings on the docs and the webp functionality is working correctly, but any non-webp files that might be served in CSS files is resulting in an error:

Validation failed for settings: Redirection to conversion script is not enabled

It would be helpful if anyone figured out a way to combat this on WPEngine, please.

Support at WPEngine indicated they are aware of the issue and working towards a fix. No timeline or anything, unfortunately.

Yup– I included this thread in my support chat and told them to keep an eye on it since anyone else experiencing the issue might report here as well. I foresee an afternoon filled with exporting lead data. Now is a good time to install Flamingo or CF7DB plugins if you haven’t already!

Ok, thanks folks. I’m raising the issue with support. I believe that it’s probably webhost related.

Hey everyone– my clients are both on WPEngine. Are any of your affected sites hosted there as well? I am trying to find a common thread here. Two of the sites I can see that are affected have different WP Core and PHP versions but it is still impacting both sites.

We are having this problem as well. Two of our clients hosted on WPEngine have reported that their emails are blank. We CC’d ourselves and we are using Google Apps/GSuite and in our gmail account a file is attached called ‘noname’ and it includes the multi-part email content.

We didn’t perform any plugin updates on the site but since it’s on WPEngine there may have been a plugin or Core updates on these sites.

Both sites reported the issues within the last 24 hours and they have the following versions:

Site 1:
PHP 7.2
Core: 5.2.3
CF7: 5.1.1

Site 2:
PHP 7.3
Core: 5.1.2
CF7: 5.1.1

Here is a link to the ‘noname’ file we received as an attachment: https://bitbucket.org/snippets/thetrickster/dL8Ky8