PASSED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 3c4f4b709e9e7e2f090c87327a1131d576e677c5.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 0cef55c5eb17b8815d5a2dd6875a040e8ff2e7b5.

Navigate to the new web content within the Web Content List from the root site. You will NOT be able to view the content at all, and instead the error "The selected web content no longer exists." appears.

Fixed on:
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 4166a5e8894ce3c6024bfc549545e5fc74c1320c.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 6535813184f8681e14487b205c17df1caee259d0.

Navigate to the new web content within the Web Content List from the root site. You will be able to view the content correctly.

Committed on:
6.1.x GIT ID: 98045213e5979578590ebf48027896839135a6cd.
6.2.x GIT ID: 98045213e5979578590ebf48027896839135a6cd.

This is a regression bug. The original behaviour was that if in community B you could see an article from community A, then after click in the article's title you could see it in the community B web content list portlet.

Hi Jevon Wright,

Thank you for your report. I was able to reproduce this issue in our current trunk head. I will update this ticket to reflect this issue.