When embedding discourse comments in static pages the blacklist/whitelist css functionality is broken.
The blacklist only seems to work initially if the discussion topic is created during the first user visit to the static page. If you wait for the topic to be created from the rss feed the blacklist/whitelist doesn’t have any effect. Even if you get the correct content in the opening post by visiting the static page first, after an hour the opening post updates itself and reverts to a state like it would have been with empty blacklist/whitelist.
It seems when the system checks for updates to the static page the whitelist/blacklist gets bypassed.
Steps to reproduce:
- Embed Discourse comments in your blog
- Write “p” in settings>embed blacklist selector
- Write a blog post and don’t visit the page
- Wait a few minutes for the comment topic to get created from rss feed
- The opening post has full contents of (every p element in) the page and blacklist doesn’t have any effect
Or
- Embed Discourse comments in your blog
- Write “p” in settings>embed blacklist selector
- Write a blog post and visit the page
- Notice a comment topic with mostly empty first post being created immediately like it should
- Wait an hour
- Watch the topic opening post update itself with again all the content from the static page
edit. updated with more information