Arghghhghghghhhhhhh!
Has anyone successfully managed to set their config file for any of the popular WYSIWIGs to prevent them from trying to 'properly' format the source code? This is really starting to p!ss me off.
I don't use a WYSIWIG myself but my clients need do. The problem is that I go in and initially format all their pages beautifully and then when they go in to edit them the WYSIWIG reformats everything and strips tags. This means hours of work reformatting the pages again.
I notice that FCKeditor has a BASIC toolbar option but I've no idea how to set it.
I'd be mighty obliged to anyone out there who could provide a version of this editor that didn't reformat exising source.
Hopefully block editing will remove the need for anything but the barest of formatting options in the future.
FCKeditor and WYSIWIGs in general
-
Alex_Leipzig
Re: FCKeditor and WYSIWIGs in general
Must be really annyoing. I'm also afraid of the day when my users will start to edit the pages...
But, actually I haven't had problems with reformatted code. Did you mean the quote-issue, that was already discussed elsewhere? You could also use single quotes (') for the module tags. Don't know if that's the problem, though.
But, actually I haven't had problems with reformatted code. Did you mean the quote-issue, that was already discussed elsewhere? You could also use single quotes (') for the module tags. Don't know if that's the problem, though.
Re: FCKeditor and WYSIWIGs in general
Yep i misscount the times that i tried to understand the problem of quotes, and nowdays the solution remains single quote (')alex wrote: Must be really annyoing. I'm also afraid of the day when my users will start to edit the pages...
But, actually I haven't had problems with reformatted code. Did you mean the quote-issue, that was already discussed elsewhere? You could also use single quotes (') for the module tags. Don't know if that's the problem, though.
Re: FCKeditor and WYSIWIGs in general
I think there are drawabacks with all WYSIWYG. Maybe a tailored version would be better as proposed in another thread.
The tag insertion could be a separate button like in this demo:
http://www.primaat.com/htmlarea?func=vi ... rumId=1002
(The right button for inserting macros).
The editor must also be told to keep away from everything between {}. We would probably need a new interface to tell a client what parameters are supported for the tag.
The tag insertion could be a separate button like in this demo:
http://www.primaat.com/htmlarea?func=vi ... rumId=1002
(The right button for inserting macros).
The editor must also be told to keep away from everything between {}. We would probably need a new interface to tell a client what parameters are supported for the tag.
