Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter gusdude

    (@gusdude)

    I was able to find the conflict on a function named google_api_php_client_autoload. When I renamed the function in Simple Calendar, everything worked. I didn’t go back to Private Google Calendars to see if the same conflict was happening. I was getting a different type of conflict that I couldn’t seem to get any indicators what was happening. Private calendars are quite useful for intranets like woffice simply because you are getting information to an internal group of people.

    Thank you again for your response. Like I said before, I think your plugin was great and I would have paid money to have it!!

    Thread Starter gusdude

    (@gusdude)

    Thank you for the response. I solved the issue by using the https://simplecalendar.io/ plugin instead. Both the woffice google login and private google calendars from simple calendar are able to work together with a slight fix on a function name conflict. There is something common with Google authentication that seems to be colliding among various code.

    Gerard

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