Xinha Discussion Forum

Ja, ich habe dich schon verstanden.

Mit xinha_config.stripBaseHref = true; (das ist sowieso die default einstellung) wird vom anfang der URL der part abgeschnitten, der durch xinha_config.baseHref definiert wird. Mit der o.g. RegExp sollte dabei bei deinem Beispiel http://www.xy.de heraus kommen, was genau das bewirken sollte, was du möchtest.

//Step 3 im Newbie Guide
xinha_config = xinha_config ? xinha_config() : new Xinha.Config();
xinha_config.baseHref = document.location.href.replace( /^(https?:\/\/[^\/]*)(.*)/, '$1' );
/*
vielleicht stimmt die regex auch nicht, mach mal
alert(xinha_config.baseHref );
und prüfe ob genau http://www.xy.de herauskommt 
*/

Wenn es immernoch nicht klappen sollte, bin ich gern bereit mal einen blick auf deinen code zu werfen

Unfortunately this is a bit of a struggle, because it is done by the browsers.

Have a look at these config variables that deal with this issue:
xinha_config.expandRelativeUrl
xinha_config.baseURL
xinha_config.stripBaseHref
xinha_config.stripSelfNamedAnchors

What I meant is in this version you have to do this step from the newbie guide

             // THIS BIT OF JAVASCRIPT LOADS THE PLUGINS, NO TOUCHING  :)
             if(!Xinha.loadPlugins(xinha_plugins, xinha_init)) return;

because it loads important parts of the code.
This has been changed in the meantime and will be no different in the next release.

Leave out the doctype definition (=>quirksmode), and wonder!
Google "ie overflow quirksmode"

seems to be sth wrong with your files, try an update

Each array you want to index with string keys should be an Object.

Nevermind,  this happens to every php-coder

Hi, had a look at your code now and found the error
Change

tmpIconArray = new Array();

and the other instances of new Array() to

tmpIconArray = new Object(); // you don't want to use an "Array" here

or easier

tmpIconArray = {}; //this is the same as new Object()

var array = ['value1','value2'];
var associativeArray = {'key1':'value1','key2':'value2'};

(Just to show the difference)

Why it behaved differently with and without Xinha, I don't know

It's really simple: It does not more than what  would happen with an HTML submit button. The data of the form is sent to the URL defined in the action attribute of the form. Any further action is up to the server-side script.

If I get you right you want to load new contents in the editor. If that's the case, you don't have to insert a whole new textarea in the page. Use the Xinha method setHTML() instead.

var newHtml = "some HTML";

xinha_editors.myTextArea.setHTML(newHtml);

please give more details. see http://xinha.gogo.co.nz/punbb/viewtopic.php?id=899

Especially:
* have you checked the parameters in plugins/ImageManager/config.inc.php
* does this occur if you switch to HTML mode and back to wysiwyg

Ok I think there is nothing more at this point I can say without seeing the actual installation, sorry

It's also advisable to use the form /path/from/webroot/to/file/ (with leading slash)

Seems XinhaCore.js is not loaded.
Is suppose this path is wrong   

as it doesn't correspond with this