Cloning design assets and associated files


(Ryan Archer) #1

Having much difficulty cloning a design asset file along with its children (customisations, images, JS, CSS, etc)

It's a big job and the system keeps throwing errors about 75% in and it just doesn't go anywhere.

 

I'm doing some major edits on an existing website which makes extensive use of the 'mysource file' referencing. Is it normal for a clone procedure to fail in this manner? I've tried to do it on a smaller scale before and I think the system failed because when cloning nested content under a design asset it did not give a unique asset name - so there was a file naming conflict.

 

This is probably a good reason why I'm not too particularly fond of the 'mysource file' referencing system - I think you can really build yourself into a bad corner if you want to do some heavy customisation in the future that goes beyond using design asset customisations (right now the design file is just so full of customisations and nested content/variables that it just falls over and makes a HIPO 50% of the time...


(Bart Banda) #2

Have you tried using the export and import function of the design? I can't remember if it copies over design customisations though, and perhaps your versions of Matrix is your downfall again? 


(Ryan Archer) #3

Yeah, I am prioritizing the upgrade first before doing this stuff I think.

No, I have not tried the export/import function, where would I find more information on this feature? Is it here at this link? http://manuals.matrix.squizsuite.net/tools/chapters/export-assets-to-xml-tool


(Anthony Ponomarenko) #4

Yup thats it, the import is also a link on that page as well.

 

I know there have been several bug fixes to the export with designs recently so not sure how well it will run in 4.18