Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-24118

Basefile editor doesn't show escaped XML characters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Endpoint (Commercial)
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • Asterisk Version:
      18.9
    • Distro Version:
      12.7.8-2302-1.sng7
    • Distro:
      FreePBX Distro

      Description

      EPM v16.0.77.1

      When editing the Basefile for our Cisco phones, EPM does not display values with escaped XML characters correctly. I'm trying to get this exact line added to the basefile, as-is:

      
      <Caller_ID_Map_1_>(&lt;:9,&gt;xxxxxxxxxxx.)</Caller_ID_Map_1_>
      

      If I add an entry with Parameter="Caller_ID_Map_1_" Value="(& lt;:9,& gt;xxxxxxxxxxx.)" (without the spaces; see EDIT at the bottom), then EPM will add this line correctly (verified by looking at the generated config files on disk). However, EPM will display the following:

      
      <Caller_ID_Map_1_>(<:9,>xxxxxxxxxxx.)</Caller_ID_Map_1_>
      

      Even worse, if I click on that entry to edit it, the input for Value populates with "(<:9,>xxxxxxxxxxx.)", so if I save it again then EPM actually saves "(<:9,>xxxxxxxxxxx.)" instead of the escaped version. This will look the exact same when viewed in EPM, so the only way to verify if the correct (escaped) version is saved is to look at the generated config files on disk (or "View Source" in a browser).

      EPM should display the actual value that it has saved, so that What You See Is What You Get.

      EDIT: Apparently this bug tracker also has issues with unwanted escaping of XML characters 🤦‍♂️

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                alexp1 alexp1
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.