Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Class 'MongoDB' not found #177

Closed
anned20 opened this issue Dec 10, 2016 · 6 comments
Closed

Class 'MongoDB' not found #177

anned20 opened this issue Dec 10, 2016 · 6 comments
Assignees

Comments

@anned20
Copy link

anned20 commented Dec 10, 2016

phpinfo() shows that MongoDB is correctly loaded.

@sn0opy
Copy link
Member

sn0opy commented Dec 10, 2016

The old MongoDB driver in PHP is gone and the new one is not yet supported in F3.

#111

@anned20
Copy link
Author

anned20 commented Dec 11, 2016 via email

@bcosca
Copy link
Collaborator

bcosca commented Dec 11, 2016

@ikkez can you stress-test the latest commit against cortex?

ikkez added a commit that referenced this issue Dec 12, 2016
@ikkez
Copy link
Member

ikkez commented Dec 12, 2016

the cortex tests still work fine within the old mongo extension and mongo 2.x.
I wasn't able to get the new mongodb extension and mongo 3.4 to run in my php7 dev environment on my mac OS yet, due to some weird mac dependency issues, but I'll try to test this on a debian system soon as well.

@bcosca bcosca closed this as completed Jan 7, 2017
@ptdev
Copy link
Contributor

ptdev commented Jan 9, 2017

Hey there.
I've now tested these changes with both drivers and it seems to be working fine. That said, I've since upgraded my installations to php7 (was basically just waiting for this) and have been using mostly the new drivers.

This compatibility with the new mongodb driver should get included in the stable channel as a v3.6.1 to ease composer deployments on php7 environments without having to rely on dev-master as a repo.

Just a though.
And great job as usual.
cheers.

@ikkez
Copy link
Member

ikkez commented Jan 9, 2017

This compatibility ... should get included ... as a v3.6.1

yes I totally agree. Just let us solve some other little issues that came up, so we can provide a better patch release, maybe at the end of this month.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants