I just installed SexyBookmarks on a site. It is exactly what the designer wanted.

However that particular site has a moderately huge number of custom content types and the only place the designer wanted the SexyBookmarks was on the full blog posting pages.

When enabled, SexyBookmarks adds itself to every content type with the default profile and display on Teaser and Full node.

To make sure it doesn't appear on any pages except the blog, the only solution I can see is to go through each content type and set the profile to -None- and display on -None-, although I suspect setting one of them to None is sufficient.

With a large number of content types, that was time consuming. Perhaps a better solution would be to default to -None- on both settings and let people enable SexyBookmarks rather than having to disable them.

Again, thanks for a great module.

Comments

Freshy88’s picture

Freshy88 commented

Hey greggmarshal,

The easy way to do this is within the modules /includes/sexybookmarks.inc file - changing line 14 to:
$profile->disabled = TRUE;

It currently defaults to false. Making this true will disable it by default (thus meaning no profiles are available to be on by default.) If you've already overridden the default settings for this profile, go to the admin page '/admin/settings/sexybookmarks/' and disable the profile.

I'll leave it up to Deciphered whether or not to do something like this in the module - it adds a step to setting the module up and a lot of people are already having issues with the relatively simple setup so I could understand if he doesn't want to default this to disabled!

greggmarshall’s picture

greggmarshall
Location Aurora/Denver, Colorado
commented

Good points and thanks for the suggestion. I manually set profiles for the site I installed it on.

Maybe the "solution" is to put a note in either the README or on the project page with your suggestion.

shareaholic’s picture

shareaholic commented
Version: 6.x-2.0 »
Issue summary: View changes

SexyBookmarks is no longer being actively maintained. It was a port of Shareaholic for WordPress, and Shareaholic has since released an official Drupal module.

Recommended next step:

You should migrate to the official Shareaholic for Drupal module, which has updated buttons, styles, services, 100% mobile-ready and much more! - http://drupal.org/project/shareaholic

You can learn more here: https://blog.shareaholic.com/drupal-module/

shareaholic’s picture

shareaholic commented
Status: Active » Closed (fixed)