Forums - Thread Details
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 321 subscribers
  • Views 2996 views
  • Users 0 members are here
Forum Actions
Related

Problem when running CRM with php version

Yeris Nesme

Good day.

I am experiencing difficulties with SugarCRM CE Version 6.5.7 (Build 8576) when attempting to make it work with PHP 7 or later versions. After changing the PHP version on the CRM site, I am able to log in and navigate the system. However, when accessing records in the detailed view, not all information is displayed, and the related subpanels are not visible to me.

Is it possible that the PHP version I am considering is not compatible with SugarCRM CE Version 6.5.7 (Build 8576)?

I hope to have your support.

  • +1

    The issue is almost certainly one of compatibility. Sugar version 6.5 CE is way out of date and support as are all the platform components it requires to be installed upon. For reference these can be found here: https://support.sugarcrm.com/files/5da76182-6bfe-11e7-a575-06a1658893d7.pdf 

    I have had a recent (and ongoing) need to support a customer still using version 6.5 CE and to do this I have had to source and install a virtual machine running Ubuntu 12.04 in order to get the correct platform components. Even then these are the bundled ones as even the mirrors that provided the updates are no longer functioning.

    I suspect that you will need to follow a path similar to this in order to continue working with this instance.

    Thanks,

    JH.

  • 0 in reply to John Hawkins

    I appreciate the prompt response. After reviewing the documentation and discussions on other forums, a more specific question arises: Could you help me find out if SugarCRM CE version 6.5.7 (Build 8576) is incompatible with PHP 7.0 or later?

    The documentation I've read, and that you provided to me, suggests potential compatibility issues. Do you know of any success stories where SugarCRM CE version 6.5.7 (Build 8576) ran with PHP 7.0 or higher?

    Thank you, I'll look forward to hearing from you.

  • 0 in reply to Yeris Nesme

    The answer is no I'm afraid. I don't believe Sugar CE will run properly on anything higher than PHP 5.3 and you will definitely get issues if you try to run it in PHP 7 or above. I believe, from your original post, that this is what you have also found out in your current set up.

    The version is seriously out of date and not supported (hasn't been for many years now) and so the only way to really get it to work properly is to run it on the platform architecture it was built for. As per the document I linked.

    Thanks,

    JH.

  • 0 in reply to John Hawkins

    Hello John Hawkins,

    I appreciate the response and the provided information. I am in the midst of migrating SugarCE, making adjustments to custom modules based on the official PHP migration documentation.

    Given the statement that SugarCE may encounter issues in versions beyond PHP 5.3, I would like to know if there is any possibility that my migration process could be functional in PHP 7 or higher. Has anyone successfully achieved this transition or is aware of similar cases? I am interested in any positive experiences or additional considerations that can guide my approach.

    I am dealing with deprecated functions and updating them manually, which is why I have this uncertainty about the process I am following.

    Thank you for any guidance or shared information.

  • 0 in reply to Yeris Nesme

    There is always the possibility that your migration process could be successful. Given that the issue is that the Sugar CE code base has code (functions) that are not compatible with later versions of PHP then the answer is the process you are following which is to update the Sugar CE code base to use the replacement functions or workarounds that exist for later versions.

    I would very much doubt anyone is still using Sugar CE having ported all the code to the later versions of PHP as there are forks of Sugar (such as Suite CRM) and later, supported Sugar versions that have already done this. Given that, and the fact Sugar CE is no longer supported in any way, this would generally mean the work involved to do the porting is not worth it as migrating to a supported product would be easier and less likely to keep being an issue as PHP is updated in the future.

    If you want to persist in the migration then I wish you luck. I'm afraid I know of no "magic bullet" that would help you in this endeavour.

    Thanks,

    JH.

  • 0 in reply to John Hawkins

    Presumably, a bigger problem than just the custom code not being compatible with PHP v7 is that SugarCRM v6 itself is not compatible with v7?

  • 0 in reply to Acuitus

    There is no SugarCRM CE after v6.5 it was discontinued.

  • 0 in reply to Yeris Nesme

    I'm still managing one 6.5.16 instance for one of our client. They asked to estimate the migration to a suitable version (ie the latest one), I estimate it to more than 120 days, plus minus 20 days per major version. This is kindly what I've did for passing from 7.9.3 to 10.0.4 2 years ago.

    Finally, they didn't a migration in any way, I'm still doing dev for this version, even if it is really, reaally reeaaaallllyyyyy critical application that manages antenna lines for a telecom company :-)

  • 0 in reply to Enes Saridogan

    Sounds about right?

    A big change is that everything in the browser is javascript on a single page in v7+ and not multiple php pages in v6.

    So you have to know javascript, handlebars templates, backbone, as well as the Sugar API (which is php so we are familar with that at least!)

  • 0

    hi  

    Firstly, in case it helps here is the main support page that has an archive of unsupported versions going back to v6.0

    https://support.sugarcrm.com/documentation/unsupported_versions/

    Regarding upgrading to latest version, that would be the way forward but maybe not via the usual upgrade methods jumping through each version upgrade and applying multiple fixes, upgrade code customisations, integrations etc...

    I suggest treating it as if migrating to a new CRM - which in a way most of the code is - and use an ETL tool that will help with all the data transfer part. There are many around, from the free Talend Open Studio, various paid ETL tools, via SugarCRM professional services   , or depending on complexity and data size you could build your own API script.

    I'm guessing that your v6.5.x licenses have expired, so the process would be to start with a low 5 user license for the new version on SugarCloud as they also provide a sandbox version that you can use for initial testing. Or onsite if that's your preference.

    Recreate your customisations based on v13 (v14 from next month), then run the initial data migration, and test everything on the staging instance before final data migration on live.

    That would be my suggestion and I think the 'cleanest' method.

    Best wishes,


    Vincent

    .

    CRM Business Consultant