Thread

Hello,
I migratged from 1.6.1 to 1.6.2 and did make a backup with the 1.6.1 database backup utility and myphpAdmin as well. But when i tried to load (restore) from the myphpAdmin backupfile I didn’t get all my templates. After some analysis I assumed that the cause of the error were the comments {!-- --} that seemed to mess up (crash) somehow the the whole file. I tried then with the backupfile I made with the EE backup utility from 1.6.1 and ohh luckily that worked well. But then being successfully arrived in 1.6.2 I realized that this backup-tool (that really saved my migration) isn’t available anymore in this new release 1.6.2 and I wonder how to migrate in the future.
I have quite a lot of comments {!-- like this --} in my templates but they seam to mess up this whole backup restore procedure.
I am disappointed to sea that this backup utility isn’t part of 1.6.2.
Also I wonder if this comments really are the cause of the problem as it did seam to me.
Is there another way to do comments that don’t mess up the backup file done with myphpAdmin?

Any comments appreciated that help give EE migration plan some more reliability.

Just on further addition to this post.

Probably the misery is not caused from 1 line comments like {!-- one line --} but from multi-line comments like
{!-- multi line
inactive template text
inactive template text
inactive template text
--}

For me it seams this is critical for backup restore procedure with myphpAdmin (but obviously not for the backup utility from ExpressionEngine 1.6.1)

Is there another way to inactivate template text?

I’ve never experienced this problem, blackhorse.  What version of phpMyAdmin are you using?  Two hyphens together is a standard for a SQL comment, but it should be protected inside the dump.

Thank you very much for your answer!! I am glad that it doesnt seam to be a general problem and probably I messed something up.
I did make the backup with phpMyAdmin Version 1.6.4 on Linux.
But now I am back on Windows Vista and intend to stay here.
For me this post can be closed.