Great module - it's almost perfect for our needs. However...
I set "access similarterms content" permission to both "Anonymous" and "Authenticated", but the block does not appear to anonymous users.
Even tried setting Block visibility, though it indicates visibility defaults to all users.
Is there another setting somewhere that I'm missing?
Thanks!

Comments

rmiddle’s picture

rmiddle commented

It is likely 1 of 2 issues. 1) #309180: blocks disappeared or 2) Block Cache isn't updating turn off block cache and see if that makes a diff.

Thanks
Robert

rmiddle’s picture

rmiddle commented
Status: Active » Postponed (maintainer needs more info)
petertj’s picture

petertj commented

I also experienced this problem last night, and yes, turning off block caching makes it behave properly.

I realized this was probably the case because the block was not updating when navigating nodes, and failed to go away when not on a node with appropriate taxonomy - i.e. it was visible on taxonomy/term which is not its normal behavior.

rmiddle’s picture

rmiddle commented

This issue is suppose to be fixed in Drupal 6.4 but the block cache code under 6 still seems to be a little funky.

Thanks
Robert

petertj’s picture

petertj commented

Follow-up question: shouldn't block caching in core handle this automatically? Or does the module need to implement something in order to support block caching?

petertj’s picture

petertj commented

Whups, rmiddle and I posted at the same time. Is this already discussed in an issue for the core team?

rmiddle’s picture

rmiddle commented

The Block gets cached automatically by core. I turned off the block cache based on the api requirements but there was a glitch in core that meant that core didn't always pay attention to the cache settings and sometimes caches even when you tell it not too. This effected views as well. It is supposed to be fix in 6.4.

Thanks
Robert

rmiddle’s picture

rmiddle commented

#6

Read this ticket for the details.

#277573: Block gets cached causing invald results under 6.x

rmiddle’s picture

rmiddle commented
Status: Postponed (maintainer needs more info) » Fixed
petertj’s picture

petertj commented

Thanks for the link - however, that issue appears to have been closed, and now this one is marked "fixed"... but there still appears to be a problem.

Here's what I'm seeing in a totally current Drupal6.4 installation with block caching on:
- block doesn't appear to anonymous user, even though no access limit is set
- block always appears to authenticated user, but doesn't update when changing nodes or taxonomies.

rmiddle’s picture

rmiddle commented

Patertj,

As I said. It is supposed to be fixed in 6.4. I have code installed that disables the cache for Drupal 6. Try running the DB update from that ticket and see if it fixes your issue.

Thanks
Robert

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.