0013682: Unable to modify existing calendar event - TypeError: Cannot read property 'hasPoll' of undefined #6767

Closed
Gloirin opened this Issue Jun 9, 2018 · 5 comments

Comments

Projects
None yet
1 participant
@Gloirin

Gloirin commented Jun 9, 2018

Reported by jan on 3 Jan 2018 15:31

Version: 2017.08.10 Community Edition

When editing an existing calendar event (change end time for example) the following error occurs:

index.php?method=Tinebase.getJsFiles&b94e376341a6662d43fc155c502e7413a94c3647:formatted:10567 Uncaught (in promise) TypeError: Cannot read property 'hasPoll' of undefined
at Tine.Felamimail.GridPanelHook.bodyFn (index.php?method=Tinebase.getJsFiles&b94e376341a6662d43fc155c502e7413a94c3647:formatted:74610)
at Tine.Felamimail.GridPanelHook.updateAction (index.php?method=Tinebase.getJsFiles&b94e376341a6662d43fc155c502e7413a94c3647:formatted:69805)
at Tine.widgets.ActionUpdater.<anonymous> (index.php?method=Tinebase.getJsFiles&b94e376341a6662d43fc155c502e7413a94c3647:formatted:18988)
at Tine.widgets.ActionUpdater.each (index.php?method=Tinebase.getJsFiles&b94e376341a6662d43fc155c502e7413a94c3647:formatted:19027)
at Tine.widgets.ActionUpdater.updateActions (index.php?method=Tinebase.getJsFiles&b94e376341a6662d43fc155c502e7413a94c3647:formatted:18984)
at L.updateEventActions (index.php?method=Tinebase.getJsFiles&b94e376341a6662d43fc155c502e7413a94c3647:formatted:61198)
at i.Event.fire (ext-all.js:7)
at L.fireEvent (ext-all.js:7)
at L.<anonymous> (ext-all.js:7)
at i.Event.fire (ext-all.js:7)

Fix for this issue is attached.

Steps to reproduce: This problem affects only some users (don't know why).

Create a new calendar event.
Edit the event.
Change end time.
Save.

Additional information: This problem affects at least Firefox 57.0.3 and Chromium 63.0.3239.84.

@Gloirin Gloirin added this to the 2018.02.2 Community Edition milestone Jun 9, 2018

@Gloirin Gloirin self-assigned this Jun 9, 2018

@Gloirin Gloirin closed this Jun 9, 2018

@Gloirin

This comment has been minimized.

Show comment
Hide comment

Gloirin commented Jun 10, 2018

Related to #6770

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by jan on 3 Jan 2018 22:50

corrected patch file attached

Gloirin commented Jun 11, 2018

Comment posted by jan on 3 Jan 2018 22:50

corrected patch file attached

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by 12delta on 9 Jan 2018 21:39

This is for all that search a different JavaScript console error messeg: TypeError: e is undefine
This is because of the compressed JavaScript. The real error message "TypeError: record is undefine" is shown, if the debug more is enabled: https://www.tine20.org/forum/viewtopic.php?t=9562
And the above patch only take place, if this debug more kept enabled.
(I searched a lot. But didn't found it, because this information was missing.)

Gloirin commented Jun 11, 2018

Comment posted by 12delta on 9 Jan 2018 21:39

This is for all that search a different JavaScript console error messeg: TypeError: e is undefine
This is because of the compressed JavaScript. The real error message "TypeError: record is undefine" is shown, if the debug more is enabled: https://www.tine20.org/forum/viewtopic.php?t=9562
And the above patch only take place, if this debug more kept enabled.
(I searched a lot. But didn't found it, because this information was missing.)

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by WolfgangAndreas on 16 Jan 2018 12:11

Works for me. This also fixed #0013688

Gloirin commented Jun 11, 2018

Comment posted by WolfgangAndreas on 16 Jan 2018 12:11

Works for me. This also fixed #0013688

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by pschuele on 22 Feb 2018 15:35

thanks for the patch - this has also been fixed in our git.

Gloirin commented Jun 11, 2018

Comment posted by pschuele on 22 Feb 2018 15:35

thanks for the patch - this has also been fixed in our git.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment