I am using WP Armour extended on a site with Gravity Form. And it is not working. I get allways the message “Spamming or Javascript is disabled!”. Initially I thought it had to do with the plugin WP Fastest Cache. I checked that Delay option for JS is not selected, I excluded the page and wpa.js. Then I deactivated the plugin but still no success. I am using WP Armour 2.2.14 and WP Armour Extended 1.39
The page I need help with: [log in to see the link]
Is our plugin currently inactive there ? So far i couldn’t find our plugin’s js files being loaded in the website. It is needed to add the required fields for the form.
If our plugin is active then there is high chance your cache plugins is serving the old cached js files which doesn’t have our latest js files. If so, i suggest your to clear the cache of the cache plugin.
That’s really weird. Issue here is the the css files is loaded that means our plugin is active but only js files are not being loaded. Any chance you can send me temp/staging details at [ email deleted ] ? I will try checking myself and looks for the cause.
@kdfijter Please revoke that access, the developer made a mistake that could get them banned and their plugins closed.
@dnesscarkey Your brand account has been made a forum spectator and is not permitted to use the forums. Use a real person account to reply and acknowledge your error here.
You wrote this.
Any chance you can send me temp/staging details at [ email deleted ] ? I will try checking myself and looks for the cause.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
This includes temp or staging sites.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
Ask the user to install the Health Check plugin and get the data that way.
Ask the user to create and post a link to their phpinfo(); output.
Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
