frustrated999
Forum Replies Created
-
Forum: Plugins
In reply to: [Max Mega Menu] Submenu not showing w iPad in potrait modeGot it working. After reading through the excellent documentation on your website the lightbulb went on when I came across the following code for my theme Customizr. Once that was inserted the drop down worked properly with iPad in portrait mode.
.navbar-inner {
min-height: 0 !important;
}.navbar-inner div.social-block {
display: none;
}.navbar-inner button.btn-navbar {
display: none;
}.navbar-inner .nav-collapse,
.navbar-inner .nav-collapse.collapse {
overflow: visible;
height: auto !important;
}Forum: Plugins
In reply to: [Max Mega Menu] Submenu not showing w iPad in potrait modeThanks for the suggestion. I tried it in the style.css file for the Customizr Child theme being used as well as in the theme’s custom CSS via the web GUI and the same issue occurs. When the iPad is in portrait mode the submenus on Screens/Carts, projectors etc do not show up.
No I can’t however I have downloaded the PHP file locally and will wait until I get another alert tomorrow re the hash for the file changing. Then I can do a file comparison and see what is what. I wonder if the the daily Wordfence scan is what is causing this alert to be triggered by the other security plugin? Wordfence shows no changed files after its scans.
Ok thanks. I logged into my Dropbox account and then clicked on the link in the Plugin to reauthorize it. Did a backup without any problem. Thanks.
This plugin is installed on 2 website and both of their backups failed tonight with the same error message. The Dropbox account has 11GB of freespace available. I got the plugin to work by using the option to reset all the settings and reauth it with DropBox.
My Dropbox is using 2FA and I am wondering if the plugin is having issues with being able to handle 2 factor authentication?
Is it possible to have the developer fix this problem in the perms.php once and for all since its alot easier for them to do it that to have all of their users have to do it.
Every time I have updated this plugin I have to go an implement this change to fix this problem. It is still happening in 4.6.8 of the plugin.
Bump
There are over 1100 of these locked out hosts whose bans shortly expire or expire in days or weeks.
What option is generating these locked out hosts?
Why are these IP addreseses for the locked out hosts not showing up in the .htaccess rewrite rules in the plugin’s dashboard? When one manually inserts a banned IP there is a series of corresponding entries in the .htaccess rewrite rules.
Seems that the plugin uses the .htaccess for some bans and not others. Is this correect?
Hopefully fixed but only time will tell.
I am using several security plugins in the sites of which iThemes Security plugin is one of them. I never allowed iThemes to be able to write to the .htaccess or wp-config.php files as I am afraid it would lock out the site completely because it thinks its the only security option installed in WordPress.
As such I have decided to disable the user and ip blocking options in iThemes Security and rely on another security plugin to handle that process.
Even after disabling the banning of IPs the plugin is still showing screen after screens of Locked out hosts which is false since the plugin does not have rights to write to .htaccess nor is it suppose to ban hosts.
Well there are 5 other people who have been having the same problem and I am not sure that their problem is also caused by the same issue or not.
WordPress firewall was culprit
Is there any way of removing all the banned usernames aka the 5 or 6 screen fulls of “admin” users along with the 5 screen fulls of IP addresses that the plugin has banned without having to go line by line checking each and every one? Is the plugging just creating a flat list of usernames and does not check to see if that username is already in the list?
I am trying hard not to turf this plugin since there is a serious issue with it not being able to save any changes.
This is resolved by the above fix however it may be moot as several other more serious issues exist with this plugin that may require removal of it completely.