When I clone a view that has page displays in it, the cloned pages have the same url.

I.e. if a page display's path is /blog-view-1 then the path for the cloned page display of the cloned view is still /blog-view-1. It might be good to add into the cloning feature to rename these pages to something like /blog-view-1-cloned, sort of like for the cloned names of the views are done (clone of ___ view).

Doing so would prevent page/path conflicts.

CommentFileSizeAuthor
#4 1270304-change-url-clone.patch984 bytesdawehner
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

I guess there should be definitive some action moved to the display to react on cloning of a view.

Some of the examples might be this here, but i guess some people could be confused here.

dawehner’s picture

Assigned: Unassigned » merlinofchaos

@merlinofchaos

* What do you think first about inform the system about cloning?
* do you think this certain request is a common use case?

sprice’s picture

I guess that the common use case would be whether or not people have a tendency to clone views that have page displays in them. It's part of my workflow (i.e. setup an initial version of the view sometimes clone it to add in other aspects of the view... sort of like 1.0 and 2.0 versions of the view).

dawehner’s picture

FileSize
984 bytes

here is a basic start of this patch.