*note* I posted this in the general forums last week with no action, so maybe it's better here **
I have a site where I want users to be able to enter an event that is placed in the moderation queue.
This is fine for basic events, but if there is a repeated event (using both the event and eventrepeat mods), the user can never get to the repeat options page until the original event clears by the moderator.
Any ideas on how to allow a user to enter a repeated event that still has moderation without changing the mods?
If the module has to be changed, does anyone want to do that?
Comments
Comment #1
seanbfuller commentedYou may actually be experiencing this bug in event.module:
http://drupal.org/node/57589
Check the events that you are creating and make sure that the original and the repeating events have the "In Moderation Cue" marked under Publishing Options. If so, then the event and eventrepeat modules are setting the moderation flag correctly, but event module is not checking for it when rendering the calendar.
Let me know if that works for you.
s
Comment #2
rjleigh commentedActually, I am referring to something else. When a node is set to be placed in the queue and not published, it disappears after the user submits it. Of course, for a repeat event, that is a problem, because the user would then have to return to the site after the post is approved (and there's no notification of this) to add the repeat pattern.
This is too much trouble for a moderated community calendar type of application, which I am trying to implement.
Comment #3
seanbfuller commentedAh, OK.
Yeah, that is definitely an issue in the current 4.7 version due to the workflow. The cvs version, which is still has a few issues before it should be considered viable, I'll leave this issue open for others to see until current cvs moves to 4.7.
Comment #4
rjleigh commentedI wasn't clear about your response - are you saying it is addressed in the current CVS, or only that you will consider adding it to the feature set?
Comment #5
seanbfuller commentedIt should be addressed in the current CVS. Sorry for the confusion.
Comment #6
seanbfuller commentedMarking this as won't fix for 4.7.x-1.x. You will probably want to upgrade to 4.7.x-2.x, which should be posting soon. (Most of the issues that are left in the 2.x version were present in the 1.x version as well.)