hasSessionStore debacle

[byordereurope]

Hi Folks,

Guess what. Once more in my life i am totally wasting my time to write this down.

I did a fresh install of laravel recently with an update done yesterday.
All of the sudden the creation of the user fails. It produces this fine error...

Call to undefined method Illuminate\Http\Request::hasSessionStore()

Further investigation of the problem online pushed me again into the direction of Ardent.
But ofcourse, they use to blame laravel, because yeah the framework changed something. But me it tells they are not capable of holding up with the development.
A thread on the internet stated, that laravelbook was no longer maintaining the project, which means he made money enough with his books and is now enjoying his life, which i can understand ofcourse.

But fact remains, once again it is Ardent that fails this package.

Second fact, if the only thing that changed is that laravel changed hasSessionStore() into hasSession(), and that that command is specifically only ONCE in the ardent source-code, then what is the problem of just changing just that one command? You have to explain me because i am totally lost here.

As i have predicted many times is past tickets, what is the problem of just switching to the standard laravel validation procedure if that only requires you to maybe add at least 15 new lines of source-code? You know i choosed this package because the inventors had done a real good job in my eyes, but all the past ardent troubles i ran into that broke this fine package should be an indication that maybe something IS wrong with relying on an external package, while the laravel validation functionality is core of the framework?

Can you please explain me how a good idea can turn into a pile of mess ???

I told you before... each time this stuff happens, that means maybe thousands if not even more programmers worldwide run into a broken package, turn around and never look back. Others facing again an Ardent nightmare, while fixing it only takes 5 times the del-keystroke. Confide is not the only one in laravel world, but still people made choice for this package because it seem very good to them. Now for the x time they are all left behind, because two little project that trying to run onto the wave of the success of laravel, make this framework look like a piece of shit. Because it breaks.

When you guys are going to realise that a lot of people already use your package, and when that thing breaks they put the finger on you, while you at your time are going to blame ardent for not keeping up. So we contune the never ending blame-game ???

Get rid of Ardent and fix your controller in your code to use standard laravel validation possibilities and make us back happy for gods sake, because sooner or later you will have no users left. You guys can even compete with sentry2 for gods sake, doesn't that mean anything to you ?

Start a crowdfunding project if you need money, but do not let your followers in the dark as you do now, because i can tell you, we do not appreciate that.

If you start a crowd funding project i am happy to be the first investor.

[Zizaco]

@byordereurope, you have my respect and I totally agree with you.

The ardent has been an issue for a long time now. I agree with every single point you stated.

I'm dropping the ardent dependency and reviewing the whole codebase. See #209
Plus i'm going to do a workaround for users of the current version in order to not fall into the hasSessionStore problem.

[Zizaco]

Fixed: 3c74dbd
@byordereurope, if you have any issue, please let me know.