An other quality update.

Many thanks gVectors team. Appreciated.

Thank you for the update.

I did not test it yet after the installation on my test site but the first thing that I've noticed and liked about it is that only loged-in members can see the avatar of other members.

Posted by: yossik

Thank you for the update.

I did not test it yet after the installation but the first thing that I've noticed liked about it is that only log-in members can see the avatar of other members.

 

There is an option to allow this (front) or not.

Posted by: yossik

Thank you for the update.

I did not test it yet after the installation on my test site but the first thing that I've noticed and liked about it is that only loged-in members can see the avatar of other members.

Please follow to this post. There was a bug with old versions, they were not controlling  the avatar view permission. Now with this version this is under control and you should enable "View Avatars" permission for Guests usergroup: https://wpforo.com/community/wpforo-announcements/wpforo-1-4-0-is-released/#post-11426

@Robert, the Awaiting Moderation bug still present affecting seasoned users (> 5 posts, dani_tx and tbl777 ).  These workarounds have not fixed the problem:

1. disabling Akismet
2. downgrading to wpforo 1.3.1
3. creating a new userID and then assigning old posts to that userID in the phpMyAdmin interface

Workaround fix by creating a new user: For user dani_tx, we resorted to creating a new user daniel_tx, creating 6 posts to pass the new user Awaiting Moderation and he is now finally free of having posts Await Moderation. This the splits off the use from their old posts.

Any solution by wpforo developers?

This is a significant problem requiring administrator oversight to approve busy user posts. Can you investigate and advise if this problem is to be fixed?

Posted by: nando4

 

Any solution by wpforo developers?

This is a significant problem requiring administrator oversight to approve busy user posts. Can you investigate and advise if this problem is to be fixed?

I'm sorry but there is no solution from our side. We've never faced with such issue. I think the user had something specific. We can't follow and debug such cases. We'll keep monitoring such cases in future.

Thank you for your feedback about v1.4.0. All posts are taken under consideration and most of them are already fixed in 1.4.1 (it's just released, please update). Topic is closed. For new issues please open a separate support topics for according forums.