Closed (fixed)
Project:
Gallery
Version:
5.x-2.0
Component:
Code / API
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Feb 2008 at 17:18 UTC
Updated:
23 Feb 2008 at 23:13 UTC
I have 7 Albums...they all have the exact same permissions. I can navigate to my G2 installation directly and see all of them without logging in.
If I go back to Drupal only 5 of them show up for an unauthenticated user. When I log in they are all there but I want them all visible regardless.
What am I doing wrong?
~Beka
PS: I did crosspost this to the Gallery > Drupal support forum but it looks like that place is a little dead. I thought I might have more luck here.
Comments
Comment #1
bekabug commentedOk... I have worked around this by only adding albums from the G2 installation and not from within Drupal. As soon as I added a test album from G2 directly, all the other albums showed up in Drupal.
I deleted the test album from within G2...authenticated users do not see the Test album any longer but if you aren't logged in you see the test album. The test album goes to either an Empty page within drupal that is titled Gallery or a G2 error. It has been flip flopping on the error/page that it gives me. What is going on!?
Is this normal?
Comment #2
profix898 commentedAre you talking about the menu links to G2 albums in Drupal as generated by the GalleryMenu module? Or does this happen for the actual "Gallery" page as well?
P.S. The support forums are not really dead, but unfortunately there are very few people helping with support on the gallery module for Drupal :(
Comment #3
profix898 commentedIts indeed a bug in the gallery module (and one that must be around for a while). If the page cache is enable in Drupal anonymous users are served with a cached version of the requested page directly. What means they dont see changes made in G2 until the cache is invalidated and rebuilt. Drupal does this whenever a node is being added/updated/deleted, but gallery module does not for G2 items.
I just committed a patch to fix this bug for the 5--2 branch. Please try and reopen in case the issue persists.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.