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

Avoid fatal error when use PSR 4 loading through ClassLoader #468

Closed
lgnap opened this Issue May 18, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@lgnap

lgnap commented May 18, 2016

Hello,

The class loader integrated into code is a old version and support only PSR-0 and doesn't support PSR-4.
Indeed the ClassLoader (retrieved from composer) is now supporting PSR-4 loading and the version provided with this package not.

This is blocking PSR-4 loading with the following Fatal

Fatal error: Call to undefined method Composer\Autoload\ClassLoader::setPsr4()

In PHP, it's impossible to exchange a already loaded class with a newest version.

I 'll update the file and will do a merge request when I have this ticket id.

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye May 18, 2016

Owner

Thanks, we'll get this tied into the 1.2.0 update that we'll be releasing soon. Appreciate the help!

Owner

angelleye commented May 18, 2016

Thanks, we'll get this tied into the 1.2.0 update that we'll be releasing soon. Appreciate the help!

kcppdevelopers added a commit that referenced this issue May 26, 2016

Merge pull request #469 from Antidot-be/Issue-468
Provide a ClassLoader enabled to use PSR-4 loading (close #468)
@shippingmanager

This comment has been minimized.

Show comment
Hide comment
@shippingmanager

shippingmanager May 30, 2016

Hi Angelleye,

When will be the version 1.2.0 available ? We definitely need the fix ASAP because some clients have the issue and we 're dependent on you. We do really hope to get it for this week.

Thanks for your understanding ;)

shippingmanager commented May 30, 2016

Hi Angelleye,

When will be the version 1.2.0 available ? We definitely need the fix ASAP because some clients have the issue and we 're dependent on you. We do really hope to get it for this week.

Thanks for your understanding ;)

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye May 31, 2016

Owner

@shippingmanager The fix has already been merged into our release branch. We'll be releasing it soon, but if you want to grab it early you can download it here.

Owner

angelleye commented May 31, 2016

@shippingmanager The fix has already been merged into our release branch. We'll be releasing it soon, but if you want to grab it early you can download it here.

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