Upgrade 8.4.2 to 9.0.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • yuri
    Member
    • Mar 2014
    • 8631

    #16
    > It seems that the problem is caused by my custom entry points located in custom/Espo/Custom/EntryPoints/

    What exactly was in the problem file? It loaded the library code.
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    • DashingUno
      Member
      • Apr 2022
      • 48

      #17
      yuri

      As far as I understand, the issue is the mising required files as mentioned before?
      Should we just manually add them to the EspoCRM-upgrade-8.4.2-to-9.0.2.zip\vendorFiles\paragonie\random_compat\lib and be done with it
      Or will this be included in official version later down the line?

      Whats the correct course of action for us here?

      Comment

      • yuri
        Member
        • Mar 2014
        • 8631

        #18
        I don't think it's because of missing files. The v9.0 has breaking changes. Before upgrading, the script goes though custom files to check for incompatible usages. To avoid the system complete crash after upgrade, to prompt the user to fix incompatibilities first.

        It looks like some custom file includes the library code. Maybe though the "use" statement in the beginning of the file.
        If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

        Comment

        • yuri
          Member
          • Mar 2014
          • 8631

          #19
          Try uninstalling TCPDF extension, upgrade and then install it back.
          If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

          Comment

          • shalmaxb
            Senior Member
            • Mar 2015
            • 1622

            #20
            My experience with third party extensions:

            Sometimes the uninstall routine in Admin does not uninstall certain extensions completely. So after having uninstalled from the GUI go to the folders client/custom/modules and custom/modules to see if there is anything from one of the uninstalled extensions still present. Delete these files.
            Have a look in your database table "extensions" and delete as well all rests of those extensions.
            Rebuild your instance. In many cases this already solves such problems as described.

            After that, re-install your extensions one by one and see if all works well. If one extension starts to cause the problem again, it is likely a compatibility issue with the upgraded espoCRM version and the developer of that extension should take a look at that.

            Comment

            • Stefan
              Member
              • Jul 2021
              • 67

              #21
              Originally posted by yuri
              > It seems that the problem is caused by my custom entry points located in custom/Espo/Custom/EntryPoints/

              What exactly was in the problem file? It loaded the library code.
              HTML code that I include in several Entrypoints. There is no php code in the file, that is mentioned in the error message.

              To be more precise, I have a custom navigation bar for several EntryPoints in custom/Espo/Custom/EntryPoints/helper/navbar.php, which I load into the corresponding EntryPoints via include (<?php include('helper/navbar.php'); ?>) and this navbar.php was displayed in the error message.
              Last edited by Stefan; Today, 12:20 PM.

              Comment

              Working...