MySQL Bugs: #16852: "Update Issue" lock-up, infinite Expected Resolution Date numbers

Bug #16852	"Update Issue" lock-up, infinite Expected Resolution Date numbers
Submitted:	27 Jan 2006 19:36	Modified:	2 May 2007 21:02
Reporter:	Yuriy Kotsarenko	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Eventum	Severity:	S1 (Critical)
Version:	Eventum 1.7.0	OS:	Windows (Windows)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When clicking on "Update Issue" button to edit an issue, it loads part of the page until "Expected Resolution Date" field appears and then locks up on FireFox or simply hangs on Internet Explorer. If you click on Expected Resolution Date, you'll see large numbers like 113839 and constantly increasing (each time you click on the field, there are more numbers there). This basically makes issues ineditable.

How to repeat:
Fresh Eventum installation, created two projects, added statuses and categories. Also edited priorities (names & colors). Created a single issue. On issue listing page, clicked on the issue, entered Issue viewing screen. Then clicked on "Update Issue".

The screenshot of the problem

Attachment: problem.gif (image/gif, text), 26.32 KiB.

Hi,

in templates/en/update_form.tpl.html, line 216, try changing end_year from "+1" to a concrete value like '2009'. I have been unable to reproduce this on my own.

Best Regards

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

exactly, the problem is in that line, but when you have a release date in the past i think.
greetings.

I've cheated and i have a fixed start and end date now, it works ant i only have to update it on 10 years or so :)

 {html_select_date time=$expected_resolution_date field_array="expected_resolution_date" prefix="" start_year=$expected_resolution_start_year end_year="2010" all_extra='class="default"' year_empty="" day_empty="" month_empty="" day_value_format='%02d'}

Hi,

Since I can't reproduce this on my system can you please try this fix?

Replace the line causing trouble with this:
{html_select_date time=$expected_resolution_date field_array="expected_resolution_date" prefix="" start_year=$expected_resolution_start_year end_year=`$expected_resolution_start_year+10` all_extra='class="default"' year_empty="" day_empty="" month_empty="" day_value_format='%02d'}

The proposed solution didn't work, since the initial year is bugged as well.

Changing the problematic code to the following text fixes the problem:
{html_select_date time=$expected_resolution_date
field_array="expected_resolution_date" prefix=""
start_year="2000" end_year="2010"
all_extra='class="default"' year_empty="" day_empty="" month_empty=""
day_value_format='%02d'}

I've experienced this problem on several hosts already and in all versions of Eventum, including the latest beta. My guess is that $expected_resolution_start_year variable is miscalculated.

I am trying to avoid hard coding date values in this code.

I see 2 posts that are related to this:
http://www.phpinsider.com/smarty-forum/viewtopic.php?t=4377&sid=332e5da2c5f094ac82a9eb6796...
http://bugs.php.net/bug.php?id=30215

I have gone ahead and assigned the year value from PHP which should solve the problem. The patch is here:
http://eventum.mysql.org/patches/bug_16852.patch.txt and will be in the 2.0 release

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".