Sugarcrm 4.5. Studio Does Not Work

[THEBLADEJANE]

Hello,

I just installed SUGARCRM 4.5. as downloadable and run into issues when opening the Studio ->

The layout Studio does not load completely...means that the site is not completely loaded ( in the html-source the stream suddenly stops ) and I therefor cant do anything, means that the Studio is completely unusable.

When I try to add a custom field and save it, it is not saved really and does not show up neither in the list or in the customized module (e.g. Accounts) .

Running on Apache 2
PHP
MYSQL 4.1.14

Anybody with any idea ?

Thanks in advance,

[psbrogna]

One minor thing that may or may not help is that when I was adding in custom fields in 4.5, I had to click 'save and publish' to see the changes take affect anywhere. I don't know what the 'save' button does.

[eduardobaer]

I am having exactly the same problem...
the Studio Layout page does not load... anyone can help?

Regards,
Eduardo

Hello,

I just installed SUGARCRM 4.5. as downloadable and run into issues when opening the Studio ->

The layout Studio does not load completely...means that the site is not completely loaded ( in the html-source the stream suddenly stops ) and I therefor cant do anything, means that the Studio is completely unusable.

When I try to add a custom field and save it, it is not saved really and does not show up neither in the list or in the customized module (e.g. Accounts) .

Running on Apache 2
PHP
MYSQL 4.1.14

Anybody with any idea ?

Thanks in advance,

[damiankarlson]

To those having problems with the Studio -- if you've uploaded the package anywhere, it is possible that a page wasn't transferred properly. Try uploading again. Better yet, run an md5sum against the compressed file locally, upload it to your site and run md5sum again to compare. If it matches, unzip the file in the appropriate folder and continue.

I've been running the 4.5 code for a while now. I was running daily builds, and now I'm running the GA drop. Studio is working great for me. The site is in development, and I run it locally on my notebook during development.

D

[JWG]

I am having the same problem, the Studio : Edit a Module : Accounts (or any of the others) : Edit Layout comes up with a blank page as per the attached screen dump.

Regards - Jack

[antcrm]

Same here in our 'production' environment. The problem does not appear on my test systems. The main difference between
production and testing environment is the PHP version (4 vs. 5). All systems comply to the given requirements in the Sugar4.5 release notes. That is all I know for the moment.

server production: PROBLEM
-PHP Version 4.4.2-1.1
-Mysql 5.0.24-Debian_3-log

server etch: WORKING
-PHP 5.1.4-0.1
-Mysql 5.0.24-Debian_1-log

server sarge: WORKING
-PHP 5.1.6-0.dotdeb.2
-Mysql 4.1.15-Debian_0.dotdeb.4-log

[JWG]

The problem server is running:

Suse / 9.1
Apache / 2.2.2
PHP / 5.1.4
MySQL / 5.0.21

[jeffjw]

We're having the same issue with the Studio. I can't seem to edit any of the layouts.

PHP Version 5.0.4
Apache/2.0.54 (Fedora)
Zend Engine v2.0.4-dev
MySQL 4.1.20
mbstring installed as a PHP module

Warning: Please upgrade Studio Files using the upgrade in the administration panel

I've upgraded the studio files as mentioned in the warning, but the Studio still doesn't work for any of the modules I'm using; calls, notes, accounts, etc.

Jeff

[majed]

If you can do me 1 more favor.

Replace this line in config.php
error_reporting(0);

with

//error_reporting(0);

Then go into studio and let me know what the error is that is printed on the screen.

We have changed the error_reporting level to 1 in studio for patch b so that people will have more information when fatal errors occur. The reason we adjust the error_reporting level is because in the code there are sections that report errors when no record id is passed in. These notices are important when running the application, but not so important when editing layouts in studio.

Thanks,
Majed

[majed]

Just found a machine that can reproduce this issue. You have register globals turned on this is causing the scope of a session variable and a global variable to collide. This has been addressed and will be availbale in 4.5 If you would like to fix on your local machine do a global replace of $GLOBALS['studio'] with $GLOBALS['studioConfig']

Thanks,
Majed