Home → Bug Reports →

En dash removed/hidden from custom metadata field

• Edit

Sarah Johnson Li

29 Apr, 2015 06:36 PM

When an en dash is placed in a Custom Metadata field and saved, the en dash does NOT appear in the View > Properties screen OR when Editing the asset. However, it does appear when the field is displayed on a page.

1. Copied "1965–1967", which contains an en dash, and pasted into Custom Metadata text field of image asset. Saved changes.
   
2. Viewed asset properties and the dash is missing: http://grab.by/GS9Y (Creation Date)
   
3. On the Edit screen, the en dash is missing: http://grab.by/GSa4
   
4. Viewed the page asset where the Creation Date custom field is displayed, and it appears normally: http://grab.by/GSa6

NOTE: accented e and copyright symbol appear just fine in all locations. It just seems to be the en dash. I did not try an em dash.

Cascade Version: 7.10.2

Apologies if this has been resolved in newer versions of Cascade Server.

1. 1 Posted by Ryan Griffith on 29 Apr, 2015 07:08 PM

   

   Hi Sarah,

   I was not able to reproduce the behavior you described in my local 7.10.2 and 7.12.5 instances. See attached screenshot for reference.

   Curious, are you seeing this behavior in all browsers? Also, can you confirm what collation and encoding you are using on your database?

   Please let me know if you have any questions.

   Thanks!

   • Screen_Shot_2015-04-29_at_3_07_11_PM.png 190 KB
   • Edit

2. 2 Posted by Sarah Johnson L... on 29 Apr, 2015 07:12 PM

   

   Hi Ryan,

   This is happening in PC Chrome, PC Firefox, and Mac Chrome or Safari. I'll have to find out about the collation and encoding, but I'm guessing that may be the issue if you can't reproduce it.

   Incidentally, what collation and encoding are you using on your instances? If ours turns out to be different, I guess we should change it?

   Thanks,
   Sarah

   • Edit

3. 3 Posted by Ryan Griffith on 29 Apr, 2015 07:23 PM

   

   Thank you for following up, Sarah.

   My local instances are running on MySQL with a default character set of utf8 and collation of ut8_unicode_ci.

   Please keep me posted on your findings and let me know if you have any questions.

   Thanks!

   • Edit

4. 4 Posted by Sarah Johnson L... on 01 May, 2015 05:31 PM

   

   I was told BINARY collation and the UTF-9 Unicode

   Thanks,

   Sarah Johnson Li
   Web Developer | Rollins College

   • Edit

5. 5 Posted by Ryan Griffith on 04 May, 2015 07:08 PM

   

   Hi Sarah,

   Those settings could very well be contributing to the behavior you are encountering. Our recommended character set and collation settings would be the ones I listed previously.

   If you have a test instance, I would suggest trying to adjusting the database settings to see if this resolves the behavior.

   Please let me know if you have any questions.

   Thanks!

   • Edit

6. 6 Posted by Sarah Johnson L... on 04 May, 2015 07:23 PM

   

   Thanks Ryan! I'll ask our sysadmins to update the test instance and we'll see if that fixes the problem :)

   Sarah

   • Edit

7. 7 Posted by Ryan Griffith on 04 May, 2015 07:48 PM

   

   Not a problem at all, Sarah. Please keep me posted on your findings, or if you have any additional questions.

   Have a great day!

   • Edit

8. Ryan Griffith closed this discussion on 27 May, 2015 07:30 PM.

9. Sarah Johnson Li re-opened this discussion on 23 Jul, 2015 03:22 PM

10. 8 Posted by Sarah Johnson L... on 23 Jul, 2015 03:22 PM

    

    Hi Ryan,

    Following up on this, we did change the setting in our test instance, but page asset content has been converted to chinese characters and the error "Content is not allowed in prolog." appears in the view screen.

    I guess we can't switch it successfully with existing content? Should we try to copy over the production database and see if it still happens?

    Thanks,
    Sarah

    • Edit

11. 9 Posted by Ryan Griffith on 23 Jul, 2015 07:22 PM

    

    Hi Sarah,

    Based on your description, it sounds like there was a conversion problem. Do you happen to know how the collation and character set settings were changed?

    Thanks!

    • Edit

12. 10 Posted by Sarah Johnson L... on 23 Jul, 2015 07:25 PM

    

    I honestly don't know how they changed it. I would have to ask the sysadmin. Is there an non-ideal way to change those settings?

    • Edit

13. 11 Posted by Ryan Griffith on 23 Jul, 2015 07:47 PM

    

    Hi Sarah,

    You should be able to use the alter database and alter table commands. See the following for additional information:

    • https://dev.mysql.com/doc/refman/5.0/en/charset-conversion.html
    • http://stackoverflow.com/questions/6115612/how-to-convert-an-entire...

    Note: you may be running into an issue where the new character set does not support the same characters, but let's hope that's not the case.

    Another possible solution could be what is outlined on this page where your content is already UTF8, but the database is just incorrect. In that case you would:

    • export the database using the current (incorrect) encoding
    • manually change the character set within the export file to the correct one
    • drop and re-create the database using the correct encoding
    • import the updated export

    Please let me know if you have any questions.

    Thanks!

    • Edit

14. 12 Posted by Sarah Johnson L... on 27 Jul, 2015 08:14 PM

    

    Thanks Ryan,

    I'll pass this along, but IT upgraded our test instance before trying to switch this back. This will get interesting...

    Sarah

    • Edit

15. 13 Posted by Ryan Griffith on 28 Jul, 2015 11:42 AM

    

    Hi Sarah,

    If the encoding is still incorrect on the test instance, the steps I outlined previously should still be valid.

    To summarize, they would:

    • Turn off Cascade on the test instance
    • Export the test database using the current encoding
    • Manually edit the export file to change the encoding settings
    • Drop and re-create the database using the correct encoding
    • Import the export file
    • Start Cascade on the test instance

    Please let me know if you have any questions.

    Thanks!

    • Edit

16. 14 Posted by Sarah Johnson L... on 29 Jul, 2015 07:04 PM

    

    Hi Ryan,

    Just an update, our sysadmin and db admins are trying to resolve another issue with logging in after they upgraded the test instance. I don’t know if it has anything to do with the character encoding change, since I was able to login before the upgrade. Once they make progress on that, I’ll let you know if the steps you provided resolved it.

    Thanks,

    Sarah Johnson Li
    Web Developer | Rollins College

    • Edit

17. 15 Posted by Ryan Griffith on 07 Aug, 2015 01:53 PM

    

    Thank you for following up, Sarah. Please keep me posted on how things go and let me know if you have any questions.

    Thanks!

    • Edit

18. 16 Posted by Sarah Johnson L... on 14 Aug, 2015 03:33 PM

    

    Looks like we're in the clear! Thank you for your help Ryan. :)

    • Edit

19. 17 Posted by Ryan Griffith on 14 Aug, 2015 03:46 PM

    

    Thank you for following up, Sarah, I am glad to hear you were able to resolve the issue.

    I'm going to go ahead and close this discussion, please feel free to comment or reply to re-open if you have any additional questions.

    Have a great day!

    • Edit

20. Ryan Griffith closed this discussion on 14 Aug, 2015 03:46 PM.