I have the permissions set for anonymous users to view blocks created Agenda module, but for some reason i can only display the list of of events when I'm logged in as a user. As soon as I logout as a user and display my home page where the Agenda block is displayed the block just says "No Upcoming Events".

Comments

glidetothehoop’s picture

glidetothehoop CreditAttribution: glidetothehoop commented

Update: It was working for a while and now it "No Upcoming Events" is showing regardless of anonymous user is browsing or if a registered user on the Drupal site is logged in. It seems to be intermittent.

glidetothehoop’s picture

glidetothehoop CreditAttribution: glidetothehoop commented

Update2: I did determine one thing...if I going into the Administrative menu and go to Performance and clear all cache (including pages for anonymous users and cache blocks, then when the home page refreshes that has the Agenda block it shows "No Upcoming Events". Eventually the events show back up, but can someone tell me why after saving a change within the Agenda configuration AND then flushing my cash...why don't the events get listed right away? I don't understand the delay.

Any explanation that anyone can give would be greatly appreciated.

avilao’s picture

avilao CreditAttribution: avilao commented

I have the same issue.

lanarenee’s picture

lanarenee CreditAttribution: lanarenee commented

Same problem here though it is not isolated to anonymous users - it is for all users. When I run debug, I get the following:

Found following calendars:
Array
(
[0] => enagy@virginia.edu
)
Fetching feed from http://www.google.com/calendar/feeds/enagy%40virginia.edu/public/full?hl...
Warning: Failed to load XML

I have tried disabling the module, removing its files completely from the server, downloaded the most up to date version, reloading and re-enabling. Still does not work after clearing the cache countless times.

The calendar is shared publicly and I have also test other calendars that are shared publicly.

This is occurring on both Drupal 6 single site, and sites on Drupal 7 multi-site

8bernard8’s picture

8bernard8 CreditAttribution: 8bernard8 commented

same issue. No upcoming events. Debug doesn't show any information.
Somebody has ideas why it doesn't work?

stinky’s picture

stinky CreditAttribution: stinky commented

Same here.

Mattin’s picture

Mattin CreditAttribution: Mattin commented

... and the same here on drupal 7.32 and 7.34. It worked fine until last weekend, but on Monday or Tuesday no events are shown and debug doesn't connect. Perhaps Google has made some changes? Any drupal-modules are the latest version.

Frief’s picture

Frief CreditAttribution: Frief commented

Have a look at THIS https://www.drupal.org/node/2376795

guschilds’s picture

guschilds CreditAttribution: guschilds commented
Version: 7.x-1.4 » 7.x-2.x-dev
Category: Support request » Bug report
Status: Active » Postponed (maintainer needs more info)

If you're experiencing this problem, please see #2376795: Unable to Connect to Google (Calendar API v2 is deprecated) and make sure you've upgraded to the 7.x-2.0-beta1 (or later) release. Please be aware that the 'access agenda content' permission is not working as expected in that release (see #2388291: 'access agenda content' permission is not respected).

Postponing until #2388291: 'access agenda content' permission is not respected is fixed and this can be tested again. I don't think this bug will still exist at that time.

guschilds’s picture

guschilds CreditAttribution: guschilds commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

The original issue was not related to the deprecated API, but everything from comment #3 and on was. This has been resolved. See the project page and #2376795: Unable to Connect to Google (Calendar API v2 is deprecated) for more information. #2388291: 'access agenda content' permission is not respected was also just fixed, but that issue would not have been causing the original problem. It is likely that the original problem was caused by connectivity issues with the API. I'm going to close this because the module has been rewritten to work with a different API. Please open a new issue for any similar problems and include thorough steps to reproduce. Thanks!