Hi,
I realized this morning that my websites were down, connecting to them I saw the upgrade required page so I made it but most af the parameters and settings were lost, so I made a restore database backup from yesterday but this is what I get :
"Fatal error: Error MySQLi : SHOW FULL COLUMNS FROM `[Prefix]admintoobject` failed. MySQLi sent error Table 'xxx_admintoobject' doesn't exist in /home/xxx/public_html/zp-core/functions-db-MySQLi.php on line 78"
Can you help me ?
info :
Zenphoto version 1.4.5.7
theme Zpskeleton lightly modified
PHP : 5.3.22
MySQLi : 5.1.67
Comments
The error tells a table is missing. If you installed new setup should have created that. Look at the database via phpmyadmin or whatever tools your host provide to see if it is there or not.
Sure that your server has no other problems as sites are not "down by themselves" for no reason?
thank you for your reply.
The backup and the script belong to the same version, this is what I don't get.
You may be right about my server.
This morning I found some of the directories of my Zenphoto installation (which is in a subdirectory) in the root directory of my website.
All of them in the root directory were empty and appeared on the server while I was not connected. This is really weird.
As a file based system, ZP found these directories and shown the required upgrade page.
Maybe I should try a brand new life and work as a crash test dummy.
I'll make a complete restore of the website
Symlinks are created on the root folder so Zp propose an "update required" page instead of the gallery index.
Can you reproduce that ?
Did you contact your host in case they changed something? Maybe sbillard has any other idea later today.
Yes I did, as usual, they say nothing has changed.
Anyway it works at last for me with a previous full website backup but I think that the "protect setup script" in cloned installation could be involved.
Yeah maybe Stephen will have an idea about it.
Thank you for your reply and for your work.
As to the script protection: About the only way things could be wrong with the situation you describe is if you were protecting the scripts on the master install after already loading the overview page on the clone.
Of course we really should not allow clone installs to make that change so that will be fixed.
"the only way things could be wrong with the situation you describe is if you were protecting the scripts on the master install after already loading the overview page on the clone"
you must be right, I'm pretty sure this this is what I did.
Thank you about the ticket that I've missed (the one that I've found got a different line number for the error).