You are not logged in.
Yes, they do the same job in the end, you really only want one of them (although don't know why they would conflict in that way).
Must be a problem in your Stylesheet
1: Check that the stylesheet is loaded properly (look in Firebug)
2: Use firebug to Inspect the button and look at styles on it
3: Look for errors in firebug console
4: Use process of elimination to find problem in stylesheet (delete stuff until it works then you know what the problem is).
Ahh, I agree. I've never used XinhaLoader.js (I didn't develop it either!), but I always thought that it's sole purpose in life was to show loading messages. So if you don't want loading messages, lose XinhaLoader :-)
I wonder why we have that config option at all, seems it wouldn't do much.
I would guess that your config is happening too late in the process (so loading has already started when you set showLoading = false)
Change it in the XinhaCore.js itself.
Agree, hide the loading with the config option, I never use it.
Also, you need to have the textarea displayed (visible) when doing generate, sounds like you already do, but just make sure, otherwise things tend to get screwy.
There is a lot more than only XinhaCore.js that gets loaded, it's all the ajax loaded parts of Xinha that can get stuck in cache.
Try a different browser, Google Chrome for example.
Clear out your cache totally. Try again.
Check all security setting in firefox.
Try different browser (chrome).
Yes if you like, we really have no "stable" or "beta", indeed releases are really just "when somebody feels like it", most everybody should (and to my knowledge does) take Xinha straight from trunk :-)
Largely correct. Paste is handled by the OS in almost all cases. See the config options however in XinhaCore.js, but if you are using Mozilla, none of that has effect owing to the fact that paste in Mozilla can only be done by CTRL-V (security restriction) which is not captured.
Yes I think stripBaseHref is what you want.
However: the handling of links in this regard can differ browser to browser. If it were me, I'd be handling this server side (and I do), by using a regular expression search/replace to ensure that all links are correct. Of course the old adage of not trusting aything the browser sends your server stands anyway ;-)
The HTML provided by word/your OS is outside of the control of Xinha, Word must provide div tags to the copy buffer.
Although I don't recall Word doing that, perhaps your source Word document is poorly designed/formatted (which is pretty much par for the course with 99% of Word documents!)
ejucovy is a new and welcome developer to Xinha :-)
ejcovey: See the addToolbarElement method in Xinha.js, DefinitionList doesn't use it (it just pushes onto the toolbar), but could, and probably should insert it's buttons somewhere around the standard list buttons.
In it's simplest form it takes as three parameters
1: the button id (previously registered with registerButton)
2: the id of the button you want to insert this button relative to
3: one of, -1 for "insert before", 0 for "replace" and 1 for "insert after"
look for errors in your javascript console.
Recommend you use absolute paths (/sandbox/images/) and I think a trailing slash is required.
Simple reason is, that's largely how the browsers handle contentEditable/designMode, by making a document in an iframe editable.
It's not in any way like using a textarea.
No, I'm fairly certain that all need to be the same language.
Can't help you with IIS/Windows server configuration.
Typically you can't use asp and php both in a page. One or the other. Name your file .php, or port php-xinha.php to asp.
Sounds to me like your .html is not being parsed by PHP. Have you configured your IIS to run .html as PHP?
Correct you can't set in the textarea html tag itself unless you write something to do it in your config step 5, like perhaps this...
function merge_object(a,b)
{
for(var j in b)
{
if(typeof a[j] != typeof b[j] || typeof b[j] != 'object')
{
a[j] = b[j]
}
else
{
merge_object(a[j], b[j]);
}
}
}
for(var o in xinha_editors)
{
var xn_eval = "{ }";
var xn_config = null;
if(typeof xinha_editors[o]._textArea.hasAttribute != 'undefined')
{
if(xinha_editors[o]._textArea.hasAttribute('xinhaconfig'))
{
xn_eval = xinha_editors[o]._textArea.getAttribute('xinhaconfig');
}
}
else if(typeof xinha_editors[o]._textArea.xinhaconfig != 'undefined')
{
xn_eval = xinha_editors[o]._textArea.xinhaconfig;
}
var xn_config = null;
try
{
if(!/^\{/.test(xn_eval)) //\}
{
eval("xn_config = {" + xn_eval + "}");
}
else
{
eval("xn_config = " + xn_eval);
}
}
catch(e)
{
try
{
xn_config = eval(xn_eval);
}
catch(e)
{
continue;
}
}
if(typeof xn_config == 'object')
{
if(typeof xn_config.toolbar != 'undefined' && xn_config.toolbar.length)
{
xinha_editors[o].config.toolbar = xn_config.toolbar;
delete xn_config.toolbar;
}
merge_object(xinha_editors[o].config, xn_config);
}
}then you could use
<textarea name="youreditor" xinhaconfig="{ toolbar: [
["popupeditor"],
["separator","formatblock","fontname","fontsize","bold","italic","underline","strikethrough"],
["separator","forecolor","hilitecolor","textindicator"],
["separator","subscript","superscript"],
["linebreak","separator","justifyleft","justifycenter","justifyright","justifyfull"],
["separator","insertorderedlist","insertunorderedlist","outdent","indent"],
["separator","inserthorizontalrule","createlink","insertimage","inserttable"],
["linebreak","separator","undo","redo","selectall","print"], (Xinha.is_gecko ? [] : ["cut","copy","paste","overwrite","saveas"]),
["separator","killword","clearfonts","removeformat","toggleborders","splitblock","lefttoright", "righttoleft"],
["separator","htmlmode","showhelp","about"]
] }"></textarea>Because nobody made it. Feel free to make a plugin to do it.
In your config.
/** STEP 5 ***************************************************************
* If you want to change the configuration variables of any of the
* editors, this is the place to do that, for example you might want to
* change the width and height of one of the editors, like this...
*
* xinha_editors.myTextArea.config.width = '640px';
* xinha_editors.myTextArea.config.height = '480px';
*
************************************************************************/Looks fine, you must have introduced another error or bad file permissions.
Use absolute paths. For example
images_dir = /home/you/public_html/images
images_url = /images
also check the settings in the xinha configuration for strip_base_href
First, ensure your cache is totally empty.
Then try again. If it doesn't work, open firebug and look in the console and network panels, perhaps something is reported there.