With my client, the lecturer of a course has to be considered as a "resource", too. Because, if s/he is already lecturing, there can be no more lecture with the same person.

CommentFileSizeAuthor
#1 resource_conflict-2.0-749852.patch7.56 KBraphaelhuefner
#1 resource_conflict-2.x-dev-749852.patch7.5 KBraphaelhuefner

Comments

raphaelhuefner’s picture

raphaelhuefner commented
StatusFileSize
new resource_conflict-2.x-dev-749852.patch7.5 KB
new resource_conflict-2.0-749852.patch7.56 KB

These patches are working (at least for me) proof of concept code.

Not very beautiful, much copy'n'paste: I plan to add 2 more issues to resource_conflict which hopefully clarify why these patches are only a "proof of concept".

raphaelhuefner’s picture

raphaelhuefner commented
Status: Active » Needs review
raphaelhuefner’s picture

raphaelhuefner commented

I would like to make this userreference thing into something which is attached via a hook like proposed in #750598: hook(s) for field- and node-handlers in order to not bloat the resource_conflict module too much. That's why the patches in #1 are "proof of concept", only.

deviantintegral’s picture

deviantintegral commented

Are you using Content Profile? When I've had to implement this, we were all ready using profiles-as-nodes which meant that you could book the node profile instead of the user.

As it's entirely reasonable to not be using that module, this concept seems OK, though I don't think it would really be a "userreference" as I doubt we'd use any of the code from that module.

raphaelhuefner’s picture

raphaelhuefner commented

Re #3: Making this into an external module has happened in #750598: hook(s) for field- and node-handlers #6 (direct link: http://drupal.org/node/750598#comment-3369386 )

ohthehugemanatee’s picture

ohthehugemanatee commented
Status: Needs review » Closed (fixed)