Duplicated Element in tree

[Tiffany]

Has anyone seen this? We are using v10 and I just noticed weird things
happening in SmartTree Project Structure. If I populate a txt_content
field and then go into SmartTree and see two txt_content elements for
the page. One is populated and one is not. The problem worsens when
the red dot for the element doesn't populate the duplicate and no text
appears. Weird. Any ideas?

[Gavin Cope]

Actually, yes, I've now seen this.

After upgrading 10.1 SP2 HF1 to 10.1 SP2 HF5, the Published charset for the project Language Variant was reset from UTF-8 to SERVER. SERVER - in this case - equated to Unicode so when publishes started, things broke in a major way.

What does this have to do with duplicating placeholders? :)

At the same time, any new placeholders I created on templates would get duplicated in the instance of the template exactly as you described.

I've done nothing but set the Published charset back to UTF-8 which has fixed my publication problems but also when I create placeholders now, I get no duplication. I had to delete and recreate the few placeholders I had created (and had duplicates) but when I recreated them, they no longer created duplicates.

Hope this helps.

Cheers,

Gavin

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

[Joel Kinzel]

Yes we have seen this. We were given a tool by support that eliminates this, but we are now also seeing this with content classes. We use the "Share Content Classes" feature heavily and it only seems to happen to us in the "child" projects.

Also an interesting note: Each placeholder has it's own unique ID, and you never know which one the system is actually evaluating/using. The tool that support gave us eliminated the un-used elements, but IMO, it is not adequate. There is obviously a bigger issue going on here which needs to be fixed. I'm not sure if it has been fixed in any of the recent HF patches though as I haven't had a chance to read the release notes recently.