-
Notifications
You must be signed in to change notification settings - Fork 205
Should not depend on Input::hasSessionStore() #155
Comments
This patch seems to fix the error message. I'm not entirely sure that calling Request::hasSession() is the right thing to do.
|
I'm getting the same problem when I run my tests. |
Same problem occurring here on a fresh install of Laravel 4.1 and just following the setup guide. The exception is reported as: Call to undefined method Illuminate\Http\Request::hasSessionStore() |
+1 |
Same error here... huge site so need a fix please. Also it produces the error when seeding the Users table which worked great before. |
If you update your |
thanks for you temporary fix |
Tried the temp fix in my composer.json file and still no luck... none of the test users can register now at all. Call to undefined method Illuminate\Http\Request::hasSessionStore() Please provide a fix. |
I'm in no way qualified to answer any of these questions, and so what I'm about to say could be totally backwards, but after you added in the repositories bit, did you do a |
Absolutely... composer update :) and no what you said is not totally backwards, its good to check... Its easy to forget to run composer commands. Thanks |
Ok this fixed it... I went back a version on Laravel... run composer update. I guess this will have to do until this issues is resolved. |
I have no idea how to actually go about doing this, but the only other thing I can think of is to drop back to an version of Laravel that still has the I'd suggest starting by looking here: https://packagist.org/packages/laravel/framework then modifying the Keep doing this until you find one that works (then report back here and let us all know which one works. |
Ha, you beat me to it, good job :) |
I had the same error appearing when using a simple validation on an email field. I dropped down from 4.1.18 to 4.1.16 and works fine. |
@LimeBlast - No worries, your feedback is most appreciated. |
Here's the Laravel commit that removed |
@LimeBlast thanks for digging. For those using Entrust, you'll need to manually set your Ardent tag to 2.4.1 as Entrust has switched to requiring 2.4.x which if you use Ardent's repo will be 2.4.0. You can use this composer.json block to fix that. It essentially forces a package version of 2.4.1 that points to my fork's (or yours if you change it) to the HEAD of master. It's a slight improvement over #133 block. It's been tested to be compatible with 4.1.18 so you don't have to be dropped back to 4.1.16.
|
thanks @bexarcreative-daniel. Is there likely to be an official ardent 2.4.1 release soon? |
I had this error has well, using an early version of Laravel fixed it. It'd be interesting to have a release to fix this issue though 👍 |
@58bits I've released a similar MIT licensed package that uses traits and is unit tested and is compatible with Laravel 4.2. You might want to consider it if you need more frequent tag releases. https://github.com/esensi/model |
I use Entrust, which depends on Ardent. I recently upgraded to Laravel 4.1. Now my tests fail with the following backtrace:
The reason seems to be that the method call
Input::hasSessionStore()
has been removed as of Laravel 4.1.In my test no session store is available, I think.
The text was updated successfully, but these errors were encountered: