This error can occur in Console log but it doesn't affect the functionality of Amelia nor your website's functionality. Sorry about that, our developers will try to find a way to remove the error in one of the future versions of Amelia.
Upon activation, Amelia creates .js files in ../wp-content/plugins/ameliabooking/public/js/chunks/ folder (it also creates the CSS folder which is used for getting the styles of the front-end plugin), and they are cached by your website and browser.
Those files are related to all Amelia's front-end views (booking view, catalog view, search view, and so on), and they are named like this (for example):
amelia-booking-booking-d75fee1483afaeb1628f.js
When you update the plugin, those files are deleted and replaced with the new files, and their names change, so your cached page may still be looking for amelia-booking-booking-d75fee1483afaeb1628f.js while it is actually amelia-booking-booking-g35odd2568ljo9en25s2ef.js (again - an example).
Deleting the cache is not mandatory for all installations, but it can happen, so you probably need to delete cache, and the issue should be resolved.
Hi, i have console log error form Amelia Js, can u check this ? see image in copy
Hi
Thank you for reaching out to us.
This error can occur in Console log but it doesn't affect the functionality of Amelia nor your website's functionality. Sorry about that, our developers will try to find a way to remove the error in one of the future versions of Amelia.
Upon activation, Amelia creates .js files in ../wp-content/plugins/ameliabooking/public/js/chunks/ folder (it also creates the CSS folder which is used for getting the styles of the front-end plugin), and they are cached by your website and browser.
Those files are related to all Amelia's front-end views (booking view, catalog view, search view, and so on), and they are named like this (for example):
amelia-booking-booking-d75fee1483afaeb1628f.js
When you update the plugin, those files are deleted and replaced with the new files, and their names change, so your cached page may still be looking for amelia-booking-booking-d75fee1483afaeb1628f.js while it is actually amelia-booking-booking-g35odd2568ljo9en25s2ef.js (again - an example).
Deleting the cache is not mandatory for all installations, but it can happen, so you probably need to delete cache, and the issue should be resolved.