Signup module integration with DS 7.x-1.3

Create a custom field and use this:

  print $object->content['signup']['#value'];

Ok, great!

Swentel, thank you so much for developing the DS module (and all of the helpful videos). DS takes Drupal to the next level.

I'm using DS (7.x-1.3), and I'm trying to integrate it with CCK Signup (7.x-1.0-alpha4). Sorry I'm not too savvy with PHP. I first tested that when I toggled on one of the Display Suite templates that the node's signup link disappeared (as expected based on Ole Martin's original support request). Then I tried adding a custom field:

(1) On 'Manage Display' I clicked "Add Code Field"
(2) Label = "Signup test"
(3) Entities = "Node"
(4) Field code =

<?php
  print $object->content['signup']['#value'];
?>

Then I get the following errors:

• Notice: Undefined variable: object in eval() (line 2 of /home/whopkins/public_html/studentardor.com/sites/all/modules/ds/ds.module(674) : eval()'d code).
• Notice: Trying to get property of non-object in eval() (line 2 of /home/whopkins/public_html/studentardor.com/sites/all/modules/ds/ds.module(674) : eval()'d code).

I know this sort of falls outside the scope of the Display Suite module, but if you can help out at all it would be very, very appreciated. Again, thanks so much for developing the Display Suite. It's a work of art!

Best,
woop

Instead of $object, it's $entity, so the code should be:

$entity->content['signup']['#markup'];

Thanks for the quick response swentel. Unfortunately the same error is still occurring, even using the above snippet. I didn't want to keep bugging you about it -- and I tried to solve it on my own, but to no avail. I'm stalled. If anything else comes to mind as to why it's not working, I would greatly appreciate it!

woop

(Again, if I turn off Display Suite, CCK Signup works. When I turn it on and make the custom field visible, I get the errors that I posted before.)

Anyone have any luck with this?

i got an eval() error i had <?php tags in the field so i just posted the $entity-> ,... directly in
check the screenshot. looks like its working ;)

I also tried to put the signup side by side with the content with the help of Display Suite

If I use the php code

$entity->content['signup']['#markup'];

I got the same kind of error as woop_light got

If I place just
$entity->content['signup']['#markup'];

with display suite code option I just get "$entity->content['signup']['#markup'];" showing in the right column

Any clue ? Thanks

it sounds like you textformat isnt taking in php or "display suite" format.
make sure you uses that else it wont print the php magick :)

look at the screenshot i posted in #11

thanks for your reply

however there was already the following settings done (Drupal 7)

1/ activating php filter module (in modules)
2/ Creating a new textformat for display suite code (in configuration/text format)
3/ when creating the regarding node with signup, assign text format "displaysuite code"

and with this settings I got the 2 cases :
the one when typing full php syntax in the Display Suite field code , in this case there is an error message
the other one with just "$entity->content['signup']['#markup'];" as you suggest it, but only text "$entity->content['signup']['#markup'];" was displayed in the right column.

When desactiving Displaysuite module I saw the sign up form at the bottom of the node. With Display Suite the idea was in theory to have a left column with the content and a right one with the signup form related to the event. If I use the standard node display the signup form is at the bottom of the post and in this case not immediatly visible.

There was no block option for signup module, I tried several css tricks with no luck, there was no views solution in order to display the signup form, panels feature seems not working. What I want to do is showing content on the left and the regarding signup form for the event on the right. If I understand correctly, I think that this is exactly what you succeeded to do.

Perhaps I missed one step. Thanks

With me it's also not working and I have tried the same steps. Hope to find a solution soon.

yup -- i've been in the same boat as clo75. would really love to work this out.