when I want to work with Api v8 I got a strange error: /Api/access_token gives me “File not found.” (which is a custom message, because if I use /Api/abcdef it gives me Server Error 404 Page Not Found - which is the standard message)
When I use Api/index.php/access_token though, everything works normally.
Because of some previous problems with the cache I got an updated upgradeAccess.php and thus a different but working .htaccess:
I tested it by redirecting the Api/access_token bit to google.com and it works.
I currently restrain from applying the filechanges (in 9 files) from the other thread, because I can not overlook what else might be affected.
I will just use the direct path to the api in the meantime and wait for an official patch.
Oh, so this is the same issue as that other thread? The .htaccess fix solves this here?
Yes that should already be part of 7.11.9, but it’s best to wait for 7.11.10.
It is coming out pretty soon - we’re past the “code freeze”, nothing new is going into it, but there is always an element of uncertainty here because it can only be released when it passes all the tests. We’re currently improving the test system itself, and some testing processes, so some things are still a bit in an evolving state, which doesn’t help with setting dates.
So: it’s certainly possible that it is coming out on Monday, but I can’t guarantee it.
But I follow everything that goes on in GitHub and I am in constant contact with the Product Team. You could say I cooperate in the link between the Product Team and the Community.
Oh, so this is the same issue as that other thread? The .htaccess fix solves this here?
I don’t know if it does resolve this issue. Instead of changing 9 files back and forth (and possibly make a mistake or missing other related changes) I decided to wait. I think I nailed the issue down to .htaccess, which means I can use the API without rewrite in the meantime.
You could say I cooperate in the link between the Product Team and the Community.
Thank you for your great job there. I am evaluating to shift to SuiteCRM with two customers who use cloud CRM right now. Apart from the well rounded and feature rich core SuiteCRM and great extensions it is your support heavily tipping the scale.
I’ve managed to get /Api/access_token to work by enabling mod_rewrite module and changing directive ‘AllowOverride None’ to ‘AllowOverride All’ in Directory for CRM installation (this steps are missing in SCRM’s docs, but maybe it is not direct relevance for the CMR).
However, any others /Api calls (e.g., /Api/V8/meta/swagger.json) don’t work.
Posted some logs and findings on Github (comment 1, 2)