New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: Content warnings #36
Comments
Alright, I think a sort of semi-automated CW (“new blog post” or something, maybe based on tags or similar) is already possible through the current filter mechanism (but would require some custom PHP). Let me get back to you with a code example once I’ve figured this out. The alternative would be an extra text field for a completely “manual” CW. I was hoping to eventually rework the meta box anyway, but I might be able to something even before that happens. |
OK, so it is possible to add the following to, e.g., a
Unfortunately, it doesn't look like I can add an optional second argument ( |
OK, so with that new parameter (not up on WP.org, yet!) you should be able to do something like:
And then you could either modify Not sure when I'll push to WP.org, maybe in a week or so. Could be in the future I add a CW setting, but it will probably be limited to static text (which you could then override using the filter). |
thanks! |
Thank you! |
On some Mastodon instances it is considered polite to add a content warning for bot-posted toots like these. I would love to be able to have a configurable content warning, ideally one which allowed the CW to include the title of the Wordpress post.
Thanks for considering.
The text was updated successfully, but these errors were encountered: