-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
policies spelt wrong (twice) and "# Remove custom welcomeBannerImageFileName" has a bug if welcomeDialog is false. #134
Comments
Thanks for the heads-up, @Honestpuck; I'll take a look. |
While I did find two misspellings, I was unable to replicate the removal error with SYM
|
Did you set |
The only change I made was: (I want the banner image in the main SYM dialog.) |
It popped up again today. I will see if I can replicate exactly what
happened. I think it has something to do with the images when you have
welcomeDialog set to false. I'm back working on SYM full time now.
…On Wed, Jan 24, 2024 at 12:15 AM Dan K. Snelson ***@***.***> wrote:
@Honestpuck <https://github.com/Honestpuck>:
The only change I made was:
welcomeDialog="${6:-"false"}"
—
Reply to this email directly, view it on GitHub
<#134 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZIRBOF265GPZJ62CVRCALYP6ZXPAVCNFSM6AAAAABCGNLD4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGAZTQMRSGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Addressed in SYM |
Describe the bug
policies is spelt 'polcies' in two strings. Do a search and replace :)
If you are running with
welcomeDialog
set tofalse
the script attempts to remove a non-existentwelcomeBannerImageFileName
and failsThis has output of:
The problem is that when the variable is empty the -e test is testing for the existence of
var/tmp/
which is true but then therm
command attempts to remove/var/tmp
and fails, giving the error seen.To Reproduce
Set "welcomeDialog" to false
Expected behavior
The routine to remove the file would not run.
Environment (please complete the following information):
Additional context
This code works:
It would also work if you changed the
-e
(does it exist) to-f
(is it a file) but I prefer the more explicit check.The text was updated successfully, but these errors were encountered: