I’ve just got to my desk this morning and have reports from users that all of our HTML pages are displaying error
“Something went wrong: Failed to get parentOrigin: Request failed with status code 404”
We run on the Cloud version so im assuming that this is relating to an update pushed recently? Has anyone else seen this issue? I have also raised a support ticket, but thought I would check here to see if anyone has a quick fix while I wait for a response from support
Our documentation for the HTML page feature on developer.seatable.com previously showed examples of including the seatable-html-page-sdk JS library from a CDN like this:
This caused the already generated pages with a <script> tag like this to break after the latest release of the SDK a few hours ago since the browser would always download the latest version of the JS library.
HTML pages used for production purposes should have used a pinned tag like 0.0.13 from the get-go. We have already updated our documentation to reflect this (see Low-code quickstart - SeaTable Developer Manual, beware of some caching issues on GitHub’s end):
<!-- Using the "latest" tag is not recommended for production - use a pinned version to ensure stability -->
<script src="https://unpkg.com/seatable-html-page-sdk@0.0.13/dist/index.min.js"></script>
As for the remediation:
Our developers are already working on manually resetting the latest tag to point to version 0.0.13 to ensure that existing HTML pages with a latest tag are working as expected.
EDIT: We’ll let you know in this thread once this is done.