Announcement

Collapse
No announcement yet.

EspoCRM 7.1.0 released

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • murugappan
    commented on 's reply
    Hi @macdpi , check if the UserID and Group ID correctly defined in the config as shown in unix "stat <your espocrm instance>" UID and GID respectively.

  • espcrm
    commented on 's reply
    You won't get much help using this thread.

    You might want to go with this method instead: https://forum.espocrm.com/forum/inst...age2#post61187

    Even I follow this method I still fail to get it working perfectly. I have to delete some 'bad' extension (code no longer compatible) for it to work.

    Also did you upgrade using CLI?

    I recently upgrade for about a month now, it working fine although I lost a few free extension which I could keep using without it.

  • macdpl
    replied
    After update from 6.1.10 there are blank screen - no login. The login page shows after set /data/config.php useCache to false. But after that i have problems:

    rebuild give 500 error and in log

    RROR: Slim Application Error Type: TypeError Code: 0 Message: Return value of Espo\Core\Utils\File\Permission::chownReal() must be of the type bool, null returned File: /public_html/application/Espo/Core/Utils/File/Permission.php Line: 449 Trace: #0 /public_html/application/Espo/Core/Utils/File/Permission.php(327): Espo\Core\Utils\File\Permission->chownReal('data/tmp/tmp1eU...', 65746) EspoCRM Forum /public_html/application/Espo/Core/Utils/File/Permission.php(190): Espo\Core\Utils\File\Permission->chown('data/tmp/tmp1eU...', 65746, false) Forum /public_html/application/Espo/Core/Utils/File/Manager.php(380): Espo\Core\Utils\File\Permission->setDefaultPermissions('data/tmp/tmp1eU...') #3 /public_html/application/Espo/Core/Utils/File/Manager.php(322): Espo\Core\Utils\File\Manager->putContentsUseRenaming('data/config.php', '<?php\nreturn [\n...') #4 /public_html/application/Espo/Core/Utils/File/Manager.php(429): Espo\Core\Utils\File\Manager->putContents('data/config.php', '<?php\nreturn [\n...', 2, true) Groups /public_html/application/Espo/Core/Utils/Config/ConfigWriterFileManager.php(83): Espo\Core\Utils\File\Manager->putPhpContents('data/config.php', Array, true, true) Uncategorized Groups /public_html/application/Espo/Core/Utils/Config/ConfigWriterFileManager.php(95): Espo\Core\Utils\Config\ConfigWriterFileManager->putPhpContentsInternal('data/config.php', Array, true) Special //public_html/application/Espo/Core/Utils/Config/ConfigWriter.php(199): Espo\Core\Utils\Config\ConfigWriterFileManager->putPhpContents('data/config.php', Array) Visitor Messages /application/Espo/Core/Utils/Config/ConfigWriter.php(182): Espo\Core\Utils\Config\ConfigWriter->saveData('data/config.php', Array, 'microtime') Private Messages /application/Espo/Core/DataManager.php(223): Espo\Core\Utils\Config\ConfigWriter->save() Albums /public_html/application/Espo/Core/DataManager.php(146): Espo\Core\DataManager->updateCacheTimestamp() #11 /public_html/application/Espo/Core/DataManager.php(118): Espo\Core\DataManager->clearCache() #12 /public_html/application/Espo/Controllers/Admin.php(87): Espo\Core\DataManager->rebuild() #13/public_html/application/Espo/Core/Api/ActionProcessor.php(123): Espo\Controllers\Admin->postActionRebuild(Array, '', Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) #14 /public_html/application/Espo/Core/Api/RequestProcessor.php(136): Espo\Core\Api\ActionProcessor->process('Admin', 'rebuild', Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) General Discussion /application/Espo/Core/Api/RequestProcessor.php(111): Espo\Core\Api\RequestProcessor->proceed(Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) Announcements public_html/application/Espo/Core/Api/RequestProcessor.php(82): Espo\Core\Api\RequestProcessor->processInternal(Object(Espo\Core\Api\Route), Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) Feature Requests /public_html/application/Espo/Core/Api/Starter.php(103): Espo\Core\Api\RequestProcessor->process(Object(Espo\Core\Api\Route), Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) Installation and Upgrade Help /public_html/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(43): Espo\Core\Api\Starter->Espo\Core\Api\{closure}(Object(Slim\Psr7\Request) , Object(Slim\Psr7\Response), Array) Extensions /vendor/slim/slim/Slim/Routing/Route.php(384): Slim\Handlers\Strategies\RequestResponse->__invoke(Object(Closure), Object(Slim\Psr7\Request), Object(Slim\Psr7\Response), Array) Developer Help /h/public_html/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): Slim\Routing\Route->handle(Object(Slim\Psr7\Request)) Bug Reports /public_html/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): Slim\MiddlewareDispatcher->handle(Object(Slim\Psr7\Request))

    Some ideas?

    Leave a comment:


  • espcrm
    commented on 's reply
    See if Maintenance mode is turn off yet. When you upgrade it get activated.

  • murugappan
    commented on 's reply
    @yuri,

    We checked and corrected the api. These were due to the migration of servers. Currently, all working fine.

  • Paulina
    commented on 's reply
    murugappan
    1. Logs says nothing
    2. Not yet, will try

  • murugappan
    commented on 's reply
    Paulina and @LexD

    (1) Have you checked the espocrm logs? What message do you get?
    (2) Did you switch to different version of PHP? Example. From PHP 7.3 to 7.4 or 7.4 to 8.0?

  • Paulina
    commented on 's reply
    Same issue. Did you find any solution?

  • yuri
    commented on 's reply
    Please new topics for such issues.

  • LexD
    replied
    Since we updated 7.09 -> 7.1.3 the cron jobs are not working anymore.
    https://URL#Admin/jobs also no activity.

    Anyone else with this problem?

    Leave a comment:


  • espcrm
    commented on 's reply
    Kindly share links as I'm been aware and not active on forum. Thanks.

  • murugappan
    commented on 's reply
    Hi Yuri,

    Yes we are using some apis. Will the api documentation show the latest methods?

  • yuri
    commented on 's reply
    Maybe you have API requests being made to your Espo with non-allowed methods?

    We upgraded the Slim library in v7.0 that's must be the cause why errors started to occur.

  • murugappan
    replied
    Hi

    Since version 7.0.9, now upgraded to 7.1.3 we have been getting the following error in the logs:
    "ERROR: 405 Method Not Allowed Type: Slim\Exception\HttpMethodNotAllowedException Code: 405 Message: Method not allowed. Must be one of: GET, POST, PUT, DELETE File: /home/dmsemastpa/public_html/emasdms/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php Line: 94 Trace: #0 /home/dmsemastpa/public_html/emasdms/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php(58):"

    We waited after installing upgrade 7.1.3 but the problem is still persisting (error log attached). It does not seem to have any impact as yet but we need to eliminate the error before any significant impact occurs. Appreciate any help
    Attached Files

    Leave a comment:


  • murugappan
    replied
    Hi dev77 paul

    We have installed a copy of the production instance in the following environment:

    (1) "dev" - DEVELOPMENT which is used to enhance the existing production copy for new requirements. This is where we upgrade and test all our enhancements.
    (2) "tst" - TESTING which is used to migrate from "dev" so that the users can test the changes
    (3) "stg" - STAGING which is used to migrate from "tst" and kept there until we can get a suitable time to down the "prd" environment (see next) and migrate the changes to the production version.
    (4) "prd" - PRODUCTION which is used for production-approved version to be used in "live" (or public) use.
    (5) "vnl" - VANILLA which holds a copy of the dev,tst,stg or prd version at any one time to test php or mariadb upgrade.

    How we do this is:
    (1) We set up to two servers (with our hosting provider) - say "Server1" and "Server2"
    (2) Server1 is a dedicated server containing only the "prd" version of the instance and is usually a high capacity server. In this server we can create multiple accounts for different app instances. Example: Server1 may contain "marketingcrm" under account "marketing.company.com" and another instance "supportcrm" under account "support.company.com".
    (3) Server2 may be a dedicated server or vps server (suggested as is cheaper) with the same capacity. This server contains "dev.company.com", "tst.company.com", "stg.company.com", "vnl.company.com" accounts. Unders these accounts, the related instances can loaded, developed and tested.

    I hope this helps.
    Last edited by murugappan; 05-04-2022, 10:14 AM.

    Leave a comment:

Working...
X