Home → Bug Reports →

Invalid xml prefix - "cascade:href-asset-id" - attribute on a tag

• Edit

Darren

14 Mar, 2014 12:33 PM

Hi,

We just had an issue popup where a content editor was editing a few pages and received the following error on save.
Invalid XML: The prefix "cascade" for attribute "cascade:href-asset-id" associated with an element type "a" is not bound.

The error appeared for WYSIWYG editors on the page when they contained links. Looking at the source of the editor I saw this for each of the links.

<a cascade:href-asset-id="2b419afb0a480e59004bd4d2a6cfb7e0" cascade:href-asset-type="page" href="site://Directory/artssciences/english/keane-sexton_molly">Molly Sexton</a>

It looks like this has been identified before and I was hoping there is a global fix we can do to keep our users from seeing it. Right now our work around is to clean out the "extra" attributes via the HTML view and it'll save correctly.

It was mentioned here as a reported bug. That linked to bug report 1768 but I wasn't able to view it.

Any insight to the status of a fix or how we can handle it is appreciated.

Here's a quick run down of info that might help:

• We're running 7.10
• Doesn't appear to be happening for every page
• Only happening to links placed in WYSIWYG editors using the link toolbar button

Thanks
Darren

1. 1 Posted by Ryan Griffith on 14 Mar, 2014 01:00 PM

   

   Hi Darren,

   This issue is caused by a new background job that was added to Cascade Server 7.8 to rebuild entity relationships (for the Relationships tab). If this job is stopped abruptly by shutting down Cascade too soon, the assets that were being processed at the moment will become corrupted. The corrupted data will result in cascade:href-asset-id and cascade:href-asset-type attributes leaking to the WYSIWYG editor on edit. This causes the markup to be invalid and prevents the user from being able to make any modifications to that asset unless these attributes are manually removed.

   Although I do not have an official timeline, we do have an open internal issue logged to address this in the near future. The good news is we can manually fix affected assets within the database.

   When you have a moment, please follow these steps:

   • Run the following query to get a count of affected assets:

     select * from cxml_structureddata where textData not like '%http://www.hannonhill.com/CascadeServer/%' and textData like '%cascade:%'
     

   • Backup your database
   • Run the following query to update the affected assets:

     update cxml_structureddata set textData = REPLACE(textData, '<system-xml>', '<system-xml xmlns:cascade="http://www.hannonhill.com/CascadeServer/">') where textData not like '%http://www.hannonhill.com/CascadeServer/%' and textData like '%cascade:%'
     

   • Confirm the number of affected rows matches the select statement from above
   • Confirm the affected assets are now working as expected within Cascade Server

   Please let me know if you have any questions.

   Thanks!

   • Edit

2. 2 Posted by Darren on 14 Mar, 2014 01:06 PM

   

   Ryan,

   Thanks for the quick response and workaround.

   We'll run through this process the next time we can get our dba's time.

   -Darren

   • Edit

3. 3 Posted by Ryan Griffith on 14 Mar, 2014 03:51 PM

   

   Not a problem at all, Darren. Please keep me posted on how things go.

   I will make a note to follow up sometime next week if I don't hear from you in the meantime.

   Have a great day!

   • Edit

4. 4 Posted by Ryan Griffith on 19 Mar, 2014 08:30 PM

   

   Hi Darren,

   I wanted to follow up to see how things are going. Were you able to go through the steps I outlined in my previous comment? If so, are you still encountering any issues with the prefix?

   Please let me know if you have any questions.

   Thanks!

   • Edit

5. Ryan Griffith closed this discussion on 26 Mar, 2014 03:35 PM.

6. Darren re-opened this discussion on 27 Mar, 2014 01:24 PM

7. 5 Posted by Darren on 27 Mar, 2014 01:24 PM

   

   Hi Ryan,

   Sorry for the delay. We've identified there are 284 affected assets.

   We haven't had the chance to fix those but it seems straight forward. I'll keep you posted.

   -Darren

   • Edit

8. 6 Posted by Ryan Griffith on 27 Mar, 2014 02:08 PM

   

   Not a problem at all, Darren, thank you for following up.

   I'll go ahead and make a reminder to follow up sometime next week if I don't hear from you in the meantime. Please keep me posted if you run into any issues or have any additional questions.

   Thanks!

   • Edit

9. 7 Posted by Ryan Griffith on 04 Apr, 2014 07:16 PM

   

   Hi Darren,

   I was going over some older discussions and noticed this one is still open. Were you able to follow the instructions in my previous comment? If so, are you still experiencing the prefix issues?

   Please feel free to let us know if you have any other questions.

   Thanks.

   • Edit

10. Ryan Griffith closed this discussion on 08 Apr, 2014 05:54 PM.

11. Darren re-opened this discussion on 11 Jun, 2014 12:28 PM

12. 8 Posted by Darren on 11 Jun, 2014 12:28 PM

    

    Ryan,

    I know this was old and closed but wanted to give you a heads up. We were able to follow the instructions and fix the issue this morning.

    Thanks
    Darren

    • Edit

13. 9 Posted by Ryan Griffith on 11 Jun, 2014 12:38 PM

    

    Awesome news, Darren, thank you for following up. I am glad to hear the fix did the trick for you.

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

    Have a great day!

    • Edit

14. Ryan Griffith closed this discussion on 11 Jun, 2014 12:38 PM.