You are not logged in.
Only way I can think off the top of my head would be to hook into updateToolbar (I think there is a plugin method which can hook here) and then scan the edited dom to find such table-in-table and remove it. But I think it would be quite slow.
Sounds like a server issue. Use the developer tools in Chrome, or Firebug to look at the response you are getting to requests, first one I'd look for is scan.php (part of Linker).
Try in a different browser for a start.
Yes, could be a proxy issue if the proxy is broken or blocking the code for some reason, perhaps it's a ad-blocker or something too.
Perhaps it's late, but I don't see where you are calling any of the Xinha initialization code. If you are just using "Xinha.addOnloadHandler(xinha_init);" then that's not going to do what you want, it would be a race condition with your Ext.onReady I'd expect.
As for the previous, do it outside Xinha. Xinha is for HTML (tag soup), it will probably be well-formed XML but not likely to be valid XHTML at all.
You don't, not from Xinha. Add it after you get the data from Xinha into your web application's backend.
You will need to use your browser's developer tools/javascript debugger to investigate further. My GUESS is that it is something to do with the change to the selection model in IE and the changes done in Xinha to work with it.
It's not a big enough issue to put my time into at the moment. Patches very welcome though.
I doubt that GoogieSpell would work, it appears to be for textareas only.
A quick look at NHunspell indicates to me that it is an engine which you woudl have to write an interface for.
Your best bet probably is to rewrite the SpellChecker plugin in .NET and maybe use NHunspell as it's engine (instead of the aspell engine).
Correct, Firefox (and others?) does not permit Javascript to access the clipboard for security reasons. This security restriction can be disabled by editing the firefox config from memory, but because it's not a very good thing to do, Xinha does not promote (or support) this.
You can simply replace the [] with ["cut","copy","paste","overwrite","saveas"] in the above to have the buttons appear, but if it will work for you or not depends on the browser.
I don't recommend having these buttons at all.
Less than with 0.95!
Interesting, it seems to be a bug in sizing the iframe.
I don't have time to look into it currently, but you might find the cause in Xinha.prototype.sizeEditor (XinhaCore.js)
Could be a standards/quirks mode thing maybe.
Let me know if you find it.
Please use Xinha 0.96.1
Inspect the CSS within your browser's developer tools - it's easiest to select Inspect Element outside the Xinha area and drill down through the iframe in your DOM inspector. At a guess you might find there is padding or margin on the body element somewhere.
It is simply not valid. Read the W3C HTML specification, write valid code.
You probably have invalid HTML.
<table><form><tr>and
<table><tr><form>are INVALID HTML and will cause this effect.
Linker is a plugin, remove it.
http://trac.xinha.org/wiki/NewbieGuide
/** STEP 2 ***************************************************************
* Now, what are the plugins you will be using in the editors on this
* page. List all the plugins you will need, even if not all the editors
* will use all the plugins.
*
* The list of plugins below is a good starting point, but if you prefer
* a simpler editor to start with then you can use the following
*
* xinha_plugins = xinha_plugins ? xinha_plugins : [ ];
*
* which will load no extra plugins at all.
************************************************************************/
xinha_plugins = xinha_plugins ? xinha_plugins :
[
'CharacterMap',
'ContextMenu',
'ListType',
'Stylist',
'Linker',
'SuperClean',
'TableOperations'
];Does your server support PHP?
Various pugins require PHP, Linker is one of them (unless you bypass scan.php with your own alternative).
<textarea><?php echo htmlspecialchars('<h1>The HTML</h1><p>You want to edit.</p>'); ?></textarea>Or whatever the equivalent is in your preferred language.
The below however is NOT valid, very common mistake...
<textarea><h1>The HTML</h1><p>You want to edit.</p></textarea>Yes, remember to entise (in php, use htmlspecialchars)
First, Xinha is not intended for precise anything.
Second, have you tried with 0.96.1?
Third, try with different paragraph handler (see config).
Your checks seem like a fine idea to me, for your specific case.
You can report a bug for ImageManager that it should check more carefullly that delete etc is permitted, but if it gets fixed is another question (of course, you could fix it and submit a patch :-)).
Yes probably is a bug really, there is not sufficient checking to prevent deleting *from the default directory*.
You should use a different directory (images_dir) than the default (which is "demo_images"), and do NOT set the directory in the config.inc.php, use the proper passing method, this will make it much harder for people to attack.
with(xinha_config.ImageManager)
{
<?php
require_once('/path/to/xinha/contrib/php-xinha.php');
xinha_pass_to_php_backend(
array(
'images_dir' => '/path/to/images',
'images_url' => '/images',
'allow_upload' => true
)
);
?>
}Xinha can only edit HTML, the only way to edit RTF with it, is to convert your RTF into HTML (and back again!) - probably not practical at all.
"Rich Text" is often used in two contexts,
1) in a specific sense to mean ".rtf" files, which is a specific format of file used by word processing software intended for cross platform document sharing, not that common these days since Word .doc files basically won the war.
2) in a generic sense to simply mean "text with other stuff like images, tables etc" for which HTML, and word docs, and whatever else all qualify.