You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a post is saved, we store a couple pieces of metadata:
documentclouddocuments stores all the shortcode attributes. I don't know what it's used for.
wide_assets set to true|false to hint to the template that the post contains, well, wide assets. Several StateImpact sites respond to this hint according to Use oEmbed #16 (comment) and a Hangout conversation with @eyeseast
We have to make at least one change: both pieces of metadata are stored as hashes keyed by document slug. But now that we support notes – which are children of documents and thus whose URLs contain the document slug – we can have two embedded resources on the same post with the same hash key.
My recommendation:
Determine if documentclouddocuments post meta is necessary (@eyeseast?) and if not, remove it
If resource is a note, include note ID as part of hash key to distinguish from documents.
When a post is saved, we store a couple pieces of metadata:
documentclouddocumentsstores all the shortcode attributes. I don't know what it's used for.wide_assetsset totrue|falseto hint to the template that the post contains, well, wide assets. Several StateImpact sites respond to this hint according to Use oEmbed #16 (comment) and a Hangout conversation with @eyeseastWe have to make at least one change: both pieces of metadata are stored as hashes keyed by document slug. But now that we support notes – which are children of documents and thus whose URLs contain the document slug – we can have two embedded resources on the same post with the same hash key.
My recommendation:
documentclouddocumentspost meta is necessary (@eyeseast?) and if not, remove it