Composer conflict?

Şahin
(@flyinghawk)

9 years, 3 months ago
Hi There!

I am experiencing a major problem to get your plugin to work.
I just introduced composer to my current wordpress installation as a base, meaning that I load/install all plugins via composer.json. Before that, it was a default installation, so all plugins were just installed manually.

Now I get some errors and I guess it is some kind of conflict with the autoloading function of composer? But that’s just a guess.

PHP Fatal error: Uncaught Error: Class 'Carbon\Carbon' not found in {...}\wp-content\plugins\google-calendar-events\includes\functions\shared.php:230

I load your plugin via:
"wpackagist-plugin/google-calendar-events": "3.1.9",

and wpackagist is defined as:
```
"repositories":[
    {
      "type":"composer",
      "url":"https://wpackagist.org"
    }
]
```
and I also have a custom namespace loaded via:
```
"autoload": {
    "psr-4": {
      "sample\\": "wp-content/themes/sample-theme/_includes/"
    }
}
```
( I removed the actual names and path ).

Couldn’t find any related thread to this.

Thank you in advance!

Cheers,
Sahin

Viewing 8 replies - 1 through 8 (of 8 total)

Plugin Contributor Nick Young
(@nickyoung87)

9 years, 3 months ago

When you include our plugin this way does it also include all of our composer files that we use? Maybe it doesn’t and that’s why the error comes up? (we are including Carbon via composer)

Thread Starter Şahin
(@flyinghawk)

9 years, 3 months ago

Hey Nick,

thx for the response. As far as I can see, all the files are included. I also did a manual search and also tried to try out stuff like including the missing files via require_once etc.

For example the carbon folder is under
vendor/nestbot/carbon/ and has the for example the src/Carbon folder included where the Carbon.php class is included.

Other Ideas? Or any informatino I could provide you with?

Cheers,
Sahin

Plugin Contributor Nick Young
(@nickyoung87)

9 years, 3 months ago

This isn’t directly related to the Carbon issue, but maybe there is something here that will help?

https://github.com/wp-cli/wp-cli/issues/2241

If that doesn’t help I would have to keep looking.

Thread Starter Şahin
(@flyinghawk)

9 years, 3 months ago

Hi Nick,

thx for the link. I will read through and try out some other possible solutions. Will come back if I have any solution for this issue.

Thx for your help anyway!

Cheers,
Sahin

Plugin Contributor Nick Young
(@nickyoung87)

9 years, 2 months ago

Yes please let me know if that helps or if you find something. I am curious to see what the issue is as well.

I will let you know if I come across anything else as well.

Thanks!

martinwelte
(@martinwelte)

9 years, 2 months ago

Hey Nick,
The Workaround suggested by pratyushpundir (@pratyushpundir) in this issue https://wordpress.org/support/topic/carbon-issues/
suggesting to add these 3 dependencies to the global composer.json file:

“nesbot/carbon” : “1.21.0”,
“google/apiclient” : “*”,
“mexitek/phpcolors” : “dev-master”

seems to solve the problem. Maybe there is a Namespace conflict in the plugin when using a composer based installation. Since this should not be a permanant fix, i would like to hear from you if you find a better solution.

Plugin Contributor Nick Young
(@nickyoung87)

9 years, 2 months ago

Thanks for the update. I will add this information to the issue.
Thread Starter Şahin
(@flyinghawk)

9 years, 2 months ago
Hi there,

I can confirm the issue-workaround by adding the following packages to my dependencies:
```
"nesbot/carbon": "^1.22",
"google/apiclient": "2.0",
"mexitek/phpcolors": "dev-master"
```
Hope that helps.

Cheers,
Sahin

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Composer conflict?’ is closed to new replies.