I have a problem when adding a new customer via the back end on a client's website which is still in development. I want the emails and phone to be mandatory fields, but even though I have set these as mandatory in general settings, it still doesn't work.
I saw on an old ticket one of the support people recommended deactivating Amelia plugin, then purge cache, re-activate the plugin, and clear cache again, but that hasn't worked.
I've even disabled the caching plugin (Siteground Optimizer), then switched off these fields as mandatory, saved, then re-enabled them, and still no joy.
My client keeps on forgetting to capture this information when bookings come in via phone call, so customers aren't getting notifications, and/or the client can't phone them! This is the obvious answer, but I'm scratching my head now.
This needs to be set for each booking form separately in customize section. If you are using for example catalog form and you set this in step by step those settings will not apply then because you did not customize the catalog form.
they are enabled on every booking form in the customiser, even events and booking version 1, as well as general settings. However, these 2 fields are still not mandatory when adding a customer manually in the back end.
Please send the URL of that page and also please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.
My apologies for the oversite, these fields can not be set as mandatory for the backend only for customers on the front end. This is designed like that because this is your choice if you are going to fill in those data or not on the backend but you can force your customers to enter those data on the front if you wish.
In light of this, we encourage you to kindly consider submitting this valuable suggestion as a feature request through the following link: https://features.wpamelia.com/. The prioritization of feature development is greatly influenced by the number of customer requests received. By participating and expressing your support, you contribute significantly to the potential expedited implementation of this feature.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
I'm not sure I agree this is a feature request but an oversight by yourselves (not trying to be rude).
If any business owner sets it to mandatory to capture the email and/or the phone number from the customers in the front end, then they have made a conscious decision that this information is needed for their business, so would naturally expect to capture it via the add new customer if a customer phoned in for a booking, but could be easily missed due to human error.
The only time I could see your point is if the business didn't offer the ability to phone in to book, and only offered bookings online. In that case you wouldn't ever use the add new customer form.
Surely this is simple to add by your dev team to the existing logic of making email and/or phone mandatory in the general settings. Especially as your existing setup isn't logical, and that has been shown time and time again in the number of support tickets raised, where people make these 2 fields mandatory in general settings and keep asking you why this isn't working on the frontend, and the answer is you ALSO have to make them as mandatory on the customizer forms. This to me seems to make the general settings options irrelevant, so might as well be used for the 2 fields in the add new customer.
Adding this as a feature request will either take years to get traction or never get implemented.
I sincerely appreciate your input and understand your concerns. We do receive a multitude of diverse proposals from our valued customers, and there is often a perception that implementing these suggestions might take an extended period. It's important to note that our goal is to cater to the collective needs of our user community, rather than fulfilling individual requests on a daily basis, which would be impractical.
In order to streamline this process, we kindly request that you, like all our esteemed users, submit your suggestions through the designated channel where others also contribute their ideas.
Regarding your specific point about the general settings and customizable forms, your observation is indeed valid. When Amelia was initially introduced, the booking forms were more straightforward, requiring only general settings. However, over time, we have expanded our offerings to include 8 different forms, including both 1.0 and 2.0 versions. This expansion provides users with the flexibility to employ distinct permissions for various booking forms. Consequently, some users may require mandatory fields on one form while not on another.
Regrettably, we currently have a single backend system that serves all users, making it challenging to set mandatory fields for some users without affecting others. Our philosophy aligns with the expectation that all users' employees will follow established procedures and fulfill their responsibilities diligently. Therefore, if a field is said to be mandatory, it is assumed that employees will complete it as part of their job.
However, I would like to assure you that we are actively planning a redesign of our backend system, which will be undertaken once our front-end redesign is completed. This redesign aims to address the issues customers raised and provide a more versatile solutions. We kindly urge you to share your suggestion through the link we provided, although the choice is ultimately yours, and we respect your decision. Your feedback is valuable as we strive to enhance our platform to better meet your needs and those of our user community.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
Thank you for understanding and we will close this one also but as we mentioned should you have any further inquiries, feel free that you open separate tickets for each question and we will gladly help you there.
Hi,
I have a problem when adding a new customer via the back end on a client's website which is still in development. I want the emails and phone to be mandatory fields, but even though I have set these as mandatory in general settings, it still doesn't work.
I saw on an old ticket one of the support people recommended deactivating Amelia plugin, then purge cache, re-activate the plugin, and clear cache again, but that hasn't worked.
I've even disabled the caching plugin (Siteground Optimizer), then switched off these fields as mandatory, saved, then re-enabled them, and still no joy.
My client keeps on forgetting to capture this information when bookings come in via phone call, so customers aren't getting notifications, and/or the client can't phone them! This is the obvious answer, but I'm scratching my head now.
Any recommendations?
Thanks
Hello,
Thank you for reaching out to us.
This should be an easy fix. YOu need to set that mail and phone fields are mandatory in customize section as well like this
This should help.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best.
Have a nice day.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
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
Hi Marko,
Sorry that was already done in both the customizer and general settings both phone and email are set to mandatory.
Mandatory for these 2 fields only works on the frontend, but not when you add customer in the backend.
Hello again,
This needs to be set for each booking form separately in customize section. If you are using for example catalog form and you set this in step by step those settings will not apply then because you did not customize the catalog form.
Can you please check this and let us know.
Looking forward to your reply.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
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
Hi Marko,
they are enabled on every booking form in the customiser, even events and booking version 1, as well as general settings. However, these 2 fields are still not mandatory when adding a customer manually in the back end.
Hello again,
Please send the URL of that page and also please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.
Looking forward to your reply.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
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
Hello again,
My apologies for the oversite, these fields can not be set as mandatory for the backend only for customers on the front end. This is designed like that because this is your choice if you are going to fill in those data or not on the backend but you can force your customers to enter those data on the front if you wish.
In light of this, we encourage you to kindly consider submitting this valuable suggestion as a feature request through the following link: https://features.wpamelia.com/. The prioritization of feature development is greatly influenced by the number of customer requests received. By participating and expressing your support, you contribute significantly to the potential expedited implementation of this feature.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best.
Have a nice day.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
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
Hi Marko,
I'm not sure I agree this is a feature request but an oversight by yourselves (not trying to be rude).
If any business owner sets it to mandatory to capture the email and/or the phone number from the customers in the front end, then they have made a conscious decision that this information is needed for their business, so would naturally expect to capture it via the add new customer if a customer phoned in for a booking, but could be easily missed due to human error.
The only time I could see your point is if the business didn't offer the ability to phone in to book, and only offered bookings online. In that case you wouldn't ever use the add new customer form.
Surely this is simple to add by your dev team to the existing logic of making email and/or phone mandatory in the general settings. Especially as your existing setup isn't logical, and that has been shown time and time again in the number of support tickets raised, where people make these 2 fields mandatory in general settings and keep asking you why this isn't working on the frontend, and the answer is you ALSO have to make them as mandatory on the customizer forms. This to me seems to make the general settings options irrelevant, so might as well be used for the 2 fields in the add new customer.
Adding this as a feature request will either take years to get traction or never get implemented.
Hello again,
I sincerely appreciate your input and understand your concerns. We do receive a multitude of diverse proposals from our valued customers, and there is often a perception that implementing these suggestions might take an extended period. It's important to note that our goal is to cater to the collective needs of our user community, rather than fulfilling individual requests on a daily basis, which would be impractical.
In order to streamline this process, we kindly request that you, like all our esteemed users, submit your suggestions through the designated channel where others also contribute their ideas.
Regarding your specific point about the general settings and customizable forms, your observation is indeed valid. When Amelia was initially introduced, the booking forms were more straightforward, requiring only general settings. However, over time, we have expanded our offerings to include 8 different forms, including both 1.0 and 2.0 versions. This expansion provides users with the flexibility to employ distinct permissions for various booking forms. Consequently, some users may require mandatory fields on one form while not on another.
Regrettably, we currently have a single backend system that serves all users, making it challenging to set mandatory fields for some users without affecting others. Our philosophy aligns with the expectation that all users' employees will follow established procedures and fulfill their responsibilities diligently. Therefore, if a field is said to be mandatory, it is assumed that employees will complete it as part of their job.
However, I would like to assure you that we are actively planning a redesign of our backend system, which will be undertaken once our front-end redesign is completed. This redesign aims to address the issues customers raised and provide a more versatile solutions. We kindly urge you to share your suggestion through the link we provided, although the choice is ultimately yours, and we respect your decision. Your feedback is valuable as we strive to enhance our platform to better meet your needs and those of our user community.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best.
Have a nice day.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
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
Hi Marko,
I understand you have to follow procedures, so I'll create a feature request.
Hopefully it will get implemented. Feel free to close the ticket.
Hello again,
Thank you for understanding and we will close this one also but as we mentioned should you have any further inquiries, feel free that you open separate tickets for each question and we will gladly help you there.
We wish you all the best.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
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