Page 1 of 1
Schedule error when selecting date range
Posted: Thu Jul 12, 2018 5:39 am
by tadd
I get
TypeError: this.parserDatesRange is not a function
when trying to select a date range when setting up a new schedule using date range.
Any ideas.
Using Timetrex version 11.2.4 community edition on Linux.
Re: Schedule error when selecting date range
Posted: Fri Jul 13, 2018 3:39 pm
by shanec
Please post an uncropped screenshot of the error message that you are receiving.
Re: Schedule error when selecting date range
Posted: Sat Jul 14, 2018 1:42 pm
by tadd
I do not get an error message. The schedule simply does not apply.
I then get the Debug with sample message attached
Re: Schedule error when selecting date range
Posted: Sat Jul 14, 2018 2:28 pm
by tadd
Another transcript of error
Re: Schedule error when selecting date range
Posted: Mon Jul 16, 2018 8:30 am
by mikeb
Are you able to replicate the issue at will? If so, please provide detailed steps so we can replicate it on our end.
Re: Schedule error when selecting date range
Posted: Mon Jul 16, 2018 8:55 am
by tadd
Yes this happens all the time.
process:
Log in as admin - Click on attendance - Schedule- new -schedule window opens -click on date calendar -select range tab and select date range pick any 2 or more free dates. The moment you get out of the range tab the processing view pops up and I receive debug emails. before I even attempt to save the new schedule. When I click on Save the web-page becomes unresponsive.
I get the same error when I follow the same process for Scheduled Shifts.
Re: Schedule error when selecting date range
Posted: Mon Jul 16, 2018 9:01 am
by mikeb
Unfortunately I'm not able to replicate the issue. Could you please try to replicate it on our public demo located here?
https://demo.timetrex.com/
Username: demoadmin1
Password: demo
Re: Schedule error when selecting date range
Posted: Mon Jul 16, 2018 9:21 am
by tadd
Feature is working correctly on the demo
Re: Schedule error when selecting date range
Posted: Mon Jul 16, 2018 9:25 am
by mikeb
I'm not aware of any changes since v11.2.4 that would make a difference in this case...
Have you made any modifications to TimeTrex's source code on your end?