hasSessionStore has been removed

[plmarcelo]

hasSessionStore() method has been removed. In its place hasSession() method should be used.

Reference: laravel/framework@328e6cf

[dalabarge]

+1

[mouhsinelonly]

+1

[globsecure]

+1

[cannap]

+1

thx for this nice package

[dhardtke]

+1

[lucasceballos]

+1

[ezynda3]

+1

[hskrasek]

+1

[vinicius73]

+1

[mgufrone]

+1

[jaketoolson]

+100

[matula]

+1

[dwolfhub]

+1

[ejunker]

+1 In the meantime I've just adjusted my composer.json to lock my app on Laravel 4.1.16

"laravel/framework": "4.1.16",

[mbbender]

+1 2.4.x doesn't seem to work for me.

[EdgarsK]

+1

[ghost]

+1

[remluben]

+1

[RyanNielson]

+1

[warksit]

See #154

[markalanevans]

+1

[markalanevans]

2.4.* doesn't fix it.

[mishbah]

👍

[mgufrone]

wow, it's already 12 days. hope this commit will be evaluated soon. 👍

[cillosis]

+1

[grahammccarthy]

+1!!

[mishbah]

@mgufrone 👍

[markalanevans]

+1

[RyanNielson]

Any other contributors able to merge this and release? I'd like to be able to use the most recent Laravel with it. Currently I have to use 4.1.16 if I want to use Ardent without changing it myself. @laravelbook

[vinicius73]

@laravelbook this more than a few months without activities on github.
Do not know and do not know if something may have happened to him.
If this keeps up I think I will have to create a fork of ardent and work on it.

[mouhsinelonly]

@vinicius73 i think it's time for someone more interested in doing some free work to create a fork and i pledge to contribute as much as my time allows :)

[RyanNielson]

I mean the last update is only a month ago which isn't too bad to be honest. But a fork is always an option in the meantime.

[mouhsinelonly]

i guess we'll just wait and see ,and edit the source code manually until
@laravelbook get back ,probably he's just busy with work

2014-01-30 Ryan Nielson [email protected]:

I mean the last update is only a month ago which isn't too bad to be
honest. But a fork is always an option in the meantime.

Reply to this email directly or view it on GitHubhttps://github.com//pull/156#issuecomment-33700948
.

Mouhsine Bakhich * ,Developper Trans Gulf For Information Technology
Phone : ***********
Email : [email protected]
Rue 41 N° 6 Av Sidi Said
biougra chtouka ait baha 87200
MA

[igorsantos07]

Sorry boys, but first of all, laravelbook does not take care of this
anymore.

Second, I've been busy with my paid job and couldn't even stop at home to
see GitHub. I'm slowly getting back to life and seeing my emails slowly as
well.

Third, you don't need a fork. You can just learn to use Composer the right
way and discover:
A) how to use another branch as the main branch for a package
B) learn how to lock a version/commit, so other updates don't break your
current system

I'm going to merge this tonight or tomorrow. Please stop complaining or
revolting and bear with me. A couple of +1 is enough, but filling my inbox
with +1 won't make my time get free faster.

Finally, if there's anyone interested in entering the Ardent team, we can
talk about. I'm just afraid of making its code even worse, since there are
some parts that are currently quite fragile. We need more quality, not more
quantity ;)

Igor Santos
-- Desenvolvedor Web
[enviado do meu celular]
On Jan 30, 2014 2:28 PM, "mouhsinelonly" [email protected] wrote:

i guess we'll just wait and see ,and edit the source code manually until
@laravelbook get back ,probably he's just busy with work

2014-01-30 Ryan Nielson [email protected]:

I mean the last update is only a month ago which isn't too bad to be
honest. But a fork is always an option in the meantime.

Reply to this email directly or view it on GitHub<
https://github.com/laravelbook/ardent/pull/156#issuecomment-33700948>
.

Mouhsine Bakhich * ,Developper Trans Gulf For Information Technology
Phone : ***********
Email : [email protected]
Rue 41 N° 6 Av Sidi Said
biougra chtouka ait baha 87200
MA

Reply to this email directly or view it on GitHubhttps://github.com//pull/156#issuecomment-33704430
.

[moura137]

In short, make a fork and change you without bothering to contribute.
@igorsantos07, it surprises me that answer.

[ejunker]

@igorsantos07 I appreciate your work on Ardent but 6 days ago you said you were going to merge this. It is a one line change and very low risk. Please merge.

[igorsantos07]

I'm just saying that accepting a PR is not the only way to use the code, if
you read the your tool's manual.
I'm not expelling anyone from here.
Furthermore I got someone willing to help, and maybe he can give us a hand
in the next days :)
On Feb 5, 2014 3:21 PM, "Renato Moura" [email protected] wrote:

In short, make a fork and change you without bothering to contribute.
@igorsantos07 https://github.com/igorsantos07, it surprises me that
answer.

Reply to this email directly or view it on GitHubhttps://github.com//pull/156#issuecomment-34213493
.

[tbergeron]

I don't get what is going on, we're talking about merging one small line of code. Nothing fancy, and this would be greatly appreciated by the quite large amount of people who uses your code.

I took a second, forked your repo, fixed that line and simply added this to my composer.json file:

    "require": {
        "laravelbook/ardent": "master"
    },
    "repositories": [{
        "url": "https://github.com/tbergeron/ardent.git",
        "type": "git"
    }],

In a minute, Ardent was up and running. Why all of this? I mean all you have is click on a button.

Hope this temporarily help someone.

[RyanNielson]

Thanks for creating a temporary solution. I'd love to help on the project, and I've already contacted Igor a few days back. I haven't heard back yet, but I'm hoping I'm the person he's referring to in his last comment.

[igorsantos07]

@tbergeron the short explanation is: I haven't touched my computer in ages, and I can't do this kind of thing from my day-to-day job. Also, there's no way to do merges and stuff from my phone, and I would need space/time to close the related issues, merge, and release a new tag. :P

[igorsantos07]

Finally, while this PR got a lot more attention, this is a dup. See you all on #154 :)