I want to make instances of the editor that just insert a media element - image, flash, pdf etc.   I stripped down the toolbars to reveal only the appropriate buttons, and it works great except --- how can I discourage the editor from surrounding the resulting tags with <p></p> tags - or any other tags for that ...

Any suggestions how I might apply regular expressions to the contents of the editor before it gets posted to a database?   I've got a couple of issues that this might fix.   1. The business of converting ''curly quotes'' to straight quotes 2. I need to fiddle with the paths returned by the link builder. Why? Its ...

No, the demo site worked fine.   On my pages, it asks if you want to clean the Word HTML, but it displays the ''curly quotes'', where on the sample site, it shows the straight ones. Then when the page is submitted all the curly stuff is just gone.   Hmmm, what could I have done wrong.....   It is version 4.5.0.1 as near as I ...

I've got a really cranky client who's unhappy that she's unable to paste word documents (were talking many)  into her site with this editor without losing all the quotation marks and apostrophes in her documents. My only solution (unsatisfactory as far as the client is concerned) is to do a global search and replace in Word to replace ...

Hi Adam I know, I must seem like a puppy that won't go away, but....   I have discovered that my configuration problem only occurs in my IE6 browser. Firefox works properly.   To recap the issue,  when I use autoconfigure="whatever" it works. If I use ...

It's not the renaming.   If I use ConfigurationPath=''~/CuteSoft_Client/CuteEditor/Configuration/AutoConfigure/Simple.config'' I get the error   but if say AutoConfigure=''Simple'' it works.   Also, the ConfigurationPath code works on my localhost, but not when I'm using my remote production server.Same file - go ...

I tried my other experiment - I took my custom config file, renamed it to simple.config, put it in the autoconfig folder, and it WORKED!!!   So, it seems there was/is something wierd about the ConfigurationPath command. The javascript error muttered about expecting a hex value around character value threehundred and something in the line ...

I got the simple menu buttons, but the same error. I'll email you the URL and you can try it yourself.   I'm also going to try another experiment - to rename my config file as simple.config and see if it doesn't work using autoconfig=''simple.config''   DOug

Ah, but wait ... there's still a glitch.   I keep getting a javascript error whenever I do a ConfigurationPath=''whatever.config''. My custom toolbar setup shows this, but it's also true of all the files in my autoconfig folder.   So if, for example, I say AutoConfigure=''Full'', everything works, but if I say ...

Rats!   Doug blushes! Operator error .... as usual.  Doug forgot to post his config file to the server. Doug apologises and tries to quietly slip away.....   Thanks   Doug