Home → Web Services →

Migration tool is generating "Content is now allowed in prolog" errors

• Edit

craig.haiss

22 Jun, 2016 05:21 PM

Hi there!

Our custom migration tool (migrates HTML into blocks instead of pages) is generating the following error for each HTM in the zip file...

"Error on line 1: Content is not allowed in prolog."

I've research this on Google and discovered that it is often related to the file format issues (utf-8, etc.) OR strange characters that precede the doctype declaration at the beginning of the file. However, I'm seeing neither of these issues in the files we're trying to migrate. Also, we've used this migration tool on similar UTF-8 files; it's just this batch that is giving us grief.

Can you take a look at the zip file and tell us if you can spot any strange formatting that would cause such an error? (Note that these files were translated by our translations vendor and sent back to us. Perhaps a file encoding issue or strange characters were introduced during translation. Also, the XML files migrate fine; it's just the HTM files that generate errors.)

Thanks!

• esAR_files.zip 204 KB

1. 1 Posted by Ryan Griffith on 15 Jul, 2016 08:29 PM

   

   Hi Craig,

   My apologies for the delayed response. I was going over some older discussions and noticed this one is still open. Were you able to track down the cause of the error you were running into?

   Please feel free to let us know if you have any other questions.

   Thanks!

   • Edit

2. 2 Posted by craig.haiss on 18 Jul, 2016 01:16 PM

   

   No problem, Ryan, thanks for responding! Yes, we were able to resolve this. We noticed the translated files were saved as UTF-8. We saved them as ANSI, and then the migration worked perfectly.

   I'll close the thread. Thanks again!

   • Edit

3. craig.haiss closed this discussion on 18 Jul, 2016 01:16 PM.