@inde
It seems that there are many kinds of possibilities may cause this mistake. Maybe only a small negligence, so please don't worry too much. I have a suggestion:

• Copy a new backup file first, then open it with a large file editor( such as PilotEdit ), copy and execute only one table sql statement at a time, until you find one single error sql. Then we can have a research and be much easier to seek the solution.

I did that already. All is fine till we reach comments and other textual fields. I did the correction on comments to see how much time it will take and it's huge ! Something bugs me. Why a backup which is completed normally with the same parameters than usual is not working the same day I did it?

I tried lots of backup I have made since 2 years and none of them is working except the whole folder backup made with tar. Unfortunately it is too old to be relevant...

Now the problems I have...

Accents and symboles are transformed in all&#XXX; -> not accepted by MYSQL import because of semicolon... Do I have to replace them ?

Same probleme with smileys like ;) :-) ;) which are generating errors... Why???????????

What the sake of having a backup of text which creates so much errors. That's insane! Is there a way to avoid that????

Here a sample of error I encounter...

In evo_coll_settings

(8,'blog_footer_text','©$year$ by $owner$')
(11,'blog_footer_text','©$year$ by $owner$'),
(12,'blog_footer_text','©$year$ by $owner$'),
(13,'blog_footer_text','©$year$ by $owner$'),
(14,'blog_footer_text','©$year$ by $owner$'),
(15,'blog_footer_text','©$year$ by $owner$'),
(16,'blog_footer_text','©$year$ by $owner$'),
(18,'blog_footer_text','©$year$ by $owner$'),
(19,'blog_footer_text','©$year$ by $owner$'),
(20,'blog_footer_text','©$year$ by $owner$'),
(21,'blog_footer_text','©$year$ by $owner$'),
(22,'blog_footer_text','©$year$ by $owner$'),
(23,'blog_footer_text','©$year$ by $owner$'),
(24,'blog_footer_text','©$year$ by $owner$'),
(25,'blog_footer_text','©$year$ by $owner$'),

the semicolon between &copy and $year is not accepted...

Same problem with a February 2015 backup

can anybody check its backup and tell me what am I suppose to have in these fields???

in evo_coll_settings

accepting (22,'ping_plugins','ping_pingomatic,evo_twitter'),
refusing (23,'ping_plugins','ping_pingomatic,evo_twitter'),

accepting (11,'plugin18_twitter_msg_format','Nouveau post: $title$ $url$ #b2p'),
refusing (23,'plugin18_twitter_msg_format','Nouveau post: $title$ $url$ #b2p'),

refusing (23,'plugin18_twitter_msg_format','Nouveau post: $title$ $url$ #b2p'),
accepting (23,'plugin18_twitter_msg_format',''),

What kind of nonsense is that??????

@inde

Where do you paste and execute your sql statement? It's impossible to cause this error only by a semicolon unless you use the command line which consider the semicolon as an end mark. Don't you use the phpMyAdmin sql textarea to execute your sql statement?
However the best way I guess is executing the command mysql> source your-backup.sql to import backup data into your mysql database. In this way, would you also meet a 1064 error ?

haharen, you are just the BEST!

First try with the plesk backup did not ended up correctly but the phpmyadmin's one went like a breath!

I was using phpmyadmin import option and that was just the problem. I will never do it again!

I still have the phpbb files not loaded for a reason I still have to discover but the blogs are back!!!!

Thanks so much!

I will try again the update tonight. Do you have an idea why the previous one I made stopped in the middle of the database upgrade?

@inde

Perhaps the page execution time of your web server is limited in a relatively short time.
Can you modify the configuration file php.ini? If you can, please increase the value of max_execution_time ( default is 30), you can set it to 300( or more ), and restart the apache server, then have a try.

Ok I will try that tonight and will let you know... thanks again and again!

@inde
You're welcome.
Waiting for your good news.

haharen,

I realize how huge the evo_session is. Do I really need to keep all records?

@inde wrote earlier:

Do you have an idea why the previous one I made stopped in the middle of the database upgrade?

"stopped in the middle of" does give no workable info.

Please make a complete screenshot next time you have an error.

@Haharen -> One more time you saved my life! max_execution_time was the problem and 300 was not enough. 600 did the trick and everything went perfectly right. You're damn efficient. Thanks a zillion times!

@François -> Sorry for that. I meant the page where the update in converting all files. It stopped in the middle of the PHP files with error to all files.

Now it's working just fine. The back office is just perfect. Too bad there are so few 3 colonnes templates. The installed Zen is not working anymore. I may have to reinstall from a fresh download.

Thanks for all guys and keep up the good work.