Hi,

 

bit of an update. Got it to take content - by putting the Editor directly in the aspx page, not dynamically from the code behind.

 

However it now gets more complex. We're trying to use Atlas in this site (Microsoft's take on Ajax - so basically it doesn't post the whole page back and refresh the page, but makes the call behind the scenes so to speak and repaints only the relevant controls)

 

So the scenario is I have a Treeview on one side of the page - this automatically uses the callback functionality so it doesn't have to refresh the page, and dynamically loads a list of web pages and, under each of those, the content assigned to them. Clicking an item of content opens it for editing on the other side of the page. This side includes a text box for a name, summary, start and end dates etc and the CuteEditor (or it hopes to). Using Atlas the page doesn't need to do the whole postback and 'flicker' but the textboxes etc are redrawn with their new values.

 

If I take the Editor out of the page, this works as it should - I can debug and see values being assigned into text boxes etc on the page and all appears correctly. If I put the CuteEditor in, I can still see the values being assigned (including into the Text property of the Editor) but now nothing changes on the client, not even the textboxes which previously did.

 

Are there any known issues with Atlas/Ajax? It would take a lot of code to send the whole example, so are there any bits that might help?

 

Thanks

Clare