It would be great to back-port the DiggThis ability to choose the position of the links themselves using relative weights, so that we can place the link above or below the title, content, teasers, etc.

Comments

TheCrow’s picture

Version: master » 6.x-2.x-dev
Assigned: LouisEric » TheCrow
Status: Active » Needs work

Im working for provide a field for Node Displays (related to Display Suite) module.

dddave’s picture

Count me in for testing. Great news!

TheCrow’s picture

StatusFileSize
new1.19 KB

Hello dddave there is the first Implementation!

Can extract it under service_links folder and enable the related module in Display Suite group (admin > modules )

:))

dddave’s picture

Status: Needs work » Needs review

Uh, I hope I find some time tonight...

dddave’s picture

Title: Position the links on the page via UI » Position the links on the page via UI / Display Suite integration
Status: Needs review » Needs work

Basically working. However:

1. Positioning the label (custom or default) inline is not working. It is always above.

2. Fisheye displays image+text

Also: Textlinks and Icon+text links are displayed as list whereas icon links are displayed inline. I would strongly favor that all links default to inline display.

TheCrow’s picture

StatusFileSize
new1.19 KB

Thanks dddave,

About label, unfortunately i don't have any control over it, i think this problem should be solved by CSS how happens for other fields too.

Fisheye has been fixed and also other formats now show inline (no more lists).
The unique bug is due to the presence of Fisheye block in the same page where is displayed Fisheye field, but if you change in js/service_links_fisheye.js,
the row:
$('#fisheye').Fisheye({
with:
$('.fisheye').Fisheye({

should work well also in this case.

dddave’s picture

Nice!

Only problem I could find was that the fisheye display (working!) isn't left-aligned as all other options are. Could you default it to the left?

As about the field label positioning: this seems to be a ND bug. This isn't working for fivestar fields either. Going to take a look into this...

Leaving this to needs work because of the fisheye-links position.

TheCrow’s picture

StatusFileSize
new1.2 KB

alignment of fisheye happens inside service_links_fisheye.js
the row is:

halign : 'center'

maybe i could make this param variable...

i added the reference to service_links_show() function and i noticed an error about use of $fields variable :P

i would like also provide a checkbox for every service (in admin > services) for show each one in a separated field but i still have to work on it.

dddave’s picture

Sorry for the lack of feedback. Kind of forgot about this issue.
Anything special to review here? Tested with the latest dev and it still seems to work.

TheCrow’s picture

added in dev right now, it has the support for single services too :P

HS’s picture

How does this work again? I placed the 'plugins' folder inside the 'service_links' folder. But how do I use this?

I'm not using the Dev release though.

-Edit-

OK figured it out. I'm missing the Display suite module. Not really keen on installing yet another module for this simple functionality though :(

TheCrow’s picture

Hi HS, this is an addon for Display Suite, not a simple functionality, but an easy way for displays only the requested fields of your content's type or change their weights without overwrite the node[-type].tpl.php and other functions into your theme...
The fields availables with Node Displays (separated module of Display Suite group) are not only CCK fields: you can move Title, Author, Date,...
Obviously you dont need Display Suite and this plugin if you choose to overwrite the theme's files manually.

The dev version of Service Links contain a new API (service_links_render_some()) that return a single or a filtered group of the services loaded that can be handled and placed everywhere in your theme (an example is in the code of Service Links Displays).

HS’s picture

Thank you, TheCrow.

TheCrow’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.