Closed Amoeba00 closed 1 year ago
You cannot move preset to any folder excet the folder where all other files are. Because preset tries to import module from $PSScriptRoot folder.
Agreed - I'm then suggesting that you could specify that in the documentation since folks who customize their own script will most likely just move that script item and download the latest version of the script. At the very least - the pop-up box could also be used to remind users to make sure the imported script is in the sophia folder and no where else - since the message about needing to update sophia would be incorrect at that point. Just a thought. Thanks for the work on this project. Please keep it up!
I'm working 6.5.0 already. :)
Prerequisites
Steps to reproduce
Using the wrapper application and importing a preset:
If the preset is NOT in the default Sophia Script folder (where the default Sophia.ps1 script resides), it won't load and instead generate a message about a new version of Sophia Script being found.
Moving the same script to that default folder, will result in proper preset loading and expected behavior.
Steps to Reproduce: Start Wrapper - load default preset from sophia folder - (optional: make changes) - export preset to folder outside of the default - load that preset.
You will then see message about new version and pressing No/Cancel - results with empty preset (yes results in expected browser launch behavior but wrapper still "broken"). Move that same preset to the original default folder and import it. No issues.
Note: If it helps, last time I used this was on a Win10 machine with Sophia v5.14.3 and Wrapper v2.5.7 - with no issues importing from different folder.
Windows Version
Win 11 Pro 22H2 (22621.1555)
Sophia Script version
6.4.4