Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I've been trying to figure out what's the issue, but it shows up in the layout configuration form, yet doesn't show up at the node display. Checked content types in SL configuration, permissions.
Comment | File | Size | Author |
---|---|---|---|
#14 | 1789332-ds-compatability.patch | 749 bytes | boznik |
#1 | 1789332-service_links-display_suite-compatibility.patch | 933 bytes | barraponto |
Comments
Comment #1
barraponto CreditAttribution: barraponto commentedThis patch solves the issue for me, however it does need some work: it needs to upgrade the current layouts and needs to address the service_link-per-field case (didn't even look at it).
DS is not supposed to be upgraded from 7.x-1.x to 7.x-2.x, so we don't need to care about that, but we do need to care about updating the layouts configured previously to this patch. And of course, we should care about supporting both DS 7.x-2.x and 7.x-1.x
BEWARE: Using this work-in-progress patch requires re-adding the service links field to the layouts. Please see #1789332-4: Service Links Displays stopped working with DS 7.x-2.x
Comment #2
7wonders CreditAttribution: 7wonders commentedpatch applied cleanly but I still dont seem to be able to get service links to show up through ds. I have tried setting the Service Links Group field to all options and still nothing :(
Comment #3
Danny EnglanderSame issue here, patch applied cleanly but no joy with Display Suite pages. I cleared cache as well. Works as expected on other non-Display Suite pages. When I removed Display Suite from a given content type, Service Links then worked as expected.
Comment #4
barraponto CreditAttribution: barraponto commentedLet me explain: I've not implemented an update function (I should, someone should). But if you want this to work right now, remove the service links field from the display BEFORE applying the patch. Then apply the patch and add it again.
Comment #5
xtfer CreditAttribution: xtfer commentedThis patch works fine, however you will need to re-add the Display Suite reference to the Service Links group after applying, as the key Display Suite looks for has changed.
Comment #6
barraponto CreditAttribution: barraponto commentedThis is not RTBC if there's no upgrade path (re-adding stuff). Also, the patch doesn't even check what version of DS you're running, it just assumes 2.x.
Comment #7
Taxoman CreditAttribution: Taxoman commentedComment #8
TheCrow CreditAttribution: TheCrow commentedInstalled DS 1, enabled SLD, configured some service and added to a content type, then updated DS to the 2.x version, runned update.php and cleaned the cache, everything is working fine.
Can someone helps to reproduce the error?
The patch above doesn't mean so much to me, being the id of the field not following any standard for DS...
Comment #9
Simon Georges CreditAttribution: Simon Georges commentedComment #10
dddbbb CreditAttribution: dddbbb commentedI just bumped into this problem as well: Service links not appearing on nodes where a Display Suite layout has been enabled. What are people doing to get around this if the patch above is no longer receiving any attention?
Comment #11
dddbbb CreditAttribution: dddbbb commentedI'm a muppet. Forgot about the block that service links creates for you. I'll use that.
Would be nice if the DS feature worked though.
Comment #12
maxperience CreditAttribution: maxperience commentedI'm new to Drupal and thought I had the same issue. This is what solved it for me.
Go to /admin/config/services/service-links/services , there you'll see a column "Displays" next to the column "Show"
Select the services you need under the "Displays" column and Service Links Displays will display. At least that's what worked for me.
Comment #13
peterwgnd CreditAttribution: peterwgnd commentedFollowed the advice in #12, which worked for getting the links to appear again, but I've lost the header. Any idea how to recover that bit?
Comment #14
boznik CreditAttribution: boznik as a volunteer commentedI just ran into this problem and fixed it with this patch.
Comment #15
John Bickar CreditAttribution: John Bickar commentedSetting to "needs review" for @boznik and testbot.