I can't seem to get the share link to work on a D5.7 installation. I'm not sure why. I've tried to uninstall, reinstall, run update.php etc. I can't get it to show at all. I've tried stitching to Garland (just to test) and the link doesn't show at all. I'm not assuming this is a bug, but I also can't assume it's not. I have a lot of modules enabled so maybe there's a conflict? I followed all of the installation instructions for Service Links, Forward, etc. I added the necessary selections in the Site Configuration for all three modules. Enabled (what I assume are) the correct permissions. I'm really stretching to guess, so I thought I'd post here - is there any way to debug to see what's going on, why the link won't show?
Thanks in advance for any help --
Scott
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | share-235827.patch | 688 bytes | zoo33 |
Comments
Comment #1
catchI'm having the same issue. The "Share this" link works fine, can't get it to work with forward and service module - tried serveral different combinations of settings.
Comment #2
mr.j commentedSame here. Just upgraded from an older version. All my previous settings were lost and now the link won't show up at all.
I am using the dev version, not the alpha.
Comment #3
greenskin commentedWhat do you have set on 'admin/settings/share'?
If you are using Service Links, what do you have set on 'admin/settings/servicelinks' under the fieldset titled 'When and how to show the links'?
If you are using the Share Link service for Share make sure you generate your custom script to add to the Share settings page. Visit http://sharethis.com/publisher?type=stapi to generate the script code.
Comment #4
zoo33 commentedI too experienced this problem after upgrading from 2.x-alpha1 to 2.x-dev. Found a discrepancy between the settings form and the swich statement in share_nodeapi() which seems to be the culprit. Voila, a patch!
Changing version to 5.x-2.x-dev. My apologies to the original poster if I'm hijacking this issue.
Comment #5
greenskin commentedThis has been fixed in the latest dev snapshot as well as Alpha 2.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.