You are not logged in.
What version Xinha?
A small bug, if you m change your default error_reporting PHP setting to ignore warnings it will help. Otherwise, on that line change "is_null" to "isset".
I'll ticket this so ImageManager is tested sometime with warnings enabled.
It's a PHP builtin see the PHP manual.
You should use mysql_real_escape_string instead of addslashes becase who knows if mysql will change in the future to need something else quoted.
You have magic_quotes_gpc turned on. This means that anything in $_GET/REQUEST/POST will already have slashes added to it, invisibly and automatically.
I strongly suspect it's a problem in your PHP, not us. Can you duplicate using the example code.
First, why are you using stripslashes, addslashes escapes (roughly, you should really be using mysql_real_escape_string()) special characters, mysql doesn't store the slashes, ergo, you don't stripslashes on the way out because there are none (if there are, you probably had magic_quotes_gpc turned on in the first place, the wisdom of that is left for another day).
Second, you havn't given anywhere near enough information to help you.
This is a known and long standing bug in mozilla.
Nothing we can do about it - https://bugzilla.mozilla.org/show_bug.cgi?id=148794
Just remove all plugins you do not require (you probably do require Enter-Paragraphs and FullScreen even if you're not specifying them), leave the rest which is of negligable size anyway.
Your example is completely incorrec html, of course the browser screws it up for you, it doesn't know what to do with it.
Firstly, you should be using double quotes. Secondly you do not escape by using backslashes anywhere in HTML or XML for that matter.
Use ' as the proper HTML entity "escape sequence" for ' if you must use single quotes to quote attributes.
Read the newbie guide, it tells you how to add plugins.
I don't think it would be possible. If it were, it would be
1. very difficult to implement
2. very slow
3. very unreliable
new plugins are always welcome however, knock yourself out ;-)
Do it server side in your language of choice. Eg in PHP $cleanContent = preg_replace('/<\\/?p>/i', '', $dirtyContent);
Please post a ticket in the bug system and state which plugins you have selected and any errors you get, I see there was a recent change to the GetHtml plugin.
There is that windows character set that gets used quite often... ummm....Windows-1252, could be that?
Xinha is only a "widget" how you put it to use is up to the developer. Xinha in and of itself does not provide any useful function out of the box, you must write the other stuff to use it however you wish.
Xinha is an HTML editor, not a php, or asp, or jsp or whatever editor.
There is currently no built in way to do this, all HTML edited by xinha must be well formed valid html.
For example, this is not...
<table>
<? ... ?>
<tr>
</tr>
<? ... ?>
</table>
for two reasons, firstly <? ... ?> isn't valid HTML (the browser *might* let you away with it because <? is a processing instruction in XML, but I doubt it), and secondly because you can only put thead, tbody, tfoot and tr inside a table tag.
There has been talk in the past about making something like the dreamweaver "shielded" code, but it's not clear how that would work with keeping the HTML code valid for Xinha.
Your styles don't specify any classes, there is nothing for the user to select from.
I think it's just more the fact that we don't have any developers who use RTL languages so we're not at all familiar with how these things are normally done :-)
If there are any developers out there who use some rtl language on a computer please chime in, even better if you know Javascript :-)
Interesting, looks like Xinha might be winning against FCK over there. The RTL problem hasn't been reported before that I am aware of, looking at the code it's obvious that it would be a problem (because the rtl/ltr button only changes the direction of the parent block element). I don't know if EnterParagraphs (or IE) would maintain that directionality in new paragraphs created by hitting enter in the changed one, I doubt it.
When you change style related to Xinha in Gecko (eg set display:none on some ancestor, change position, visibility etc) you should deactivateEditor() before doing it, this works around bugs in gecko.
It's done by the browser, not Xinha. Either is a valid CSS colour specification.
Could be many reasons, what browser for a start. My advice.. live with it, the web isn't supposed to be pixel perfect.
Other than that, try setting pixel based fixed widths.
You have a character set mismatch I expect. The second URL you give is served as UTF-8, that's good. Check that the page you have Xinha running on is also served as UTF-8.
You must add it to the toolbar
xinha_config.toolbar.append(['AddContent']);
Also, I can't run DeerPark A2 because it has a nastily regular habit of causing XFree to totally lock up (my guess is it's throwing the old unexpected async reply) so no input works, can't even switch out to the console or ctrl-alt-backspace, forcing me to do a hard reset of the machine, which really ticks me off. I'm not keen to see if FF1.5 still does that, 1.0.6 doesn't at all.
There has been a bug reported against DPA2 for quite some time: https://bugzilla.mozilla.org/show_bug.cgi?id=301869
Nobody at moz seems to be interested though.
I'll look when I get a chance, but not any time soon. I look forward to your fix, or bug report to moz (as it seems likely a bug in moz, not xinha) ![]()