[#3698] - schedule with start and/or end date cannot be saved

Category:
Bug report
Priority:
High
Status:
New
Project: Severity:
Major
Resolution:
Open
Component: Reproducibility:
Always
Assigned to:

Hi all,

When the Jasperserver locale is set to "de" I get the error "Ungültiges Datum" (="invalid date") whenever i try to save a schedule with a specified start date and/or end date.

Environment:
JasperServer Version 5.6 (bundled JRS installation without any configuration changes)
Tomcat 7 (from bundled JRS installation)
Postgre database (from bundled JRS installation)
Java 7
IE 11

Error reproduction:
- Choose locale "de", "fr" or "es" on login page and log in.
- Open schedule list of a report.
- Choose "Create schedule".
- Choose start date by means of the datepicker control.
- Hit "Save".

Normal/expected behaviour:
A small popup will appear, that asks for a name and description of the schedule, and on hitting "save" the schedule dialog will close, the schedule list will be displayed and the newly created schedule appears in this list.

Experienced/faulty behaviour:
No popup. Instead a small red error message is displayed under the offending date field which states that the date is not valid ("Ungültiges Datum", "Date non valide", "Fecha no valida").

I tried this with localization set to german, french and spanish, all with the same error.
However with localization set to english, the error does not occur.

Actually we experienced this issue in version 5.5 too, but we could circumvent it by fixing the UI_DATE_PATTERN in scripts/scheduler/model/job.js to german and passing it as a parameter in calls to method "moment"
(as described here: http://community.jaspersoft.com/jasperreports-server/issues/3637)
Unfortunately this does not work anymore with version 5.6.

Any help appreciated!

Regards,
Jasmine

v5.6
jasmine.ahmed's picture
Joined: Jun 26 2014 - 5:57am
Last seen: 7 years 4 months ago

4 Comments:

#1
  • Assigned:nobody»

Hi,

Same problem here. 5.6 version, custom install (we used our already working Tomcat) but we have exactly the same problem and followed exactly the same steps.

Solution on Bug 3637 (http://community.jaspersoft.com/jasperreports-server/issues/3637) didn't work, either.

Regards.

#2
  • Priority:Normal» High
  • Severity:Minor» Major
  • Assigned:» anonymous

Hi,

I have the same problem with Jasperserver 5.6.1 custom install.
The Solution on Bug 3637 (http://community.jaspersoft.com/jasperreports-server/issues/3637) didn't work, either.
Any help is appreciated!

Regards

Rainer

V5.6.1

#3
  • Assigned:nobody»

Hello all,

the problem is still up-to-date using version Jasper server version 6.0.1
The workaround described also does not work for this version.
Any help is appriciated as there's also no work-around.

Best regards,
Carsten

#4

Hi again,

the bug was fixed in Version 6.1.0! (at least for locale "de")

Thanks,
J.

Feedback
randomness