My site is down after a simple update

Issues
1

After updating a simple link on my navbar, my website went down and is now showing the error: “Application error: a client-side exception has occurred (see the browser console for more information).”

Mona 2025-06-15 at 22.22.56@2x
Mona 2025-06-15 at 22.22.56@2x1920×1014 132 KB

Does someone what could be causing this. I am using the visual editor without touching the code.
Thanks!

Public link: managerhacks.io

2

Hello @simona_dimitrova, are you using a custom app host? Because it seems like the error might be coming from there. Also, please share your project id for further investigation.

3

We investigated further and its actually an issue on our end. We are working on a fix.

4

Thanks, Sarah! I just went to look for the custom app host (I had no idea what that is ;)) and indeed, I am not using a custom app host. I hope you find a solution soon! Thanks

5

Hi! I have the same problem - on this site: https://kramar-paluan.plasmic.run/.

6

Hello, the issue should now be fixed for everyone.

7

Hi, this is still happening for us:

Error: PLASMIC: Failed to load chunk-XFXOZO3S.js: Error: Unknown module @plasmicapp/host/registerFunction
    at Registry.load (_app-2c1ef7f34d42dc30.js:1:26932)
    at Object.getComponent (_app-2c1ef7f34d42dc30.js:1:68400)
    at be (_app-2c1ef7f34d42dc30.js:1:72007)
    at we (_app-2c1ef7f34d42dc30.js:1:72912)
    at oo (react-dom.production.min.js:157:137)
    at Bo (react-dom.production.min.js:180:154)
    at Ki (react-dom.production.min.js:269:343)
    at Lu (react-dom.production.min.js:250:347)
    at Nu (react-dom.production.min.js:250:278)
    at Pu (react-dom.production.min.js:250:138)
    at bu (react-dom.production.min.js:243:163)
    at react-dom.production.min.js:123:115
    at scheduler.production.min.js:18:343
    at Ql (react-dom.production.min.js:122:325)
    at Yl (react-dom.production.min.js:123:61)
    at Kl (react-dom.production.min.js:122:428)
    at hu (react-dom.production.min.js:237:203)
    at To (react-dom.production.min.js:170:408)
    at Object.onDataFetched (_app-2c1ef7f34d42dc30.js:1:56462)
    at _app-2c1ef7f34d42dc30.js:1:70238

We’re still on an older version @plasmicapp/loader-nextjs, version 1.0.415.

The same issue affects running the website locally, which prevents us from doing any work that involves a plasmic page.

Upgrading to @plasmicapp/loader-nextjs to 1.0.431 fixes the problem. However, I am unsure of what the changes are between versions, and whether there are any other hidden issues by upgrading the version.

How would you recommend that we fix it?

Thanks

8

Hey @steve_1234, you can safely upgrade the loader version.

In the meantime, we are also looking into reverting any change that may have caused this.

1 Like
9

We found the root cause of the issue as well and have deployed a fix. You shouldn’t need to update your loader version anymore. Simply changing your project and re-publishing/generating should also fix the issue.

10

Thanks. I’ve upgraded the loader version and deployed the site. Everything is working as expected at the moment

1 Like