As previously announced via banners and our newsletters, support is no longer available through this platform.

For easier navigation, you can still click on "Submit a Ticket" here, choose the appropriate category, and you'll be redirected to the correct support channel for your plugin.

You can still access your previous tickets and browse public tickets, but please note that responding to tickets is no longer possible.

Paid customers: Please log in to your store account for support.

Pre-purchase questions: Use the support widget in the bottom-right corner of our websites:
https://wpamelia.com
https://wpdatatables.com
https://wpreportbuilder.com

Okay
  Public Ticket #2613396
Calendar update issue
Closed

Comments

  •  2
    Curtis started the conversation

    So when people book online theirs no issue with the appointment showing up in my google calendar, though theirs an issue when an appointment which was created under someone else's schedule is then rebooked to my own schedule.

  • [deleted] replied

    Hello Curtis, 

    There isn't a possibility of moving events in Google calendar from one employee to another automatically, when the employee assigned is changed in Amelia appointments, unfortunately, with the current Google synchronization. We are aware of this limitation, and this is in our to-do list for future improvements of the plugin, but for now we can't say exactly when this will be implemented. 

    If you have any other questions or concerns feel free to open a new ticket and we will gladly help out.

  •  2
    Curtis replied

    Why won't the plugin simply delete the other appointment in one calendar and create a new one in mine?

    Just add an if then that condition.


    I don't see why i would need to go delete the entire appointment on my side then re create it

  • [deleted] replied

    Hello Curtis,

    This is the way how Google sync in Amelia is implemented and working , employee change in Amelia can't update the Google events, and at the moment there isn't anything that could be done to change this, unfortunately . But, like I mentioned,  this is in our to-do list for future improvements of the plugin and I hope it will be implemented soon. Sorry for the extra work this creates.