When upgrading an older site to the new Distro that happened to be using the uuid module and panels we noticed behavior of cloned panel pages (have the same uuid) due to so many panel pages having the same uuid's (we resolved them by re-creating from scratch the (cloned) items)), for instance "title" change on one panel propagaged to all cloned panels with that uuid that were intended to have different titles. There was also other undesirable behavior we noticed but that is just one example.

The "Clone" capability is tempting for site builders to use because it allows site builders to quickly build similar type pages or variants however cloning seems to be hampered by uuid because the uuid gets cloned but the point of "cloning" in this use case is to make a new panel page the same as the last one except make it "NOT unique". The last part "not unique" is the key to understanding this issue.

In theory (I haven't tested this yet) would it help site-builders if they disabled the uuid module so they can clone things without having a uuid problem then "after cloning" the uuid module could be re-enabled after the site-building is done?

This might be something we want to test and if it is successful add it to the distro documentation as we are making use of uuid in other areas (like linkit and menu deployment and the deploy module).

Any thoughts?

Comments

joseph.olstad’s picture

Issue summary: View changes
joseph.olstad’s picture

Issue summary: View changes
joseph.olstad’s picture

Issue summary: View changes
joseph.olstad’s picture

Issue summary: View changes
joseph.olstad’s picture

Maybe we could create two wetkit features:
1) a "feature" called "wetkit fast sitebuilding on for cloning"
and
2) a feature called "wetkit fast sitebuilding off for production with uuid" which would enable-disable the correct modules and variables related to work that needs to be done by site-builders and configuration that needs to be used in production environments.

documentation would have to be added for usage.

Maybe there's another simpler solution?

? ideas

joseph.olstad’s picture

actually, there's probably a hook in the panels "clone" that we could use that would exclude uuid from the generated "clone"
?
this would probably be more seemless to the end user, forget comment#5

This way we wouldn't have to document , it would be seemless to the site-builder and more intuitive behavior, that we would expect from "clone".

sylus’s picture

I am pretty sure this has been completely resolved in the latest release of panels / ctools that v1.3 will have? Confirm?

joseph.olstad’s picture

Status: Active » Closed (works as designed)

Works beautifully as suggested!

tested on 1.x dev (1.3) and uuid is no where to be found in the "clone"

When in doubt, test first!

This is good to know, because I was having doubts about "clone" but now it works perfectly.

Thanks!

joseph.olstad’s picture

I enabled all modules that use uuid and it still worked after testing.

Super!