Hello Laura,

Thank you for reaching out to us.

Instead of the http:// beginning of the URL, it has to start with the https://.

Please test that out and let me know if it works or not.

In regards to iCal sync, Unfortunately, there is currently no such option with Amelia's built-in features. You can suggest that feature on the following link: https://features.wpamelia.com/ 

We carefully follow suggestions from our customers and the more votes the feature gets, the more priority we put on implementing that feature in one of the future updates.

Hello Laura,

Apologies for the delayed answer. Uros is out of the office, i will fill in for him.

As already stated, the URI needs to start with https:// instead of http://. Google Console doesnt recognize the URI with http. Unfortunatelly, there is no other way to solve this, since this is related to the invalid URI. 

Make sure that the URI is with https on both Amelia and console, and try like that.

Hello Laura,

Apologies for the delayed answer, i can see the screenshots. Can you please share access to your Google Cloud console? Unfortunatelly, there is no other way of fixing this, since is related to the URI mismatch, so we would like to troubleshoot it on both ends.

Thanks. Looking forward to your reply.

Hello Laura,

I'm looking for the Google Console access, but seems like it can't find the invite in my inbox. If i understand it correctly, you were able to change the credentials for Calendar API, and how it seems to be working properly?

Hello Laura,

Thanks for the access, but it requires confirmation from your side 

Hello Laura,

Looks like we are having a hard time matching our timing. I will make sure that i request access tomorrow morning at 10AM Central European Standard Time (not sure about your timezone), so you can confirm the access.

Thanks

Hello Laura,

15:00 to 17:00 tomorrow works for me, but here is something that you can try since you are going to troubleshoot it.

Try adding the "www." in front of "fisioterapiayosteopatiabarcelona.es" in URL. Make sure that it's the same URI in both places. 

Let me know if it works or i will enter tomorrow to troubleshoot further.

Hello Laura,

Great to hear that! Finally, we can solve the issue with URI and Google Calendar.

Let me give you more information regarding the Google Calendar sync and how it works. The sync between Google Calendar and Amelia only works from the moment when the integration has been made. That means that the appointments that were made prior to the integration, unfortunatelly, won't be integrated in Google Calendar. Only the appointments that are made with the successful integration will be registered in Google Calendar and Amelia.

The same Google account you've used to configure Google Calendar API needs to be used to connect with employees since the Client ID and Secret ID credentials from this console account have been used in Amelia. This will secure the connection between these two, but if you want to connect other employees with their calendars, you can just simply select "use another account" once you click on "sign in to calendar".

You would need to create a separate account for employee of course, otherwise, if you connect multiple employees to same calendar, they will share the same calendar and "busy" slots. 

If Employee already has events in the Google calendar marked as busy, those will not be available for booking in Amelia – this will prevent overbooking. Rescheduling, canceling, or deleting the appointment needs to be done in Amelia. Suppose you reschedule the appointment in Google Calendar. In that case, that will not reflect in Amelia, but if you reschedule the appointment in Amelia, it will be updated in Google Calendar as well.

I hope it helps. Please, let me know if you have any other questions.

Hello Laura,

Thanks for the feedback! That's interesting, indeed. We never thought that it would work like this. We could use this "hack" for future use cases. For the recurring appointment function, i see that my colleague is working on this issue already. He will get back to you as soon as possible.

Anyway, make sure that you reach out to us for any other issues or questions that you have.

Hello Laura,

I've just checked with the developers

You can add this hook:

function amelia_add_previous_appointments($newUser, $oldUser)
{
    $container = require AMELIA_PATH . '/src/Infrastructure/ContainerConfig/container.php';
    $googleCalendarService = $container->get('infrastructure.google.calendar.service');
    $appointmentRepo = $container->get('domain.booking.appointment.repository');
    
    if (!empty($newUser['googleCalendar']) && !empty($newUser['googleCalendar']['calendarId'])) {
       $appointments = $appointmentRepo->getFiltered(['providers' => [$newUser['id']]]);
       foreach ($appointments->getItems() as $appointmentObject) {
       if (!$appointmentObject->getGoogleCalendarEventId()) {
           $googleCalendarService->handleEvent($appointmentObject, 'appointmentAdded');
        }
      }  
   }
}

add_action('amelia_after_provider_updated', 'amelia_add_previous_appointments', 10, 2);

The action is triggered when the employee is edited and saved. However, the first time you connect to the calendar and click save the loading will take a while until it adds all the previous appointments. 

I hope it helps.

Hello Laura,

Yes, unfortunately, the sync will be pushed whenever you edit the employee. I know that is not a great workaround, but it's the only way. I see that you already have a ticket opened regarding the recurring appointment option, i guess this would be a better option to sync the previous appointments, for sure. My colleague is already working on fixing that issue, we will get back to you as soon as possible. 

Hello Laura,

Well, to be honest, it's a tricky part to use "recurring" appointment workaround for loading the old appointments. We have never used this before, but the Google Calendar itself can be buggy, indeed. I guess you've already tried reconnecting the Google Calendar to employee? Increasing the maximum number of events in Google Calendar? I would have to double-check with the developers if this workaround is usable and it doesn't have any other consequences.

Hi again Laura.

We sincerely apologize for the oversight, and we appreciate your feedback. We have taken action to improve the documentation based on your suggestions. Now, there is a "Key Points to Remember" section at the beginning of the article, ensuring that important information is highlighted upfront before diving into the integration setup process.

Regarding your suggestions:

1. Developing a solution to trigger a complete reload of appointments poses technical challenges. There is a limit to the number of requests that can be sent to a calendar per minute, so if there are a lot of appointments to be moved, there's still a possibility that they won't all be updated. Some Amelia users have limited website memory (512 or even 256 MB), which could lead to performance issues. It represents a challenge because there would be a hook that refreshes every time there is a change in either the Appointments section or in the Employee's profile. This would result in a lot of traffic and memory usage, and it could lead to critical errors for those users. While we do have plans to implement a full 2-way sync and handle retroactive appointment additions and calendar changes, we must proceed cautiously to mitigate risks. We understand your frustration and are committed to improving features, but we must consider the diverse user base and potential impacts of changes. Our WordPress user base comprises tens of thousands of users, each with unique needs and configurations.

2. Implementing bulk editing for appointments is a valid suggestion. However, the complexity arises from the checks Amelia performs when creating or editing appointments. For instance, if you wish to reassign 50 appointments to a different employee, ensuring the new employee has availability for each slot can be challenging. Each modification could result in blank dates or times, necessitating manual adjustments. While we appreciate your feedback and understand the need for efficiency, we must balance this with maintaining system stability and user experience.

We appreciate your perspective, and your suggestions are valuable to us. When working on integrations and features, we consider numerous factors that can impact our diverse user base. While your use case aligns with many others, making changes to accommodate specific needs could potentially affect users with different requirements. We aim to maintain a balance between addressing individual needs and ensuring the overall functionality meets the varied needs of our users.

Additionally, implementing changes carries the risk of conflicts or unexpected issues that may arise from modifications to the existing code. Our priority is to ensure system stability and prevent any disruptions that could occur as a result of changes.

Your understanding is greatly appreciated as we navigate these considerations. Your suggestions have been promptly shared with our management and development teams for further evaluation. We are committed to resolving these matters in a timely and precise manner.

Thank you once again for your valuable input and for being a part of the Amelia community.

Hello Laura,

Thank you for providing valuable information. We do agree that integration with Google Calendar is not complete and it can be improved. Certainly, we will take this information in consideration when improving the integration and other features.

I will close this one, but don't hesitate to reach out regarding any questions or issues that you have.

Thank you and have a nice day!