dwinden
Forum Replies Created
-
I noticed from your screenshot that you seem to only have the See what’s new notice displayed.
Could you confirm that you initially also had the other notice displayed:New! Take your site security to the next level by activating iThemes Brute Force Network Protection. Get Free API Key
but the x button did work properly on that notice so it is no longer displayed ?
Also please confirm you are now using the iTSec plugin 5.5.0 release.
dwinden
As of the 5.4.x or higher release the iTSec plugin settings are ALL stored in one database option: itsec-storage.
Manually set the value for the show_new_dashboard_notice setting (global section) to 0 in the itsec-storage option and it should be ok.
dwinden
Ok. After receiving your feedback I also believe this is probably not a browser (client) issue.
I’ve analyzed how this actually works.
The notice should normally (and permanently) disappear but ONLY after clicking on the x button.
Clicking on the “See what’s new” button will not disable the notice.So what exactly happens when clicking on the x button ?
There is an ajax call executed which does nothing more than save the setting named show_new_dashboard_notice (which is part of the global section) with a value of 0 in the wp_options table itsec-storage option.
The notice is only displayed if show_new_dashboard_notice equals 1 (which is the default value).
It seems that somehow the ajax call is unable to change/save the value of the show_new_dashboard_notice setting to/as 0 in the database.
Weird thing is that only when the ajax call returns a success response the notice is hidden …
But it seems that even when setting show_new_dashboard_notice to 0 fails, a success response is always returned !
There is no check performed to verify saving/changing the show_new_dashboard_notice to 0 was actually successfull.Are you sure there are no errors in the error_log related to saving (wp_options table) options in the database ?
dwinden
What browser and what version of that browser are you using ?
What is your client platform ?(Win 7, 10 etc).
Did you try from different browsers ?
Are there any errors in the web server error_log ?
Are there any errors in the browser javascript console ?Several people have reported this issue lately.
There is ab-so-lu-te-ly no progress whatsoever in any of the other topics.This is typically an issue that probably needs to be looked at/debugged while being logged into the WordPress Dashboard.
A TeamViewer session could do the trick.
dwinden
@tzal
What browser and what version of that browser are you using ?
What is your client platform ?(Win 7, 10 etc).
Did you try from different browsers ?
Are there any errors in the web server error_log ?
Are there any errors in the browser javascript console ?Several people have reported this issue lately.
But there is ab-so-lu-te-ly no progress whatsoever in any of the other topics.This is typically an issue that probably needs to be looked at/debugged while being logged into the WordPress Dashboard.
A TeamViewer session could do the trick.
dwinden
What browser and what version of that browser are you using ?
What is your client platform ?(Win 7, 10 etc).
Did you try from different browsers ?
Are there any errors in the web server error_log ?
Are there any errors in the browser javascript console ?Several people have reported this issue lately.
But there is ab-so-lu-te-ly no movement whatsoever in any of the other topics.This is typically an issue that probably needs to be looked at/debugged while being logged into the WordPress Dashboard.
A TeamViewer session could do the trick.
dwinden
What browser and what version of that browser are you using ?
What is your client platform ?(Win 7, 10 etc).
Did you try from different browsers ?
Are there any errors in the web server error_log ?
Are there any errors in the browser javascript console ?Several people have reported this issue lately.
There is ab-so-lu-te-ly no movement whatsoever in any of the other topics.This is typically an issue that probably needs to be looked at/debugged while being logged into the WordPress Dashboard.
A TeamViewer session could do the trick.
dwinden
XML-RPC can be used for the good but also for bad things.
The feature’s description says it all:WordPress’ XML-RPC feature allows external services to access and modify content on the site. Common example of services that make use of XML-RPC are the Jetpack plugin, the WordPress mobile app, and pingbacks. If the site does not use a service that requires XML-RPC, select the “Disable XML-RPC” setting as disabling XML-RPC prevents attackers from using the feature to attack the site.
dwinden
Ok, great.
There doesn’t seem to be any info available for that particular combination of versions. Not even on the Developers tab Compatibility sidebar widget. On that same page it does say:
Requires: 4.1 or higher
Compatible up to: 4.5.2So it will probably work fine but it might be best to set up a 4.4.3 test env first to find out.
Anyway if you agree please mark this topic as ‘resolved’.
dwinden
Yup, next log into Admin Dashboard.
Navigate to the Security->Settings menu option.
Goto the Banned Users section.
If the Enable ban users checkbox is unticked, tick it and then remove your IP address from the Ban Hosts field.
Then click on the Save All Changes button.Finally click on the iTSec plugin Dashboard tab and click on the Temporarily Whitelist my IP button.
Done.
Before deciding to update to the iTSec plugin 5.5.0 release read this.
dwinden
Ok, that explains.
Manually remove the following section from the .htaccess file:
# BEGIN iThemes Security – Do not modify or remove this line
# iThemes Security Config Details: 2
# Quick ban IP. Will be updated on next formal rules save.
…
# END iThemes Security – Do not modify or remove this lineMake sure to remove ONLY the section which includes blocking your IP.
There may be multiple of these Quick Ban sections for different IP addresses in the .htaccess file.The above modification should allow you to access the site again.
Expect additional instructions for removing your IP from the Banned Users section.
Last thing we’ll do is whitelist your IP as a preventive measure 😉
dwinden
You can find the plugin version in the following file:
wp-content/plugins/better-wp-security/better-wp-security.php
dwinden
While in the iTSec plugin Settings page check the <head></head> section using the build-in inspector of your browser.
It might be the plugin is trying to enqueue the icon-fonts.css file using an incorrect path.
dwinden