Bug #29539
Importing a Site from XML does not work if DB is not empty
Status: | Closed | Start date: | 2011-09-07 | |
---|---|---|---|---|
Priority: | Must have | Due date: | ||
Assigned To: | Karsten Dambekalns | % Done: | 0% |
|
Category: | Services | |||
Target version: | - |
Description
When trying to import the T3CON11 Site via
flow3 typo3.typo3:site:import < Packages/Sites/TYPO3.T3con11Typo3Org/Resources/Private/Content/Sites.xml
I get following error:
Error: During import an exception occured. Notice: unserialize(): Error at offset 60 of 3284 bytes in Packages/Framework/Doctrine/Classes/DBAL/Types/ArrayType.php line 46
After reseting the database (delete, re-create) the command works once.
Interestingly the export command works
flow3 typo3.typo3:site:export > Export.xml
But re-importing that export results in another error:
Error: During import an exception occured. String could not be parsed as XML
Related issues
History
#1 Updated by Bastian Waidelich almost 4 years ago
- File Export.xml added
Attached the XML file that the export command creates from the most current T3CON11 site
#2 Updated by Bastian Waidelich almost 4 years ago
..As you can see the export is truncated thus creating invalid XML
#3 Updated by Karsten Dambekalns almost 4 years ago
- Category set to Services
- Status changed from New to Accepted
#4 Updated by Bastian Waidelich almost 4 years ago
- File 20110907120922fd1e50.txt added
In case of the export error an debug backtrace file is created (attached)
#5 Updated by Karsten Dambekalns almost 4 years ago
- Status changed from Accepted to Needs Feedback
Is this still an issue? For me this worked fine throughout, and I assume this to be caused by some broken data in the DB (encoding, broken import, ...) that now caused the reading of data for import to be corrupted.
#6 Updated by Bastian Waidelich almost 4 years ago
- Status changed from Needs Feedback to Closed
Karsten Dambekalns wrote:
Is this still an issue? For me this worked fine throughout [...]
I had the issue again with latest version of the conference distribution. But after re-creating the database again I can't reproduce the problem anymore.
Closing the issue for now!
#7 Updated by Bastian Waidelich almost 4 years ago
- Status changed from Closed to Needs Feedback
..Unfortunately this is not resolved.
I just got the same error again with the latest conference distribution..
#8 Updated by Bastian Waidelich almost 4 years ago
Bastian Waidelich wrote:
..Unfortunately this is not resolved.
Note: This has to do with the structure/size of the XML file. With the Flow3Org Site it works, but the T3CON site still dies with error
Notice: unserialize(): Error at offset 60 of 3287 bytes in .../ArrayType.php
#9 Updated by Sebastian Kurfuerst over 3 years ago
@Bastian: does this error still exist?
Greets, Sebastian
#10 Updated by Karsten Dambekalns over 3 years ago
- Status changed from Needs Feedback to Closed
Working fine for months now in the automated deployment… No clue how to debug this further.