HIGH PRIORITY! We updated our Amelia system to 5.0 yesterday, as you recommended. Now we are having problems scheduling appointments for the next few days. This is a huge issue!
TMS User UROS JOVANOVIC HAS A USER ID IN OUR SYSTEM. PLEASE DON"T ASK US FOR THIS; IT RESULTS IN AN UNNECESSARY DELAY.
We have an employee scheduled for June 18 at 10 am.
We have an appointment pending with a different employee on June 18 at 10 am.
When we go to the appointment system to change the employee and view the calendar, it does not show any availability for the next 7 days.
This happens on a new appointment as well as an existing appointment. Screen shots attached to Ticket #3065059.
In gENERAL settings, we cannot change the minimum time required before booking - we get an error on Save - #503.
HIGH PRIORITY - NO ONE REPLIED TO THIS REQUEST YESTERDAY
I performed checks on your website regarding this issue and there seems to be an issue with the permissions and there is a following error in the console. Please contact your hosting provider and they will be able to assist you with this issue.
Please let me know if you were able to resolve this issue.
We were able to resolve the issue with the settings, related to the IP address and firewall. Thank you.
However, the major problem has not been addressed: We still have issues when scheduling appointments within the next 7 days, on the Backend. This is a HUGE IMPACT!
Attached is a screenshot of the calendar - I cannot schedule anything until June 23.
On your recommendation, we upgraded to Amelia 5.0 a couple of days ago, and that is when we first saw this problem. Should we back it out? We did not have this problem until we applied the "upgrade."
We have error 403 now, when we try to change anything in the settings.
The 403 Forbidden Error happens when the web page (or another resource) that you’re trying to open in your web browser is a resource that you’re not allowed to access. It’s called a 403 error because that’s the HTTP status code that the webserver uses to describe that kind of error.
You usually get this error for one of two reasons. The first is that the owners of the webserver have properly set up access permissions and that you’re really not allowed access to the resource. The second reason is that the owners of the webserver have improperly set up permissions and you’re getting denied access when you really shouldn’t be.
You need to contact your hosting provider because you have an issue with your permissions.
Once you do that please let us know if everything is back in order.
-
Now, this is my IP address : 178.148.34.140 ( it has to be whitelisted in order for me to help you)
Perhaps only that is blocked, but you have to also try when you log in from your computer, to check if they also block your IP adress.
When your hosting claims this time that everything is in order,
please check this video i am sending you.
If you use Google Chrome, press F12 to open Developer console, and keep network tab open as i did.
Then try to change any setting, and see if you still get error 403. If that happens, you have to contact your hosting again, because it will mean they still haven't solved permission issues.
-
Let us know when this gets resolved and we can proceed to assist you with any Amelia issues.
As you are aware, we still have issues when trying to schedule appointments within the next 7 days, on the Backend. This is a HUGE IMPACT!
On your recommendation, we upgraded to Amelia 5.0 a couple of days ago, and that is when we first saw this problem. Should we back it out? We did not have this problem until we applied the "upgrade."
We set up a userid for you; you should have received an email from the system about that.
1) Did you receive it?
The minimum time required before booking has help text that states: "Set the time before the appointment when CUSTOMERS will not be able to book the appointment." See screen shot attached.
The problem is that that "minimum time required before booking the appointment" on the BACKEND now has the same value as the "minimum time required before booking the appointment" value for the customers.
On the BACKEND, I should be able to schedule anytime I want. BEFORE the new release, I could schedule appointments on the BACKEND any timeframe that I wanted. Now I cannot.
It seems that this is a new bug that was introduced in the Amelia 5.0 release.
2) When is the next release, when scheduling appointments on the backend at any time will be FIXED?
You requested a video and I can make that. However, I have been scheduling for over a year and know what I am doing. I don't want our information to be on this public site.
3) How shall I get the video to you?
I want this ticket to remain public, as this new release caused a SIGNIFICANT IMPACT to our work!
"Of course, if you can also tell me what is the current setting for minimum time required before booking, in the General Amelia settings, but also in the service, if you can check?"
Before, I sent a screen shot of the "Minimum time required before booking" in General Settings.
Attached is a screen shot of Employee availability in the "WORK HOURS" tab - we offer 1 service each day at 10 am. (This employee has no days off.)
The developers flagged this as a bug, you are correct - in versions before 5.0 , we were able to ignore the time ahead set for booking for customers, admin could do it to override.
If you wish, you can reroll Amelia to the older version 4.6 ;
i sent it to you in that private reply; if this facility is crucial for you right now;
And our devs are working on fixing this bug;
It should be finished by the time we release the new update; Please check the patch notes on this changeLog page when update happens;
If you see the bug fix noted, you can update to the new version and it will be fixed.
HIGH PRIORITY! We updated our Amelia system to 5.0 yesterday, as you recommended. Now we are having problems scheduling appointments for the next few days. This is a huge issue!
TMS User UROS JOVANOVIC HAS A USER ID IN OUR SYSTEM. PLEASE DON"T ASK US FOR THIS; IT RESULTS IN AN UNNECESSARY DELAY.
We have an employee scheduled for June 18 at 10 am.
We have an appointment pending with a different employee on June 18 at 10 am.
When we go to the appointment system to change the employee and view the calendar, it does not show any availability for the next 7 days.
This happens on a new appointment as well as an existing appointment. Screen shots attached to Ticket #3065059.
In gENERAL settings, we cannot change the minimum time required before booking - we get an error on Save - #503.
HIGH PRIORITY - NO ONE REPLIED TO THIS REQUEST YESTERDAY
Debbie
Attached files: Error on save.jpg
Hello Debbie,
I performed checks on your website regarding this issue and there seems to be an issue with the permissions and there is a following error in the console. Please contact your hosting provider and they will be able to assist you with this issue.
Please let me know if you were able to resolve this issue.
Looking forward to your reply.
Kind Regards,
Uros Jovanovic
[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
We were able to resolve the issue with the settings, related to the IP address and firewall. Thank you.
However, the major problem has not been addressed: We still have issues when scheduling appointments within the next 7 days, on the Backend. This is a HUGE IMPACT!
Attached is a screenshot of the calendar - I cannot schedule anything until June 23.
On your recommendation, we upgraded to Amelia 5.0 a couple of days ago, and that is when we first saw this problem. Should we back it out? We did not have this problem until we applied the "upgrade."
Attached files: calendar.jpg
Hi, Debbie
We have error 403 now, when we try to change anything in the settings.
The 403 Forbidden Error happens when the web page (or another resource) that you’re trying to open in your web browser is a resource that you’re not allowed to access. It’s called a 403 error because that’s the HTTP status code that the webserver uses to describe that kind of error.
You usually get this error for one of two reasons. The first is that the owners of the webserver have properly set up access permissions and that you’re really not allowed access to the resource. The second reason is that the owners of the webserver have improperly set up permissions and you’re getting denied access when you really shouldn’t be.
You need to contact your hosting provider because you have an issue with your permissions.
Once you do that please let us know if everything is back in order.
-
Now, this is my IP address : 178.148.34.140 ( it has to be whitelisted in order for me to help you)
Perhaps only that is blocked, but you have to also try when you log in from your computer, to check if they also block your IP adress.
When your hosting claims this time that everything is in order,
please check this video i am sending you.
If you use Google Chrome, press F12 to open Developer console, and keep network tab open as i did.
Then try to change any setting, and see if you still get error 403. If that happens, you have to contact your hosting again, because it will mean they still haven't solved permission issues.
-
Let us know when this gets resolved and we can proceed to assist you with any Amelia issues.
Attached files: Desktop 2022.06.17 - 11.23.25.08.DVR.mp4
Kind Regards,
Miloš Jovanović
[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
Hi, Milo,
We have white-listed your IP address.
As you are aware, we still have issues when trying to schedule appointments within the next 7 days, on the Backend. This is a HUGE IMPACT!
On your recommendation, we upgraded to Amelia 5.0 a couple of days ago, and that is when we first saw this problem. Should we back it out? We did not have this problem until we applied the "upgrade."
Hi, Milos,
We set up a userid for you; you should have received an email from the system about that.
1) Did you receive it?
The minimum time required before booking has help text that states: "Set the time before the appointment when CUSTOMERS will not be able to book the appointment." See screen shot attached.
The problem is that that "minimum time required before booking the appointment" on the BACKEND now has the same value as the "minimum time required before booking the appointment" value for the customers.
On the BACKEND, I should be able to schedule anytime I want. BEFORE the new release, I could schedule appointments on the BACKEND any timeframe that I wanted. Now I cannot.
It seems that this is a new bug that was introduced in the Amelia 5.0 release.
2) When is the next release, when scheduling appointments on the backend at any time will be FIXED?
You requested a video and I can make that. However, I have been scheduling for over a year and know what I am doing. I don't want our information to be on this public site.
3) How shall I get the video to you?
I want this ticket to remain public, as this new release caused a SIGNIFICANT IMPACT to our work!
Attached files: customer appointment help text.jpg
Hi, Milos,
You said:
"Of course, if you can also tell me what is the current setting for minimum time required before booking, in the General Amelia settings, but also in the service, if you can check?"
Before, I sent a screen shot of the "Minimum time required before booking" in General Settings.
Attached is a screen shot of Employee availability in the "WORK HOURS" tab - we offer 1 service each day at 10 am. (This employee has no days off.)
Is this what you wanted to see?
Attached files: Employee hours.jpg
Hi, Debbie
Sorry for the delay, i checked with developers.
Thank you for confirming all the details.
The developers flagged this as a bug, you are correct - in versions before 5.0 , we were able to ignore the time ahead set for booking for customers, admin could do it to override.
If you wish, you can reroll Amelia to the older version 4.6 ;
i sent it to you in that private reply; if this facility is crucial for you right now;
And our devs are working on fixing this bug;
It should be finished by the time we release the new update; Please check the patch notes on this changeLog page when update happens;
If you see the bug fix noted, you can update to the new version and it will be fixed.
Let me know if you have any questions. Thank you
Kind Regards,
Miloš Jovanović
[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