Error loading page of Module Builder

[rpothin]

Hello,

Working on a project on the latest versions of SugarCRM (6.2.0 and 6.1.6), I encountered an error in loading the page in the Module Builder, this error being visible under / var / log / httpd / error_log.

Below are the errors displayed in the error_log, after page load Module Builder (some files are missing):
----------------------------------------------------------------------------------------------------------------------------
[Wed Jun 08 09:47:51 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/include/javascript/yui/build/layout/blank, referer: http://172.16.20.18/SugarCE-Full-6.1...=index&type=mb
[Wed Jun 08 09:47:51 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/include/javascript/yui/build/resize/blank, referer: http://172.16.20.18/SugarCE-Full-6.1...=index&type=mb
[Wed Jun 08 09:47:51 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/include/javascript/yui/build/tabview/blank, referer: http://172.16.20.18/SugarCE-Full-6.1...=index&type=mb
[Wed Jun 08 09:47:51 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/include/javascript/yui/build/treeview/blank, referer: http://172.16.20.18/SugarCE-Full-6.1...=index&type=mb
[Wed Jun 08 09:47:51 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/include/javascript/yui/build/calendar/blank, referer: http://172.16.20.18/SugarCE-Full-6.1...=index&type=mb
[Wed Jun 08 09:47:51 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/include/javascript/yui/build/datatable/blank, referer: http://172.16.20.18/SugarCE-Full-6.1...=index&type=mb
[Wed Jun 08 09:47:52 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/include/javascript/yui/build/paginator/blank, referer: http://172.16.20.18/SugarCE-Full-6.1...=index&type=mb
[Wed Jun 08 09:47:52 2011] [error] [client 172.16.20.123] File does not exist: /var/www/html/SugarCE-Full-6.1.6/cache/themes/Sugar5/css/layout_sprite.png, referer: http://172.16.20.18/SugarCE-Full-6.1...ss/yui.css?c=1
-----------------------------------------------------------------------------------------------------------------------------

These errors are sometimes accompanied by:
-----------------------------------------------------------------------------------------------------------------------------
PHP Warning : ZipArchive::extractTo(.../cache/upload/upgrades/temp/CFq4aP/): failed to open stream: Is a directory in .../include/utils/php_zip...php line 74
-----------------------------------------------------------------------------------------------------------------------------

I initially became aware of these errors on version 6.2.0 when tested on the module builder, which were concluded by an error (below) during a test deployment package.
-----------------------------------------------------------------------------------------------------------------------------
"An error has occured during deploy, your package may not have installed correctly."
-----------------------------------------------------------------------------------------------------------------------------

Having found no solution on the forums, I then moved to version 6.1.6, where the deployment of a package is done, it seems, properly, but I noticed the same errors appear.
I have therefore concluded that these errors were only due to the loading of the page ...

In that case, why does the deployment is done correctly on version 6.2.0?
Version 6.2.0 is it a stable version?

For information, the server is running on Cent OS 5.5 with php 5.3.6 and mysql 5.5.13.

Thank you in advance for your help.

[sts]

Error messages with "blank" files:
That does not seem to be an error with the new releases. I've checked my logs and I found the same messages (for the files with "blank" in the name) with my 6.0.1 installation. It only occurred for a short time after installation and then never again. As far as I remember there were no problems to fix. At least I never had serious problems with that installation.

The other messages I've not seen yet. Maybe there is a problem in creating files:
Did you check the access rights for cache and the other directories where the package/module deployment will put files?