You are not logged in.
I see that your setup can't work this way, but ad hoc I wouldn't know how to solve the issues, unfortunately.
If you want support, I'd ask ask and advise you to load Xinha the way described here: http://xinha.webfactional.com/wiki/NewbieGuide
Is it right that you refer to the backslashes before the quotes? That's PHP's magic quotes function, you can easilyremove them like this
$value = (ini_get('magic_quotes_gpc') ? stripslashes($value) : $value);
If you mean that the quotes are encoded into > (which I don't see in your post, but maybe it's because of the forum display), there's nothing todo about it
Edited: Sorry,I have been waiting to long. What was here before was not my answer, just an accident ![]()
You have not set the right paths
It should be /editor/xinha/XinhaCore.js instead of /xinha/XinhaCore.js and also _editor_url = "/editor/xinha/"
You don't need the script tags (<script type="text/javascript"></script>) inside the .js file
This exception has nothing to do with Xinha; I don't know if it's the source of your problem, but I doubt it.
If your problem persists, I would ask you to put your stuff on a server, than one can see it in action. It's hard to see problems just by looking at the code
rename your config file to a .php extension
maybe you also have to add
header('Content-type: text/javascript');at the top of the file
Don't worry, that's not a bug, it's a feature ![]()
We are using opacity effects for some things as disabling the buttons and it's a simple fact that IE doesn't support the CSS opacity property, so we have to use Microsoft's proprietary filter effect.
The other error has nothing to do with Xinha, it's from Trac, the system that runs the Website
you have to load XinhaCore.js before my_config.js
ExtendedFileManager is a full replace for and advancement of ImageManager. You don't have to and should not enable both. Please check if there are any conditions in that the error occurs and submit a ticket.
Without any information about the configuration that is ignored, I doubt that anybody can give you an answer
Let me here say thet the great thing about Stylist is thet it allows to select more than one class at a time, which wouldn't be possible with a simple select. May may wish to try the DDynamicCSS plugin instead
The setting where text is only submitted after changing to text mode normally happens when the form is submitted without prior execution of the onsubmit event (form.onsubmit() in javascript).
You can see this in your application by applying this test case:
1. Enter the edititing mode and wait for the editor to be loaded
2. open Firebug and execute the following line in the console
document.forms[0].onsubmit = function () {alert('onsubmit is executed NOW')}3. click OK.
YOu will notice the alertbox only appears after the editor has vanished
4. repeat steps 1-3. you will now notice the alert popping up BEFORE the editior disapperas
I have no idea why this happens, but maybe it helps you track the error
btw. nice application
but I sense the danger of massive memory leaking issuses
btw do you have any idea where these junk characters at the end of some paragraphs come from?
I have tested your page in both IE6 and 7 and everything worked, except that the page always scrolled to bottom when switching from HTML to WYSIWYG.
Safari is indeed not supported at the moment. I would like to see that though, but I'm not sure when this will happen.
I'm sorry, this was my fault. It has to be
function saveme()
{
var editor = xinha_editors.xinhaeditor;
editor._toolbarObjects.savesubmit.cmd(editor);
}I recommend you update your installations.
Download it from here: Downlodad
Read the change log here: Change log
put it in the config below this line
xinha_config = xinha_config ? xinha_config() : new Xinha.Config();The appropriate CSS selector for the HTML view is .htmlarea textarea.xinha_textarea , so you could add something like this to your document
<style type="text/css">
.htmlarea textarea.xinha_textarea {font-family: Times !IMPORTANT;}
</style>This bug has recently been fixed. There will be a new release within the next few days, if you could wait so long
I could add a switch to the plugin, if you really ask me for, though I'd rather suggest you to simply add a button to the toolbar using the code below
// create the button
// parameters: id, tooltip ,image url, whether button should be enabled in text mode, the function to call on button click
xinha_config.registerButton("save", "Save", _editor_url + "images/ed_save.gif", true, function(editor) {editor._textArea.form.submit()});
// add the button to the toolbar
// parameters: id (the one given above), next to which button, before|replace|after (-1,0,1)
xinha_config.addToolbarElement("save", "popupeditor", -1);just fixed in the trunk see http://xinha.webfactional.com/ticket/1091
sorry the svn URL is http://svn.xinha.webfactional.com/trunk/
You can obtain the source code with proper variable names by either checking out svn from http://svn.xinha.python-hosting.com/trunk/ or downloading the Nightly from the download page
Hi Sergio,
please report bugs in our ticket system.
Paste your text in the HTML view
var xinha_table = xinha_editors.youreditor._htmlArea; // this the Xinha table that lives where the textarea used to be
var container = xinha_table.parentNode;To check whether a given object is a Xinha you could check for the existence of a characteristic member, e.g.
var isItaXinha = typeof yourobject._htmlArea == 'object';1) FullScreen has not been a "real" plugin for ages, as it has always been loaded automatically, even if not in the xinha_plugin list.
The distinction between "plugins" and "modules" has been introduced to show which parts have to be present for Xinha to work ("modules") and which are optional ("plugins"). When I did this change I failed to realize that obviously many people were including FullScreen in their plugin list. Sorry for that, folks.
2)No, unfortunately not.