WordPress should not display private posts in public RSS feeds, except for those privileged users you mentioned, and even they need to be viewing the feed in a browser where they’ve logged in to your site. If your WordPress does display private posts in the feed for everybody, there’s something wrong; perhaps a misbehaving plugin or theme.
[Since version 4.1.6](https://wordpress.org/support/topic/how-to-disable-mshots-service/#post-12939728), Akismet has a filter which [allows you to turn off the site preview popups](https://wordpress.org/support/topic/how-to-disable-mshots-service/#post-12944077) (”mShots”):
function disable_akismet_mshots( $value ) {
return false;
}
add_filter( ’akismet_enable_mshots’, ’disable_akismet_mshots’ );
Happy to see the plugin get a new lease on life from an active and engaged developer. I only use a small portion of the features (suggested local tags), but this features alone makes it one of the most useful plugins for me.
Thanks for keeping Simple Tags alive!
Simple Tags is great in picking exact local tag matches from the post text, but with Finnish (and probably some other languages as well), inflection often causes it to miss relevant suggestions (from Local tags). For instance, when using the inessive case ”Helsingissä” in the post, Simple Tags won’t suggest (previously added local tag) ”Helsinki”.
A fuzzy matching feature would help here.
While Simple Tags’ future was in limbo, I tested some other plugins, and one of them (maybe Smart Tag Insert) had such a feature: it showed related tags using some kind of fuzzy matching. I have no idea how difficult this feature would be to incorporate into Simple Tags though.
I know I can show all tags with the ”Click tags” feature, but with close to 2000 pre-existing tags, the full list is quite unwieldy.
The release of WordPress 5.0 brought up an issue with the use of gutenberg_parse_blocks() in aesop.php: apparently for WP versions with Gutenberg integrated, parse_blocks() should be used instead of gutenberg_parse_blocks(), otherwise a fatal error occurs when Gutenberg tries to redefine WP_Block_Parser_Block.
You can reproduce this even with Twenty Nineteen, by adding <?php $blocks = gutenberg_parse_blocks( $post->post_content ); ?> to header.php.
Replacing gutenberg_parse_blocks() calls with parse_blocks() seems to work around the issue (for me at least), and the issue here, if any, is apparently just one of confusion: renaming the function broke backwards compatibility, but since gutenberg_parse_blocks() is still defined, instead of a ”Call to undefined function” you get this attempt to redefine WP_Block_Parser (via inclusion of parser.php), resulting in the ”name is already in use”.
My test blog is running WP 5.0-beta3-43867 with Gutenberg 4.3.0-alpha-0841246 (from Daniel Bachhuber’s nightly), and the theme I’m using is Cover2 (Github here), which also appears to exhibit this in single post view.
I’ve narrowed it down to this function (called from header.php), where the gutenberg_parse_blocks() call triggers the issue.
I’m not saying I’m 100 % sure it’s Gutenberg and not the theme(s) at fault here, but I just thought I’d post this just in case it helps to find out either way.
Thanks for the excellent plugin! I’ve only had one issue so far: the previews are apparently saved encoded, which makes any decoded preview content unsearchable with WordPress’ search function (whereas searching for a piece of the encoded string brings up the matching post). If you could implement searchability of the decoded content, that’d be great.
The plugin refers to $post->post_type before testing it exists, which triggers an error for WP’s built-in (though hidden-by-default since forever) ”link” post type. The error appears quite harmless, as it doesn’t seem to interfere with the link editor’s functionality in any way.
WP_DEBUG on (define as true)add_filter( 'pre_option_link_manager_enabled', '__return_true' );),Links > Add NewSimple Tags’ Settings box in the sidebar shows the following notices:
Notice: Undefined property: stdClass::$post_type in [path to wp]/wp-content/plugins/simple-tags/inc/class.admin.post.php on line 46
Notice: Undefined property: stdClass::$post_type in [path to wp]/wp-content/plugins/simple-tags/inc/class.admin.post.php on line 54
The shortcode examples on the FAQ page seem to be rendered (”It’s only fair to share…” + sharing icons) by the plugin instead of being shown as code. You should probably escape the shortcodes in those examples.