Fix loading api files for external modules

[kadogo]

Fix #9116 Fix load api for external modules

Actually the API from external modules are not loaded automaticaly
This PR try to find the right path for a module if it's find in the custom directory

[eldy]

This feature should be implemented into 7.0 or 8.0
Did you check with a such version ?

[bilbo-the-hobbit]

hello @eldy,

this fix is for our dolibarr version 7.0.3 and is need for the api to work. we have some integration between gitlab and dolibarr and without this patch the call to the dolibarr API doesnt get trough.

Cheers

[eldy]

PR was pushed into 6.0 branch. Same with 7.0, no implementation of new features are allowed in an already released version.

Note that if using dolibarr 7.0.3, if your module is called "abc" then having the api file
api_abc.class.php should already be supported with standard code :
getModuleDirForApiClass will return $moduledirforclass = abc
And into the api/index.php file, the code
dol_buildpath('/'.$moduledirforclass.'/class/');
shoudl works when your module is inside custom/abc

With no need of this patch.

[kadogo]

Hello @eldy

It is true when the API file have the same name of the module.

Most of time the API file is set in plural (example timebaskets, interventions).

You can see it clearly #9116 where he searchs "timebaskets".
My patch show the probem because I need to force the path to timebasket.

Cheers.

[frederic34]

@kadogo did you try to name your api class file api_timebasket.class.php and in this file to declare class TimebasketApi extends DolibarrApi

[kadogo]

@frederic34
I showed the issue to the author he better know what to do about the modules.
The issue here is that timebasket have 2 different API class.
Eldy said that only 1 API file is authorized so I wait to know what will do the author.

[eldy]

This bug or the feature request seems to be fixed or included into last recent stable version, so I close the issue.