Uploaded image for project: 'Railo'
  1. Railo
  2. RAILO-918

Reverting to 3.1.1.000 after update to 3.1.2.001 breaks CFDUMP

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Rejected
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Steps to Reproduce:
      Hide

      1. Install version 3.1.1.000
      2. Execute update to 3.1.2.001 through the server admin manual update function
      3. Remove the update, revert to version 3.1.1.000
      4. Execute a CFML script with <CFDUMP>

      Show
      1. Install version 3.1.1.000 2. Execute update to 3.1.2.001 through the server admin manual update function 3. Remove the update, revert to version 3.1.1.000 4. Execute a CFML script with <CFDUMP>
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Manually (outside administrator) reinstalling version 3.1.1.000

      Show
      Manually (outside administrator) reinstalling version 3.1.1.000

      Description

      After applying patch update 3.1.2.001 (and probably other versions) to a 3.1.1.000 installation and subsequently removing the update again, the CFDUMP tag no longer works and fails with the error:

      you need at least version [3.1.1.011] to execute this tag

      The Error Occurred in /usr/local/tomcat/lib/railo-server/context/library/tag/Dump.cfc: line 35
      33: <cfargument name="parent" type="component" required="no" hint="the parent cfc custom tag, if there is one">
      34: <cfif server.railo.version LT "3.1.1.011">
      35: <cfthrow message="you need at least version [3.1.1.011] to execute this tag">
      36: </cfif>
      37: </cffunction>

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                micstriit Michael Offner
                Reporter:
                dzgn Tako Bruinsma
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: