You are not logged in.
More correctly
<textarea name="html_content" id="html_editor"><?php echo htmlspecialchars($YourHTML)</textarea>Not using special chars would not be good ![]()
You cannot simply copy and paste an image from a word document into your HTML, it simply is impossible. You have to upload the file to the server, and link it. You can use the ImageManager plugin to do this, or the ExtendedFileManager, or InsertPicture. These plugins will all require PHP to be available on the server, and appropriate permissions set on the directory you are uploading images to.
var myHTML = xinha_editors.yourEditor.outwardHtml(xinha_editors.yourEdior.getHTML());
The majority of buttons will not work in text mode, textmode is just a plain textarea, not a contentEditable iframe.
Depends on your server environment. How did the "hacker" upload the phising files, through one of the Xinha plugins? Are you allowing uploading of files (through Xinha) to any old joe bloggs off the street?
In general, the PHP process needs to have write access to where it will write the files, some servers run PHP as mod_php which means it will run as the webserver's account ("nobody" or "www-data" usually), and so your directories probably need to be world writable. Some servers will run PHP code as your own user account, so your directories only need to be user-writable.
gusc: I'd suspect that IE makes it difficult and that whatever it was written for in the first place only had to be used in Gecko. Email me for SVN & Wiki access (make sure to put Xinha in the subject so I see it).
If I remember corrected, I tried to make it work with % heights when I re(re(re))wrote the framework of the editor iframe etc, but ultimately failed.
Xinha will submit it's contents just like a normal TEXTAREA element. You can do whatever you want with it once it gets to your server.
You need to ask WordPress developers. Xinha has nothing to do with that.
xinha_editors.yourEditor._onGenerate = function() { /* do your stuff */ }
set it after makeEditors and before startEditors
I have sent koto login details for SVN and Trac. As for EFM replacing IM. I think we should keep both. Some people might not require everything that EFM does and only wants and only want IM features (and not to mention, having a plugin disappear when people upgrade would be problematic).
The intention has always been to have a stable download of "1.0" when the list of bugs to be fixed for 1.0 was emptied. Like most things however, that list seems to shrink for a bit, and then grow again.
Perhaps if somebody would like to suggest a revision that they think is a candidate for "almost stableness" then I (or anybody else with Wiki access) can can put that online as a 1.0 pre-release ;-)
As for the broken-ness in IE, I'm not sure what IE's problem is, as you can see in the code mharris posted, the commented out stuff shouldn't ever be able to cause IE to infinite loop. Should it? I mean, it's setting a couple of styles on table cells, and doing the same on all the panels (of which there are probably 0 or 1).
No "devlopers" forum is necessary, that is what Trac and the bug tracker in it is for - http://www.xinha.org/
FYI we have 9 developers with SVN commit access and 15 with access to change the Wiki. All developers are busy volunteers who have jobs to do and businesses to run. More are always welcome.
Xinha is only designed to edit valid HTML. If your $someword$ is not valid HTML, expect it to be stripped (by the browser rather than Xinha).
Looks like you took the code from the example. You should simply follow the NewbieGuide
Doubtful it would work with Xinha, but whatever the case, we are not mind readers you would have to post a link to the script.
Ensure that your HTML is validly nested
<table>
<form>
<tr>
is invalid, as is
<tr><form><td>
invalid nesting can cause this type of problem.
Please see http://xinha.python-hosting.com/wiki/Tickets for info on how to create tickets, but yes key events are handled in _editorEvent.
Pressing enter causes a paragraph break, pressing shift-enter causes a new line. It's the same in word processors, and WYSIWYG html editors. It's also been discussed to death here before. Short answer - use CSS to make your paragraphs have less top/bottom margin.
All ampersands in HTML unless they form part of an entity are required to be converted to & no matter if they are in an element's attribute or text. That's the specification. The browser internally converts & to the raw ampersand.
As for absolute link stripping, there are a couple of config vars you can play with...
// specify a base href for relative links
this.baseHref = null;
// we can strip the base href out of relative links to leave them relative, reason for this
// especially if you don't specify a baseHref is that mozilla at least (& IE ?) will prefix
// the baseHref to any relative links to make them absolute, which isn't what you want most the time.
this.stripBaseHref = true;
Submit a feature request http://xinha.python-hosting.com/wiki/Tickets but I'm not sure if it's possible
Install the LiveHeaders plugin for Firefox and try it (and look at the headers to see if everything loads properly), chances are there is some permission problem or something and ImageManager is not getting installed.
Xinha only edits HTML, your special tags are not part of HTML, so you need to work around it somehow with some string replacements on the server side of things as you imagined.
Such a button would be easy enough to make,
xinha_config.registerButton({ id: 'hide_panels', tootip: 'Hide Panel', image : 'someimage.gif', textMode: true, action: function(editor) { edit.hidePanels() }});
or something close to that should do the trick.
See other thread.