I got it.
The problem was that cuteeditor refuses to render (either a textbox only or a nonfunctioning editor with javascript errors), when not being put into a server form.
Nothing can be done to avoid this problem from my position.
Since my project uses userdefined forms (the classical way without postbacks and viewstates) i did not want to have the server form that results in a client form.
Before migrating to .NET2.0 i wrote kind of a hack to simulate a server form that now didnt work any longer due to some internal changes.
I now have a simple httphandler rendering the page contents, userdefined controls and the cuteeditorwrapper control. this control will create a dummy page control, add a server form and an instance of the cuteeditor control and render. since the server form added is also a wrapper that removes its form markup, everything is fine now.
if someone is interested in the code (simple and relyable now), write me.
thanx adam for suggesting to help me.
it'd be great if you could give me some answers:
- what's done internally with the server form?
- where is the settings and user data saved, when not in the viewstate?
- is there any security lack or problem with my solution above?
cheers,
matt