Bit51 (part of the iThemes family)

Well, with wp-content yes, there could be issues with upgrading other plugins. As it is a documented feature in core however you should not have any issues there (basically a plugin dev could hard-code wp-content rather that getting the path dynamically).

As for the tables, the same thing is true. It is a documented WordPress feature (you can in fact name them anything you want on install) however, over the years I’ve run into at least one plugin (that I can remember) that hardcoded it’s database calls using the default prefix.

Hello,

I hope to have a better way to list plugin issues with individual features in the near future. Thanks for the report. Do you know which features were causing the issue?

You can delete the “bwps_away_mode” option from your options table.

Thanks Curtiss. I’m hoping to have a better way of documenting plugins that are incompatible with specific features soon (I do not consider them bugs but rather look at them in the same fashion as opening ports in a firewall on your computer).

Sure,

1.) This isn’t a bug but is in fact a result of changing the directory. There is no good way to scan the database to update each for the new paths as doing so could lead to other issues (broken external links, etc). That is why this feature is recommended ONLY for new blogs.

2.) I’ve only heard of this happening once or twice and, at least in one case, it has been resolved.

3.) Another issue that is VERY sporadic however most who have reported it indicate it is fixed.

4.) This could be, I do not list features incompatibilities with individual plugins as bugs but rather just something that has to be opened in order for your site to work (the concept is similar to opening apps to access through the firewall on your local computers). That said, I am working on a way to better document these incompatibilities.

@dan, no change on that one. It is however turned on with the “One-click” feature which may be where the conflict began.

Peter, everything there is pointing to some strange interaction with caching and the options array. For example, defaults would only be populated if the array wasn’t already found in memory, etc. Can you email me at info [at] bit51 [dot] com? I would like to ask you for a temp account to poke around and see what I can learn about the problems you’re having.