Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0
-
Fix Version/s: EE-3.0.0.BETA, 3.0.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Portlets, Liferay 5 and 6
Description
When a page has an ace:dateTimeEntry portlet AND any other ace portlet, the calendar doesn't display and the following error is displayed in the Chrome console "Uncaught RangeError: Maximum call stack size exceeded", along with a stack trace showing multiple calls to $.datepicker._updateDatepicker(). In FF, the browser freezes and eventually crashes.
This problem starts occurring at revision 27849 in the trunk, with a fix forICE-7701. Since it only occurs in the presence of another ace portlet, most likely this issue is related to wrong jQuery references and/or resource loading issues.
This problem starts occurring at revision 27849 in the trunk, with a fix for
Activity
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Fix Version/s | EE-3.0.0.GA [ 10262 ] | |
| Fix Version/s | 3.0.1 [ 10282 ] | |
| Assignee Priority | P2 | |
| Assignee | Arturo Zambrano [ artzambrano ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #27983 | Wed Feb 22 13:33:01 MST 2012 | art.zambrano | |
| Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/ace/component/resources/icefaces.ace/datetimeentry/datetimeentry.js
|
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #27984 | Wed Feb 22 13:45:23 MST 2012 | art.zambrano | |
| Files Changed | ||||
MODIFY
/icefaces3/branches/icefaces-3.0.x-maintenance/icefaces/ace/component/resources/icefaces.ace/datetimeentry/datetimeentry.js
|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Salesforce Case | [] | |
| Fix Version/s | EE-3.0.0.BETA [ 10324 ] | |
| Fix Version/s | EE-3.0.0.GA [ 10262 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee Priority | P2 |

Fixed at revision 27983 in the trunk and at revision 27984 in the maintenance branch.
The fix consisted in checking to see if the timepicker plug-in was already set up and avoid setting it up again.