Admin is now READ ONLY.. (didn't install the patch correctly)

**sneakysnier** · 2 Jul 2009, 01:56 AM

Hi folks - can't find anything with the search function so need to post...

I upgraded to the lastest security patch (1.38a) and all seemed fine - could access admin with no issues.
After reading the security recommendation to rename the admin account i renamed mine accordingly... and didn't think much of it.

Today i've come to make some changes to the site but find that i cannot make a single change - whether adding another user or changing ANY config settings...when i click 'APPLY' i'm simply taken back to the 'stats' page....

Very confusing (well it is for me)..... would this likely to be a database issue or perhaps a config file that could be causing the problem?

Cheers
Ian

**Coffee1** · 2 Jul 2009, 05:09 AM

I also tried the security patch on 1.3.7. I am not proficient at this, and ended up restoring to a previous date. Also, prior to adding the secutity patch I had uploaded images for new products. I have now lost all images. I removed the new images, but still not displaying previous images. Now I cannot change anything in admin. Any Help would be appreciated. I have been searching the forum for 2 days.
Thank you
www.bluestilly.com

**sneakysnier** · 2 Jul 2009, 08:54 AM

Just for further info:

I can create another customer through the store front end - but can't remove the user via the admin control panel. The only way i can remove the user is directly via MySQL.

The 'only' thing i've been able to edit in the admin control panel so far was removing the PayPal express module. No other edits appear possible - even altering store details.

The strange thing is the redirect to the 'stats' page every time i press 'apply' to an edit - regardless of which page i'm editing.

Cheers
Ian

**sneakysnier** · 2 Jul 2009, 09:27 AM

Ok - problem solved!!

I checked the content of the newly updated /admin/includes/functions/html_output.php file and noticed that the line of code that should have been added wasn't there..(see: Amending html_output.php by hand - in the 'readme.html' file - security_patch_v138_20090619).

So the 'fix' was to remove the broken html_output.php file and replace it (not overwrite) with the new one. (I'd simply overwritten it last time and something must have gone pear shaped).

So yes - Pilot Error !