If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
> It seems that the problem is caused by my custom entry points located in custom/Espo/Custom/EntryPoints/
What exactly was in the problem file? It loaded the library code.
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.
As far as I understand, the issue is the mising required files as mentioned before?
Should we just manually add them to the EspoCRM-upgrade-8.4.2-to-9.0.2.zip\vendorFiles\paragonie\random_compat\lib and be done with it
Or will this be included in official version later down the line?
I don't think it's because of missing files. The v9.0 has breaking changes. Before upgrading, the script goes though custom files to check for incompatible usages. To avoid the system complete crash after upgrade, to prompt the user to fix incompatibilities first.
It looks like some custom file includes the library code. Maybe though the "use" statement in the beginning of the file.
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.
Try uninstalling TCPDF extension, upgrade and then install it back.
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.
Sometimes the uninstall routine in Admin does not uninstall certain extensions completely. So after having uninstalled from the GUI go to the folders client/custom/modules and custom/modules to see if there is anything from one of the uninstalled extensions still present. Delete these files.
Have a look in your database table "extensions" and delete as well all rests of those extensions.
Rebuild your instance. In many cases this already solves such problems as described.
After that, re-install your extensions one by one and see if all works well. If one extension starts to cause the problem again, it is likely a compatibility issue with the upgraded espoCRM version and the developer of that extension should take a look at that.
Comment