Bit51 (part of the iThemes family)
Forum Replies Created
-
I’ll take a look for future releases. It shouldn’t be hard to expand on the current system but, as life has gotten rather crazy lately, it will be fall before I start on new features.
Turning off hide backend will fix it until the next update.
Thanks for the updates. I will work these in to the next update. I’m starting to think I’ll need a second dev on this one to keep up so I am most grateful for the code.
This is a problem that has popped back up with the release of WordPress 3.4. I will have a fix in an upcoming update.
Well, I’ve looked in my spam box and don’t have any extra emails. You can try me on skype at ChrisWiegman. I’m usually available most of the US workday.
This is a problem that has popped back up with WordPress 3.4. I will be working on a fix for an upcoming update.
You can’t see the changes on the front end or are you looking to edit in the backend? The former is caching. The latter means you have turned off the editor in “system tweaks”
It sounds to me as if your MySQL server is having issues with the DBDelta function that creates/updates the database tables. You could try increasing MySQL cache to see if that fixes it or disabling all other plugins and see if that gives it enough to activate. Frankly, in the case of the latter you will have issues when the plugin updates and I would not advise it.
@maximan
2.60.*.*
2.61.*.*
2.62.*.*
2.63.*.*While I realize it is longer the performance improvement available with using only wildcards means I will not be changing it anytime soon.
Thanks for the report. I will fix it for the next release.
I would be willing to bet it was the file change detection hitting cpu caps. This isn’t all that uncommon on shared hosting as the feature simply takes a lot of ram and cpu.
Did you rename wp-content? That can happen if old paths are kept in the cache after renaming the directory.
@calik1d there is no requirement for SSL in the plugin. In fact most sites on which I employ it have all but ssl turned on due ssl not being available.
Clear the “Better WP Security” section from your .htaccess, turn off the feature, and then resave. Some server will have compatibility issues with options on that page.
It could be someone trying to open the archive for author 1, it could be a bot looking for it’s existence. I have seen attacks against user 1 in the last few months so either is possible.