You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My issues are that A) the directories have changed since the introduction of SuiteCRM-Core and the /legacy directory.
Plus B) the use of the composer. From what I understand Composer can be run on both the root directory and the legacy directory.
After upgrading to 8.5.1, I tried;
installing the DAVServer files in the directory: /public/legacy/custom/DAVServer/
installing the suiteDav.json file in the directory: /public/legacy/custom/Extension/application/Ext/Composer/SuiteDav/
edited the file /public/legacy/composer.json and added ["sabre/dav": "*"] to the "require" section.
in the same file, I left the line in the "require-dev" section unchanged: ["phpunit/phpunit": "^9.5",]
executed [composer update sabre/dav] from the directory /public/legacy/ as per Sabre DAV instructions.
Are these steps correct, or have I derailed somewhere. Plus, is there a way to do this without composer; like a package with compiled files?
The text was updated successfully, but these errors were encountered:
Hi,
I once had this working in a trial setting on a SuiteCRM 7 version, but can't get it to work on 8+.
Tried several times and even considered switching systems to get this functionality. Dolibarr has a pretty sweet one which worked on the first try; https://github.com/Befox/cdav and https://github.com/Dolibarr/dolibarr/tree/7a389299c31986e7ae354cdf7141eaf28e6a8a39/htdocs/includes/sabre
My issues are that A) the directories have changed since the introduction of SuiteCRM-Core and the /legacy directory.
Plus B) the use of the composer. From what I understand Composer can be run on both the root directory and the legacy directory.
After upgrading to 8.5.1, I tried;
Are these steps correct, or have I derailed somewhere. Plus, is there a way to do this without composer; like a package with compiled files?
The text was updated successfully, but these errors were encountered: