Date error after version migration.

[wfilho]

Hi All !

I had a problem with my SugarCRM installation (v.4.5.0.f), our administrator change the password with (mysqladmin -u root -p NEWPASSWORD) and Sugar stops to work. We sad all the possibilities to solve the problem, but because the "time" we choose reinstall all the system and migrate to the new version v.4.5.1.a. We did the follow:

- MYSQLDUMP of our database (v.4.5.0.f)
- Reinstall the system with (v.4.5.0.f)
- Restore the data from the DUMP FILE
- Migrate the version v.4.5.0.f to v.4.5.1
- Rebuild Extension and Relationship
- Migrate the version v.4.5.1 to v.4.5.1.a
- Rebuild Extension and Relationship

Everything was ok, but today, when we saw our Task List in (ACTIVITIES / TASKS) all the DUE DATE is 01-01-2000. When we open the task, the dates are ok, we save, but in this view all the tasks keep unchanged (01-01-2000).

We did a lot of things at the same time, so it's more difficult to identify the real cause of that problem. I thougth that can have a function in REPAIR option on ADMIN menu, but I don't know what and I don't want to make another mistake like the other one (password) |o|

I really appreciate any help !

Thanks in advance !

Wellington

[wfilho]

Hi All,

Just a little observation about this thread. We use SugarCRM to control our department activities. The users open tasks for a general user and each one see the task list, choose a task and change the ASSIGNED TO for themselves.

So, in the old version (v.4.5.0.f) we had identified a kind of "bug". When we filter the tasks , all the dates was showed in "red", meaning it's late, even when the task wasn't late. We did some tests and when we add the DUE TIME FIELD in the list view, the field DUE DATE started to work fine, showing the tasks with the correct colors (BLACK, YELLOW and RED).

WE SOLVE THE PROBLEM DESCRIBED DOING THE FOLLOW:

We exclude the field DUE TIME of the list view. Only doing this, the field DUE DATE starts to work fine and show the correct colors. So, the workaround that we use to correct the problem ("bug") in the old version causes a new kind of "bug" in the new version.

- Sorry if I'm using the word "bug" for something that is supposed to work like I thought that is a bug. And sorry for my poor english. I'm a newbie in the system and I'm not a developer professional !

I really apreciate to hear from the experts about this thread.

Regards.
[]'s

Wellington