Input area unresponsive

First off, apologies if a similar question has already been submitted/answered - i took a brief look through the first few pages and didn't see anything that seemed to match, but i could have missed it. I also looked through the docs and the code to see if there was an obvious solution to no avail.

I have been attempting to install the latest version of fckeditor (2.6.3), and everything seems to be set up, with one large problem: the text area seems to appear (there is a white box), but is unresponsive - no cursor, and no text appears when typing. I also notice that it does not have the border that it does in the demo and where i have seen it elsewhere - just a white background.

Firefox gives me no indication of a problem. IE, however, says there was a 200 server error when loading fckeditor/fckstyles.xml - specifically a syntax error (unexpected T_STRING on line 1). I have not touched that file, nor do i see any obvious problems with it (for what that's worth).

I suspect this to be some kind of error caused by some configuration on my server, but i'm not sure what. I *do* have xml files set to be parsed as php (for setting up rss feeds elsewhere), but i don't know why that would cause a problem - and unsetting that parameter doesn't seem to help. I don't see anything in php.ini that would be suspect either.

Thoughts?

~PS

Fri, 03/06/2009 - 03:26

conanman

Joined: 06/03/2009

Posts: 1

Re: Input area unresponsive

My error was in both I.E.7 and Firefox too.. the firefox message was more telling: it went something like this

Error: junk after document element
Source File: http://www.myurl.com/fckeditor/editor/fckeditor.html?InstanceName=FCKeditor1&Toolbar=Default
Line: 2, Column: 1
Source Code:
<b>Parse error</b>:  syntax error, unexpected T_STRING in <b>C:\www\myurl\www\fckeditor\fckstyles.xml</b> on line <b>1</b><br />

to see the actual error go to http://www.your.url.com/fckeditor/fckstyles.xml and it'll make sense...

cos i did that I figured this out. You have fallen foul of the W3C compliancy freakshow.

it is actually simple.. you have xml set to parse as php... that means that "xml" is not "xml" anymore but "php" you probably did this in apache at some point and something like this was probably in your httpd.conf.. you did this cos you wanted to at some stage and it's very useful... perhaps you're not the admin guy nevertheless the code will be to tell apache something like this:

AddType application/x-httpd-php .php .htm .html .xml

this also was done in conjuction with this in php.ini

short_open_tag = On

the two together means PHP will always think the fckstyles.xml file is PHP... it has a quick butchers at it sees the first <??> as CODE in php (sadly it's not code at all ) it's just the idiot who set up XML forgot that php uses those self same tags to mean something!!!! yes that's right <??> is all over the internet in 1.7 billion web pages as meaning "here comes some php" and yet the guy in W3c said "i'm more important that all of you the <? now means a (incredibley redundantl) nothing-to-do-with-php xml header declaration (that does actually nothing but sate his useless anality) and that (now) means ALL worldwide xml could fail without being aware of it.

<?xml version="1.0" encoding="utf-8" ?>

change that line in fckstyles.xml to

<?= '<' . '?xml version="1.0" encoding="utf-8"?' . '>'; ?>

and it will fix it