"Gallery Block" not visible to anonymous users

First of all, check that in the section blocks your check the option, show to anonymous users.
Then go to admin/content/node and select your gallery Gallery, check Assist: Public or Public to all.

Hello,

I have the same issue. In Gallery Block -> Settings I tried enabling "Show only for certain roles" -> anonymous and registered, but that doesn't help (I want to show it for all anyway)

Anonymous users can view the Gallery node fine (public for all).

I'm using current 6.x-dev from Nov 11

I have the same issue in version 1.18 where the gallery is not visible to anonymous users. If I log in as an authenticated user with the same privileges as the anonymous user then they can see the gallery.

Observations and Steps: I created a new drupal installation (6.19) as a test site with a fresh installation of Gallery Assist and Gallery Assist Lightboxes and created a gallery with a few pictures. I also installed the devel module and added some debug code to the function gallery_assist_check_public_status() in the file gallery_assist.module. When observing the contents of the variable (approx line 3068 in gallery_assist.module) $node->gallconf[$node->type]['ga_public_status'] I noticed that for users that are logged in it has the correct value of 2 (Public for all) and for the anonymous user the value is NULL.

I'm wondering why the anonymous user would see this value as NULL and an authenticated user sees the correct value?

As a temporary workaround I changed line 3068 from:
$ga_public_status = $node->gallconf[$node->type]['ga_public_status'];
TO:
$ga_public_status = 2;

so my clients gallery is viewable to all anonymous users.

Thank you so much to the contributors who created this module I use it often!!

This worked for me too-Thanks

I have the same issue.

Thanks jasonl, my solution was:

in file:

./sites/all/modules/gallery_assist/gallery_assist.module

change line 3071:

$ga_public_status = $node->ga_public_status;

by:

$ga_public_status = $node->data['ga_public_status'];

What is the solution for 6.x.1.19-beta5 version?