How To DEFINE EDITABLE REGIONS?

Is there a way to define areas that a user can and cannot edit? I am having problems with my users deleting php code, and I wondered if there was a way to "lock" the code so that it can't be edited...

Any help is HIGHLY appreciated (possible reward!)

Thanks!
Jon

Sun, 10/08/2006 - 11:11

alfonsoml

Joined: 31/12/2006

Posts: 3737

RE: How To DEFINE EDITABLE REGIONS?

You can look at the following plugin/patch: https://sourceforge.net/tracker/index.p ... tid=737639

It might be more complex than your needs because it also supports custom XML tags, but you'll have to mess with the code if you want to have only one editor with several editable/non-editable parts in it.

Mon, 10/09/2006 - 09:42

jonnymcg

Joined: 28/11/2006

Posts: 7

RE: How To DEFINE EDITABLE REGIONS?

That's an intersting patch Alfonso. I had been reading through the forums, and saw the defineeditable=false (I think that's the variable) mentioned a few times. Does anyone have any experience using this variable to prevent NOOBS from deleting PHP code by accident?

Mon, 10/09/2006 - 10:51

alfonsoml

Joined: 31/12/2006

Posts: 3737

RE: How To DEFINE EDITABLE REGIONS?

contentEditable=false does just that: preventing the editing of its content (and only in IE), it doesn't care if you delete it or not.
That patch tries to avoid those problems (and I mean that it *TRIES* not that it's bulletproof), the perfect solution is to not include anything non-editable inside the editor.

Mon, 10/09/2006 - 14:11

jonnymcg

Joined: 28/11/2006

Posts: 7

RE: How To DEFINE EDITABLE REGIONS?

Hi Alfonso... Im wondering if I can take another approach, such as a javascript based "mouse redirect" so that no matter where a person clicks on their site in the editor, they will end up in the correct region...

see, the problem is that we use templates with php code on them which is necessary to generate the dynamic content like menus and photogalleries... that's great, but when someone goes to edit their site, they end up deleting important stuff, and get "php" errors on their page...

any more ideas?
Jon