Right now, it's April. We're starting to plan some of our development for a few months down the road, and assigning projects to be due in August, September, and later. However, when we enter a due date of, say, August 15, 2005, in the "New Issue" dialogue, we're told that the due date is invalid.
What's up with that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry it took so long to get back to you about this.
Unfortunately, the .js patch you supplied doesn't solve the problem. It looks to me like it's expecting a string called REVERSE_DATE_RE which is validates the date string against. The comments say that REVERSE_DATE_RE and REVERSE_DATE_TO_ISO are both defined in coreconfig.php, but I can't find those strings in that file. This doesn't explain to me why, though, dates nearer in the future cause no problems. It appears, by the way, that the system is fine with dates up through July 31; dates from August 1 and after are the ones that cause problems.
If you try to view the HTML source of any page, right at the top of the file, in the header section, all those variables should be defined.(From a server-side point of view the template is tpl/page_main.tpl.php).
As far as the other error goes, this is fairly weird. I would love to take a look at both for you. Is there any chance you can temporarily give me access to your installation? My email address is philipx@users.sourceforge.net. If you could email me a user/password and give me access to a new, empty test/project, I would really appreciate it.
What browser/version are you using?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah, okay, I found the variables in the source code. Spiffy.
I personally don't have a problem allowing you to have temporary access to our PB installation, but I'll have to clear it with my boss. He won't be in until Monday, unfortunately, though perhaps our office manager can give me a positive answer. I'll let you know.
The first error -- the date error -- seems to be cross-browser/OS. It showed up in Firefox on Windows and on Linux, as well as in IE on Windows 2000 and IE running under WINE on Linux. The second error I only received in FF on Linux, but that's the only platform I tested.
Our PB installation is v 0.04, though it's from a fairly recent CVS snapshot (sorry, I don't know the exact date of the snapshot).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, if you manage to get anything working please let me know. FWIW, you could create an empty project (name if test) and only give me access to that project.
Or, if you got a little bit of time, please try the following:
- bring up the New Issue form and save the page (complete)
- bring the local/saved page in your browser and see if your getting the same error(s). if you do, just zip the saved file and folder and email them to me. I think that's probably all I need.
Thanks for your patience.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's a fun one.
Right now, it's April. We're starting to plan some of our development for a few months down the road, and assigning projects to be due in August, September, and later. However, when we enter a due date of, say, August 15, 2005, in the "New Issue" dialogue, we're told that the due date is invalid.
What's up with that?
Thanks for letting me know.
Please use the file attached to this patch:
https://sourceforge.net/tracker/index.php?func=detail&aid=1196124&group_id=114475&atid=668469
or get the latest js/general.js from CVS.
Thanks!
ph
Sorry it took so long to get back to you about this.
Unfortunately, the .js patch you supplied doesn't solve the problem. It looks to me like it's expecting a string called REVERSE_DATE_RE which is validates the date string against. The comments say that REVERSE_DATE_RE and REVERSE_DATE_TO_ISO are both defined in coreconfig.php, but I can't find those strings in that file. This doesn't explain to me why, though, dates nearer in the future cause no problems. It appears, by the way, that the system is fine with dates up through July 31; dates from August 1 and after are the ones that cause problems.
Also, applying the new general.js file produced a JavaScript error: Error: parentElem has no properties
Source File: http://trinitydlc.extensiondlc.net/projectbench/js/general.js
Line: 302
This made the "new issue" form unusable. I went ahead and reverted back to the older version.
If you try to view the HTML source of any page, right at the top of the file, in the header section, all those variables should be defined.(From a server-side point of view the template is tpl/page_main.tpl.php).
As far as the other error goes, this is fairly weird. I would love to take a look at both for you. Is there any chance you can temporarily give me access to your installation? My email address is philipx@users.sourceforge.net. If you could email me a user/password and give me access to a new, empty test/project, I would really appreciate it.
What browser/version are you using?
Ah, okay, I found the variables in the source code. Spiffy.
I personally don't have a problem allowing you to have temporary access to our PB installation, but I'll have to clear it with my boss. He won't be in until Monday, unfortunately, though perhaps our office manager can give me a positive answer. I'll let you know.
The first error -- the date error -- seems to be cross-browser/OS. It showed up in Firefox on Windows and on Linux, as well as in IE on Windows 2000 and IE running under WINE on Linux. The second error I only received in FF on Linux, but that's the only platform I tested.
Our PB installation is v 0.04, though it's from a fairly recent CVS snapshot (sorry, I don't know the exact date of the snapshot).
Okay, if you manage to get anything working please let me know. FWIW, you could create an empty project (name if test) and only give me access to that project.
Or, if you got a little bit of time, please try the following:
- bring up the New Issue form and save the page (complete)
- bring the local/saved page in your browser and see if your getting the same error(s). if you do, just zip the saved file and folder and email them to me. I think that's probably all I need.
Thanks for your patience.
Philip,
I've set up a temporary account and project for you on our installation. Details are sent to your e-mail address.
Thanks, I replied to your email and I believe to have fixed the issue.
Please let me know. Thanks.