Type: Regression Bug
Affects Version/s: 6.2.X EE, 7.0.0 M3
Environment:Tomcat 7.0.42 + MySQL 5.5.34. Portal master GIT ID: 71df7032dd58476836eb8fa4ee4e879b6865c967.
- Add Asset Publisher and Blogs portlets
- Add blog entry 1 and blog entry 2
- Edit blog entry 1 and save as draft
- Click the blogs draft in AP
User should not see a redirect error.
As a user, clicking the blogs draft in the AP will redirect to an "The asset could not be found." error.
After a deeper analysis, I've found that blogs logic is correct, and is setting the asset as visible only if the blogs entry is approved.
The problem in in the Asset Publisher logic, that is showing non visible assets.
This is reproducible the indexer enabled or disabled.