Side Content display problems for anonymous users when block cache enabled
label10 - May 15, 2009 - 15:36
| Project: | Side Content |
| Version: | 6.x-2.0-rc1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | block caching |
Jump to:
Description
Hi thanks for this cool module. It is coming in handy for my, if only I can get the sidecontent to show for anonymous users, especially once I clear the cache, the whole thing disappears and only admin can see content. I try to update and i get the error below
require_once(database/updates.inc) [function.require-once]: failed to open stream: No such file or directory in /public_html/sites/default/modules/sidecontent/sidecontent.install on line 97.

#1
In Administer > User management > Permisions
Have you enabled 'access side content' for authenticated users?
#2
Feel welcome to re-open this issue, but I think it was just a settings error.
#3
Hi,
we're experiencing the same problem with 6.x-2.0-rc1.
Configuration:
* /admin/user/permissions - "access side content" - checked for all roles; "create side content" - checked for some roles
* /admin/build/block/configure/sidecontent/0 - visible for all roles on all pages
Greetings, -asb
#4
You may need to clear away the cache: administer > site configuration > performance, scroll down the page and CLEAR CHACHED DATA :-)
#5
No, in our setup it was definitely no caching issue; however, we're not using the module (because of this issue) anymore.
Greetings, -asb
#6
"I try to update and i get the error below"
Try to update the module or a node?
Need more info to try and replicate this bug. Anyone else having the same problem?
#7
This is happening to me too, except the issue is that when Side Content is enabled for one node, it appears on all nodes for anonymous users.
After a bit of tweaking I found that clearing the caches fixed it briefly, but disabling the Block Cache in 'Site configuration' -> 'Performance appears to have fixed the problem.
Can anyone else confirm this is the case?
#8
yes... I'm having the problem noted in #7