Bugzilla – Bug 1047249
Regression: Using Vibe markup to create a link to a new (nonexisting) entry seems to be broken
Last modified: 2018-01-24 20:02:23 UTC
Vibe is throwing an error when using Vibe markup ("[[entry title]]"-syntax) under 4.0.3 to create a link to new entry in the same folder. Steps to reproduce: 1. create a folder in Vibe - no matter which type of folder 2. create an entry inside that folder with title "entry 1" 3. in the description field use the wiki syntax to add a link to another entry in the same folder by typing "[[entry 2]]" into the description field 4. save entry 1 5. open/view entry 1 and click on the link to entry 2 which is being created and rendered by Vibe 6. Vibe will notify you that "[The requested page does not exist yet.]" giving you a "Create Page" button to create entry 2 (until here everything is working as designed) 7. Clicking the "Create Page" button is throwing an error and "entry 2" isn't been created: == HTTP Status 400 - Required string parameter 'p_name' is not present type Status report message Required string parameter 'p_name' is not present description The request sent by the client was syntactically incorrect. == If the target entry "entry 2" is already existing then markup link are working fine and as designed. This used to work fine before. Even under 4.0.2 it is working fine. Tested and reproduced on 5 different Vibe installations, some of them customer sites. Customers haven't been notified by us about this bug, yet, but we cannot tell when they will come along this bug themselves. Please fix this asap since this functionality is widely used. We'll wait a few days before some of customers will open an SR on this.
One customer came back to us today: Customer is running Vibe 4.0.2 and needs to upgrade to 4.0.3 urgently, since links to anchors inside the description field are being deleted by the OWASP filter under 4.0.2. This customer is using anchors AND Vibe markup ("[[entry title]]") as one of the main tools and features when publishing and providing content on their intranet portal. There's an important workspace in their Vibe system that is going live productively in 1.5 weeks. Customer is a world leading manufacturer and supplier of systems for commercial vehicles of a certain type - so this bug has high services priority! Customer will open an SR in the next days, but I just wanted to let you know that this customer will definitely need an FTF in a week or so. Customer is not amused that in each and every minor version of Vibe something that has been working before is broken or broken again. HTH Cheers
By the way: This bug already made it into the Novell forums (wasn't me ;-) ): https://forums.novell.com/showthread.php?t=504761
This is now fixed: 4.0.4 (trunk): svn rev 23874 4.0.3 FTF: svn rev 23875 The fix is in the ssf JSPs: webapps/ssf/WEB-INF/jsp/entry/view_no_title_entry.jsp
This fix is in the Vibe OnPrem 4.0.4 build 20170920202857. open source project revision 23878, and closed source project revision 8221.
This fix is in the Vibe OnPrem 4.0.3 build 20170920212321. open source project revision 23879, and closed source project revision 8220.
We checked out the JSP from SVN and did some tests. Seems to work fine for us! Thanks a lot, David. Erik
Verified: Vibe_OnPrem/enterprise/4.0.4/20170922202845