Re: BxeTextClipboard_keyhandler is not defined
Christian Stocker <[email protected]> Wed, 15 Nov 2006 13:23:14 +0100
| Newsgroups | gmane.comp.cms.bitflux.general |
|---|---|
| Organization | Bitflux GmbH |
| Message-ID | <[email protected]> |
Hi That was an error in our code. It's fixed now, you can do an svn up :) chregu On 15.11.2006 13:05 Uhr, Jason Lane wrote: > Hi people, > > I'm using Bitflux for the first time, so I may have missed some stuff. > However when I try and save in BXE_2 I get a > "BxeTextClipboard_keyhandler is not defined" error [line 1185 of > widget.js]. > > Any ideas? > > MTIA > > Below is my conf: > > <?xml version="1.0" encoding="ISO-8859-1"?> > <!-- $Id: config.xml 687 2004-04-29 08:32:39Z chregu $ --> > <config> > <files> > <!-- the following file definitions are presumably the most important > ones for BXE (= Bitflux Editor). They define, where exactly the > files > come from (and go to). > Some Remarks for the beginning: > - Be sure that all xml documents come with mime-type text/xml, > this is > important for files ending with .xsd/.xml and .xsl. Most > certainly you > have to adjust your webserver for doing that. > - You can't get different files from different servers/ports > (except css files) > For example, if "index.html" comes from somehost/index.html, you > can't > get the xml-file from otherhost/index.html, not even from > somehost:81/index.html. If you have can't avoid that, you need > some kind > of proxy script which redirect the traffic from one host to > another. I > wrote a PHP script, which exactly does that, if anyone interested, > contact me ([email protected]) > > You can define the file location in different ways: > The most standard is: > <file name="BX_xmlfile">xml/article.xml</file> > which gets the file with a HTTP-get from xml/article.xml > (relativ to > index.html) > > If you want to provide the location via an URL-Parameter: > <file name="BX_xmlfile" isParam="true">xml-url</file> > > and the request "index.html?xml-url=xml/article.xml" leads to > the same as the above > example. > > If you want to provide the location via an Javascript-Parameter: > <file name="BX_xmlfile" > isConfigParam="true">keyNameOfArrayElement</file> > > and the request bxe_start("config.xml",true/false, > array("keyNameOfArrayElement"=>"xml/article.xml")) leads to the same as > the above > example. (note: the example doesn't work, you have to create > your array in another way... > > Furthermore you have the option "prefix", which just prefixes > the url with > this value. The following example would do the same as above > again (postfix > is currently missing) > <file name="BX_xmlfile" prefix="xml/">article.xml</file> > > If you want to access your files with other methods than > http-get and put, you can > use the parameter "method". > It's only implemented for BX_xmlfile currently. If you need that > in more places, we could > certainly add it. > Default for BX_xmlfile is method="webdav" > Look at mozile/td/ for different implementation of it. > --> > <input> > <!-- The XML-document with the actual data --> > <!-- The default Method is "WebDav"--> > <!-- We are using isParam, which [should] suit[s] our structure > fine --> > <file name="BX_xmlfile" > isparam="true">http://dev.www.onshare.com/en_gb/cms-test/loadsave.php?XML=http://dev.www.onshare.com/en_gb/cms-test/reviews/2006/01/01.xml</file> > > <!-- <file > name="BX_xmlfile">/common/js/cms/scripts/loadsave.php?edit-url=/en_gb/cms-test/reviews/2006/01/01.xml</file>--> > > <!-- the xsl file --> > <file > name="BX_xslfile">/common/js/cms/onshare.conf/onshare.xsl</file> > <!-- The XSL-document which transforms the xml to the output > format --> > <!-- The RelaxNG (XML Schema) --> > <file > name="BX_validationfile">/common/js/cms/onshare.conf/onshare.rng.xml</file> > <!-- the language file --> > <!-- optional, if you want just english, you don't need it --> > <!-- <file name="BX_langfile">../../lang/fr.xml</file> --> > </input> > <output> > <file name="BX_exitdestination">/en_gb/cms-test/index.php</file> > </output> > <!-- You can't provide a different "method" than http.get for the > following files --> > <css> > <!-- Document specific css, which you should adjust. --> > <!--<file>/common/js/cms/css/main.css</file>--> > </css> > <scripts> > <!-- > These are the to be included js files > the important .js files are included by bxeLoader.js, but > you should > not have to worry about them. > You can also add your own js-files here. > --> > <file>/common/js/cms/js/bxehtmltb.js</file> > <file>/common/js/cms/js/table.js</file> > <file>/common/js/cms/mozile/jsdav.js</file> > <file>/common/js/cms/mozile/td/webdav.js</file> > <file>/common/js/cms/mozile/td/example.js</file> > <file>/common/js/cms/mozile/mozilekb.js</file> > <file>/common/js/cms/relaxng/AttributeVDOM.js</file> > <file>/common/js/cms/relaxng/NodeVDOM.js</file> > <file>/common/js/cms/relaxng/DocumentVDOM.js</file> > <file>/common/js/cms/relaxng/ElementVDOM.js</file> > <file>/common/js/cms/relaxng/DocumentVAL.js</file> > <file>/common/js/cms/relaxng/NodeVAL.js</file> > <file>/common/js/cms/relaxng/ElementVAL.js</file> > <file>/common/js/cms/relaxng/RelaxNG.js</file> > <file>/common/js/cms/onshare.conf/onshare.js</file> > </scripts> > </files> > <options> > <option name="lang">en</option> > <option name="serverIncludeFunction">cope2_serverIncludeURL</option> > <option name="serverIncludeElement">include</option> > <option name="autoParaElementName">para</option> > </options> > <!-- here we define the buttons for the top button bar --> > <buttons> > <!-- > the dimension tag is for defining the dimensions of your > button image and how > large each button is. > --> > <dimension width="120" height="140" buttonwidth="20" > buttonheight="20" /> > <!-- For each button, we need a definition > attributes: > col: in which column the button is in the button image > row: in which row the button is in the button image > name: the name of the button, this has to be unique and > is used as tool tip at the moment > ns: a namespace associated to the button (usually the > namespace of the element to be inserted) > type: The type of the "event" which should happen > "function": This function will be called, when the > button is clicked > "insertElement": This element will be inserted > "event": This event will be triggered > > If there's no "type" attribute, but a "action" > attribute, the event in the action attribute > will be triggered. > > If type "event" or the action attribute is defined, > the event gets the value of @name as parameter. > examples: > - inserts the element xhtml:b at cursor position > <button name="b" col="1" row="1" type="insertElement" > ns="http://www.w3.org/1999/xhtml">b</button> > - calls the function DoSomething(), when clicked > <button name="b" col="1" row="1" > type="function">DoSomething</button> > - triggers the event ToggleTextClass (and makes the > selection bold in this example) > the 2 examples are the same, the later is here for > backwards compatibility. > <button name="b" col="1" row="1" type="event" > ns="http://www.w3.org/1999/xhtml">ToggleTextClass</button> > <button name="b" col="1" row="1" > action="ToggleTextClass" ns="http://www.w3.org/1999/xhtml"/> > > --> > <button name="b" col="1" row="1" action="ToggleTextClass" > ns="http://www.w3.org/1999/xhtml" /> > <button name="em" col="0" row="1" action="ToggleTextClass" > ns="http://www.w3.org/1999/xhtml" /> > <button name="sub" col="4" row="1" action="ToggleTextClass" > ns="http://www.w3.org/1999/xhtml" /> > <button name="sup" col="5" row="1" action="ToggleTextClass" > ns="http://www.w3.org/1999/xhtml" /> > <button name="clean_inline" col="0" row="6" action="CleanInline" /> > <button name="link" col="0" row="5" action="InsertLink"/> > <button name="unlink" col="1" row="5" action="DeleteLink"/> > <!-- > <button name="create_table" col="2" row="5" > action="InsertTable"/> > <button name="Unordered_List" col="3" row="2" > action="UnorderedList"/> > <button name="Ordered_List" col="2" row="2" > action="OrderedList"/> > --> > <button name="Copy" col="0" row="4" action="ClipboardCopy" /> > <button name="Cut" col="1" row="4" action="ClipboardCut" /> > <button name="Paste" col="2" row="4" action="ClipboardPaste" /> > <button name="Image" col="3" row="5" action="InsertImage"/> > <button name="Save" col="1" row="6" action="DocumentSave"/> > <button name="Undo" col="3" row="6" action="Undo" /> > <button name="Redo" col="4" row="6" action="Redo" /> > <button name="Asset" col="2" row="6" action="InsertAsset"/> > </buttons> > <plugins> > <!--<plugin name="ServerClipboard"> > <option name="urlfunction">bxe_serverClipboardURL</option> > </plugin>--> > <!--<plugin type="gallery"> > <parameter name="virtualDir" > value="/en_gb/localisedresources/img/news/reviews/" /> > <parameter name="columnsPerPage" value="3" /> > <parameter name="rowsPerPage" value="3" /> > <parameter type="flickr" name="username" value="chregu" /> > <parameter type="flickr" name="userid" > value="49503135872@N01" /> > </plugin>--> > </plugins> > </config> > --bitflux-cms mailing list > [email protected] > http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms -- christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 44 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | [email protected] | GPG 0x5CE1DECB -- bitflux-cms mailing list [email protected] http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms