Problem after upgrading from v7.3.4 to v7.4

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

    #16
    You need to find it. In entityDefs.
    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

    • rodrigocoelho
      Active Community Member
      • Jun 2016
      • 296

      #17
      Originally posted by yuri
      You need to find it. In entityDefs.
      But what should be the midkey? I have to find in other working json?

      Comment

      • yuri
        Member
        • Mar 2014
        • 8442

        #18
        It's a link. There should not be midKeys but I need to see it to know what caused the problem.
        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
          • 8442

          #19
          You can zip and upload the whole custom folder.
          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

          • rodrigocoelho
            Active Community Member
            • Jun 2016
            • 296

            #20
            Originally posted by yuri
            You can zip and upload the whole custom folder.
            sent via email.

            thanks

            Comment

            • yuri
              Member
              • Mar 2014
              • 8442

              #21
              I'll look into and let you know.
              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
                • 8442

                #22
                You have a link "aimsuns" in User.json. It declares that there's a foreign link "users" on Aimsun side. But in Aimsun.json there's no "users" link. You might have removed it somehow.

                Either remove the link in User.json or add a needed link manually in Aimsun.json.
                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
                  yuri commented
                  Editing a comment
                  All these fixes will definitely tidy up your instance
              • yuri
                Member
                • Mar 2014
                • 8442

                #23
                There are more issues, I'll look into.
                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

                • rodrigocoelho
                  Active Community Member
                  • Jun 2016
                  • 296

                  #24
                  Originally posted by yuri
                  You have a link "aimsuns" in User.json. It declares that there's a foreign link "users" on Aimsun side. But in Aimsun.json there's no "users" link. You might have removed it somehow.

                  Either remove the link in User.json or add a needed link manually in Aimsun.json.
                  Ok, it worked.

                  I entered in the site. It asked me to disable de maintenance mode, I did it, enabled the cron and cache in preferences. After saving, it took a long time to respond, gave timeout in the crm window, and now this is the error when doing php command.php rebuild...

                  Code:
                  PHP Fatal error:  Uncaught RuntimeException: Bad data stored in 'data/config.php. in /var/www/html/espocrm/application/Espo/Core/Utils/Config/ConfigFileManager.php:97
                  Stack trace:
                  #0 /var/www/html/espocrm/application/Espo/Core/Utils/Config.php(299): Espo\Core\Utils\Config\ConfigFileManager->getPhpContents()
                  #1 /var/www/html/espocrm/application/Espo/Core/Utils/Config.php(286): Espo\Core\Utils\Config->load()
                  #2 /var/www/html/espocrm/application/Espo/Core/Utils/Config.php(97): Espo\Core\Utils\Config->getData()
                  #3 /var/www/html/espocrm/application/Espo/Core/Container/ContainerBuilder.php(168): Espo\Core\Utils\Config->get()
                  #4 /var/www/html/espocrm/application/Espo/Core/Application.php(62): Espo\Core\Container\ContainerBuilder->build()
                  #5 /var/www/html/espocrm/application/Espo/Core/Application.php(54): Espo\Core\Application->initContainer()
                  #6 /var/www/html/espocrm/command.php(35): Espo\Core\Application->__construct()
                  #7 {main}
                    thrown in /var/www/html/espocrm/application/Espo/Core/Utils/Config/ConfigFileManager.php on line 97​

                  Any idea why?

                  Comment

                  • rodrigocoelho
                    Active Community Member
                    • Jun 2016
                    • 296

                    #25
                    empty space, probably. Now, I lost the config.php info.

                    Will try to recover from backup

                    Comment

                    • rodrigocoelho
                      Active Community Member
                      • Jun 2016
                      • 296

                      #26
                      Everything working now. Thanks Yuri. If you find something else, please let me know

                      Comment

                      • rodrigocoelho
                        Active Community Member
                        • Jun 2016
                        • 296

                        #27
                        yuri, now I'm having an error in History sideview of opportunities.
                        This is the log:

                        Code:
                        [2023-04-06 22:01:49] ERROR: (21000) SQLSTATE[21000]: Cardinality violation: 122                                      2 The used SELECT statements have a different number of columns; GET /Activities                                      /Opportunity/641e066e0be648006/activities; line: 76, file: /var/www/html/espocrm                                      /application/Espo/ORM/Executor/DefaultSqlExecutor.php
                        [2023-04-06 22:01:49] ERROR: (21000) SQLSTATE[21000]: Cardinality violation: 122                                      2 The used SELECT statements have a different number of columns; GET /Activities                                      /Opportunity/641e066e0be648006/history; line: 76, file: /var/www/html/espocrm/ap                                      plication/Espo/ORM/Executor/DefaultSqlExecutor.php​

                        Comment

                        • rodrigocoelho
                          Active Community Member
                          • Jun 2016
                          • 296

                          #28
                          Actually neither history or activities are being shown

                          Comment

                          • yuri
                            Member
                            • Mar 2014
                            • 8442

                            #29
                            Did you upgrade to 7.4.1?
                            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

                            • rodrigocoelho
                              Active Community Member
                              • Jun 2016
                              • 296

                              #30
                              Originally posted by yuri
                              Did you upgrade to 7.4.1?
                              Yes. using 7.4.1

                              Comment

                              Working...