• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Snapin Pack Arguments double-quotes problem

    Scheduled Pinned Locked Moved Unsolved FOG Problems
    3 Posts 2 Posters 75 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      Infojoe
      last edited by

      Hello everyone !
      When snapin pack management page is loaded, double quotes in snapin arguments are not well escaped and only ‘/c’ remains (batch script) instead of ‘/c “[FOG_SNAPIN_PATH]\drivers.cmd”’. It looks like this :
      c217732c-3247-4c0e-8bf9-f020fcd454ec-image.png
      In page code, it looks like this :
      <input type=“text” class=“snapinrwa-input cmdlet2 form-control” name=“rwa” id=“snaprwa” value=“/c " [fog_snapin_path]=”" drivers.cmd"“=”">

      If I update snapin without full putting the whole again code, only “/c” remains.

      Am I the only one with this problem ?

      Thank you for the great job on this software anyway 🙂

      1 Reply Last reply Reply Quote 0
      • S
        slackenberg
        last edited by

        The same thing is happening on my end as well.

        steps to reproduce:

        • create new snap pack
        • select powershell script template
        • notice the string in Snapin Pack Arguments that includes quotes
          **-ExecutionPolicy Bypass -File "[FOG_SNAPIN_PATH]\MyScript.ps1"
        • attach zip file
        • click add and wait for the snap pack tosave
        • go back to view the snap pack and see that anything including and after the first double quote vanishes.
          ** powershell.exe -ExecutionPolicy Bypass -File

        Fog server OS is Alma 9.7
        Fog == 1.5.10.1733

        fog-sp-2.png fog-sp-1.png

        1 Reply Last reply Reply Quote 0
        • S
          slackenberg
          last edited by

          Looking at my other Fog server at home, it does not appear to have the same issue. I can dig deeper here but on the surface, the major difference is that the home machine is Ubuntu 24.04 with fog version 1.5.10.1650

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          139

          Online

          12.4k

          Users

          17.5k

          Topics

          156.0k

          Posts
          Copyright © 2012-2025 FOG Project