Recent Bloggers does not show corrent amount of posts

• Type: Bug
• Status: Closed
• Resolution: No Longer Reproducible
• Affects Version/s: 6.1.1 CE GA2
• Fix Version/s: 6.2.0 CE M4
• Component/s: Collaboration, Collaboration > Blogs
• Labels:
  • community-verifier
• Environment: Liferay 6.1 CE GA2 bundled with Tomcat and Liferay 6.1 CE GA2 + Tomcat 6.0.35 + MySQL 5.1.66
• Similar Issues: Show 4 results ; ;

  LPS-6358	The number of the Posts is wrong when deleting Blogs in Recent Bloggers Portlet in Oracle
  LPS-8445	Recent Bloggers portlet display's posts that are to appear in the future
  LPS-5324	Are the number of "Posts" in Recent Bloggers supposed to decrease with deleting a blog entry?
  LPS-45277	Inconsistent behavior with the number of posts in Recent Bloggers when scoped

When user 1 has created a blog and saved it as a draft, and user 2 publishes the blog user 1 wrote, the "recent bloggers" portlet does not count this as a post at all (not from user 1 nor from user 2). It is not untill either user 1 publishes this or any other blog himself or untill user 1 is impersonated and using this impersonation publishes a blog, this blog (and other blogs that were published by someone else than the author user 1) will count as posts in the "Recent Bloggers" portlet. How to reproduce:

1. Create a page
2. place blogs portlet and recent bloggers portlet
3. create a blog with user 1 and save it as a draft (not published at all)
4. log in as a different user and publish this blog -> recent bloggers portlet will remain empty
5. log in as user 1 again (or impersonate user 1)
6. publish the blog -> recent bloggers portlet will show user 1 has 1 post

[Jaakko Yli-Koivisto]

Thank you for the report. As part of our community verifier
program, I am taking a look at this issue. If it is no longer a concern or you have additional
information that will help in troubleshooting it, please let me know.

[Jaakko Yli-Koivisto]

Can't reproduce issue.

I have tested this issue against Liferay 6.2.0 CE M4 Tomcat bundle with MySql 5.5.17.

It has likely been solved in a recent release and I recommend this can be closed.