I upgraded to 2.9 (from 2.8) because of the security warning, but now the addThis button is appearing on nodes that it did not used to show up on. Specifically, on node blocks created with the nodeblock module.

I'm not seeing any way to turn off the button for specific content types. Is there a change from the new version that I can comment out or something, in order to get the old behavior back?

Comments

les lim’s picture

les lim
he/they
Primary language English
commented

If you fully uninstalled AddThis before you upgraded, you might have lost your previous AddThis settings. Check the content type settings for your nodeblock content type (admin/content/types) and see if the "Show AddThis" setting is checked.

fastballweb’s picture

fastballweb commented
Status: Active » Fixed

Ah, I see ... the checkbox is under workflow settings. Thanks very much!

Maybe there is a more intuitive place for that checkbox? When I think of workflow, I think of the people creating the content, not the ones viewing it. But at least it's there.

And there must have been something preventing the button from showing before, because that box was also checked in my production environment, with the old version of AddThis, and the button wasn't showing up on those nodes.

dalin’s picture

dalin
he/him
Primary language English
Location 🇨🇦, 🇲🇽, 🌍
commented
Status: Fixed » Active

Agreed, the upgrade did somehow enable the addthis button for all content types, i.e. ones that were previously disabled.

vesapalmu’s picture

vesapalmu commented
Assigned: Unassigned » vesapalmu
Status: Active » Postponed (maintainer needs more info)

Could you please provide more information on what kind of environment you had when this happened? I have updated this module to five different environments now and haven't seen this happen.

You are right about that the checbox should be in some other place. We are about to clean up the admin interface for 3.0 version and all configuration will be visible in one place after that.

fastballweb’s picture

fastballweb commented

Well, maybe I wasn't very clear ... it seems that the problem, if any, was that the checkbox must not have worked properly in certain circumstances in old versions of this module. That quirk just happened to come in handy for me, considering that I didn't know the checkbox existed.

Now that I know about the checkbox, the behavior of the module makes sense as is so I am not aware of any problems that need to be fixed. I'd had it enabled on all content types the whole time, but when the module started actually behaving correctly in that regard, I had to figure out how to turn them off.

I am curious whether this is related to the theming issue from this thread? [691032] It's possible that the nodeblock module has a template file that disables the links.

I can't speak for dalin, but in my case the upgrade didn't make disabled types enabled ... it just started to correctly display types that had been enabled all along.

vesapalmu’s picture

vesapalmu commented
Status: Postponed (maintainer needs more info) » Closed (fixed)