Bug: Selector with undefined layout fails to import.

[NormanRouxel]

Scenario:

Create a new selector and some new layouts that are chosen by the selector.

Then export a partial site design that includes that selector but not all of its layouts.

Now import that partial site design into a new site. The selector doesn't import and no error message is issued.

This is probably a problem in V9 too.

[cdicken]

Hi Norman

Many thanks for reporting this. I can reproduce it in v8, but, for the record, it doesn't seem to be a problem in v9.

EDIT

OK - I can now see this in v9. The layout selector won't import if the layout(s) it points to doesn't exist on the target machine. In understand now.

[leehack]

Empty list layouts seem to be suffering the same fate, does actinic fail to copy something if it has nothing in it? If for example you want to change the marketing lists in the sidebars, to add your own headers, you need to remove the actinic code bringing in the titles. If you do this in the list layout settings and then PDS, your changes are not carried over, the actinic code remains.

[jont]

Lee .. add in some <!-- &nbsp; --> to empty lists and this should resolve when transferring PDS to clients.

[leehack]

Hi Jonty, cheers i will give it a go. On the 'Overall Design' tab i have &nbsp; in the Empty List Entry and on the Rows and Columns tab i have some minimal code, a <hr/>, so it is not fully empty, but still fails to transfer. I've seen your comments before on empty layouts and although i called it 'empty', it is in fact heavily reduced from the standard actinic method (not empty), so i didn't think your findings would apply.

I will give it a go though and report back, cheers. Why do we need to add code, when our initial action was to actually reduce the code, can someone put some more grease on my pole please.

[jont]

can someone put some more grease on my pole please.

You supply the rubber gloves and I will be there in 45 minutes big boy!

When I remove the <td> code from the layout lists (as I float everything with CSS) adding to all of the cells with a comment code seems to appease Actinic when transferring. It is as if Actinic decides that the list is faulty when left blank so it will populate with the default code. Which is nice

[leehack]

This is the same situation, tables being removed and code streamlined, in fact there is little of the standard code left, apart from a &nbsp; It seems to hinge on whether the 'Overall Design Tab' contains code or not as other changes work fine for me. Determined to bloat they appear to me, adding comments although a clever workaround is ludicrous IMO. It's been known for at least 12 months that the PDS fails, this all on the back of V8 being the software for the 'designer'. I need to go ride my bike, my few months of calm are about to be undone.

[TraceyHand]

Lee .. add in some <!-- &nbsp; --> to empty lists and this should resolve when transferring PDS to clients.

interesting tip!

I wonder if this would resolve the problem I had upgrading a site between V8 and V9, where I'd stripped all the tables out of the list layouts, only to find them, very kindly , all stuffed back in when I upgraded even though I did select the 'do not upgrade my layouts' option!