Timeline for Unable to Port Bundles in Web8
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2018 at 14:15 | comment | added | ThatITBloke | The items listed in the error message do appear in the export log. We've used the piece-meal approach to importing when we've had schemas refuse to import before, so I'll try that for this too. | |
| Jan 8, 2018 at 14:14 | comment | added | ThatITBloke | [deleted because I was replying to the wrong question] | |
| Jan 8, 2018 at 13:12 | comment | added | Dylan .. Mark Saunders | also worth considering is breaking your import into specific parts; try schemas, then templates, then content etc. often part of our standard "quick checks" | |
| Jan 8, 2018 at 13:05 | comment | added | Dylan .. Mark Saunders | Can you update the reference to "Item /webdav/...[full path]." ... is this [full path] something that matches your export log? | |
| Jan 5, 2018 at 10:53 | comment | added | ThatITBloke | I'm testing using a couple of existing CTs, two new test content components (which are as basic as possible - some dummy text in our most basic content schema) and a single page (using default PT and no metadata schema) using those CTs/Components. When you say I'm 'likely not exporting dependencies', is that a specific option or are you asking if the dependant items are being exported? If it's the former, I'm not sure where that option is, and if it's the latter then I know all dependency checkboxes are selected and the dependent content is in the exported file. See above for log. | |
| Jan 5, 2018 at 10:30 | history | answered | Dylan .. Mark Saunders | CC BY-SA 3.0 |