Making WordPress.org

Opened 8 months ago

Closed 8 months ago

#5743 closed defect (reported-upstream)

Not possible to subscribe to meetings of certain teams with Google Calendar

Reported by: psrpinto Owned by: psrpinto
Milestone: Priority: normal
Component: Make (Get Involved) / P2 Keywords:


The Upcoming WordPress Meetings page allows subscribing to the meetings of individual teams using Google Calendar.

However, for certain teams, Google Calendar erroneously states that the user does not have permission to subscribe to the calendar:


Steps to reproduce:

  1. Go to https://make.wordpress.org/meetings
  2. Select Core under "Filter by team"
  3. Click on the "+ Google Calendar" button
  4. Click "Add" in the popup that appears
  5. The "Request access" popup is displayed

This issue affects the following teams:

  • All teams
  • Core
  • Meta

For other teams, subscribing with Google Calendar works as intended.

Change History (6)

#1 @tobifjellner
8 months ago

Seems to be those teams that contain sub-teams.

Last edited 8 months ago by tobifjellner (previous) (diff)

#2 @psrpinto
8 months ago

It seems the calendar has no concept of sub-teams, so I don't think that's the culprit.

#3 @psrpinto
8 months ago

I downloaded the meetings-core.ics file and put it on Dropbox. I then imported the Dropbox public link into Google Calendar:

(not an actual Dropbox link)

This worked correctly, which proves (?) the issue is not related to the content of the files, since the Dropbox file should be exactly the same as the file Google Calendar retrieves through the "+ Google Calendar" button:


Maybe HTTP Response headers are the culprit. Will continue researching.

#4 @dd32
8 months ago

The meeting calendar is developed here: https://github.com/Automattic/meeting-calendar

@psrpinto Would you be able to create this ticket upstream there?

#5 @psrpinto
8 months ago

As requested, moved ticket to GitHub: https://github.com/Automattic/meeting-calendar/issues/115

Last edited 8 months ago by psrpinto (previous) (diff)

#6 @psrpinto
8 months ago

  • Resolution set to reported-upstream
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.