Skip to content
This repository has been archived by the owner on Apr 2, 2020. It is now read-only.

Explore best method of handling shortcode display in feed and other restricted contexts #38

Open
davisshaver opened this issue Jul 6, 2015 · 1 comment
Open

Explore best method of handling shortcode display in feed and other restricted contexts #38

davisshaver opened this issue Jul 6, 2015 · 1 comment
Labels
discussion

Comments

@davisshaver
Copy link
Member

Feeds, print, mobile, oh my. The benefit to shortcodes is that we can output conditionally based on context. But as pointed out in #35, we should figure out an abstracted/patterned way to handle this use case.
@davisshaver davisshaver mentioned this issue Jul 6, 2015
Closed
@danielbachhuber
Copy link
Contributor

👍

For the JS-based shortcodes, I thought it would be cool to create an image-based fallback, potentially with a headless browser. But, totally worth exploring what our options could be.

danielbachhuber added a commit that referenced this issue Nov 12, 2015
@danielbachhuber
Convert encoded versions of & back to their normal self for parsing
5d74327 
WordPress encodes `&` to `&` on save, and then encodes any `&` to
`&` on display using `wp_texturize()`. For `parse_url()` to work
properly, we need to make sure ampersands are always `&`
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danielbachhuber @davisshaver