Known Issue: "Toolbar 'Custom' does not exist!" and Work Around

If you create an HTMLEditor preset using the Preset Manager and remove items from the toolbar, a javascript error will occur when viewing pages that use the preset:
"Toolbar 'Custom' does not exist!"


To work around the problem, create the preset while applying the HTMLEditor instance to the page instead of through the preset manager.

Go to Insert -> WebAssist -> HTMLEditor

Click the customize button next to preset and modify the toolbar buttons. When you click OK you will be prompted to save a preset.

You can then apply the saved preset to other pages without getting the javascript Error.

Sometime a simple workaround for me is simply upload the .js on custom folder which i usually forget when i change a lot of preset..

ps: i works in team environment, so we use check in/out feature...

This "solution" does not help! When do you finally post an update the fixes this problem!? Even reinstalling an deleting the Dreamweaver's cash still show all presets.

Good point Victor - this fixes the problem for me after I make edits by hand or through the wizard. I do not auto enable uploading related files so have to remember to send the related js files manually.

DW CS4 makes this so much easier where it shows you the related files across the top of the page - click the file to see the source code (if in Split View) then Ctrl-Shift-U to send that particular file to the server. THis has been saving me loads of time hunting down related files, then opening, editing, and uploading them individually.

I'm finding this very frustrating! Despite having created presets, when I make a change to the page, the editor 'loses' the default contants it should be updating. I then go back into edit the settings, apply the correct field, then when testing I get the "Toolbar 'Custom' does not exist" error. I then try to change it to one of the presets, but it fails every time. I'm really annoyed about this, as I only wanted to make a minor change and have so far wasted three hours trying to correct something which should work properly straight out of the box!

I now have numerous presets listed, but none of them work if I try to apply them -how do I get rid of them so I can start from scratch (yet again!)

To delete a preset, open the preset manager. Go to Insert -> WebAssist -> Preset manager. Select the HTMLEditor presets option from the product list. select the preset you wish to delete and click the delete button.

If you continue to have problems, please send a link to the problem page.

  then Ctrl-Shift-U to send that particular file to the server  

Another cool tip I had no knowledge of. Makes me wonder how many others I'm missing out on. Nice one, - thanks.

Originally Said By: Jason Byrnes

  If you create an HTMLEditor preset using the Preset Manager and remove items from the toolbar, a javascript error will occur when viewing pages that use the preset:
"Toolbar 'Custom' does not exist!"


To work around the problem, create the preset while applying the HTMLEditor instance to the page instead of through the preset manager.

Go to Insert -> WebAssist -> HTMLEditor

Click the customize button next to preset and modify the toolbar buttons. When you click OK you will be prompted to save a preset.

You can then apply the saved preset to other pages without getting the javascript Error.  

this doesnt work for us that have super suit cause we are stuck unless we pay again... for html editor so we stick to the last irite version that we can download, and no custom toolbar works any way to solve this????

See my reply to the other thread you started for this question:
showthread.php?p=32251&posted=1#post32251

Any progress on this problem? I encountered it trying to apply an editor to a dynamically named textarea and following the directions above did not resolve it.

I was also baffled that it wanted to name the element bio_php_echo_1 but the drop down also offered bio_<php echo $cnt1; ?>

I would humbly suggest that if all editing of the toolbar and styles is done by presets, that there be an option for site wide rather than DW wide presets. Anytime I apply a css file and styles, it will probably be just for that site and I don't want a ton of presets to accumulate, but I don't want to delete the site's presets either.

I am hopeful, but I am still struggling with this to the point it is easier to apply ckeditor myself than to use the extension.

Meanwhile, I have cleaned everything I did out and removed the generated presets and will try again tomorrow. The only variation on what I did was I customized the toolbar and did not create the preset at all. When I got the error, I came back and followed this procedure to generate a preset, but the error was still there. It might have been a caching error or because of my initial edit.