EspoCRM v6 Discussion Thread [v600 | v.6.0.0]

[espcrm]

UPDATE: Please note that v6 feature is "Frozen" status, but have hope for 6.1! See: https://forum.espocrm.com/forum/gene...1313#post61313

Version v6 is expect to plan to be in August, check out the milestone here: https://github.com/espocrm/espocrm/milestone/96

As it is a major update (currently we are on version 5.x.x | v593) I thought I should make this thread to discuss about version 6 in general and perhaps to write what you would like to see in version 6. Whether or not it will get made in the update but there is always hope.

Perhaps even discuss about what wrong with v5.9, it is a good chance try and get it "fix" for v6 before we have an "too late, can't do it now maybe in v7".

---
1 Feature I would like have is:
Repeat Task/Meeting without relying on Workflow.


---

https://github.com/espocrm/espocrm/issues/1756

To start off one thing I like to do is, rush into new enhancement if it seem easy to do by manual patch (copy/paste the file & code). I noticed this Enhancement today available for v6 and it look good. Setting is quite a hassle even if you create good layout and category, but having a search will just cut down on "where was that menu again" issue.

So I will be adding this patch and reporting back if I run into issue.

PS. I upload these these file to a Github as a single .zip file if you would just like to "upload and extract". It bad practice but I don't do backup for certain thing:

https://github.com/o-data/EspoCRM-Manual-Patch

[espcrm]

Over the past few weeks I see yurikuzn did lots of this ORM commit which all seem to be backend thing so have to wait for v6.0.0 to arrive.

But today I just saw this new Issue was added: ORM improvements #1766 https://github.com/espocrm/espocrm/issues/1766

One part that I find interesting is this:

• Mass insert

Might be far fetch, but does that mean we might finally get Mass Document upload. Crossing my finger.

[yuri]

Hi All,

I've been doing a lot of code refactoring for last weeks, almost all core classes were rewritten to a certain extent. Not sure if I will manage to finish all the work I have planned on schedule. There won't be enough time for testing all this change. So it's likely that we will postpone a release date for a couple weeks.

[Oleksii S.]

Sure. Late code better than faulty one,

[item]

Hello,
This is wonderfull improvement : https://github.com/espocrm/espocrm/issues/1767

Please vote

Thanks Yuri

[julobaco]

Hi, I would like to thank you for the great CRM system.

Feature which should be added to the new version v6:
* in case of export results to Excel save the selected 'Field List'. Something like when we can define for the PDF export. Because in case when we need only selected fields to export and are not the same as visible columns we have to manually selected them. Also the order of 'Fields' should be saved.

Thank you.

[yuri]

Hi,

The feature list for 6.0 is frozen. Nothing new will be added besides the current feature list available on Github. The main goal for now is a code improvement.

[espcrm]

Spotted this update that will greatly benefit performance from the sound of it:
Preloading in PHP 7.4

https://github.com/espocrm/espocrm/issues/1773

It is also a reason for me to move to PHP 7.4 once v6 arrive.

[yuri]

Actually, I doubt that this can bring a significant performance boost. Database is a bottleneck in applications like CRMs.

[peterberlin]

Hi Yuri

now existing own extensions will also work with the new code of 6.0?
peter

[yuri]

Hi Peter,

There is a likelihood that something won't be compatible. Once we release a beta, you can check.

[yuri]

We are likely to drop MyISAM support in 6.0. If we do we will provide instructions how to migrate to InnoDB.

[espcrm]

Did a quick check on what that mean. Here is an article from the 2009, it might not be accurate and don't really know much has InnoDB improve for the past 11 years but some fun reading I suppose.

https://www.kavoir.com/2009/09/mysql...-and-cons.html

Few thing that pique my interest is this section:

"MyISAM has full-text search index while InnoDB has not."

That might that mean the search system will not be better than previous version (<5.9.9 which is what we using).

[yuri]

It's not actual anymore. MyIsam is literally abandoned by Oracle. It's obsolete.

[espcrm]

Here is the Issue for anyone who want to track it: https://github.com/espocrm/espocrm/issues/1775

Question though: How do we tell if we have an MyISAM table or not? Will the EspoCRM Update take care of that conversion?

I assume I don't, and since we using MariaDB so our server is probably on what call Aria.

[espcrm]

Something to do with this?

"Each MyISAM table is stored on disk in two files. The files have names that begin with the table name and have an extension to indicate the file type. The data file has an .MYD (MYData) extension. The index file has an .MYI (MYIndex) extension. The table definition is stored in the MySQL data dictionary."

Reference: https://dev.mysql.com/doc/refman/8.0...ge-engine.html

[yuri]

The upgrade command will show a message and won't start if there is any MyIsam table.