[IGN-15475] Unable to save changes to Gateway config

[Thorbjorn_Knudsen]

As you can see in the title of the topic, the gateway settings “save changes“ is greyed out even if I try to change something in on the page.

This is an backup from 8.1.51 to 8.3.2, cannot change anything about the backup scheduling or change the homepage redirect URL or anything else, the save changes button is still greyed out.

[cmallonee]

Titles are nowhere near as helpful as screenshots; could you please include some screenshots of the page where you are encountering this behavior? Most importantly, the screenshots should include the state of the page and Save Changes button on load (when you first visit the page or after a refresh) and after you’ve changed a value on the page/form.

At this time, there are only a couple of things which drive the enabled state of the Save Changes buttons throughout the Gateway:

1. Required fields with no values. Not a factor here, because this page has no required fields (aside from System Name).
2. The current state of the form data does not differ from the back-end (no changes have been made). Unlikely, if you are indeed making changes.

[Thorbjorn_Knudsen]

Here are some images without any changes aka just opening the page

Here is 1 image where I made a change and as you can see the save changes button is still greyed out:

[cmallonee]

I’d be interested to see if there are any errors in the browser console. There will be multiple instances which declare an incorrect use of the <label> component, but anything else would be of interest. You might also want to search your logs for error and warning occurrences of “system-properties”; if that resource is not serializing properly, the page/form may not recognize changes, although I would question how it would be loading any values which are not the default.

You’ll very likely want to contact our Support team, as they’ll be able to dedicate more time to resolving this than can be afforded here on the forums.

[Melby_Miraval]

I am having the same issue. Were you able to figure out what the problem was?

[cmallonee]

It doesn’t appear that the OP reached out to Support, so I have no further guidance.

• Do you happen to see any logging within the browser console or Gateway logs when this page is exhibiting these behaviors?
• Do you have another Gateway on this same host but another port?
• Are you seeing this behavior on the same page, or a different page?

[Melby_Miraval]

1. No
2. No
3. I am seeing this behavior in http://localhost:8088/app/platform/system/gateway/settings

[cmallonee]

Could you include a screenshot of the Gateway Scripting Project field?

[Melby_Miraval]

[Melby_Miraval]

I reached out to support and they were able to figure out that the problem was the invalid value in the To Address field in the Error Reporting settings. The field had an invalid value of 25. Removing the value allowed me to save changes. A red overlay on invalid values would be helpful! Anyhow, I am not sure how that field ended up with that value, but it somehow got added in my 8.1 gateway. With that invalid value, I can Save Changes in the 8.1 version but not in the 8.3 version.

[cmallonee]

There seem to be two issues at play here:

1. A state de-synchronization between the primary and backup configurations for singleton resource pages. If you have a backup configuration in place and you’re seeing the Save Changes button remain disabled when it should be enabled, swap to the backup config and the button will immediately reflect that there are unsaved changes and will become enabled.
2. At least one field doesn’t seem to render the expected invalid warning state when loading invalid values from the back-end. The form recognizes the field is invalid, but not displaying the invalid state obviously makes it impossible for a user to determine why they can’t save any changes.

We’ve opened tickets for both scenarios. The first will be fixed within 8.3.5, and I hope to get to the second within that version as well.