Title: Invasive Plugin
Last modified: December 10, 2023

---

# Invasive Plugin

 *  [Banjoo](https://wordpress.org/support/users/ozarc/)
 * (@ozarc)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/invasive-plugin-3/)
 * Horrible plugin that invades pages its not supposed to. Have set this to ONLY
   be posts, yet its in every page of my website. It even inserts itself into the
   backend of every page, as if i want to now share my wordpress page’s backend 
   on social media. Why on earth would i ever want to do that!
 * Avoid and look elsewhere unless you enjoy your website being invaded form ever
   corner by a plugin.
 * Also, this requires another Schema plugin to work which in itself makes not sense.
 * All i wanted was a social share plugin for my posts, what i got instead was a
   plugin that inserts itself into ever corner of my front and backend, grouped 
   with another schema plugin that i didn’t want or need

Viewing 1 replies (of 1 total)

 *  Plugin Author [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
 * (@jsmoriss)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/invasive-plugin-3/#post-17266499)
 * Your review is an entertaining read, so thank you for that. Unfortunately you’ve
   based your opinion on some incorrect assumptions, and the angry / aggressive 
   tone is a dead giveaway of this. In case you’re interested, I can provide some
   more information to correct some of those assumptions.
 * The WPSSO RRSSB add-on offers a settings page where you can choose the post type(
   s) on which the buttons will appear by default, and the location within those
   pages. For example, it could be only on Posts + the content block, so buttons
   would not appear on Pages or custom post types like Products, Events, etc., and
   not in excerpts, the sidebar, or admin editing pages. Post types and locations
   are easily selectable in the WPSSO RRSSB settings page. _If buttons are selected
   to show only on Posts, and they also show on other webpages that are not (supposed
   to be) Posts, then those other pages were probably created by a plugin that doesn’t
   use WordPress post types (the default WordPress post object is “Post”, and anything
   else, like WordPress Pages are custom post types)._ If a plugin creates non-standard
   webpages without defining a post type, then there’s nothing other plugin authors
   can do about that – they would need to fix their plugin to use proper WordPress
   post types, if they don’t want their webpage to be Posts by default – that’s 
   just how WordPress works.
 * As you’ve incorrectly stated, the WPSSO RRSSB add-on can (and does by default)
   add share buttons to the WordPress editing page. Authors often find this very
   useful when they are finished writing their content, so they can share it directly
   from the editing page, instead of going to the front-end page and sharing it 
   there. I don’t know why you would believe that the share buttons would share 
   the editing page URL instead of the front-end webpage URL (aka the “canonical
   URL”). And certainly that would be easy to check just by clicking a share button.
 * You’ve stated that you don’t know why a Schema plugin would be necessary for 
   a sharing plugin, which means that you are not aware that social sites read meta
   tags and Schema markup from the webpage URL being shared. Correct and complete
   meta tags and Schema markup are essential to provide social crawlers with the
   correct information about the webpage URL being shared (ie. title, description,
   image, etc.). The WPSSO Core plugin is required so it can provide meta tags for
   Facebook and Twitter along with extra markup in the content for Pinterest (not
   to mention LinkedIn, WhatsApp and others). Adding share buttons to a webpage 
   without that webpage having complete and correct meta tags and Schema markup 
   is possible, but definitely not desirable, as social crawlers would then choose
   any random image or text it finds on the webpage – I can’t think of any site 
   owner that would actually desire this.
 * Hopefully this has been helpful in correcting some of your assumptions.
 * js.

Viewing 1 replies (of 1 total)

The topic ‘Invasive Plugin’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wpsso-rrssb_cfde76.svg)
 * [WPSSO Ridiculously Responsive Social Sharing Buttons (RRSSB)](https://wordpress.org/plugins/wpsso-rrssb/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wpsso-rrssb/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wpsso-rrssb/)
 * [Active Topics](https://wordpress.org/support/plugin/wpsso-rrssb/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wpsso-rrssb/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wpsso-rrssb/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
 * Last activity: [2 years, 6 months ago](https://wordpress.org/support/topic/invasive-plugin-3/#post-17266499)