-
Notifications
You must be signed in to change notification settings - Fork 41
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
Share link that used to work now doesn't with an error "entity too large" #174
Comments
You can increase the size using this config option, the default is 200kB terriajs-server/serverconfig.json.example Line 171 in 2c48621
Every time you click the "share button", if changes have been made to the map, then a new share link is generated on top of the existing share link. This sometimes leads to very large share links, if you keep creating new links on top of each other. A share link basically contains all user generated changes to TerriaJS state, this can become very large, especially if you are adding 100s (or 1000s) of datasets to the workbench. To compound this, if you are using the story feature, each story scene is basically a new share link. We don't have an easy way to clean up large share links, you can manually do it by inspecting network requests and posting cleaned share JSON back to TerriaJS server (at the |
The share link you provided doesn't seem to have data in it. If you were getting |
I think the main issue here, is that TerriaJS-server seems to still return a shareKey, even if the share JSON isn't saved to S3 due to the |
Error captured below.
Share URL is this: https://maps.digitalearthpacific.org/#share=s-se4QkfmUsarYesLIzoXr
The text was updated successfully, but these errors were encountered: