I just upgraded to v2.9, and cannot access any of the Amelia options with the exception of the Settings page. Dashboard, Calendar, Appointments, etc. all show nothing but a blank screen.
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, like in your case.
I just upgraded to v2.9, and cannot access any of the Amelia options with the exception of the Settings page. Dashboard, Calendar, Appointments, etc. all show nothing but a blank screen.
Actually, Dashboard shows up (and settings), but nothing else.
I figured it out. Chrome's cache needs to be cleared after the update for some reason. Never seen this before with any other plugin.
Hi Phil, thank you for your purchase!
Sorry for the late response.
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, like in your case.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables