New client some snapins doesn't work, ok with legacy client
-
@Tom-Elliott said:
I have to double check, but I’m pretty sure I added the same type of code sanitization to the run with, file, run with args fields as I do with printers. I won’t solve this until I am certain. This does not mean all bad entries from before will automatically work, but it should be fixed after updating.
Hi Tom
I think it isn’t solved.
I don’t know if it’s like in:
https://forums.fogproject.org/topic/5931/rev-4932-snapins-parameters-with-in-command-not-correct-in-database/9But in advanced pxe menu, when I write what you can see in screen captures, escape characters and accentued french characters are badly saved in database tables.
I think all these symptoms are linked, and caused by bad locales ? (my server is UTF8) or by escaped characters interpreted by PHP ?
Thanks again for your work.
Screen captures are from rev 5273In FOG Gui:
In database:
-
Bad screen capture in previous post
In database:
-
@Claude-Girard what’s the advanced file actually show? Does it display with the escaped code, or as the actual characters.
-
@Tom-Elliott said:
@Claude-Girard what’s the advanced file actually show? Does it display with the escaped code, or as the actual characters.
As you can see, && become && in database, d’ become d'
If I modify directly in database and save it, in FOG Gui all seems ok, characters are ok.
But if I save PXE Menu from Gui, after that in database characters are with escaped code again
-
@Claude-Girard I’m still confused. What does the advanced menu have to do with snapins?
-
@Claude-Girard Beyond that, what does the advanced menu show when you go to it in browser?
-
@Tom-Elliott said:
@Claude-Girard I’m still confused. What does the advanced menu have to do with snapins?
Nothing to do with snapins, but I understood when you reopened issue, that it was a similar problem than :
https://forums.fogproject.org/topic/5931/rev-4932-snapins-parameters-with-in-command-not-correct-in-database/9Maybe I am wrong but isn’t it the same problem when you say:
“I’m pretty sure I added the same type of code sanitization to the run with, file, run with args fields as I do with printers.” -
@Claude-Girard I found and believe I have fixed the issue (for all items fingers crossed).
I just pushed it to the wild too.
-
@Tom-Elliott said:
@Claude-Girard Beyond that, what does the advanced menu show when you go to it in browser?
It shows escaped codes
-
@Tom-Elliott said:
@Claude-Girard I found and believe I have fixed the issue (for all items fingers crossed).
I just pushed it to the wild too.
Thank you and sorry for confusing you, maybe my english is too bad
-
I wasn’t confused about the language, I was confused what Advanced menu had to do with snapins, but ultimately it didn’t matter really. I understood what you were getting at and I was able to make the corrects to ensure things operated properly. Hopefully it’s much better for all things.
-
@Tom-Elliott said:
I wasn’t confused about the language, I was confused what Advanced menu had to do with snapins, but ultimately it didn’t matter really. I understood what you were getting at and I was able to make the corrects to ensure things operated properly. Hopefully it’s much better for all things.
Yes but better english = better explanations !!!
Did you push these corrects on github ?
I just upgraded rev 5283 and i don’t notice any change. -
@Claude-Girard v0.9.6 is released, and this includes the snapin fix for the problem you originally posted on. (https://news.fogproject.org/client-v0-9-6/ )
-
@Jbob said:
@Claude-Girard v0.9.6 is released, and this includes the snapin fix for the problem you originally posted on. (https://news.fogproject.org/client-v0-9-6/ )
Thank you.
I just tested and for me it’s ok.
You can mark this thread solved, but I will open a new one for the others problems, discussed with Tom, they are’nt solved.
And I found a snapin bug again, but not due to client.Thanks again