Finding Format tied to velocityTransform number

chaoaj's Avatar

chaoaj

07 Aug, 2012 01:32 PM

In the cascade log I'm getting an error that refers to a velocityTransform-1344337261457 how do I crossreference this into a format so I can examine the line #'s the error is referring to?

  1. Support Staff 2 Posted by Ryan Griffith on 07 Aug, 2012 07:44 PM

    Ryan Griffith's Avatar

    Hi chaoaj,

    Currently there is no easy way to determine this; however, sometimes there may be clues within the error message that might be able to point you in a direction such as a variable name or xPath statement. You could also ask that your editors report seeing any errors when a page renders and try to track things down that way.

    I've logged a potential improvement for a future version of Cascade to include additional information with these Velocity error messages to make debugging easier. Feel free to use the link I have provided to track if the improvement has been implemented in a future release of Cascade.

    Please let us know if you have any questions.

    Thanks.

  2. Support Staff 3 Posted by Ryan Griffith on 21 Aug, 2012 01:42 PM

    Ryan Griffith's Avatar

    Hi Alvin,

    Just wanted to follow up to see if you had a chance to view my recent comment. Were you able to find the Format that was causing the errors?

    Please let us know if you have any questions.

    Thanks.

  3. 4 Posted by chaoaj on 21 Aug, 2012 08:10 PM

    chaoaj's Avatar

    Ryan,

    Thanks, I was able to find the format by isolating the publish job and
    finding the lines of code in the error log, but still wish there were a
    format label in the error log. Thanks for the idea submission you can
    close this one out.

    Regards,
    @lvin
    ------------------------
    Alvin Chao ­ IT Web
    JMU - MSC 5734 - Massanutten Hall 293
    Harrisonburg, VA 22807
    540-568-6206
    [email blocked]
    http://educ.jmu.edu/~chaoaj

  4. Ryan Griffith closed this discussion on 22 Aug, 2012 12:50 PM.

Comments are currently closed for this discussion. You can start a new one.