Support Forum

The Admins New Post Queue

YS Yellow Swordfish
Yellow Swordfish
Member

First off I would recommend that the name of this plugin changes. With the introduction of the WP Admin Bar the name is somewhat confusing so suggestions are needed.

I also think that only minimal changes are required to the current implementation to get it working in a way that suits us all and – by the way – I am ignoring any bugs that may exist at the moment as a separate issue. This is about the operation.

What goes in to the queue:

Currently ALL posts go into the queue with the exception of those made by an admin. (I know that is not totally accurate but it will do). Posts made by moderators can also be added to the queue via the admin options. More on those later.

We have been asked, in the past, if this could be changed so that only posts awaiting moderation go into the queue. I am not against this and if we want to add this option then now is the time to do it.

The current options:

Force queue removal from admin bar only: This seems to be the contentious one and as long as we get the rest right then I am happy to ditch this option. So keep it or remove it?

Allow moderators to remove new posts from the queue: Probably useful in some cases but I will not fight hard for it. So keep it or remove it?

Include posts by moderators in the queue: This really goes hand in hand with the previous option and I would suggest it has the same fate as that one.

Operation:

I think the main thing we need to change here is how items are removed from the queue. Currently, if the option settings allow it, simply reading a posts in the queue removes it. This is not going to work. So this needs to be changed so that posts are removed when they are answered with a new post. Or – when they are approved if in moderation and the forum edit tools are used.

This does leave the scenario of a post in the queue that needs no answer that could then ONLY be removed by using the admin bar but that is preferable to posts just disappearing from the queue by being read but not answered.

The personal unread post list:

This just leaves the question on whether posts in the queue (whether they need moderation or not) are always included in the admin/moderators personal unread post list. I prefer that they are but am open to argument.

So – discussion points are:

  1. Option – Force queue removal from admin bar only – remove or keep? (I vote remove)
  2. Option – Allow moderators to remove new posts from the queue – remove or keep (I vote remove)
  3. Option – Include posts by moderators in the queue – remove or keep (should go hand in hand with above)
  4. Operation – change as stated above?
  5. New Option to only include posts needing moderation – do it or not?
  6. Personal unread post list – include items in the queue whether read or not? (I vote yes)

Did I miss anything?

Oh yes – maybe we would also like to change the term ‘queue’?

5 Answers

New Answer

MP Mr Papa
Mr Papa
Member

Current Options

Force queue removal from admin bar only – I dont have a feel if other users are using this or not…  As you know, I think my personal preference is to not have it set for our site… too often reply from the topic itself because I need to see past history to fully understand the post…  then have to go back to the admin bar just to approve my own post… So I have no issue with leaving it or deleting it…  If it complicates things then I would be for removal.

Allow moderators to remove new posts from the queue – This one has never been fully understood by me.  if you trust someone enough to be a moderator, seems they should be able to remove from the queue. My preference is for our site is to have this set.  Not opposed to leaving it if others using though.  Again, if complicates things then going simple and removing might be the answer.

Include posts by moderators in the queue – Another I dont really get, but that doesnt mean others dont use it.  Trying not to limit the options by my desire for personal use.  I would say the same thing on complication level.

I guess I feel the admin queue is for posts that have not been responded to by admins or moderators.  If a post has been responded to by an admin or mod, then its not in the admin queue.  Following that logic, the last two options would go bye bye.  The posts would still be in the users unread post list so you wouldnt lose track that something got posted to the post.  Seems simple and straight forward to me. But if not overly complex, am okay with the last two options remaining for flexibility for the user.

Operation… Agree, just reading a post should not remove it from the queue.  It needs a response from admin or mod to get removed from the queue. Or as you say, explicitly approved from admin bar or forum tools.

so does sound like we are mostly in agreement…

Okay with your resolution for 1, 2 and 3…  I think we are in agreement on #4 too, but worth reading my above and make sure you think it matches too. I guess I am ambivalent on #5. I dont think I would use the option based on my #4 operations thought.  I am not against including it providing its not overly complex.  I think simplifying how all works is key now. 

My initial thought on #6 was that the admin queue and unread list were two distinct items. New posts would show in both.  Viewing an unread list post would remove it from the unread list even if it still remained in the admin queue because it wasnt answered or approved.  You wouldnt lose track of it as long as it appeared in one or the other.  BUT my feeling on that is far from strong – not at all.  If you think its useful, then I am happy for its incorporation. Were you thinking global option or individual admin option?  Which is more complex implementation? I am fine with whatever you want to do for #6.

As to admin queue, never bothered me, but perhaps its not consistent.  Since its unread post list and we use list in other places, maybe the admin list makes more sense.  Its really not a queue (first in first out kinda thing) so maybe list is more appropriate. did you have other thoughts on name?

changing the plugin name doesnt really excite me… wink

YS Yellow Swordfish
Yellow Swordfish
Member

Good so far.

The main thing to remember about the ‘personal’ unread post list and the ‘admins’ list is that the personal list DOES remove an item when the post is viewed. You do not need to reply.

If we do NOT include admins list posts in the personal list (of an admin of course) it means a post awaiting moderation would disappear from the personal list when read. if they are NOT using the admin bar then that post could escape beng approved quite easily. By keeping it in the personal list it will always be visible.

MP Mr Papa
Mr Papa
Member

absolutely concur on viewing removing from the user unread list…  it is an ‘unread’ list where as the admin list is more an ‘action needed’ list…

good point on keeping it in user list…  since we use the admin bar, really doesnt matter, but alot of folks dont use it…  so as I said, happy to force admin list stuff to stay in unread list…  just need to document and make it clear to folks… I assume one can still disable the admin list (formerly queue) altogether, right? 

YS Yellow Swordfish
Yellow Swordfish
Member

That’s a good question. The answer is yes but should we just say if the  plugin is active then the bar is displayed regardless? Or just leave it as it is. People do seem to get confused by the need for admins/moderators to visit ‘Your Admin Options’ to do things like turn on email notifications.

I am all behind changing the name from ‘admin queue’ but not sure I am that fond of ‘admin list’ other. It doesn’t really convey the right meaning. Needs some thought this as does the name of the plugin which I think should also now change.

MP Mr Papa
Mr Papa
Member

actually, the admin queue is by definition active in 5.0 if the plugin is active…  but admins/mods still individually choose whether to use the admin bar or not… and dont think that should change…

I dont have a better name handly, so your turn to suggest wink

changing the plugin name is not a trivial thing…  all the variables, function names, comments, etc need to change to match…  and everyone currently using it (granted, small number) will have to reactivate it…  and we will lose the svn history…  but not dead set against it either…