clarevanessa

Hi @wfpeter, apologies for my delayed reply coming back to this!

That’s great to read that you agree the scans have likely only been detecting false positives and I have now added the wildcard pattern you suggested to Wordfence’s settings to start excluding these files from future scans.

Thanks so much for your help!
Clare

My websites also had the same issue.

I can appreciate this is a difficult one to work out, and that would be great if you could report it to Custom Fonts and see if they can work something out or to help anyone else who runs into this in future (for now, I think we will just have to delete either Site Origin Widgets Bundle or Custom Fonts in order to work around the conflict another way). Thanks for your help anyway, Jamie, very much appreciated ??

Hi Jamie,

Thanks for your reply. At the time I started this topic, I had deactivated all plugins but reactivated them one by one until I encountered a conflict (to avoid the process being even more time-consuming!). So as per your question, I have now also tested deactivating all plugins except Beaver Builder Lite and SiteOrigin Widgets Bundle and in that state I can successfully edit and publish changes to multiple pages using Beaver Builder (and yes, the original error was occurring on more than one page of the site and using multiple modules – it wouldn’t save any changes).

I had read similar topics before posting this, and noticed a previous solution noting potential conflict issues when using the Custom Fonts plugin along with the Astra theme (our site also uses both of these). To test if the Custom Fonts plugin was involved in the conflict, I activated it at the same time as Beaver Builder Lite and SiteOrigin Widgets Bundle (while all other plugins remained deactivated) and I again couldn’t edit any page with Beaver Builder. I then reactivated all other plugins except for Custom Fonts, and I could again edit pages with Beaver Builder. Alternatively, I reactivated all plugins except for Site Origin Widgets Bundle, and I could again edit pages with Beaver Builder.

So to recap, I can edit with Beaver Builder when:
– Beaver Builder Lite and Site Origin Widgets Bundle are the only plugins activated on the site;
– Beaver Builder Lite and Custom Fonts are the only plugins activated on this site;
– Beaver Builder Lite, Site Origin Widgets Bundle and all other plugins are activated, but Custom Fonts is deactivated;
– Beaver Builder Lite, Custom Fonts and all other plugins are activated, but Site Origin Widgets Bundle is deactivated.

As an extra note, we don’t have ‘Preload Fonts’ selected in the settings for Custom Fonts (as I noted was an issue in a previous similar topic).

Also, just in case it is needed, I had disabled Beaver Builder’s Debug mode when testing the various scenarios above, but have reactivated it again – the new URL is: https://animal-communicator.com.au?fldebug=e34d20e32d56989b93a8182f24e6a5b3.

Look forward to hearing any further thoughts / suggestions and thanks in advance for your help!

• This reply was modified 1 year, 2 months ago by clarevanessa.
• This reply was modified 1 year, 2 months ago by clarevanessa.

As per @takayukister above, I think the easiest fix for now is deselecting ‘Use HTML content type’ under the ‘Mail’ tab – since it is only an email submission to you, plain text is usually adequate to receive those contact details (if the issue were with ‘Mail (2)’ submissions back to your client, then that would be more of an issue).

I did originally use the suggestion by @jameskoussertari (download WP Rollback, rolled back to version 5.71) and it worked fine to restore old functionality of the contact form notifications, but I’m not a fan of using outdated plugins as they have often caused security issues on sites I manage in the past and it’s always been my preference to find other workarounds where possible.