WP Full Picture update 8.3.0
Update 8.3.0 is a medium-sized update. It comes with a few small new features and a number of optimizations and bug fixes.
An option to hide the banner on selected pages
Some of you may think “at last”! And yes, it took us a while, but WP Full Picture now has this long-awaited feature.
You can now hide the banner on selected pages like landing pages and pages with your legal information.
Saving inline JS in files
Many of you probably know that WP FP loads a lot of JavaScript. Most of this JS is in files, however the most important one is loaded inline, to make sure that caching plugins do not break it. However, we have noticed that many of you use caching solutions that cause issues even with thins inline JavaScript.
That is why, from this version onwards, we will be working hard on combatting it using other methods.
At the beginning, we start with saving important JS in files. This is still in beta (and is marked as such) and will be progressively improved with the next updates.
You can find options to save important JavaScript files in the General Settings page > Performance tab.
Other updates and fixes
- [New] Free users can now send data to the website’s server via AJAX
- [Update] Added “nowprocket” parameter to inline JS so that WP Rocket does not break the plugin
- [Update] Custom Script now only output important data to fp.cscr object
- [Update] Added a browser console notification when a custom script is loaded and triggered
- [Update] Updated Freemius SDK
- [Fix] [GTM] Re-added mistakenly removed noscript fallback
- [Fix] [Free] WP FP settings didn’t get sent to CDB after they were changed
- [Fix] Consent banner did not hide on the privacy page
- [Fix] [i18n] Updated loading of translation files
- [Removed] Default jQuery file dependency (it is now only added when Woo is enabled)
- [Removed] [Custom Scripts] Removed a condition which prevented scripts from loading in the customizer if the “force load” was active
- [Removed] [Custom Scripts] ID field in a script section (it is not necessary)
- [Other] [GDPR Compliance Helper] Add information that Google reCaptcha is not GDPR compliant and must be replaced
- [Other] Added licence is_pro checks to all JS files
- [Other] [Woo] Moved loading of inline script with the checkout data lower the head element (100 value) to make sure that it loads after the helpers FILE
- [Other] [Consent banner] Added “noopener” attribute to “Powered by” link to remove the warning in ahrefs