Content disappears after changing content type.

turnerjd's Avatar

turnerjd

15 Jul, 2010 08:29 PM

We are on 6.7 and whenever we change the content type of a page the content disappears. I know this wan't the case before the upgrade. Any ideas?

  1. Support Staff 1 Posted by Tim on 16 Jul, 2010 08:08 PM

    Tim's Avatar

    Hi there,

    Can you tell me the following:

    • Is this during an edit or create?
    • What kinds of content types are you switching between? Basically, I'm interested to see if you are switching from:

      • Standard WYSIWYG page -> Data Definition WYSIWYG page
      • Standard WYSIWYG page -> Standard WYSIWYG page
      • Data Definition WYSIWYG page -> Standard WYSIWYG page
      • Data Definition WYSIWYG page -> Data Definition WYSIWYG page

    By Standard WYSIWYG page I am referring to a page with no data definition applied to it. By Data Definition WYSIWYG page I am referring to a page that has a Data Definition applied to it that contains a WYSIWYG.

    Thanks!

  2. 2 Posted by turnerjd on 16 Jul, 2010 08:16 PM

    turnerjd's Avatar

    Hi Tim,

    This happens during an edit. I'm switching between Data Definition WYSIWYG
    page -> Data Definition WYSIWYG page

    Please let me know if I can provide any more info.'

    Thanks,
    John

  3. Support Staff 3 Posted by Tim on 19 Jul, 2010 04:31 PM

    Tim's Avatar

    Hey John,

    I played around with this a bit more and believe I am seeing the same behavior as you are. What I noticed is that with versions prior to 6.7, if a page changed from using one data definition WYSIWYG to another data definition WYSIWYG, the data would be 'mapped' between the two fields assuming that they had the same identifier. I've confirmed that this is not the case in 6.7.

    We'll look to correct this in a future version of Cascade Server. Apologies for the inconvenience!

  4. Tim closed this discussion on 19 Jul, 2010 04:31 PM.

  5. turnerjd re-opened this discussion on 19 Jul, 2010 04:35 PM

  6. 4 Posted by turnerjd on 19 Jul, 2010 04:35 PM

    turnerjd's Avatar

    Thx!

  7. Tim closed this discussion on 19 Jul, 2010 05:09 PM.

  8. travis.munroe re-opened this discussion on 19 Jul, 2010 05:29 PM

  9. 5 Posted by travis.munroe on 19 Jul, 2010 05:29 PM

    travis.munroe's Avatar

    Tim, can you fix this by adding a feature to allow us to map old identifiers to the new ones? I've run into situations where I'd like to restructure the data definition (e.g. grouping related fields) but doing so "loses" the data of existing assets using the current data definition. The data elements whose path changed in the resulting xml of the new data definition are "left behind"... if you change the data definition back, all of the fields magically appear again which means they're still in the database. It would be very nice to be able to migrate from one data definition version to another by mapping fields/paths from the old definition to the equivalent field/path in the new definition.

  10. Support Staff 6 Posted by Tim on 19 Jul, 2010 05:38 PM

    Tim's Avatar

    Hi Travis,

    While I don't believe we'll take this route initially to correct the problem, I do think it sounds like a good idea. Please be sure to create a new idea for this on our Idea Exchange so that others can vote/comment on the item.

    Thanks

  11. Tim closed this discussion on 19 Jul, 2010 05:38 PM.

  12. travis.munroe re-opened this discussion on 19 Jul, 2010 05:41 PM

  13. 7 Posted by travis.munroe on 19 Jul, 2010 05:41 PM

    travis.munroe's Avatar

    Hi Tim,

    Can you fix this by adding a feature to let us map fields from one data
    defintion version to another? I've run into situations where I'd like
    to enhance an existing data defintion (e.g. change field identifiers;
    group related fields; etc) but doing so "loses" existing data for any
    fields whose path in the resulting XML has changed. I've found that if
    I revert the data definition changes, the fields magically appear so it
    seems they're still in the database somewhere. Although I could
    probably find the table and write a SQL script to update the paths, I
    think it would be best if Cascade Server provided an interface to map
    old field paths to the new ones and do the database updates for me.
    This could also be handy for the bulk change utility if someone had the
    need to change Content Type on a large number of pages that may or may
    not be using the same data definition.

    Thanks,
    Travis

    -----Original Message-----
    From: Tim
    [mailto:[email blocked]]
    Sent: Monday, July 19, 2010 9:34 AM
    To: Munroe, Travis
    Subject: Re: Content disappears after changing content type. [General]

  14. 8 Posted by jpetkus01 on 30 May, 2012 09:27 PM

    jpetkus01's Avatar

    Hello Tim & Travis,

    I know this issue was posted 2 years ago, but did anybody ever resolve this?

    We are experiencing the same "data loss" converting from Standard WYSIWYG page to Data Definition WYSIWYG page under version 6.7.6. We have about 2000 pages that are affected by the change and multiple users who cannot enter data until we get the issue resolved. Is there a magic script or something to fix the data mappings or will we have to fix all the pages manually in order to use the data definition?

    Any help or insight would be greatly appreciated.

    Thanks in advance

  15. 9 Posted by Bradley Wagner on 31 May, 2012 03:03 PM

    Bradley Wagner's Avatar

    Hi, we added the ability to map the contents of the WYSIWYG field in a standard page to the first WYSIWYG field in a data definition page with CSI-211 in Cascade 6.8.3

  16. 10 Posted by jpetkus01 on 31 May, 2012 04:23 PM

    jpetkus01's Avatar

    Excellent, thank you for the speedy response.

  17. 11 Posted by Bradley Wagner on 31 May, 2012 04:30 PM

    Bradley Wagner's Avatar

    Definitely.

  18. Bradley Wagner closed this discussion on 31 May, 2012 04:31 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac