Partial Design Import

[jont]

I have a site on Machine A titled "my site 2007" and an copy on Machine B titled exactly the same "my site 2007" ... all is fine.

Making changes to various layouts on Machine A .... I create a partial design snapshot and email to Machine B .... Machine B installs and none of the changes take hold.

I export a full snapshot to Machine C (which has never seen the site) ... license a new site with the same name "my site 2007" ... import the partial design snapshot ... this takes the changes and updates accordingly.

Why should this be so? Apart from products and sub-sections being added to Machine B all layouts, paths to the site etc remain identical. I even use the precise same site name to retain the quirky ability to allow 2 way editing between Actinic and DreamWeaver in outer layout (using absolute paths).

All machines are on MultiSite v8.5.0

[completerookie]

a few things,

• which version?? (assumes both have the same version)
  early versions require that you import TWICE before all the changes take place - read bug - same file, same import, just do it twice in succession - just remember to rename the backup file the second time.
• is it the layouts that give the problem - I THINK? but can't pin it down, that partial imports do NOT import layouts correctly

[jont]

Hi Kevin,

All machines are on MultiSite v8.5.0

Identical installs on all machines. Machine B had the partial imported twice - but understand this issue was resolved in 8.5 from the earlier troubles .. Machine C had a single install of the partial snapshot and everything came in fine.

It was the layouts causing the issue - this is the whole point of a partial design snapshot - to be able to export and import layouts between master and client machines. All boxes were ticked during the export so nothing was missed. Machine C imported all the layouts from the snapshot correctly as expected.

It is very peculiar that Machine C effectively did the same as Machine B and worked.

[completerookie]

Jont.
I'm on 8.0.4 - not ventured onto 8.5 but if (and its a big if) that cures my layout export / import, then I would consider it

I've spent some really frustrating hours with layouts.

I removed the <table> etc from the outside of a layout, and then removed the BeforeRow and AfterRow ( effectively the <tr> ) and replaced the inner ( <td> ) etc with <div> </div>
when I transferred to another site, the <table> appeared to comeback, the <tr> came backm but the <td> seemed to be replaced with the <divs>

its almost as though (sometimes?) the partial export (maybe the import) found nothing and replaced with <table< and <tr>

I just can't put my finger on WHY and WHERE and WHEN ( iahve tried with ALL tickboxes ticked and just the occasional ones - I'd love it if actinic was intelligent enough to know ONLY the ones I'd changed since the last export

all I know is that with <table> and <tr> getting in the way of opening and closing <div> it messes up the layouts something rotten

[pinbrook]

I've got a design snapshot at the mo that refuses to stick.

I've imported it 3 times on top of a site upgraded from 6 to 8.

Actinic support had to do my 6-8 upgrade, I've asked them into import the design snapshot too.

[cdicken]

Hi John

I think this is something that you would need to work through with support. Trouble is, their installations would probably mimic Machine C - i.e. a brand new installation.

A shot in the dark - were either Machine A or Machine B upgraded from previous versions of Actinic?

[jont]

Hi Chris,

all 3 machines were on previous versions, all upgraded to v8.5.0 at about the same time using a full removal of the existing and then a clean install of the v8.5.0. All installations are intrinsically the same.

I removed v8.5.0 this morning on Machine A and installed the latest full version (from the Actinic site) and imported the last v8.5.0 snapshots. Have yet to test on a design export.

I think it is due to the absolute / relative paths to the outer layout. Once the outer layout has been sorted in DreamWeaver I am going to sever the 2 way functionality (leaving the path relative) and add the outer_layout.html to the additional files.

John