Studio view not refreshed on Save

Hi Artis Plocins 

I believe there is a javascript error in there.

Before saving changes open the developer tools (press F12). Hopefully you will see some javascript errors at the console tab.

Let us know the error and the respective request at the network tab.

Kind regards

When Studio does not reflect your changes it's often a permissions problem.

You save, Sudio says saved, but in reality the filesystem could not complete the save operation.

Check your file permissions, my panacea is to run these from sugar root to make sure all files and directories belong to apache, and set permissions on all directories to 775 and all files to 664:

sudo chown -R  apache:apache *

sudo find . -type d -exec chmod 775 {} \;

sudo find . -type f -exec chmod 664 {} \;

Tried setting those permissions and it's not better. Setting them all to 777 doesn't make a difference either.

It's not like it can't save - it does save, but does not send back the data of the new state of it I think.

Hi, there is nothing at all in the JavaScript Console when clicking on Save & Deploy and when it disappears.

Also, no errors are added to the sugarcrm.log or Apache access.log and error.log.

I'm using a Chrome browser and it's happening for my colleagues too, and it does not happen on a different server, so it cannot be a browser issue or a SugarCRM version bug, but also, besides permissions, there isn't anything else I can think of that could affect it on the server.

Hello Artis Plocins,

We experience the same behaviour here.

Have you found a solution on your side?

Some other weird Studio behaviours seem to be related to this one. For example, we create a new dropdown field on a module, and we define a new dropdown list to associate it to the dropdown field. We can save the dropdown list but the list is not available in the dropdown field. We have to save the dropdown field as it is and then go back to the edit screen of this field to select the list we created...

Kind Regards,

Sylvain

For anyone who end up here, the problem is solved for us (thank you sugar support).

The issue is related to the Zend OpCache configuration.

By default, Zend OpCache has the value ( opcache.revalidate_freq ) set to 2seconds.

Because of the above default value, the changes in Studio are not updated immediately in the cache of Zend OpCache, thus you do not see them immediatelly in Studio.

By changing that value to 0, you will be able to view the changes in Studio as expected.
For the above change to be applied, you will have to restart apache.