TheRune
|
I've confirmed this issue with both DotNetNuke and Artisteer, and am still waiting on some kind of solution.
I would like to know however, if anyone else has WYSIWYG problems with exported artisteer skins for DotNetNuke.
/Rune
|
| |
TheRune
|
Is there really no one else who has the "What You See Is What You Get" problem when editing contents on a page with an artisteer skin??
I'm trying to find a solution to this, but I can't figure out why noone else have mentioned this problem before. Is there someone in here using artisteer skins who does not have the problem?
I can't be all alone in this cruel world of WYSINOTWYG 
/Rune
|
| |
pat
|
Whats the problem? I have issues all the time with the editor. It's not just artisteer as we've had problems with other skins too.
If its backgrounds in the editor, there is a css fix for that and it looks like there is a built in #Body in the css in the latest version which should resolve the problem - or at least allow you to simply fix it.
It could also be a problem with the editor itself. Don't moan about it on the DNN forum though as they get a bit uppity about it. OK, very uppity!
|
| |
Pat
|
The editor that ships with DNN, the telerik one, is not supported by telerik which is pretty annoying.
The CSS in the skin can play havoc with the wysiwyg editor not allowing links, colours or a range of other things tombe changed without HTML in the editor.
These issues can manifest at any time even if at some point there seem to be no issues to begin with and editing IS wysiwyg.
However it's not for sure that it is the CSS that causes problems . Neither telerik or DNN themselves have been of much help on this subject to date. I have though submitted samples of the code that the editor randomly inserts into your text to telerik.
The problem is likely to be the insertion of 'spans' which will have to be carefully edited if you want the text to appear just as you want.
All very annoying and intensely frustrating!!!!!
|
| |