Announcement

Collapse
No announcement yet.

EspoCRM 4.3.0 released

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

  • EspoCRM 4.3.0 released

    What's new:

    * Dynamic logic. Dynamic forms configurable through admin's UI.

    * Entity Manager: Base Plus entity type with Activities, History, Tasks panels.
    * Entity Manager: Person entity type now has Activities, History, Tasks panels.
    * Entity Manager: Company entity type.
    * Entity Manager: Audited relationships feature. Allows to see that records were related in stream.
    * Entity Manager: Tooltips now can be edited.
    * Entity Manager: Ability to reset fields to default settings.

    * Emails: Ability to use mailparse extension for email parsing. It will be used if mailparse extension is installed on your environment. With this implementation email fetching must work better than before.

    * Layout Manager: Ability to remove side panels.
    * Layout Manager: Ability to specify color of panels.

    * Activities: Ability to configure what entities are listed in Activities and History panels.
    * Activities: Event entity type can be added to Activities and History panels.

    * Mass Email: Ability to make opt-out link not mandatory in settings.
    * Campaigns: Ability to create target lists based on Campaign Log.
    * Target Lists: Duplicate now copies targets (contacts, leads, accounts, users).

    * Roles: Ability to manage read access to Users and Teams.

    * Dashboard: Ability to rename tabs.

    * Export: Ability to select which fields to export.

    * Import: Ability to run import in idle-mode. For big files.
    * Import: Ability to skip duplicate checking. For the sake of performance.

    * Date/Datetime fields: 'Is Empty' filter.
    * Int/Float fields: 'Is Empty' and 'Is Not Empty' filters.
    * Parent fields: Ability to search by certain entity type.

    * Preferences: 'Do not fill Assigned User if not required' parameter.

    * Tasks: Added reminders feature. Only if Date Due is specified.

    All issues:
    Enhancements: https://github.com/espocrm/espocrm/i...3Acreated-desc
    Bugs: https://github.com/espocrm/espocrm/i...sc+label%3Abug
    Changes: https://github.com/espocrm/espocrm/i...label%3Achange

    Download: https://www.espocrm.com/download/

    Upgrades: https://www.espocrm.com/download/upgrades/
    Last edited by yuri; 12-08-2016, 10:53 AM.

  • #2
    Great work everyone!

    Comment


    • #3
      nice

      thnx yuri

      Comment


      • #4
        how can i use manual update ?

        Comment


        • yuri
          yuri commented
          Editing a comment
          You can upgrade at Administration > Upgrade in your EspoCRM.

      • #5
        Is using php-mailparse automatic? I installed it but how can I verify if things are working?

        Comment


        • #6
          Can I upgrade to 4.3.0 from 4.3.0-beta.2?

          Comment


          • #7
            Got it,

            I manually changed the manifest file inside the upgrade ZIP to match my version..

            Originally posted by Frank View Post
            Can I upgrade to 4.3.0 from 4.3.0-beta.2?
            Same problem here. I can't upgrade from 4.3.0-beta.1
            Last edited by rodrigocoelho; 12-08-2016, 07:45 PM.

            Comment


            • #8
              Since the upgrade files are large I get the error 500 during upload and running upgrade within Espo (probably due to timeout on shared server).

              Is there a way to manually upgrade? Uploading the files via ftp etc.?

              Comment


              • #9
                Upgrades from beta are here: http://forum.espocrm.com/forum/annou...crm-4-3-0-beta

                Since upgrade is quite big it's recommended make sure that max_execution_time in your php is sufficient before running upgrade or just run the upgrade in the shell.

                How to run upgrade in command line interface (shell):
                php upgrade.php /path/to/upgrade/package.zip

                Comment


                • #10
                  Originally posted by SpeedBullet View Post
                  Is using php-mailparse automatic? I installed it but how can I verify if things are working?
                  If you run "php -m" in command line interface it must show mailparse in the list. By default mailparse is used if detected.

                  Comment


                  • #11
                    Congrats for this great work !
                    Thinking about upgrading soon <3

                    Comment


                    • #12
                      Update as always without problems. The best CRM on the market. Thank you!

                      Comment


                      • #13
                        The update is not working for me ... EspoCRM-upgrade-4.2.7-to-4.3.0-beta.2 neither EspoCRM-upgrade-4.2.7-to-4.3.0 , my current version is 4.2.7 , it showing BAD SERVER RESPONSE

                        Following is the php error -

                        [Mon Dec 12 16:08:40.193739 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP Warning: Unknown: POST Content-Length of 16093536 bytes exceeds the limit of 8388608 bytes in Unknown on line 0, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.979013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32187073 bytes) in C:\\wamp\\www\\ESPO\\application\\Espo\\Core\\Util s\\Api\\Output.php on line 115, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.979013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP Stack trace:, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.979013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 1. {main}() C:\\wamp\\www\\ESPO\\api\\v1\\index.php:0, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.979013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 2. Espo\\Core\\Application->run() C:\\wamp\\www\\ESPO\\api\\v1\\index.php:9, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.979013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 3. Espo\\Core\\Utils\\Api\\Slim->run() C:\\wamp\\www\\ESPO\\application\\Espo\\Core\\Appl ication.php:64, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 4. Espo\\Core\\Utils\\Api\\Auth->call() C:\\wamp\\www\\ESPO\\application\\Espo\\Core\\Util s\\Api\\Slim.php:18, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 5. Slim\\Middleware\\MethodOverride->call() C:\\wamp\\www\\ESPO\\application\\Espo\\Core\\Util s\\Api\\Auth.php:81, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 6. Slim\\Middleware\\Flash->call() C:\\wamp\\www\\ESPO\\vendor\\slim\\slim\\Slim\\Mid dleware\\MethodOverride.php:92, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 7. Slim\\Slim->call() C:\\wamp\\www\\ESPO\\vendor\\slim\\slim\\Slim\\Mid dleware\\Flash.php:85, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 8. Slim\\Slim->applyHook() C:\\wamp\\www\\ESPO\\vendor\\slim\\slim\\Slim\\Sli m.php:1315, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 9. call_user_func() C:\\wamp\\www\\ESPO\\vendor\\slim\\slim\\Slim\\Sli m.php:1175, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 10. Espo\\Core\\Application->Espo\\Core\\{closure}() C:\\wamp\\www\\ESPO\\vendor\\slim\\slim\\Slim\\Sli m.php:1175, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 11. Espo\\Core\\Utils\\Api\\Output->processError() C:\\wamp\\www\\ESPO\\application\\Espo\\Core\\Appl ication.php:205, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 12. Espo\\Core\\Utils\\Api\\Output->clearPasswords() C:\\wamp\\www\\ESPO\\application\\Espo\\Core\\Util s\\Api\\Output.php:53, referer: http://localhost/ESPO/
                        [Mon Dec 12 16:08:44.980013 2016] [:error] [pid 7068:tid 1576] [client 127.0.0.1:62870] PHP 13. preg_replace() C:\\wamp\\www\\ESPO\\application\\Espo\\Core\\Util s\\Api\\Output.php:115, referer: http://localhost/ESPO/

                        Kindly suggest !

                        I have also increased following to 1000M
                        upload_max_filesize = 1000M; post_max_size = 1000M; Still the error - Allowed memory size of 134217728 bytes exhausted (tried to allocate 16093537 bytes)
                        Last edited by HDS; 12-12-2016, 10:57 AM.

                        Comment


                        • #14
                          Increase post_max_size in your php

                          When you installed EspoCRM you must have been warned about too little post_max_size.

                          Comment


                          • HDS
                            HDS commented
                            Editing a comment
                            I have done that too and restarted the wampserver (all services), still the same issue

                            upload_max_filesize = 1000M; post_max_size = 1000M

                          • yuri
                            yuri commented
                            Editing a comment
                            I helped as i could. It's an issue with your server if error is the same.

                        • #15
                          Reg. upgradig manually: In which folder to upload the upgrade package.zip before running the upgrade via shell?
                          Thanks

                          Comment

                          Working...
                          X