DateTime Field Broken in 7.9.10

English Language - Forum SuiteCRM Feedback
1

Hi All,

Not sure where to find this error but it seems to be related to every DateTime field in SuiteCRM.

Above the entry box it shows }}, the box will take a date but not the time and doesn’t then save it. (see attached screenshot)

Looking at this in firefox I wonder if these are supposed to be part of the closing tags for the ID of the input and img tags?

Sorry - I have no idea where to find this in the code to attempt a fix,

Thanks

Kieran

2

Just checked through every module we use - this issue affects all of them.

Not sure if it is just my system or every upgrade but it renders the whole system effectively useless if you can’t process a DateTime field anywhere.

Thanks

Kieran

3

I can confirm this problem.

I didn’t have any issues with this in 7.9.9. I did the update to 7.9.10 this afternoon and this issue showed up.

A fix would be appreciated.

4

Added this as a bug #5029 in github.

5

Just seen a fix has been commited #5034

I’ve applied the fix changes manually and it works perfectly.

Thanks for such a quick resolution - really apprichiated.

6

Hi @ksmith892
Could you elaborate on how you applied that fix manually? I’m only learning as I go and don’t really know how this should be done.

7

I manually made the change in the [include/SugarFields/Fields/Datetimecombo/EditView.tpl] file and it has fixed 1 of the datetime fields.

deleted the cache from the suitecrm directory

rm -r cache

Did a Repair & Rebuild in the Admin folder & deleted the caches from the browser.

The second is still broken. The { is gone. See screenshot below.

8

Hi @nuke

I’d been looking at the call records when I checked this - as you say works fine for the first field - for some odd reason any second DateTimeCombo is broken?

I did the same as you with the same result.

9

Hi, I confirm this problem for the second date.

I copied the version 7.9.8 file to fix the problem while waiting for a fix (but there is still a problem on the online edition)

Alban

10

No need to go backward to 7.9.8, go forward to 7.9.11, it was released one day after 7.9.10 to solve this unfortunate bug (actually, two).