Skip to content
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

Global and Site SettingsCustom Error #3561

Open
jtherrien-accuraty opened this issue Jan 22, 2025 · 1 comment
Open

Global and Site SettingsCustom Error #3561

jtherrien-accuraty opened this issue Jan 22, 2025 · 1 comment
Assignees

Comments

@jtherrien-accuraty
Copy link

2sxc Version: 19.03
DNN Version: 9.13.07

The settings stack on the global and site levels still isn't working for custom settings after the recent LTS update. It does now automatically create the SettingsCustom content type, and allows you to add field definitions.

The issues start when you try to add data to the custom fields. After saving the record the Global and/or Site panel doesn't have the badge indicating that it has records, and if you try to edit the setting values they are completely blank. Each of those are actually being saved as separate records in the SettingsCustom content type that get automatically created. It isn't until you close the settings completely and reopen them that the badges show up giving you the current record count.

When the badges are there if you have only one item and try to edit it you get the "400 bad request object not set to an instance of an object" popup:
Image

If you have more than 1 you instead get a popup saying "Found too many settings for SettingsCustom":
Image

Finally, I have not been able to get those settings to show in the "Analyze Combined Settings".

@iJungleboy iJungleboy self-assigned this Jan 23, 2025
@iJungleboy
Copy link
Contributor

A quick analysis

This was accidentally introduced as we changed everything in the UI to support Ctrl+Click / Shift+Click, as the icons now have real links on them.

In some cases, it need to do some work first (such as create the content-type) and this preflight seems to cause trouble.

We'll try to fix in a few days, but will wait just a bit in case the LTS has any other bugs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants