Export/Import XML tool and archived assets

(Paul Hutchins) #1

Matrix Version: 5.4.0.3

We are looking to migrate assets from one instance of Matrix to another. I am attempting to use the Export Assets to XML Tool over smaller sections of content which is mostly successful in the testing I have done. I am however encountering issues where there appear to be assets that have the status of archived. I receive matrix warnings for all the assets and associated page contents and containers but the file is produced and able to be downloaded and imported using the Import Assets from XML Tool.

The import works as it should in the way it reproduces the structure but the content and asset names fail to come through once an archived asset is reached.

We do not have access to the export_to_xml.php script as Squiz manage our box.

Can archived assets be skipped or does their status require it to be under construction to work? Or should this just work regardless of the status?

Cheers,

Paul

(David Schoen) #2

I’m not sure about the exact errors with trying to export archived assets, but if you have a diverse set of statuses the export to xml tool will only be exporting a single version of safe edit (and related workflow statuses) assets too - e.g if an asset is in safe edit, from memory I think you lose the live version on the target instance, but you definitely don’t get both the safe edit and front end copy.

The export_to_xml.php script will behave the same as the Export to XML tool in _admin.

If you need like-for-like and you’re Squiz hosted, you should be able to request the migration be done with Mirror which will preserve status (including both versions of safe edit status assets).

(Paul Hutchins) #3

Hi David,

Thanks for getting back to my queries.

I’ve attached a couple of screen shots of the warnings/errors that I am getting when I attempt to export a section of content. The asset id’s included are assets that appear to be flagged as archived.

There are several thousand assets that need to be moved from our box to a matrix cloud install so perhaps Mirror would be the most stable option?

Cheers,

Paul

matrix-export-xml-errors-02.PNG1771x1137 189 KB

matrix-export-xml-errors-03.PNG1993x108 15.5 KB

(David Schoen) #4

Hi Paul, those warnings don’t seem to be from asset status.

Most of them are just that the core xml export tool isn’t 100% sure whether those IDs are real IDs or not and expects the user to check on them.

The last error seems like a bug, but we’d need to get test case to confirm.

Mirror is generally what we use internally for this sort of thing.