You are not logged in.
That setting does not do what you think it does - it forces all high-ascii (greater than 7 bit) characters to be url encoded even when they normally are not, but it does not affect what happens to lower ascii characters at all.
If you are in chrome, hit CTRL-SHIFT-J now and type into the console:
escape("{")
and you will see that indeed, it is escaped to %7B by the browser.
That's just how javascript's escape() function works.
Your best solution is to use some string manipulation on your end to replace %7F with { and %7D with } once you have the content out of Xinha.
Try BaseHref configuration.
This issue was identified and protected against 1 year ago in http://trac.xinha.org/ticket/1515
The source of this is...
contrib/compress.php
contrib/compress_yui.php
you should delete these files (or add a .htaccess etc, see the ticket and revision)
You should just call the event handler directly from the SaveOnBlur function.
SaveOnBlur.prototype.xinha_update_textarea = function () {
this.editor._textArea.value = this.editor.outwardHtml(this.editor.getHTML());
myEventHandlerHere();
}
You must call the DOM0 onsubmit of the form (ie yourform.onsubmit() ). Or use yourxinha.getHtml() to get the HTML and add it into the textarea yourself.
Just initialize Xinha after you display the block. How you go about doing that is entirely dependant on your own Javascript code.
I think most people use a checkout from the trunk which you are happy with (I'd suggest, the current head) along with their own modification as necessary.
"Releases" have never been a priority or much other than arbitrary lines in the sand.
Personally, I would set a class on the image, and then use javascript where you are using the HTML produce by Xinha to link up the images with that class. That would be the easiest way. Or even just modify EFM to put an onclick on the image would probably work.
Err, add your CSS stylesheet where you use the HTML you create in Xinha.
Or if you want the CSS to apply within the Xinha editor, add it to the pageStyleSheets config...
xinha_config.pageStyleSheets = ["/css/myPagesStyleSheet.css","/css/anotherOne.css"];
ExtendedFileManager.js
Search for: "var img = image;"
Just below there is the code that inserts or updates the image in the content from the selected image in the EFM, so somewhere there you will want to do your wrapping in an achor and modification of the sizes to make it thumbnailed.
Reduce the error_reporting setting in your PHP (you may need to search the ExtendedFileManager files to see if it sets it's own, I doubt it does though, so just your .ini setting will likely be all that is required.
$("#ins_news").submit(function(){
testo = xinha_editors.areapress.getEditorContent();
titolo = ins_news.titolo.value;I see some likely problems straight away.
testo and titolo are not declared, so they are global variables, I doubt you want that.
ins_news is not declared, so it is a global variable, and possibly isn't defined at all!
For example, you should better have code like...
$("#ins_news").submit(function(){
var titolo, testo;
var ins_news = $('#ins_news');
testo = xinha_editors.areapress.getEditorContent();
titolo = ins_news.titolo.value;Upgrade to latest trunk and try there. Also search forum here for IE9 problems.
Very likely a permissions/path issue.
Look at the server logs (or use a browser like Chrome or Firefox which can tell you) and see the 404 or other server errors which are being thrown because your permissions or paths are incorrect.
I expect you'll need to create your own initialisation routine, the example "xinha_init" won't be for you. Read the function, see what it does, and write your own to do what you need when you need it.
Read these methods:
Xinha.makeEditors
Xinha.startEditors
in the XinhaCore.js
At a minimum, you need to create a Xinha object and then call generate on it
var ed = new Xinha(your_textarea, your_xinha_config);
ed.generate();
You should use CSS to do it where you USE the content you created in Xinha, not in Xinha itself.
Use Xinha to create HTML, use that HTML somewhere, and use CSS in that place to enforce your style concerns.
If it is to be used in an email (email clients have bad CSS support), I would suggest just using a regexp to match all img tags and make sure they include hspace/vspace as necessary - again, nothing to do with Xinha.
It goes in your Xinha configuration in "Step 3".
Eg in the testbed.html, that's around Line 89
http://trac.xinha.org/browser/trunk/exa … d.html#L89
Naturally you need to ensure that your Xinha config is processed by PHP!
All you are doing is using the xinha_pass_to_php_backend() PHP function to put some stuff into your Xinha's config object in a tamper-proof manner.
I would just stick your user id in the PHP session, and then modify the PHP code in ExtendedFileManager to look for the user id there and ... do whatever it is you want to do with it.
Don't mess about trying to pass it on URLs and such, just use the PHP session.
Is the file in which you have the above PHP statements actually being executed by PHP? Looks like it is "testbed2.html" which in at least typical default server setups would not be parsed by PHP.
The clue is in the method name, "insertHTML", is what you are inserting valid HTML, no it is not.
Valid HTML would be "this is a test to insert to <the editor>"
That is the Linker plugin. Do not enable the Linker plugin if you don't want to use it. The normal create link dialog will show which does not have a tree structure.
I dont' recall if Xinha itself sets a minimum but the browser might.
If Xinha does, you'll find it in XinhaCore.js I expect in the method which sizes the editors (going from memory, oddly enough called _sizeEditor)
Sounds a bit like magic quotes is switched on.
I am not aware of any problem with Firefox in trunk. If you have a problem with Firefox in trunk, must be your computer. You will have to debug it. Use Firebug to observe errors.
You don't even say what browsers you are using.
Upgrade to trunk.