CMS MADE SIMPLE FORGE

CMS Made Simple Core

 
Back Back to List

[#11436] MicroTiny doesn't load on Safari on pages with additional content blocks with wysiwyg enabled

avatar
Created By: Tristan (tristan)
Date Submitted: Mon Jun 26 10:17:42 -0400 2017

Assigned To:
Version: 2.2.1
CMSMS Version: 2.2.1
Severity: Major
Resolution: Awaiting Response
State: Closed
Summary:
MicroTiny doesn't load on Safari on pages with additional content blocks with wysiwyg enabled
Detailed Description:
Since the upgrade to 2.2.1 from 2.1.6 the MicroTiny bar doesn't load anymore for
additional content blocks when editing pages with wysiwyg enabled on one tab
with the latest version of Safari. Only the first main content block loads the
ones below that are just displayed as white space:

TypeError: undefined is not an object (evaluating
'tinymce.util.Delay.setEditorTimeout')
(anonymous function) — plugin.min.js:1:395
i — tinymce.min.js:6632
fire — tinymce.min.js:6733
initContentBody — tinymce.min.js:9967
init — tinymce.min.js:9911:237
(anonymous function) — tinymce.min.js:9815
(anonymous function) — tinymce.min.js:2403
n — tinymce.min.js:418
p — tinymce.min.js:2402
(anonymous function) — tinymce.min.js:2400
i — tinymce.min.js:2353:87
Selected Element
<p class="pageinput">…</p>

When disabling wysiwyg the forms for the additional content blocks appear again.


History

Comments
avatar 
Date: 2017-06-26 11:42
Posted By: Robert Campbell (calguy1000)

I don't have a mac, and don't have safari so I don't know.
but we have upgraded tinymce in MicroTiny for 2.2.2 this may solve the issue.

Let me know after 2.2.2 comes out.
avatar 
Date: 2017-06-26 11:44
Posted By: Tristan (tristan)

What's the ETA on 2.2.2 or can I update MicroTiny before that to test?
avatar 
Date: 2017-06-26 14:05
Posted By: Robert Campbell (calguy1000)

Waiting on one more vote from a dev team member.  Hopefully release this coming
weekend.
We usually like to release on weekends, unless it is an emergency.
avatar 
Date: 2017-06-28 10:34
Posted By: Tristan (tristan)

Clearing all browser cache completely fixed it.
Updates

Updated: 2017-06-28 10:35
state: Open => Closed

Updated: 2017-06-26 11:42
resolution_id: => 10