Customising what content is accessible by EES

(Ryan Archer) #1

Is it possible to customise what content is accessible by EES?

Right now I have put EES on a page and by accessing websitename.com/_edit - the whole page becomes editable within EES.

 

We are using Twitter Bootstrap framework for making it a nice responsive, clean website and we do not want some of our users inadvertently affecting the layout of the site when using the WYSIWIG editor. Basically using the WYSIWIG editor is like stumbling around a minefield, every time an editor may change some content within a page, they may also break the design at the same time.

 

So instead of placing EES over an entire page via a design customisation, is it possible to just get it to access specific areas within page content?

(Bart Banda) #2

You can, but you would have to add some custom CSS and JS to disable those areas from being editable. 

 

Sounds like you are better off changing your homepage design so that the sensitive areas are not within the contents of the page but rather managed via metadata settings that then control the layout, or similar. 

(Ryan Archer) #3

Is that possible when the sensitive areas framework has many variations (i.e. many pages use different combinations of rows and columns for customised layout).

Is there a guide (or documentation) that explains how to do it via CSS and JS?

(Bart Banda) #4

There are some guides on customising Edit+ on the manuals:

http://manuals.matrix.squizsuite.net/edit-plus/chapters/css-customisations 

http://manuals.matrix.squizsuite.net/edit-plus/chapters/javascript-plugins 

(Ryan Archer) #5

Thanks Bart. Before I go reading, is customising Edit+ the same as EES?

Just to clarify, we are still using EES.

(Bart Banda) #6

I think its more or less the same. If you are using the latest version of EES, which is 1.5.0, I think they would be the same.