View Menu

Technical Support Forums

Free, outstanding support from WebAssist and your colleagues

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

Thread began 10/22/2009 6:49 pm by Jason Byrnes | Last modified 3/07/2010 8:54 am by Jason Byrnes | 4545 views | 21 replies


Partial Work Around and 1 Definite Bug

Ok, I have a partial work around, or further explanation of the work around provided, and one bug.

:eek: First, with regard to presets and toolbars. Click on somewhere on your page OTHER than the form element you want to apply the custom toolbar to and insert an HTML editor. This opens a BLANK HTML editor dialogue. Edit the preset as described at the beginning of this thread through that dialogue. Click OK to and save the preset, but cancel on the final dialogue to insert the editor. This saves a preset that does not include the instance (form element) name or initial value. Then use insert editor for the form element and apply the saved preset. At least that is what worked for me.

To edit the preset, again click outside of the form element and repeat the process as if inserting a new editor and cancel on the final step. Go back to your form element which will be listed as something like "MyToolbar (Custom)", change it to the updated preset. Click Ok, then edit it again to restore the initial value. At least that is what appears to be working for me.

:eek: Second, the bug is with regard to styles. I still can only do this manually or use styles if it is web site specific for each preset. Still I needed it, so I applied custom styles to the preset, but it was not working at all. The CSS file and body class were working, but none appeared in the style dropdown. Looking closer, I saw that there is a case error. The extension was producing XML like this:

<style name="accentPara" element="span" >
<Attribute name="class" value="accentPara" />

But it should be (emphasis added):

<Style name="accentPara" element="span" >
<Attribute name="class" value="accentPara" />

The strange thing is that when I look at the preset xml file, the case is correct. Also, if you edit the instance later without changing the preset and click OK, the style xml file gets corrupted apparently because the "style" settings for "MyToolbar (Custom)" are undefined. I had to edit the instance, re-apply the preset, and ctrl-z the change in the DW page to keep the edit and get the style xml file back, the correct the case error again.

Also, the extension source file should not contain the fckeditor default "Red Title" since it cannot be removed except by manually editing fckconfig.js.

P.S. This method to use styles creates the xml file with the name edit_undefinedStyles1.xml

Build websites with a little help from your friends

Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.

Build websites from already-built web applications

These out-of-the-box solutions provide you proven, tested applications that can be up and running now.  Build a store, a gallery, or a web-based email solution.

Want your website pre-built and hosted?

Close Windowclose

Rate your experience or provide feedback on this page

Account or customer service questions?
Please user our contact form.

Need technical support?
Please visit support to ask a question





Ease of use


security code refresh image

We do not respond to comments submitted from this page directly, but we do read and analyze any feedback and will use it to help make your experience better in the future.

Close Windowclose

We were unable to retrieve the attached file

Close Windowclose

Attach and remove files

add attachmentAdd attachment
Close Windowclose

Enter the URL you would like to link to in your post

Close Windowclose

This is how you use right click RTF editing

Enable right click RTF editing option allows you to add html markup into your tutorial such as images, bulleted lists, files and more...

-- click to close --

Uploading file...