Not a problem but some advice to other newbies to save a stressful couple of hours and maybe a glitch for developers to look at:
If you are testing your Amelia booking system and you input fake names and mail addresses to test, it may appear that you lose your services / categories / employees when you return to set up, Booking pages still work, but you cannot see services / categories and employees and cannot add new services without recreating a new category.
You can get them back by deleting all your "fake" customers.
I seems Amelia thinks you are the last (fake) person to book a service and not the administrator when you then return to managing your Amelia settings. It probably reads your IP address and links your name to that so removes you from seeing your services / categories / employees. I am integrating with WooCommerce so that may also have something to do with it.
Best to test in incognito mode or the equivalent (I am guessing here, I have not yet tried that but guess it would work).
Just a note to Amelia, I was on the verge of cancelling when I realised what was happening. The plugin is great but it may be worth warning people of this to prevent a bit of frustration (unless you have a warning somewhere and I have just missed it, which is possible).
Thank you for your purchase, and for this heads-up to other customers.
Something like this can only happen if you book an appointment from front-end while you're still logged into your Administrator account. If you use your administrator email address, there's even more chance that this will happen.
My guess is that "Automatically create Amelia Customer user" option is enabled in Amelia Settings/Roles/Customer, so when you booked an appointment it created a customer, and linked your Administrator account to that customer. Since the customers don't have any capabilities Admins have, the plugin saw the linked customer account, and applied the limitations to your admin user.
It's not advisable to test the plugin while logged into any WordPress role, specifically Administrator, and I know how frustrating this might have been for you. I'm glad to hear you were able to resolve the issue quickly, and keep the plugin.
I personally tried replicating this numerous times locally, but I was never able to. Fact is that it does happen, but no matter what I tried, I failed. If you're willing to record your screen for me, so I can replicate the issue locally, I'd be grateful! When we manage to replicate it, we'll check with our developers if there's anything that can be done to avoid this in the future.
Not a problem but some advice to other newbies to save a stressful couple of hours and maybe a glitch for developers to look at:
If you are testing your Amelia booking system and you input fake names and mail addresses to test, it may appear that you lose your services / categories / employees when you return to set up, Booking pages still work, but you cannot see services / categories and employees and cannot add new services without recreating a new category.
You can get them back by deleting all your "fake" customers.
I seems Amelia thinks you are the last (fake) person to book a service and not the administrator when you then return to managing your Amelia settings. It probably reads your IP address and links your name to that so removes you from seeing your services / categories / employees. I am integrating with WooCommerce so that may also have something to do with it.
Best to test in incognito mode or the equivalent (I am guessing here, I have not yet tried that but guess it would work).
Just a note to Amelia, I was on the verge of cancelling when I realised what was happening. The plugin is great but it may be worth warning people of this to prevent a bit of frustration (unless you have a warning somewhere and I have just missed it, which is possible).
Hello Tim
Thank you for your purchase, and for this heads-up to other customers.
Something like this can only happen if you book an appointment from front-end while you're still logged into your Administrator account. If you use your administrator email address, there's even more chance that this will happen.
My guess is that "Automatically create Amelia Customer user" option is enabled in Amelia Settings/Roles/Customer, so when you booked an appointment it created a customer, and linked your Administrator account to that customer. Since the customers don't have any capabilities Admins have, the plugin saw the linked customer account, and applied the limitations to your admin user.
It's not advisable to test the plugin while logged into any WordPress role, specifically Administrator, and I know how frustrating this might have been for you. I'm glad to hear you were able to resolve the issue quickly, and keep the plugin.
I personally tried replicating this numerous times locally, but I was never able to. Fact is that it does happen, but no matter what I tried, I failed. If you're willing to record your screen for me, so I can replicate the issue locally, I'd be grateful! When we manage to replicate it, we'll check with our developers if there's anything that can be done to avoid this in the future.
Thanks again!
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