EspoCRM v7.3.0 released

[murugappan]

@yuri,

Hi, thank you for the feedback. My server guys fixed the problem. It appears that there was global limit set in the php.ini which appears to override the limit i set in the local domain. After setting the global parameter it works fine now. The developers of PHP were also helpful. Thank you so much. This topic stands closed.

[yuri]

ini_set is applied only to the current process. But upgrade executes in multiple processes. You need to change your memory limit for PHP for CLI.

[esforim]

My apology... here is my experience. It might be different from you if you already using v8.1

1) Use CLI to run upgrade.
2) CLI Upgrade to one latest EspoCRM version allow.
3) Upgrade complete, upgrade again: CLI show no error except it say to "7.4 PHP" no longer supported.
4) Go to server User CP / Control Panel / GUI of My Shared Hosting Server,
5) Change PHP version to 8.1 (or PHP 8). Go back to CLI and try Upgrade command again.
6) It run for about 5 minutes
7) Done.

But your server probably will be much longer I assume since I know you have big database.

[murugappan]

HI yuri



Please accept my apologies for posting my investigation here. I posted by problem under another topic under the Installation and Upgrade category but did not get much attention or help. This is related to memory_limit error when upgrading from 7.2.7 to 7.3.2 under PHP 8.1.12 which i also posted above. After further investigation. this is what i did:

(1) I modified the code in upgrade.php to set the memory_limit in the code as below:



(2) Then ran the upgrade as per cli "php command.php upgrade".
(3) This time the memory-limit error went away and the upgrade started but terminated abruptly with the following message:

Espo\Core\Exceptions\Error::__construct(): Argument #1 ($message) must be of type string, null given, called in /home/sysdev/public_html/wellnessclinictstx/application/Espo/Core/Console/Commands/Upgrade.php on line 379

Please advise/help.

[murugappan]

esforim, I am sorry could not understand what you have done.

[esforim]

I change my GUI with my host's UserCP, here the step I did:

https://forum.espocrm.com/forum/announcements/86871-espocrm-v7-3-0-released?p=86936#post86936

[murugappan]

Hi All,

Has anyone upgraded using PHP 8.1.x? I performed the upgrade and all i got was "downloading..." and then process died just like that. I tried upgrading with PHP 8.0.7 and it worked fine. Anyone facing this problem? Appreciate any help.

On testing further, I found that I was getting the following error in the error.log:

Allowed memory size of 33554432 bytes exhausted (tried to allocate 14976300 bytes) in /home/sysdev/public_html/wellnessclinicx/application/Espo/Core/Console/Commands/Upgrade.php on line 294 

I have set the memory_limit to -1 and also 1024M. Nothing seems to work. Its odd when i do the same upgrade with PHP 8.0.7 it seems to work fine.

[murugappan]

Oh boy, the time i was expecting has come. I have many apps to migrate. Oh well, thats what keeps my boys on the job.

yuri, all the improvements and enhancement are great. Love the calendar enhancements. I was hoping and praying for them. I just created an instance and built a Clinic Management System. Only wish the items on the calendar can show the user assigned as well. That way the doctor assigned can see it at a glance. This will help identify whose appoint each one is. May be it can be done but not sure how. Great Job! I have recommended Espocrm to many users in Joomla forum as well and the excitement has started.

Thank you so much.

[nickh]

Hi yuri
Have upgraded multiple instances from 7.2.7 -> 7.3.2 using CLI. All went fine.
Now noticed all instances and all users are not receiving mail in the inbox. All connections are fine - outlook and IMAP, and scheduled job "check personal email accounts" returning "Success".
Email simply does not appear
Any suggestions please?

PHP 8.0.27
System Requirements all met

One of our users has reported many of their email filters are missing.

Hi again yuri
Please ignore that details above. This was caused by my server requiring the PHP version in the CRON job, As I upgraded PHP version to 8.0.27 from 7.4, I simply needed to amend the CRON job.

Still blown away by this product and the support you provide.!!

[esforim]

REPORTING IN:

Update all good (as far as I can tell). CLI show no error except it say to "7.4 PHP" no longer supported, so just change it to 8.1 (or PHP 8) and try CLI update again.

[yuri]

If one run into an issue that upgrade failed with the error:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'user.working_time_calendar_id' in 'field list'

try the following:

1. Rebuild from CLI:

php rebuild.php

2. Run upgrade again.

Do not use `-s` parameter with the upgrade command. Its purpose to run upgrade in a single process. Use it only if your environment requires (might be needed on shared hosting providers).

[yuri]

Upgrade is published.

Don't forget to backup if you upgrade a production.

[esforim]

Was just about to complain!

[yuri]

Upgrade not ready yet.

[yuri]

If you run into issues with upgrade, create a separate topic in the corresponding section.

Don't forget to backup if you upgrade a production. Upgrade a test environment first.

Most issues after upgrade are related to environment upgrade (PHP, webserver, file permissions, crontab, etc.). Please try not to overwhelm our support with urgencies "nothing is working, no backup".

See recommendations.