Hi,

 

I just installed the php html editor, but I'm getting this error:

 

Warning: simplexml_load_file() [function.simplexml-load-file]: I/O warning : failed to load external entity "CuteEditor_Files/Languages/en-en.xml" in /home/MYACCOUNT/public_html/newsletter/CuteEditor_Files/include_CuteEditor.php on line 843

Jenny,

 

Do you know which version of PHP are you running on your site?

 

If you are not sure, please save the following into a PHP page and run it on your server:

 

<?php

// Show all information, defaults to INFO_ALL
phpinfo();

?>

Hi Adam,

 

It's 5.2.5.

 

Since I posted earlier, I discovered that the sample file works at a different location on my server, at least, I'm not getting any error.  I moved the location of the files (I didn't realize they had to be in the same folder as the file invoking the object - mea culpa!).

 

Now I'm getting these errors:

 

Warning: simplexml_load_file() [function.simplexml-load-file]: CuteEditor_Files/Configuration/AutoConfigure/Full.config:1: parser error : Document is empty in /home/wwdnet/public_html/newsletter/wwdnewsletters/admin/CuteEditor_Files/include_CuteEditor.php on line 1106

Warning: simplexml_load_file() [function.simplexml-load-file]: in /home/wwdnet/public_html/newsletter/wwdnewsletters/admin/CuteEditor_Files/include_CuteEditor.php on line 1106

Warning: simplexml_load_file() [function.simplexml-load-file]: ^ in /home/wwdnet/public_html/newsletter/wwdnewsletters/admin/CuteEditor_Files/include_CuteEditor.php on line 1106

Warning: simplexml_load_file() [function.simplexml-load-file]: CuteEditor_Files/Configuration/AutoConfigure/Full.config:1: parser error : Start tag expected, '<' not found in /home/wwdnet/public_html/newsletter/wwdnewsletters/admin/CuteEditor_Files/include_CuteEditor.php on line 1106

Warning: simplexml_load_file() [function.simplexml-load-file]: in /home/wwdnet/public_html/newsletter/wwdnewsletters/admin/CuteEditor_Files/include_CuteEditor.php on line 1106

Warning: simplexml_load_file() [function.simplexml-load-file]: ^ in /home/wwdnet/public_html/newsletter/wwdnewsletters/admin/CuteEditor_Files/include_CuteEditor.php on line 1106

Jenny,

 

Can you tell me your file structure?

I am getting the same sort of error:

 

Warning: simplexml_load_file() [function.simplexml-load-file]: I/O warning : failed to load external entity "CuteEditor_Files/Configuration/AutoConfigure/simple.config" in /clientdata/clients/m/e/menzies.org.au/www/editor/CuteEditor_Files/include_CuteEditor.php on line 1209
Error while parsing the toolbar configuration fileCuteEditor_Files/Configuration/AutoConfigure/simple.config

 

these files have just been moved from another server where it worked perfectly..

 

any ideas on what i need to look at?

RYann556,

simplexml_load_file is enabled by default in PHP5. Please contact your host and find out why simplexml_load_file is not supported on your server.

 

Keep me posted

adam,

I stumbled on this thread whilst looking for the answer to why I was getting an error message "Error while parsing the toolbar configuration file/Configuration/AutoConfigure/Simple.config.

 

In my case it was very simple; In the call to the editor in my php script was the line

 

$editor->AutoConfigure="simple";  //Select Toolbar

 

but should have been

 

$editor->AutoConfigure="Simple";  //Select Toolbar

 

i.e. with an uppercase 'S' at the start of the word 'Simple'.   Whatever is specified here has to match exactly (case sensitive) with  a filename in the CuteEditor_Files/Configuration/AutoConfigure folder - the '.config' extension to the filename is added for you.

 

I just had the same problem after uploading a working website to my hosting provider. This also turned out to be a problem with upper-/lowercase of the config files.

I found out that  I could even upload admin.config TWICE to my hosting provider if one filename starts with uppercase and the other one with lowercase. I don't know if this has got to do with unix/linux or something else, but it's a bit misleading.

 

I prefer to keep everything lowercase anyway, and that solved the problem. Still got another one now (menus cannot be loaded???) but I suppose that hasn't got anything to do with this...