Quote:
|
Originally Posted by Sembroidery
It seems that sometimes, when you have errors on some other files (as you had on head.tpl and func.php) and the patch is not "officially" proclaimed as finnished, the SQL-patch has nevertheless either completely or partially gone through. And when you then repeat the patching process in order to fix the error-files, the SQL patch tries to run again. And then you get "duplicate entry" error messages like this because it has already created the records it need to create.
I had the same problem when updating from 351 to 352.
|
I think that your right here. It would be much better if the sql patch was applied ONLY after the files were patched and you were given a prompt to update the database