7 Jul
2009
7 Jul
'09
9:47 p.m.
On 7 Jul 2009, at 10:18, Marius Dumitru Florea wrote:
Good point! I never noticed this. Maybe this is the header to a 404
or login page?
What's the syntax of that page? Is it XWiki 2.0?
Is it the new WYSIWYG editor? Are you also using a Gecko based
browser?
Hi Marius
Thanks for the reply. The page is indeed XWiki 2.0 format, and I can
view it using both Firefox and Camino.
The previous errors doesn't seem to be related to
the WYSIWYG code.
I noticed you use the HTTPS protocol. The fact that the response has
text/html mime type instead of text/css could mean that the requested
style sheet was not found (lack of authorization maybe?).
Hmmm, well it's a possibility, but how would it be able to work on my
machine? I can view the editor logged in as me or her.
The previous errors are style sheet related and
shouldn't stop the
editor from loading.
Ok - I won't worry too much about the CSS
Error: missing
; before statement
Source File: https://wiki.patchspace.co.uk/xwiki/bin/skin/resources/js/xwiki/xwiki.js
Line: 2, Column: 2
Source Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML
1.0 Strict//EN"
The response looks like HTML instead of JavaScript. The reason could
be
that the script file is not found (as it happens with the
stylesheets).
Again, maybe the use of HTTPS and lack of authorization triggers this. None of the previous JavaScript files are related to
the WYSIWYG
code so
they shouldn't stop the editor from loading.
Can you try using HTTP and see what happens? (I'd like to know if
HTTPS
is really causing the troubles). Also, don't forget to clear the error
console before the page is loaded in edit mode.
If the page syntax is XWiki 2.0 (thus using the new WYSIWYG editor)
then
you can try to comment these lines in templates/wysiwyginput.vm :
#template("stylesheets.vm")
#template("javascript.vm")
Finally check the server log/console after the page is loaded in edit
mode to see if there are any exceptions or useful messages.
Thanks for these suggestions. As soon as I we get time, I'll make
these changes and see if it diagnoses the problem.
Thanks for the quick reply!
Cheers
Ashley
--
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran