Skip to main content
Solved

Can't save our front page edits. Any ideas?


FMEEvangelist

For about a month now, we’ve been unable to save any edits made to our community’s front page. We can use the customize button and make edits, but clicking publish just does nothing.

When I turn on debugging tools, I can see two errors:

"POST https://community.safe.com/branding/updateWidgets 403 (Forbidden)"

"Uncaught (in promise) Error: Request failed with status code 403"

 

Some more facts:

  • This happens to both my colleague and I, on our own computers.
  • We both have administrator privileges.
  • We can edit topic landing pages and custom pages without problem.
  • The widget type doesn’t matter. Whatever edits we make, publish fails.
  • We’ve tried:
    • Logging out/in
    • Restarting the browser
    • Using a different browser (tried Chrome, Edge, and Firefox)
    • Using an incognito window
    • Turning off all browser plugins
  • We haven’t changed any custom CSS recently, besides which, that should affect the whole site.
  • I don’t believe we’ve changed any custom code recently either.
  • There are no other obvious problems with the site.

In short: everything is working fine, except the Publish button doesn’t work on the home page.

Gainsight support seems to be at a loss, so I wondered if anyone here had experienced this sort of problem before? Or maybe you have some suggestions to try?

Any ideas would be appreciated. We really need to be able to make some edits!

Thanks

Mark

Best answer by FMEEvangelist

It turns out the problem was with an Alert function in one of the HTML widgets we have on the front page. 

“Unfortunately those 'alert' functions are triggering a security measure on our platform that can't be bypassed. Once those 'alert' functions are deleted, you can publish content just fine.“

So, the lesson for today is to avoid using the Alert command in HTML widget Javascript!

A big thank you to the support team at Gainsight for figuring this out 👍🏻

View original

Kenneth R
Forum|alt.badge.img+5
  • Gainsight Community Manager
  • March 4, 2025

Hey ​@FMEEvangelist - great that you’re already in touch with Support about this.  It’s not something I’ve heard of before so suspect it’s related to your instance.  Hope it gets resolved soon!


FMEEvangelist

It turns out the problem was with an Alert function in one of the HTML widgets we have on the front page. 

“Unfortunately those 'alert' functions are triggering a security measure on our platform that can't be bypassed. Once those 'alert' functions are deleted, you can publish content just fine.“

So, the lesson for today is to avoid using the Alert command in HTML widget Javascript!

A big thank you to the support team at Gainsight for figuring this out 👍🏻


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings