The recommended setting for the navigation block cache is 'per-user'. However, the gallery navigation items change depending on whether you are viewing an album or an image etc. If cached in this way these changes are missed. If you happened to view an image just after the cache was cleared then when you view an album you will lose all the 'add album' etc links.

Maybe just change the default? Maybe force it to no-cache? Maybe some other explanatory text?

Comments

kiz_0987’s picture

Priority: Minor » Normal

The cache settings for the nav block do not get saved into the database. It's not clear to me why atm -- maybe something to do with not being called 'block-0'?

profix898’s picture

Assigned: Unassigned » profix898

I just made changes to gallery_block_admin.inc in my working copy (making the image block settings reusable for other submodules). Assigning this to me to avoid conflicts. We should probably force no-cache on the navigation block then, everything else doesnt seem to make sense in this context.

kiz_0987’s picture

Thanks. Maybe page and user (or role) caching could work (since cache options can be ORed together). But it's probably overkill.

profix898’s picture

Good point. Actually all item-specific G2 blocks must be per page. Some others, like AlbumTree, MembersSummary, etc., could even be cached globally. So we should probably not give the user the choice or at least not without excluding certain options. I will make no-cache the default option and the list of selectable option dependent on the actual block.

profix898’s picture

Assigned: profix898 » Unassigned
Status: Active » Fixed

Patch committed to solve the issue. We should observe the queue for support requests about this. Because eventually the new options are not user-friendly enough ...

Anonymous’s picture

Status: Fixed » Closed (fixed)

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