danielrsmith

Has anyone solved this with the automatic browser detection still enabled?

pcbdaily trust me I get where you are coming from, just don’t want to see people blame Automatic for this. I was having the same issues as you guys, and it ended up being a plugin’s javascript causing the issue. I like you also saw the update and ran an update on my blog and had some issues. I was just pointing out that when you have clients websites on it you might want to do some testing first especially when going from the 2.7’s to 2.8 because some plugins just plain don’t work.

No offense bjsmooths but you probably shouldn’t have upgraded clients websites without testing them ahead of time. Just because WordPress releases a new version of the software doesn’t mean that every theme and plugin that you use in your production environment is going to work the same way or properly. I recommend having a testing environment that is identical to your production environment and doing WP version and plugin upgrades there before releasing them to your clients. This helps with the possibility of downtime with your paying customers.