View content with Asset Publisher when Title contains special quotes

• Type: Bug
• Status: Closed
• Resolution: No Longer Reproducible
• Affects Version/s: 6.1.30 EE GA3, 6.2.0 CE M4
• Fix Version/s: 6.2.0 CE M4
• Component/s: WCM, WCM > Publication > Asset Publisher
• Labels:
  • community-verifier
• Environment: GNU/Linux 64 bits ; JVM 1.6_u35 ; HSQL ; Chrome 25
• Similar Issues: Show 5 results ; ;

  LPS-31006	Display webcontent with Asset Publisher and single quote in Title
  LPS-19800	Couldn't select related assets if the asset title contains single quote
  LPS-28500	Cannot select a Document in Web Content Portlet when its title contains single quote
  LPS-28422	« the asset could not be found » error when a content's title is modified
  LPS-8429	User that is not allowed to view Web Content, can see it via the Asset Publisher

When a Title of web content contains a special (non-web) quote (e.g. quote from MS Word) in the Title field, the Asset Publisher link doesn't work to view this web content on its display page. It just renders the current page again, without any changes.

[Miguel Angel Júlvez]

Thank you for the report. As part of our community verifier program, I am taking a look at this issue. If it is no longer a concern or you have additional information that will help in troubleshooting it, please let me know.

[Miguel Angel Júlvez]

Fox, thanks for the report. I tried to reproduce this issue on Liferay Portal Milestone 4 build
(available at http://www.liferay.com/community/releases) but could not. Here are the
steps I tried:

• Fresh installation
• Added new web content on control panel with title “MS Word Quotes” (with ms word quotes)
• Added asset publisher to page
• Checked web content published is on the list
• Clicked on web content title
• The web content was showed fine
• Tested with (title, table, abstract, full content display settings) and tested with "Set as the Default Asset Publisher for This Page" and "Asset Link Behavior" setted to "view in a specific portlet"

Please ensure you have a fresh environment with no other issues that may interfere with the bug. If you still experience this issue, please let me know how to reproduce the issue and we can re­visit it. If I cannot reproduce this issue, it cannot be fixed.

Thanks!

[Miguel Angel Júlvez]

No longer reproducible on 6.2 m4