Forums - Thread Details
  • State Not Answered
  • Replies 6 replies
  • Subscribers 318 subscribers
  • Views 1479 views
  • Users 0 members are here
Forum Actions
Related

Studio view not refreshed on Save

Artis Plocins

After moving a SugarCRM instance from one server to another we discovered an issue in Studio.

When modifying something in Studio, like adding or removing fields and panels in the Record View layout of the Accounts module, after clicking Save & Deploy the change reverts back to the previous state. If the page is reloaded or I click on Record View again, it shows the changes I just applied.

In the screenshot below I just added New Panel 13 with Alternative Postal Code. Once I click Save & Deploy, it disappears right there. If I refresh or click on Record View again, it appears to be saved - did not actually disappear.

To make things weirder, if I change something again after clicking on Save & Deploy and my changes disappearing, everything that I change and Save & Deploy stays changed and does not disappear on my screen. Then it stays working correctly for the module I did this for until cache refresh, After cache refresh, this behaviour starts over.

Parents Reply Children
  • 0 in reply to André Lopes

    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 {} \;

  • 0 in reply to André Lopes

    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.