Page 1 of 1

[Solved] TinyMCE cannot upgrade from 2.8.4 to 2.9.11

Posted: Wed Sep 26, 2012 4:44 am
by PBlue
After upgrade to cmsms 1.11.2, TinyMCE cannot upgrade from 2.8.4 to 2.9.11.

Screen:
TinyMCE cannot upgrade to 2.9.11.png
Any clue for this?

Re: TinyMCE cannot upgrade from 2.8.4 to 2.9.11

Posted: Wed Sep 26, 2012 7:19 am
by staartmees
upload the xml-file http://s3.amazonaws.com/cmsms/downloads ... 2.9.11.xml to your computer and upgrade TinyMCE Extensions > Modules and at the bottom of the page you can upload the xml-file to your website.

Re: TinyMCE cannot upgrade from 2.8.4 to 2.9.11

Posted: Wed Sep 26, 2012 2:47 pm
by PBlue
staartmees wrote:upload the xml-file http://s3.amazonaws.com/cmsms/downloads ... 2.9.11.xml to your computer and upgrade TinyMCE Extensions > Modules and at the bottom of the page you can upload the xml-file to your website.
I followed it and below error message was encountered:

No file was uploaded. To install a module via XML you must choose and upload an module .xml file from your computer. (empty tmp_name) (Troubleshooting)

Please kindly advise.

Re: TinyMCE cannot upgrade from 2.8.4 to 2.9.11

Posted: Wed Sep 26, 2012 8:10 pm
by Dr.CSS
I would look in the system info page for any yellow ! or red X, it could have to do with folder permissions...

Re: TinyMCE cannot upgrade from 2.8.4 to 2.9.11

Posted: Thu Sep 27, 2012 6:26 am
by PBlue
Dr.CSS wrote:I would look in the system info page for any yellow ! or red X, it could have to do with folder permissions...
I found below message from "Site Admin -> Admin Log":

ERROR DETECTED: Class 'XMLReader' not found at /var/www/html/mirror/lib/classes/class.moduleoperations.inc.php:217

Please advise what to do next.

Re: TinyMCE cannot upgrade from 2.8.4 to 2.9.11

Posted: Thu Sep 27, 2012 5:26 pm
by Dr.CSS
Try unpacking CMSMS again, maybe something is missing...

Re: TinyMCE cannot upgrade from 2.8.4 to 2.9.11

Posted: Fri Sep 28, 2012 3:13 am
by PBlue
Problem found: php-xml has not been installed!

#yum install php-xml

and then restart Apache solved the problem.

Thanks for all the help!