Viewing 6 replies - 1 through 6 (of 6 total)
  • ZinZang

    (@zinzangstudio)

    Those bits may be hidden by adding targeted rules to your CSS file, something like this:

    .header-widget-container .addtoany_share_save_container { display: none; visibility: hidden; }

    Change “.header-widget-container” to correspond with whatever widget classes you need to target.

    Thread Starter NancyN

    (@nancyn)

    Thanks, ZZS, for that tip. In my view, having to hand-code CSS for each widget to make the plug-in work is a non-starter, but perhaps that might work for others.

    Thanks again for taking the time to comment.

    ZinZang

    (@zinzangstudio)

    You’re welcome. You make a valid point, and the solution I offered is not a good way to go, and no one should take the advice. It’s terrible, actually, because it doesn’t take into account what happens when no style sheet is loaded.

    Again, you’re welcome. 🙂

    ZinZang

    (@zinzangstudio)

    This might help – in your edit post screen options for Widget Entries, do you have a check box for “AddThis meta”? If so, this should allow enabling and disabling AddThis for particular Widget Entries.

    Hope that one helps. 🙂

    Thread Starter NancyN

    (@nancyn)

    Alas, no such option is provided. That option DOES appear on Page and Post edit screens, however the screen options provided in the Widget entry editor are only “Show on screen” (‘Slug’ is the only option) and “Screen Layout” (allowing 1 or 2 columns). ‘

    Thanks anyway! 😉

    ZinZang

    (@zinzangstudio)

    Solution!

    Add <!--nosharesave--> to the Text edit screen of a Widget Entry.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Clashes with "AddThis"’ is closed to new replies.