Support » Plugin: Timely All-in-One Events Calendar » Calendar navigation stopped working when site moved to HTTPS

  • Resolved lisabeewd

    (@lisabeewd)


    We just converted our website to full HTTPS and found the navigation buttons in our calendar are not working. We are unable to move from one month to another or from a Day view to a Month view. When looking at the source code we see the json links are set to HTTP. Our WordPress Home and Site URLs include the HTTPS so we are wondering if this is a calendar cache issue.

    We know it has to do with the HTTPS vs HTTP because when we moved our website back to HTTP the calendar navigation started working again. (We are at Timely All in One Event Calendar version 2.1.9)

    We are looking for what we need to do with the AI1EC plugin when we move our website back to HTTPS.

    https://wordpress.org/plugins/all-in-one-event-calendar/

Viewing 2 replies - 1 through 2 (of 2 total)
  • We use

    get_page_link();

    to create the links. I think that uses home_url(). Can you check what does calling get_page_link( $cal_id ); returns with $cal_id being equal to the calendar page id

    Thread Starter lisabeewd

    (@lisabeewd)

    Aha … I think we discovered the problem. There seems to be a conflict with the WordPress HTTPS plugin. Once we deactivated the plugin, everything seemed to work fine.

    I did check what is returned when using get_page_link() like you suggested. I found it returned HTTP even though the home and site urls were set to HTTPS. It seems the function actually returns the link based on the page protocol and when we deactivated the HTTPS plugin (which wasn’t actually allowing us to access the test page using HTTPS) and accessed the test page with that code using HTTPS then it returned the link with HTTPS.

    It seems that the AI1EC plugin is not the one causing the issue. Thank you for responding so quickly to our inquiry!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Calendar navigation stopped working when site moved to HTTPS’ is closed to new replies.