I worked around this issue by assigning session variables in my "add" and "edit" pages. Because I'm using the editor in different parts of my CMS, I could not define the value of strEditorContent in the RTE_textarea.asp file alone. The data for that string had to be able to come from different tables in my database.
The workaround requires editing the pages where the forms reside so you need to know simple coding but it basically boiled down to this:
On the RTE_textarea.asp page, I change the value at the bottom from strEditorContent to Session("strEditorContent")
On the pages where I add a record, I define the variable as:
Session("strEditorContent") = ""
On the edit pages, I define the variables right after opening up the recordset:
Session("strEditorContent") = rs.Fields.Item("field").Value
That also makes the code defining strEditorContent in the display_message.asp page irrelevant so I commented it out. Any instance of the variable was replaced with the session variable.
No, it's not perfect but it works. It's also important to make sure that non-cached pages show up when the add and edit files are loaded into the browser. Of course, that opens up a whole other can of worms because of the ways "no-cache" in the header works in different browsers. For a tutorial on work around for that, see
http://www.htmlgoodies.com/beyond/nocache.html
I don't know how folks will react to this (since it's not really integrated into the whole RTE "system") but that's how I got it to work for me.
Edited by cbeaudry - 14 December 2004 at 8:07pm
textarea from database
Topic Options
Post Options
Thanks(0)
somebody with some ASP knowledge help me with the code recently posted. I am testing the possibility to use RTE while ADD entries to a db and while EDITING past entries. While ADDING works great, but TO EDIT I canīt SEE on the EDIT PAGE the content from the DB in a Rich text browser.
