Skel.js and Content Block (tinyMCE)

Permalink
I'm trying to build a theme based on the skel.js framework and have an issue where something in skel.js is causing tinyMCE to fail when putting a content block in edit mode.

The editor loads, but shows only raw html. The URL's to the various add ons to build the wysiwyg toolbar are all showing 404's. It looks like an extra '/' is added by skel.js. Disabling skel.js when the page is in edit mode eliminates the issue but obviously not a good solution.

Has anyone else had this issue. I found a post with a similar problem but no resolution, only a suggestion that it could be a jquery conflict.

 
RMDWebDesign replied on at Permalink Reply
RMDWebDesign
I had the same issue, was about to abandon ship and use bootstrap instead. Just fixed it there by removing the skel.js panels addon.

Ross.
soupmedia replied on at Permalink Reply
Yeah, that's what I ended up doing too. The panels.js need a more recent version of jquery - loading the latest jquery fixed all the issues I was having, but broke a lot of the editing in C5.

I started doing a conditional load of jquery based on whether the user was logged in or not, but it got messy trying to edit content in panels.

I think 5.7 will be using the latest jquery but it's not ready for production yet.
RMDWebDesign replied on at Permalink Reply
RMDWebDesign
Did you opt for a different panel script? I had a look for one but couldn't find one that allowed multiple panels on the same side. I've resorted to building one using pretty basic jquery and css but I'm sure it's missing a lot of essential features (swipe control, etc). I would prefer something off the shelf.

Ross.
soupmedia replied on at Permalink Reply
Thanks Ross.

I ended up doing a check for whether the user was logged in and if so, not
loading the skel stuff.
If not logged in, load the latest jquery and all the skel scripts etc.

I had to recode my package controllers though because using the newer
jquery broke the automatic asset loading from c5, so things had to be
loaded with attachHeaderItem() and package relative paths.
Other than that, it all works well.