cc88757e2a
ref https://app.incident.io/ghost/incidents/107 - We have a rare bug that causes the initial `POST` request to create a new post from the editor to be skipped or fail. Subsequent `PUT` requests then fail because there is no post ID, potentially resulting in data loss. The aim of this commit is to start saving revisions of posts in the editor to the browser's localStorage, as a last-ditch option to restore lost work. - Since we don't know where the bug is yet, and to protect against future bugs, we've deliberately avoided depending too heavily on the `lexical-editor` controller or the ember store. We've aimed to create a direct route to the state in the editor, by hooking into the `updateScratch` method (effectively the `onChange` handler for the editor). - The `scheduleSave` function on the new `local-revisions` service is called immediately upon any changes to the state of the lexical editor, which is effectively every keystroke. The service has some logic and timeouts, so it doesn't actually save a revision on every change to the editor. - The "schema" of the datastore is a simple key-value store, where the key is of the format: `post-revision-${postId}-${timestamp}` if the post has an ID, or `post-revision-draft-${timestamp}` for an unsaved draft. There is also an array of all the revisions' keys, which allows us to clear all the revisions without having to loop over every key in localStorage (along with some other conveniences, like filtering). - There is currently no UI for viewing/restoring revisions. In the event that you need to restore a revision, you can access the service in the browser console. You can access all the saved revisions using the `list()` method, which logs all the revisions to the console by title & timestamp. You can then choose a revision to restore, and call `restore(revision_key)`, which will `POST` the revision's data to the server to create a new post. - Since localStorage data is limited to a 5mb quota in most browsers, the service has a mechanism for evicting the oldest revisions once it meets the quota. If a save fails because it would exceed the quota, the `performSave` method will evict the oldest revision, then recursively try to save again. --------- Co-authored-by: Steve Larson <9larsons@gmail.com> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| apps | ||
| ghost | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| LICENSE | ||
| nx.json | ||
| package.json | ||
| PRIVACY.md | ||
| README.md | ||
| SECURITY.md | ||
| yarn.lock | ||
Ghost.org •
Forum •
Docs •
Contributing •
Twitter
The easiest way to get a production instance deployed is with our official Ghost(Pro) managed service. It takes about 2 minutes to launch a new site with worldwide CDN, backups, security and maintenance all done for you.
For most people this ends up being the best value option because of how much time it saves — and 100% of revenue goes to the Ghost Foundation; funding the maintenance and further development of the project itself. So you’ll be supporting open source software and getting a great service!
Quickstart install
If you want to run your own instance of Ghost, in most cases the best way is to use our CLI tool
npm install ghost-cli -g
Then, if installing locally add the local flag to get up and running in under a minute - Local install docs
ghost install local
or on a server run the full install, including automatic SSL setup using LetsEncrypt - Production install docs
ghost install
Check out our official documentation for more information about our recommended hosting stack & properly upgrading Ghost, plus everything you need to develop your own Ghost themes or work with our API.
Contributors & advanced developers
For anyone wishing to contribute to Ghost or to hack/customize core files we recommend following our full development setup guides: Contributor guide • Developer setup
Ghost sponsors
A big thanks to our sponsors and partners who make Ghost possible. If you're interested in sponsoring Ghost and supporting the project, please check out our profile on GitHub sponsors ❤️
Getting help
Everyone can get help and support from a large community of developers over on the Ghost forum. Ghost(Pro) customers have access to 24/7 email support.
To stay up to date with all the latest news and product updates, make sure you subscribe to our changelog newsletter — or follow us on Twitter, if you prefer your updates bite-sized and facetious. 🎷🐢
Copyright & license
Copyright (c) 2013-2024 Ghost Foundation - Released under the MIT license. Ghost and the Ghost Logo are trademarks of Ghost Foundation Ltd. Please see our trademark policy for info on acceptable usage.