Custom Query
Results (40 - 42 of 11754)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #40 | fixed | avoid this.DOMDocument has no properties | ||
| Description |
If the user hasn't configured properly the paths and/or the permissions to send xml files he may get an error trying to load for example the StylesXmlPath file. I've added some extra code (in my branch) in FCKXml.prototype.LoadUrl so he can learn better of the problem and see what the server has sent. If the reply can't be processed as XML then he can choose to see what the server has sent, hopefully this will lead to some people finding out their problems. |
|||
| #41 | worksforme | Firefox: ToolbarLocation=Out:elementId raises an error | ||
| Description |
I was trying to setup a "nice" sample file for the FCKConfig.BodyId setting and when I put the toolbar out of the editor the sample failed to load in Firefox raising an error, and trying to debug it makes Firefox crash really easily. I just don't know right now how to fix it, might be a timing issue: after the iframe for the toolbar is attached maybe the reference to the document isn't valid and must wait a little? For easier testing I've commited the html sample 14 although it will need still review before it's added to the trunk. |
|||
| #42 | fixed | The ol/ul list property window always searchs first for a UL element. | ||
| Description |
reported in https://sourceforge.net/tracker/?func=detail&aid=1559466&group_id=75348&atid=543653 The fix is in my branch: I pass a parameter in the url to the dialog and then according to that parameter I do the search for that item. |
|||
