Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 371 subscribers
  • Views 86 views
  • Users 0 members are here
Forum Actions
Related

Issues when doing upgrade 14.0.3 to 25

Adrian Arauz

Hi, we recently upgraded from version 14.0.3 to 25.1.2 and the environment is behaving strangely.

We've noticed that every time we perform a repair, we have to move sugar_grp7.min.js to the cache folder.

This ensures that the dashboard and module list views load upon login; otherwise, nothing is visible unless the screen is refreshed.

Has anyone else experienced this?



And we have another problem, the API usage isn't working correctly. In this case, looking at the console, we get a 200 but this message:

"no Route matched with those values"



Parents
  • 0 Sugar Employee Badge

    Hi Adrian,

    The problem pertaining to sugar_grp7.min.js would seem to indicate that the repair process is not successfully completing. That particular file is a core file corresponding to the Sidecar client. As for the reasons as to why the process may not be properly completing, that can vary from permissions problems, disk space issues or PHP settings. It is difficult to give you a specific reason without having a clearer understanding of your environment and corresponding configuration. However, I would suggest reviewing your PHP settings, it is possible that increasing the memory_limit, max_execution_time and/or max_input_time may help. In my case, mine are set to 1GB, 300 and 300 respectively, and is for a development environment that I use for various instances (ranging from version 13 - 25) with varying degrees of customizations. 

    As for your second problem, that usually happens when one specifies improper parameters when invoking the API. For example, to read a record in the Accounts module, my invocation needs to be GET /Accounts/<id> but I may get the error you are seeing (or other error) if my invocation doesn't match that. You need to share more details on what it is you are attempting to invoke via the API for us to provide you with more precise help. 

  • 0 in reply to Angel Magana

    Hi

    Thanks for replying. We have higher values ​​in the PHP file, with 4GB and 1200.

    The disk space issue can't be the problem because we have more than 500GB. Any suggestions?

    For the second problem, we discovered a very long timeout issue. We requested the server to increase the timeout, and it worked perfectly after that.

  • 0 Sugar Employee Badge in reply to Adrian Arauz

    What happens if you delete the contents of ./cache and then reload Sugar in your browser? Does it rebuild the contents properly? 

    Which version of PHP are you using? 

    I am having a hard time connecting timeout parameters to that API message you were getting. Per my previous reply, it is difficult to provide more useful guidance without a clearer understanding of the environment.

Reply
  • 0 Sugar Employee Badge in reply to Adrian Arauz

    What happens if you delete the contents of ./cache and then reload Sugar in your browser? Does it rebuild the contents properly? 

    Which version of PHP are you using? 

    I am having a hard time connecting timeout parameters to that API message you were getting. Per my previous reply, it is difficult to provide more useful guidance without a clearer understanding of the environment.

Children
No Data