You are not logged in.
Xinha is for editing HTML, not PHP, your PHP makes the HTML invalid.
That said, look at PreserveScripts plugin.
Thanks wymsy, I'd forgotten!
Use latest trunk. Enjoy.
Well, you need to use <font> tags if you are dealing with email really, not CSS. You need to do some research in how styles in email works, because different email programs do different things with it.
I am not familiar with the software. You would need to contact the developers of webedit. This sort of thing requires knowledge of javascript and probably whatever programing language webedit is written in.
You need "something", either an existing CMS, or something you write yourself.
<% is not an valiud html or XHTML, or even XML tag. There is no such thing as <%, it's totally invalid. So it's not surprising that it does not work.
Try the latest trunk/nightly.
Sorry, I speak English only, but I can guess that your problem...
If Xinha is here: www.domain.de/admin/xinha
You should have: _editor_url = "/admin/xinha/"
Suggest you use Firebug and inspect the DOM/CSS to see what you need to alter.
Blockquote is probably only handled by the indent/outdent function in IE I suspect. This is all behaviour defined within the web browser itself.
All block elements are supported to my knowledge. Refer HTML specifications.
This isn't really a Xinha question, anybody can post anything they want to your server, no Xinha required, you should always perform input validation if you are using Xinha or not.
Xinha does not (claim to) produce valid XHTML, browsers are not strict about it, and Xinha really doesn't bother to attempt to enforce it (too difficult, too problematic).
You should simply strip out tags, attributes and URLs you do not wish present.
For PHP, I use a modified version of the Safe HTML parser by Roman Ivanov, it strips these
* <li>opening tag without its closing tag</li>
* <li>closing tag without its opening tag</li>
* <li>any of these tags: "base", "basefont", "head", "html", "body", "applet",
* "object", "iframe", "frame", "frameset", "script", "layer", "ilayer", "embed",
* "bgsound", "link", "meta", "style", "title", "blink", "xml" etc.</li>
* <li>any of these attributes: on*, data*, dynsrc</li>
* <li>javascript:/vbscript:/about: etc. protocols</li>
* <li>expression/behavior etc. in styles</li>
* <li>any other active content</li>
I modified it mostly to permit certain embeds which are OK, youtube etc.
Look at CharCounter plugin
Not using format block. It's built into browsers, it only understands block elements.
Look through the plugins, maybe something there, or create your own to wrap the appropriate span.
Compression should make no difference as long as yuou are using the same version, but I wonder if you are using the current trunk uncompressed and the old .96b or something compressed. In which case you should take the main trunk uncompressed and compress it yourself.
I never use compressed code, I leave that to the server (gz compression).
Span is not a block element, you can't do it.
You should use the current trunk, it contains many fixes.
http://trac.xinha.org/browser/trunk
Click "Zip Archive" at the bottom.
Thanks mokhet, that clears it up for your plugins, I'll make the changes for you later today.
@wymsy
From the HTMLArea licence,
1) Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
That's really the main point of the HTMLArea licence, doesn't say anything about not adding extra conditions, just that you can't take away that stuff. So, if the CC licence was applied in combination with that (a two part licence if you like), it would be OK from a technical standpoint I think to change as the plugin modifiers have done.
I think it's ok from a "intention of the BSD licence" standpoint anyway, the idea is not to restrict you, just to make it clear the author has copyright and bears no responsibility if it eats your grandmother.
Personally, I'd much rather see everything HTMLArea/BSD, that's the most useful to the developers who need to use Xinha without worry of licenceing.
Goes back to making a separate "not-so-free" package of these slightly awkward things. Maybe pulling them into their own subversion area too.
Thanks for raising this question Sven.
Generally speaking, Xinha is intended to be BSD/HTMLArea licensed.
Some plugins may be differently licensed, the fact that they are included probably implies that Xinha has (special) permission to distribute them, but they remain in their own licence, plugins are non essential and can just be deleted if you find the particular plugin's licence can not be utilised.
The Tango and Crystal icon sets have as you note CC and GPL licences.
It is not required to use these icon sets, you can remove the iconsets, and set
_editor_icons = 'Classic';A quick look at the code (Ray would know more) indicates that the bare default, where neither _editor_icons nor _editor_skin has been configured, would not use Crystal or Tango (effectively, it would use our own Classic).
In summary, I believe that you can remove these iconsets without any problem, same goes for any plugins which you don't want. In future, I suspect that we should probably make a separate distribution somehow.
Any other developers have an opinion... Ray?
At what point are you utilising $article_text
None that I can see!
Read how Linker plugin works, plugins/Linker/Linker.js
Please donload the latest trunk and try with that,
Go here: http://trac.xinha.org/browser/trunk
Click "Zip Archive" at the bottom of the page.