I’ve received the same issue.
I noted that somehow you’ve left out the js-dev and css-dev folders which in turn returns a 404 (Not Found) error when WP_DEBUG is turned on.
Seems to be a simple fix by just including these folders and files or removing the check for WP_DEBUG on load_zerspam_settings:178.
Great plugin regardless.
You’re getting that error because you probably have WP_DEBUG enabled. When enabled, the plugin uses dev versions of the scripts to develop. If you’re a developer, you need Grunt installed and the code compiled in order to load the scripts. The dev scripts aren’t included in the main release because their just that, for development purposes only.
Thanks for the feedback.
Hey Ben,
Thanks for the great plugin, but could you perhaps add this info to the FAQ section?
It might help others avoid the need to search the support questions to understand why it occurs…
Thanks,
Guy
Please reconsider this behavior.
WP_DEBUG should not effectively disable a plugin I have installed.
I use WP_DEBUG to debug my own development, not the development of plugins from others.