fancydressqueen Posted September 30, 2012 Share Posted September 30, 2012 (edited) So I upgraded my site from prestashop 1.3.1 to 5.0.17 using the autoupdate module via my back office. I then checked the front side of the site and found that the friendly URLs were causing issues. I decided to rollback the installation and did so again via the autoupdate module. I refreshed both the front and back office of the site, which produced blank screens for both. I downloaded a the prestashop 1.3.1 zip installation file and uploaded the missing themes, tools, translations and upload folder via FTP to my site. It then appeared via the front office like normal and I was able to get to the back office login page. I tried to login and it stated that the user or password weren't recognised. I accessed the database and found the employee field empty. I created a new user and had a new password sent via the back office login. I was then able to login to the back office but have found that all of the tabs are now missing. Is this an admin access issue or do I need to upload more missing files from the botched rollback? If I need to edit my access rights can I do this via my database as I obviously can't access the employee tab in the back office. Thank you. Edited September 30, 2012 by fancydressqueen (see edit history) Link to comment Share on other sites More sharing options...
fancydressqueen Posted September 30, 2012 Author Share Posted September 30, 2012 I've just realised that a number of the fields in my database are missing. I have a backup created by the autoupdate module but the files are in 6 different zip files. Do I simple merge all of the data in the text files and upload them to the database? The missing fields include the ps_access field, which I presume controls my admin priviledges. Is this correct? Link to comment Share on other sites More sharing options...
fancydressqueen Posted September 30, 2012 Author Share Posted September 30, 2012 Scrap this, I've fixed it. I deleted all of the fields in my database and uploaded 1 by 1 the backup database copies taken by the autoupdater. Everything is now back to normal. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now