chrisc01

I’m using the latest v1.1.4 and it has caused extensive 500 Internal Server errors every time a page is accessed. Unusable at present.

Well, that was quick – the host company had left php4x as an option so I had to use the AddHandler command in the htaccess:-

AddHandler application/x-httpd-php5 .php

All now works OK

My login issue has been sorted. Confirm that WPAU does not reactivate plugins after the DB upgrade – or rather the option does not reappear after – but other than that, fine. WP-Cloner is broken, but that’s it on the downside so far.

To access WPAU you’d have had to have logged in Satish so did you go the SQL route to establish new users?

Satish, I think the problem here is generic rather than specific to your bog.

I was also asked to upgrade the database but that should have rung the alarm bells anyway as to why it was asking. Surely going from 2.5.0 to 2.5.1 shouldn’t require a DB update.

Teach me to actually jump in on an update when first announced.

Yes, got the same here – can’t login and just redirects to the home page with a 404. Oops.