Steps to reproduce

1. Create a folder
2. Create a restricted section
3. Assign restricted section to folder
4. Add exclusion of restricted section to anonymous role content read policy
5. Clear all cache
7 Enable all debug output and disable all cache (specifically ViewCache)
6. Load url of folder in public site as anonymous user
7. Notice the login form is not included in $module_result.content output in pagelayout.tpl and the following debug output errors ...

Brookins Consulting
added a comment - 09/Aug/07 1:27 PM Apologies,
The above patch file does not resolve the issue properly, kernel.content.view.php.nocache.return.result.array.patch
As it creates other secondary issues for content view results which are not restricted by section, role, policy restrictions.

1. While the previously submitted patch solved the issue incorrectly, the problem remains in the latest svn trunk (3.10) sources.

2. The problem appears to be focused around a problem where 'Access Denied' permission errors which occurs while trying to access content displays the first time correctly yet, while that result is cached it is not stored in cache as a serialized array. So when you access the content a second time and the cached response is used instead it only returns the content, not in an array.

3. We are not certain but it seems to be caused by the cache system's storage of the error response content incorrectly for 'Access Denied' errors.

Brookins Consulting
added a comment - 10/Aug/07 2:29 PM 1. While the previously submitted patch solved the issue incorrectly, the problem remains in the latest svn trunk (3.10) sources.
2. The problem appears to be focused around a problem where 'Access Denied' permission errors which occurs while trying to access content displays the first time correctly yet, while that result is cached it is not stored in cache as a serialized array. So when you access the content a second time and the cached response is used instead it only returns the content, not in an array.
3. We are not certain but it seems to be caused by the cache system's storage of the error response content incorrectly for 'Access Denied' errors.
4. We still see this as an outstanding 3.10 cache related problem

This issue has been automatically closed due to the lack of activity over a long period of time. It is very likely that it is obsolete, but if you think it is still valid, do not hesitate to reopen it and mention why.

ezrobot
added a comment - 10/Oct/12 5:30 PM This issue has been automatically closed due to the lack of activity over a long period of time. It is very likely that it is obsolete, but if you think it is still valid, do not hesitate to reopen it and mention why.