Hi. I have so many console errors related to amelia. This makes my websites very slow. My plugin is updated to latest version. Please check this and how it can be fixed?
Sorry for the delayed response, we don't work on weekends.
These Errors look like a caching issue.
Please go to ../wp-content/plugins/ameliabooking/public/js/chunks and check the file name. Verify that "amelia-booking-booking-........js" is different than what you see in the console, and if that's correct, it means that the old js files are cached (most likely somewhere on the server).
You can try clearing the site's cache using a caching plugin. If it doesn't help, you will have to reach out to your hosting provider, and see if they can clear the cache on the server (wherever the file is cached).
Could you please provide us with temporary WP Admin access and FTP credentials, so we will look into the issue from the inside? You can post the credentials as a reply to this ticket, just make sure you use private mode.
We don't interfere with any data except for the plugin and, of course, we don't provide login details to a third party.
And also, please send us the URL to the booking page.
We couldn't find any errors related to Amelia on this page anymore:
Please update the plugin to the most recent version 3.2 (which was released yesterday) and clear the cache. If the errors occur again, please send us the exact pages you have these issues on, since the page we inspected works fast and doesn't show errors.
at the moment only one console error appears on that page - Cannot read property 'replaceChild' of null. This Error doesn't affect Amelia's functionality.
We can't get rid of it right now, but the fix will be included in one of the coming updates. So, you can ignore this error until then since it has no impact on the plugin's perfomance.
Hi. I have so many console errors related to amelia. This makes my websites very slow. My plugin is updated to latest version. Please check this and how it can be fixed?
Hi, Hussnain!
Sorry for the delayed response, we don't work on weekends.
These Errors look like a caching issue.
Please go to ../wp-content/plugins/ameliabooking/public/js/chunks and check the file name. Verify that "amelia-booking-booking-........js" is different than what you see in the console, and if that's correct, it means that the old js files are cached (most likely somewhere on the server).
You can try clearing the site's cache using a caching plugin. If it doesn't help, you will have to reach out to your hosting provider, and see if they can clear the cache on the server (wherever the file is cached).
Looking forward to hearing from you.
Hi, I checked but the file name in the plugin directory is the same as what I see in the console. Please see the attachement.
Hi, Hussnain!
I have to contact my colleagues regarding your case.
I will get back to you at the earliest possible time.
Best Regards.
Hi, Hussnain!
Could you please provide us with temporary WP Admin access and FTP credentials, so we will look into the issue from the inside? You can post the credentials as a reply to this ticket, just make sure you use private mode.
We don't interfere with any data except for the plugin and, of course, we don't provide login details to a third party.
And also, please send us the URL to the booking page.
Looking forward to hearing from you.
Hi again, Hussnain!
I forwarded these credentials to our developers.
I will inform you once I receive their response.
Best Regards.
Hi, Hussnain!
We couldn't find any errors related to Amelia on this page anymore:
Please update the plugin to the most recent version 3.2 (which was released yesterday) and clear the cache. If the errors occur again, please send us the exact pages you have these issues on, since the page we inspected works fast and doesn't show errors.
Best Regards.
Please check this page: https://fitcyhealth.com/mental-health-uros/
Hussnain,
at the moment only one console error appears on that page - Cannot read property 'replaceChild' of null. This Error doesn't affect Amelia's functionality.
We can't get rid of it right now, but the fix will be included in one of the coming updates. So, you can ignore this error until then since it has no impact on the plugin's perfomance.
Best Regards.