15.08.2013 Views

Ektron® eWebEditPro Developer's Reference Guide

Ektron® eWebEditPro Developer's Reference Guide

Ektron® eWebEditPro Developer's Reference Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Overriding User Customization<br />

Letting Users Customize the Toolbar<br />

You might allow users to customize <strong>eWebEditPro</strong>, but later need to implement a<br />

global change to the editor. For example, you may decide that users cannot edit<br />

HTML code.<br />

To override all user customization, follow these steps.<br />

1. Make the necessary changes in the configuration data on the server.<br />

2. Change the value of the interface name attribute. For example, if the<br />

attribute’s value is beta, you could change it to beta1.<br />

WARNING! If you override user customization, users lose all changes made to <strong>eWebEditPro</strong><br />

toolbars and menu configurations. If the users preferred those customizations,<br />

they must redo them.<br />

To understand how changing the interface name attribute of the configuration<br />

data updates all user configurations, read “Determining Which Configuration<br />

Data to Use” on page 256.<br />

Determining Which Configuration Data to Use<br />

When a user launches <strong>eWebEditPro</strong>, the following events occur.<br />

1. The browser reads the configuration data on the server to determine which<br />

data to use. The file name is the value of the interface name attribute.<br />

2. The browser looks for a customization file with that name in the temporary<br />

folder on the user’s computer. If it finds one, that configuration data<br />

determines which toolbars to display.<br />

If the browser does not find a customization file on the user’s computer, it<br />

defaults to the interface section of the configuration data on the server to<br />

determine which toolbars to display.<br />

Changes to config.xml Have No Effect<br />

Sometimes, you might change the configuration data but the changes have no<br />

effect. For example, you add buttons to the section of the<br />

configuration data, but the toolbar does not display them when <strong>eWebEditPro</strong><br />

loads in the browser.<br />

This table suggests how to fix this problem.<br />

Possible Cause Resolution<br />

Wrong configuration file - You did not modify the<br />

configuration file that is being loaded. It is quite<br />

common to edit the wrong file.<br />

Double check all the paths and the config parameter to<br />

ensure that you are using the correct configuration.<br />

Search for all config.xml files on the server.<br />

<strong>Ektron®</strong> <strong>eWebEditPro</strong> Developer’s <strong>Reference</strong> <strong>Guide</strong>, Release 5.1, Revision 1 256

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!