FOG (RC12) Settings Exit Types (legacy, efi) will not be saved after change

[x23piracy]

@sebastian-roth well, i described why i think that is a bug, there is an update button that implies that it will save changes but it doesn’t, then i found out that i can change the desired values at another place where also is a update button, that update button will save the values.

For me thats personally solved, for FOG from my opinion it’s a bug.

Regards X23

[Tom Elliott]

@x23piracy I’m unable to replicate the issue using working, and dev-branch. It really seems somebody pressed enter from a text field. I’m not saying you aren’t having the problem, I just don’t have a way of seeing it.

[Sebastian Roth]

@x23piracy Which browser do you use? Tried different ones yet?

[x23piracy]

@sebastian-roth i am using firefox, i also tried chrome now and it also does not save the options. i won’t try edge and ie is removed on my system for freedom

[x23piracy]

Hi,

here is a video of the behaviour, have a look yourself:

https://youtu.be/0_UrpJq5GS8

Regards X23

[Tom Elliott]

You’re modifying the wrong fields. Your “expand all” should not have anything directly editable underneath it.

It should fall under FOG Boot Settings:

Do you have a “tab” called “FOG Boot Settings”? If so, can you try editing from there?

[Tom Elliott]

Basically it seems you have a corrected globalSettings table.

[Tom Elliott]

I’ve moved this posting to fog problems as this is not something I can address with a patch or anything. It is quite literally a problem with the database.

Can you confirm that you have the tab: FOG Boot Settings? If you do, does this same information appear there?

I might need to remote in to take a look.

[x23piracy]

@tom-elliott said in FOG (RC12) Settings Exit Types (legacy, efi) will not be saved after change:

Do you have a “tab” called “FOG Boot Settings”? If so, can you try editing from there?

Yes i have:

we can do the remote in when ever you have time, gimme a ping.

[Tom Elliott]

Please try this SQL statement:

UPDATE `globalSettings` SET `settingCategory`='FOG Boot Settings' WHERE `settingKey` IN ('FOG_ADVANCED_MENU_LOGIN','FOG_EFI_BOOT_EXIT_TYPE','FOG_PXE_MENU_TIMEOUT','FOG_PXE_MENU_HIDDEN','FOG_PXE_ADVANCED','FOG_KEY_SEQUENCE','FOG_NO_MENU','FOG_BOOT_EXIT_TYPE','FOG_PXE_HIDDENMENU_TIMEOUT','FOG_IPXE_MAIN_COLOURS','FOG_IPXE_MAIN_CPAIRS','FOG_IPXE_MAIN_FALLBACK_CPAIRS','FOG_IPXE_VALID_HOST_COLOURS','FOG_IPXE_INVALID_HOST_COLOURS','FOG_IPXE_HOST_CPAIRS','FOG_IPXE_BG_FILE');

This should reset all those items to use the proper setting category. The problem with the ajax and the place you’re currently updating is because those fields are appearing outside of the “<form>” element. So when you click update, nothing is actually being sent to be updated. This should address those issues.

[x23piracy]

@tom-elliott Hi Tom, sorry for the late answer, yes that sql statement solved my issue. Solved!

UPDATE globalSettings
SET settingCategory=‘FOG Boot Settings’
WHERE settingKey
IN (‘FOG_ADVANCED_MENU_LOGIN’,‘FOG_EFI_BOOT_EXIT_TYPE’,‘FOG_PXE_MENU_TIMEOUT’,‘FOG_PXE_MENU_HIDDEN’,‘FOG_PXE_ADVANCED’,‘FOG_KEY_SEQUENCE’,‘FOG_NO_MENU’,‘FOG_BOOT_EXIT_TYPE’,‘FOG_PXE_HIDDENMENU_TIMEOUT’,‘FOG_IPXE_MAIN_COLOURS’,‘FOG_IPXE_MAIN_CPAIRS’,‘FOG_IPXE_MAIN_FALLBACK_CPAIRS’,‘FOG_IPXE_VALID_HOST_COLOURS’,‘FOG_IPXE_INVALID_HOST_COLOURS’,‘FOG_IPXE_HOST_CPAIRS’,‘FOG_IPXE_BG_FILE’);

@george1421 helped out with sorting the command