Database and UI doesn’t always reflect state of published content

[paulrobertlloyd]

Currently, if you create/update/delete a post, and the content store throws an error, Indiekit doesn’t reflect this in post data, and shows a post as published; post data does not always reflect the current state of a post in the content store.

As part of ensuring the robustness of Indiekit’s data, consider the following:

Creating a post

1. store.createFile methods should return the file location of the stored file, not true
2. On receipt of a file location, update a post‘s properties:
   • add storeProperties.published with date if successful, false if failed.
   • add storeProperties.url and storeProperties.path
3. Show the post in the UI with the ‘Published’ state.

If an error occurs storing content, a post will have false for store.published. We already show an error message, can now show a ‘Not stored’ status, or similar.

Updating a post

1. store.updateFile methods should return the updated file location of the stored file, not true
2. On receipt of a file location, update a post‘s properties:
   • add storeProperties.updated with date if successful, false if failed.
   • update storeProperties.url and storeProperties.path if relevant

If an error occurs storing content, a post will not have the properties.updated property. We already show an error message but can now show ‘Updates not stored’ status, or similar.

Deleting a post

1. store.deleteFile returns a boolean true (no change)
2. On receipt of true, update a post‘s properties:
   • add storeProperties.deleted with date if successful, false if failed.
   • delete storeProperties.url

If an error occurs storing content, a post will not have a store.deleted property and will show an error message. We already show an error message but can now show ‘Not deleted from store’ status, or similar.

To do

• Update store-plugins to return file location when creating/updating #661
• Update actions to add/update storeProperties.* properties after file storage action
• Update UI to reflect failure states
• Update UI to allow for retry

On these last 2, perhaps it’s less a case of providing explicit statuses, but providing a persist message on any post that has encounter issues while being saved to the content store, with an option to retry the last action?

[paulrobertlloyd]

Work in progress, showing store status in UI: