First off, great new feature for retaining SPAM into the Approval Queue for moderation instead of discarding them!

I noticed during testing that if SPAM is retained for comments, the user is given the following message:
"Your comment has been queued for moderation by site administrators and will be published after approval."

This makes sense, so users won't expect the comment to appear instantly.

When retaining SPAM through a content type, however, like a forum topic for example, there is no analagous message to the user that the post is being moderated. Instead, the user receives the "Forum Topic created" message and the node doesn't appear until the forum topic is published.

This can be confusing to users since the Forum topic isn't immediately published and there is no message that it will be moderated. In addition, after the user initially creates the Forum topic, they are redirected back to the their newly created topic and if they attempt to comment, they receive an "Access Denied" page.

There should be an analagous "Your forum topic has been queued for moderation by site administrators and will be published after approval." message for retained content types as there is for retained comments.

Thanks & keep up the great work on Mollom.
Henry

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: Retaining SPAM for content types » Misleading "Post published" status message and page redirect when retaining nodes as unpublished

Unfortunately, this logic is kinda hard-coded in the Node module in Drupal core.

As of now, I don't really see a way how the Mollom module could

  1. reliably intercept and replace the status message that's shown to the user, since messages are internally stacked in drupal_set_message() only and cannot be altered by modules.
  2. redirect to a more appropriate and accessible page, since that is very likely to be entirely different per content type (forum vs. poll vs. article vs. page), may depend on the originating/referring page, and each site may also have site-specific expectations.

So currently, all I can say is: Ugh. :-/

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Closed (works as designed)

So yeah, I'm sorry, this is a shortcoming in Drupal core that needs to be fixed in Drupal core.

Unlike the Comment module, the Node module is not really prepared for the possible situation of new nodes being created as unpublished/needing approval.

It would not make sense to introduce a custom workaround in the Mollom module. Doing so would have a very high chance of introducing conflicts with other contributed modules.

However, in slightly better news, I believe that this situation has been vastly improved in D7 or D8. So one of the root causes might very well be D6 in this case.