This usually means that the database user on the site does not have full access to the database tables. If that is the case, this page should help:
My options don’t save. How can I fix that?
If the tables are already set up correctly, you can also try turning on the option “Disable config caching” on the Wordfence options page.
Let us know if this helps, or if you are still having trouble.
-Matt R
Thank you for the fast response. Here is the outcome(s):
1. I checked the “Disable config caching” and clicked save. However, I get the ‘working’ wheel that never goes away. So I refreshed and the check was gone.
2. I then went into PHP admin which I do have, but the version I’m on is not 4.1.5, but 4.0.10.7 and I do not see a ‘Privileges’ tab, but have many other tabs. Maybe this lives in another directory tree?
Thanks for the help!
Ok, thanks for the update. If the “working” notice never completes, it might be a different problem, affecting the script that saves the option.
Can you open the javascript console while on any WordPress admin page, then click on the Wordfence Options page? Here are instructions on opening the console, if you need them:
How to open the javascript console
On the “console” tab, do any errors appear in red text? It could be a conflict with another plugin’s scripts, or sometimes the theme — if this is the case, the error messages can help narrow down where the conflict might be.
(Alternately, you could try disabling all other plugins, and see if you can save the Wordfence Options then. If it works, you can enable them one-by-one, and see which one stops you from saving the options.)
-Matt R
I actually found the issues revolves around the plugin’s use of Java and Chrome no longer supporting NPAPI plugin support. Basically, Chrome shuts down the Wordfence plugin and there is no way around it. In order to use Wordfence going forward, users will need to use IE, Safari or Firefox. I found this out because Chrome doesn’t have a Java console anywhere and Java.com says to avoid using Chrome at all for NPAPI plugin use. Once I switched to another browser, everything starts working like it should.
So you may need to update some documentation that users do not use Chrome to setup the plugin.
Thanks
Thanks for the update. Chrome is still working for me on our servers — do you have any extensions or add-ins installed in Chrome?
You’re correct that the Java NPAPI plugin doesn’t work with Chrome anymore, but javascript and java are separate. It’s a terrible name, since they’re similar in ways but have some big differences. 🙂
If you’re using a PC, the “F12” key is a shortcut to open the part of the browser with the console too — it should either split the browser window or make a second window, and there should be tabs labeled Elements, Network, Sources, etc. Usually “Console” is at the end if you don’t have additional add-ins installed in the browser.
-Matt R
I was able to check out the console and nothing came up while in Chrome. It still does not save changes, but I am ok using Safari to do this work.
Thanks.
Matt
Ok, thanks for the reply. I’ll watch for more issues in Chrome, just in case. Thanks!
-Matt R
