Unable to change registered API key.

  • daicuke

    (@daicuke)


    2 weeks, 3 days ago

    Hello,
    I’m using this plugin to display a calendar on my website.
    I want to change the account that manages my Google Calendar, so I created a new calendar with the new account, set it to public, changed the API key on the connect screen, and correctly updated the ID for each calendar to match the new calendar’s ID, but the calendar still doesn’t display.
    When I enter the old account’s ID into the calendar, the old account’s calendar is displayed. Has the API not been changed?
    I’ve changed the API key multiple times, but it still doesn’t work.
    I’ve also confirmed that the correct API key is registered in the database.

    Please tell me how to solve this…

    • I want to change the calendar displayed by switching API keys.
    • Even after changing the API key, the old calendar is displayed, and the new calendar is not.
    • Google Calendar: Public setting enabled
    • Calendar events: Public setting enabled
    • Google Workspace settings: No blocks, etc.
    • This topic was modified 2 weeks, 3 days ago by daicuke.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support john

    (@johnweru)

    2 weeks, 3 days ago

    Hi there,

    Thanks for reaching out to us and sorry for the issue.

    In this regard, based on your explanation here, this behavior is likely related to caching. Please ensure that you carry out the following upon updating the details:

    Upon carrying out the above, you may also view the calendar in incognito/private mode and see if the correct calendar is rendered.

    I hope this helps.

    Kind Regards

    Thread Starter daicuke

    (@daicuke)

    2 weeks, 3 days ago

    Of course, I’ve tried clearing the cache, clearing the browser cache, and running in private mode, but none of those worked, which is why I’m asking here.
    Please tell me what other methods I can try.

    Plugin Support john

    (@johnweru)

    2 weeks, 3 days ago

    Hi there,

    Thanks for the clarification.

    Just to clarify how the plugin works, changing the API key itself does not determine which Google Calendar is rendered. The calendar that is displayed is mainly dependent on the Calendar ID configured within your WordPress calendar settings. The API key is simply used to authenticate requests to the Google Calendar API.

    Since you have already ruled out caching, the issue is unlikely to be related to the plugin retaining the old API key. Instead, it is more likely that the issue lies with the new Google Workspace account or its configuration. This could be an issue isolated to the particular Google Workspace account or calendar settings rather than the plugin itself.

    As a troubleshooting step, could you please try creating a new test calendar under the same Google Workspace account, add a few test events manually to it and not included by third-parties, make both the calendar and its events public, and then use its Calendar ID in Simple Calendar? If the new test calendar renders correctly, this would indicate that the issue is specific to the original calendar.

    Additionally, please verify the following within your Google Workspace account:

    • Ensure that External sharing for primary and secondary calendars is enabled.
    • Confirm that the calendar’s access permissions for events are set to Make available to public.
    • Verify that the calendar events themselves are not marked as Private.
    • Check whether your Google Workspace administrator has enabled any policies restricting public calendar access or external API access.
    • If you are using a secondary calendar, ensure that it has been properly shared and is accessible outside of your organization.

    Please let us know how it goes.

    Kind Regards

    Thread Starter daicuke

    (@daicuke)

    2 weeks, 3 days ago

    I’ve previously created another calendar using the same account and a different account, and tested it by making the permissions public so that it can be shared.
    As I mentioned earlier, I’ve confirmed that there are no restrictions on access to public calendars or external APIs.
    But it still doesn’t work, which is why I’m asking this question.

    Plugin Support john

    (@johnweru)

    2 weeks, 3 days ago

    Hi there,

    Thanks for staying in touch with us.

    In this case, do you mind submitting a support ticket here: https://simplecalendar.io/contact/ for further checks on this?

    Kind Regards

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

Tags