Conversation Bug: Copy page via sitemap does not generate new Conversation block/objectBrowser Info Environment
1. Add a Conversation block to a page.
2. Post a unique comment so you can identify the block
3. Using the sitemap, drag the page to another location and select "Copy".
4. View the new page.
5. The Conversation block on the new page will already have your "unique comment" from step 2.
If you review the database, no new Conversations have been created, and both blocks on both pages share the same block ID.
I misunderstood how Block IDs work. So perhaps this is more of a general functionality question than a bug report per se.
As I understand it, duplicating a page will duplicate any blocks, in essence displaying the same block on two separate pages. As soon as you edit a block that block gets a new Block ID with the new version, but just on that specific page. So you can safely edit the block on the cloned page without affecting the block on the original page.
With Conversations, it makes sense that when you edit a Conversation block you don't want the Conversation ID to change, otherwise you'd lose your existing messages whenever you edited the block.
The problem is that when you first clone the page, the Conversation ID is cloned as well, so you end up with the same Conversation on both pages. This makes sense if you're aliasing a page, but doesn't really make sense when you're copying a page in order to slightly change the content.
Our use model is we have a series of e-learning lessons that we want to duplicate and slightly modify for a different audience. So we use the sitemap drag and copy mechanism to quickly copy the whole set of lessons (can be as high as 80 lessons in all). We expect the Conversation block to be created as unique blocks on the cloned copies, not aliases to the original conversation. That was how things worked with Concrete 22.214.171.124.
The workaround is to delete and recreate the Conversation block on each page, but when you're cloning 80 pages, that adds a lot of extra work.
I'd welcome any suggestions/workarounds/hacks to fix.