Hi!
Thanks for the great work in releasing this module!
I would like to place the buttons of socialshareprivacy between my main blog content and blog comments. Currently I haven't found a way to achieve this. SSP is using a block which can be place on top or below of main content, but not between content and comment. I would like to have the SSP block below the File Attachments.
Would be great if there would be a way to do this, because I think it's more likely that users will click on the buttons when they have finished reading the content text instead of being force to read through all of the comments before discovering the SSP block at the end of page.
Regards,
Ingo
Comments
Comment #1
ytsurkenable the FieldUI module,
and got to your block content type's fields.
there should be a socialshareprivacy placehoder ?!
plus with every blogpost there should be a checkbox telling wheter to place the SSP or not !?
Comment #2
ij commentedSorry for re-opening it again, but for me it doesn't work as designed. I have FieldUI activated, but the Social Media Buttons are still placed below the comment block. Yes, I have the checkbox for SSP when editing the content, but still no SSP right below the Content or above the Comment block.
The screenshots are from my blog (http://blog.windfluechter.net/) but it also happens on another site (http://npbhro.de) as well.
Is there any information I can provide to find out why it's not working for me? I'm running on PostgreSQL, which gave me some serious problems back in D6, but I doubt that this problem might be related to pgsql in D7.
Regards,
Ingo
Comment #3
ytsurkhave you set the permissions ?
Comment #4
ij commentedIn admin/people/permissions I see:
Administer Social Share Privacy:
[X] Administrator [ ] Anonymous User [ ] Authenticated User
access Social Share Privacy:
[X] Administrator [X] Anonymous User [X] Authenticated User
In the meanwhile I configured SSP placeholder display settings to display the header line in order to verify if the placeholder is being displayed at the end of the content block and before comments. And yes, it is placed correctly, but without the social media buttons.
Regards,
Ingo
Comment #5
ytsurkdid you add the content type after installing/enabling SSP ?
try to disable/enable SSP, this will create the placeholder fields again.
Comment #6
ij commentedI've added content after installing/enabling SSP, but there was already content before as well. The behaviour is the same for before and after enabling SSP.
I've uninstalled SSP complete now (incl. manual database clean up because there were some modules uninstall issues), set up the permissions as mentioned before, added the fields where necessary, saved everything, configured SSP settings, toggled the check mark for SSP on an existing blog entry, but still no Social Media buttons...
Any ideas?
Regards,
Ingo
Comment #7
ytsurkprobably in conflict with another module ...
can I maybe access one of your drupal installations,
or could you hand-out one to me ? (everything zipped & database)
Comment #8
ij commentedYesterday evening I sent you a message on Twitter to @ytsurk. I'm @ingoj on Twitter.
Anyway, this morning I discovered that there actually are SSP buttons on http://blog.windfluechter.net/blog, but not when displaying the node itself.
"Great!", I thought, "I just need to adopt the default field display settings to the full node settings and then I'm fine!" But it didn't work as expected: I reordered the placeholder field below the file attachment field as well, saved all settings and now the SSP buttons were gone again! I cleared the caches, but no improvement.
I guess, something is messing it up, but can't figure out what is causing the problems.
Comment #9
ytsurkwe were in contact,
and it seems like the field formatter was not corretly setup ..,
don't know becuase of postgreSql or something else ..
Comment #10
ytsurki completly reworked the field handling.
now using a custom one insted of list_option
Comment #11
ij commentedYes, I can confirm that SSP now works without problems on two of my sites.
A really big thanks to ytsurk, who did a great job in fixing this bug!
Comment #11.0
ij commentedreparaphrase some sentences