Okay, I will do some testing then and see if I can get everything to function correctly. :)

I fixed the error preventing the db query from working, and have attached the updated product.

Allowing users to reply to their own moderated threads isn't something this was ever intended to do, and so I will have to figure out how to make that happen. Once I have, I will post. :)

Okay, this updated version will allow users to reply to their own moderated threads, and to edit their own moderated posts. :)

Thank you very much, Mark :up:
It is working on 4.2.3
Because I have AJAX function turned on the new post appers only after full page refresh, before that user still sees "Your post will not be visible until a moderator has approved it for posting" message. Other then that the hack works great. Thanks again.

On my dev site, I also have the "Quick Reply" enabled, and the new post shows up immediately. This is when a thread has been put into the moderation queue by a mod/admin. How are threads/posts being put into the moderation queue on your site?

Perhaps if I know this, I can duplicate the conditions you have and fix this remaining issue. :)

Are you by chance using my automated post reporter product, that puts posts/threads into the moderation queue automatically, if a user posts certain flagged words, or necro-posts?

The reason I ask is that I do get the behavior you describe with that product (which is by design), and what I can do is incorporate this feature (allowing users to see/edit their own moderated posts) into the automated post reporter, and then if you elect to allow users to see/edit their own moderated posts, I can turn off the error message.

The automated post reporter product is in need of an overhaul as it was the first product I wrote, and so look for an upgrade including this feature at some point (I don't want to give any kind of timeline at this point). :)

I have special user group with settings "Follow Forum Moderation Rules If no, posts are always placed into moderation queue" set to no. For my testing I used an account of this type.

I can confirm that it's due to another modification which moderates based upon keywords (in my case it's Glowhost's Spam-o-matic). Sounds like your product does the same thing. I always found it better to moderate based upon keywords rather than having an entire board's threads/posts go into moderation via vbulletin's settings. I mean who has time to do all that approving? So I used glowhost's spam-o-matic to only look for spam keywords in order to put posts/threads into moderation and when I tested your updated product by entering a bad keyword and it still gave me that annoying "Your post will not be visible until a moderator has approved it for posting" popup, and even further it wouldn't let me edit the post after I did a manual refresh.

I'd gladly switch to your post reporter product when you update it to work with allowing users to see and edit their own moderated posts/threads without getting that annoying popup about needing a moderator approval first. To me it just seems better for members not to see that popup since it only annoys them. It's better that when they post something that is moderated that the post/thread appears and is editable as if nothing is wrong. While in the background moderators efficiently approve the post/threads without the user being none the wiser that it was moderated to begin with. It'll also cut down on members making duplicate posts/threads to bypass the moderation.

Is there possible Mark, that they can see attached images they upload?
Now attached images dos not show up. I do not have in settings moderate attachments. I realized this because 4-5 members try to upload image again and again as they do not see the image, it shows with the X. After approve is ok.
As admins - Mods we can see the image.


Thank you very much

I used this hack in the past by modifying the files as per the O/P and 2nd Post. On my new forum (4.2.5) I tried doing it using the XML product, and that's doesn't seem to work.
I'll uninstall the product and try the manual modification again.