Home → Bug Reports →

Parser Error: null (CSI-723)

• Edit

Eric L. Epps

04 Sep, 2015 05:52 PM

Just wanted to provide some more information and a reminder on this 18-month-old, Major bug. It appears to have gone dormant. The description states "When submitting a Velocity Format that imports another Format which contains a macro that calls another macro within a string, the following error message occurs and the form does not submit:"

It's actually any time a # occurs within double-quotes followed by a non-space character. For example, I was using Velocity to generate some CSS code which included a #. Adding the following to an included Velocity Format should also trigger the error:
#set ($randomVar = "#z")

In this particular case, I was able to find a workaround (storing "#" as a variable), but I've had a few other cases recently where I just have to go back to the old way of copy/pasting the macro/code across several different formats.

1. 1 Posted by Ryan Griffith on 04 Sep, 2015 06:47 PM

   

   Hi Eric,

   It's actually any time a # occurs within double-quotes followed by a non-space character. For example, I was using Velocity to generate some CSS code which included a #.

   This would be the intended behavior because Velocity thinks you are attempting to call a defined macro. The same can happen in certain circumstances when using $, generally when trying to generate PHP code. In both cases, your solution of either saving the # as a variable or using $_EscapeTool.h will work because Velocity recognizes this as a literal string during execution.

   Please let me know if you have any questions.

   Thanks!

   • Edit

2. 2 Posted by Eric L. Epps on 16 Sep, 2015 06:56 PM

   

   Sure, I understand why it's doing that, but the bigger issue for me is that the bug remains unresolved and is apparently ignored. I feel it deserves its "Major" priority, as it prevents me from using the #import feature in many cases.

   • Edit

3. 3 Posted by Ryan Griffith on 16 Sep, 2015 07:56 PM

   

   Ah, I see what you are saying now, my apologies Eric.

   I don't have an ETA on a fix for this at the moment, but I've gone ahead and bumped the priority a bit and attached the related issue to this discussion. You can monitor the status of it by coming back to this discussion and looking at the 'state' issue you see attached on the right-hand side. It will change from 'open' to 'closed' once we've made progress on a fix.

   I apologize for the inconvenience! Let me know if there is anything else I can help with at the moment.

   Thanks

   • Edit

4. 4 Posted by Eric L. Epps on 17 Sep, 2015 01:53 PM

   

   Thanks!

   -- 
   Eric L. Epps
   Web Developer
   Sauk Valley Community College
   [email blocked] [mailto:[email blocked]]
   815-835-6322

   • Edit

5. 5 Posted by Ryan Griffith on 17 Sep, 2015 02:32 PM

   

   Not a problem at all, Eric, my apologies for the misunderstanding there.

   Definitely keep and eye on the status of the issue along the right-hand side. It sounds like we may have identified a potential fix, but need to perform quite a bit of testing since such a change could potentially break client formats.

   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

6. Ryan Griffith closed this discussion on 17 Sep, 2015 02:32 PM.