Uploaded image for project: 'Lucee Development'
  1. LDEV-1076

Exception TagContext template paths have changed from absolute to relative

    Details

    • Type: Bug
    • Status: Deployed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.5.4.017
    • Fix Version/s: 4.5.5.000
    • Labels:

      Description

      In the current stable release 4.5.4.017, when an exception is thrown the template file paths shown for each item in the TagContext array have changed from absolute to relative.

      Test case

      currentAbsoluteFilePath = GetCanonicalPath( GetCurrentTemplatePath() ); //e.g. C:\path\thisfile.cfm
      dump( var=currentAbsoluteFilePath, label="Current absolute file path" );
      // throw an exception
      try
      	x=nonExistantVariable;
      catch( any exception ){
      	dump( var=exception.TagContext[ 1 ].template, label="Exception TagContext file path" );
      	dump( var=( exception.TagContext[ 1 ].template IS currentAbsoluteFilePath ), label="The paths are both absolute" );
      }
      

      Expected value for exception.TagContext[ 1 ].template : C:\context\path\thisfile.cfm
      Actual value: /path/thisfile.cfm

      This breaks TestBox which expects an absolute template path when reporting failed tests.

      I expect this is related to https://luceeserver.atlassian.net/browse/LDEV-1036

      Workaround

      Rolling back to 4.5.3.020 fixes the issue.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                michaeloffner Michael Offner
                Reporter:
                julianhalliwell Julian Halliwell
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: