When I check the “Our Clients” page with Google Chrome Developer Tools I see two 403 errors for these thinkup panels plugin scripts.
http://www.eamonnkilbydecorators.com/wp-content/plugins/thinkup-panels/inc/plugins/waypoints/waypoints.min.js http://www.eamonnkilbydecorators.com/wp-content/plugins/thinkup-panels/inc/plugins/waypoints/waypoints-sticky.min.js
I do not think Plugin Firewall AutoPilot Mode will automatically create whitelist rules for these scripts because of the odd/bad choice of naming convention for the additional “plugins” subfolder path that was used. ie the plugin is asking for trouble/problems by using the “plugins” folder name twice in the path structure. For future troubleshooting reference you can check your BPS Security Log to troubleshoot issues like this and then post the Security Log entry in the forum which will show exactly what is being blocked.
Add this whitelist rule in the Plugins Script|File Whitelist Text Area. Note: Using Regex code up to the /inc/(.*) folder path will ensure that the duplicate “plugins” folder naming convention used in the thinkup panels plugin will not cause a problem for the Plugin Firewall.
/thinkup-panels/inc/(.*).js
Plugin Firewall Manual Setup Steps
1. Copy and paste plugin scripts/whitelist rules to the Plugins Script|File Whitelist Text Area.
2. Click the Save Whitelist Data button.
3. Click the Create Firewall Master File button.
4. Select the Plugin Firewall BulletProof Mode Radio button.
5. Click the Activate|Deactivate button to activate the Plugin Firewall.Each plugin script/file path that you add MUST be separated by a comma and a space. Example: /some-example-plugin/api/paypal-ipn-script.php, /another-example-plugin/some-example-script.php. The path name starts with the plugin folder name (do not add /wp-content in the path name).
- This reply was modified 9 hours, 21 minutes ago by AITpro Admin.