Bit51 (part of the iThemes family)
Forum Replies Created
-
@batec drop me an email at info [at] bit51 [dot] com and we’ll see what we can work out. I’m wondering if something is processing your images before they are displayed in the browser.
500 errors are almost certainly a conflict with another plugin’s .htaccess rules.
Try turning off “Filter suspicious query strings” and or “filter long urls” in system tweaks. I’m guessing that the permalink is either too long or has keywords that could be interpreted as malicious. As an alternative, you could also try redirecting to a shortlink instead of the permalink in your theme or requiring 3rd party auth through something link the jetpack comments plugin, disqus, or something similar.
You’ve got a bunch of missing resources, scripts/images/css files/etc in the background on your site. The recommended action would be to check the BWPS logs and fix the 404 files it refers to (if my plugin is seeing them then so is Google and the other search engines). Alternatively you can disable 404 detection or increase the lockout threshold in the options to prevent it from locking out as quickly.
I’m looking at a way to use the forwarded IP reliably but there is currently no solution to your issue. By design the plugin looks for the server variable of the client IP so in the case of a proxy server it will always see the proxy itself as the end client and react accordingly.
When you say it throws you right out does this mean you are being redirected to your homepage? This would be due to away_mode restrictions. You can reset all options by deleting the bit51_bwps option from the options table in your database.
There really isn’t much that can be done if you’re running out of memory short of asking your host to increase your allocated memory. The plugin is failing on creating database tables which it does using a standard, but memory intensive, built-in WordPress script.
Now you could disable other plugins and then enable BWPS but chances are you’ll hit the same memory limit with another plugin or when upgrading BWPS, etc.
Take a look at http://bit51.com/what-is-changed-by-better-wp-security/
If you would I would appreciate it. The blank page actually sounds like a php error with error reporting turned off.
Let me see if I can detect that state @joneiseman. That should make it easier.
It would be easy to add the feature but the usability of such a feature could trouble many. For example, if a wildcard or regex was needed for a plugin exclusion (this would be the case with many of the plugins) entering it wrong could lead to all sorts of problems.
Most likely what I’ll do sometime in the near future is a low/medium/high setting for the feature to try to make it as usable as possible while also eliminating many of the conflicts.
…There are a few reasons. For one, if cached and a plugin conflict is present the site owner may not notice it as quickly if the page is cached after an options save which can cause further headache later. In addition, with database and opcode caching features such as lockouts and awaymode restrictions can actually be cached making even their manual removal difficult to detect until the cache clears. Therefor, on an options save the plugin will clear all caches and for certain other situations opcode and query caching is cleared.
Sorry about the headache. Did it throw you any errors when you activated the feature? This is a sporadic issue that I haven’t been able to reproduce on any of my sites and I would like to figure out what is causing it.
No problem. Did you find out if it was blocked or otherwise unavailable?
Well, it’s a little slower than I hoped but I’m looking at a two prong solution…
…a sticky thread on here with a link to report the plugin and the feature that are incompatible….
…then a way to report that when you activate the plugin or the feature in your own install to prevent headaches.