You are not logged in.
remove plugins you dont absolutely need. They slow down the loading significantly.
actually the version i was using from a few months ago didnt have this problem at all and multiple editors in the page handled much better.
it turns out whoever put in this "feature" has caused not just the greying out of the toolbar but it actually unloads and loads ALL your plugins when its activated/deactivated. This is another example of something that wasnt in old versions that is completely useless and cuases undue slowdowns and performance hits.
you could easily do this by putting in a tag such as "<pagebreak>" then have your processing language like PHP read it and output the data in the different pages. I just used multiple editors because we found it would be more likely for users to use it vs decide to break a page...
I found all kinds of problems upgrading. This was a very VERY annoying bug that pretty much makes linebreak useless and causes all kinds of issues using any plugins where you have no control over anything.
Look for "this.flowToolbars" in htmlarea.js and change it from true to FALSE. All should work then.
Will
Is there a way to turn off the focus editor effect (where buttons in the editor turn greyed out if outside of the editor)?
Is it me or is there not a way to put table operations button on a new line? I had it working on the old version, upgraded and now it spans 2 lines. Here is my config:
xinha_config.toolbar = [
["popupeditor","htmlmode","formatblock","fontname","fontsize","separator"],
["bold","italic","underline","separator","forecolor","hilitecolor","separator","removeformat","killword"],
["separator"], (HTMLArea.is_gecko ? [] : ["copy","paste","separator"]), ["undo","redo","linebreak","justifyleft","justifycenter","justifyright","justifyfull"],
["separator","insertorderedlist","insertunorderedlist","separator"],
["outdent","indent","separator","createlink","he3dimage","he3dfile","separator"],
["inserttable","toggleborders","separator","codebox","separator","he3dpreview","separator","he3dhelp","linebreak"]
];In firefox in the nightly example when I hit return it appears the cursor jumps to the first position then returns to where it is, causing a weird refresh effect. Can anyone confirm this?
The developer got frustrated with the code, so i'll just make a ticket for this
Has anyone tried to get phpSpell to work with xinha? http://www.master-technology.com/demos/spell/index.php . It seems like it might be a much simpler solution then the current spelll checker plugin that some of us cant get to work on our servers.
Ive talked to a developer and have hired someone to try to fix this problem.
I guess this is a bug because if you look at http://www.wysiwygpro.com/demos/demo1.php , and try a simple comparison (center some text then click left align) you can see they break you out of the div and start a new one. Xinha just places the div inside. On a page I tried formatting I ended up with about 9 nested divs...
Im finding there is no way to break out of a center. If you then align left it just adds another div inside the current div. Is there a way or workaround?
I will give this a shot as soon as I get a chance.
Thanks!
Will
Two reasons..
1. sometimes fixing bugs causes, or simply exposes other bugs
2. recently some changes were introduced into the trunk without discussing them properly first, currently the only remaining bug from these is http://xinha.python-hosting.com/ticket/337 . At this stage I am awaiting to see if somebody will fix this problem, if nobody does I might look at it to see if it's an easy fix, or will rollback the changes mentioned in http://xinha.python-hosting.com/ticket/329 I have discussed this with the developer in question and hopefully we won't see new core features introduced without discussion in future.
I was specifically refering to at least this bug: http://xinha.python-hosting.com/ticket/327 . It looks like some of the others have been fixed now. Good job.
But all of the new bugs i've found were without plugins loaded... so they must have been in core.
Gogo,
I looked at the bug fixes for 1.0, but it seems in the last few weeks there have been many new features added that have added new bugs. How can we insure the feature set is really locked and that only bug fixes are submitted at this point?
Thanks for all your efforts.
Will
in firefox, if you go to the nightly example on this site, put in 3 browsers, and click back and forth 5 times between the first and second browser the menus get all messed up.
I think i saw this happen whenever the code was added in that changed the menus from active to inactive...
can anyone confirm?
Will
Nice work!
Thats great. It doesnt look like too many changes. If only I had a damn mac (working on it) I could test it out...
1. We need a browser sniffer.
I recently found this sniffer which seems to let us access any information we need. Maybe overkill but might be worthwhile http://www.dithered.com/javascript/brow … index.html
Will
I dont know the answer to your question, but some other editors I had tried used div's instead of p's and none had the double spacing issue in IE. What was the reason xinha doesnt use that method?
well although ideal code is ideal, the reality is Apple users are growing more and more pro Safari. So if we dont support it they are going to complain and blame our sites for not supporting them. Because of this I am much more interested in finding a quick fix. Though that is party because we are building a site that supports an Apple only software so its something I now have to face... (even though I have no Mac and no damn safari)