Stillat / meerkat-statamic3

Meerkat 2 is an extremely powerful and easy-to-use comment platform for Statamic 3.
https://meerkatcomments.com/
Other
5 stars 4 forks source link

($context) must be of type Stillat\Meerkat\Core\Contracts\Threads\ThreadContextContract, null given #230

Closed ryanmitchell closed 1 year ago

ryanmitchell commented 1 year ago

I'm getting an error:

Stillat\Meerkat\Core\Storage\Drivers\Local\LocalThreadStorageManager::createForContext(): Argument #1 ($context) must be of type Stillat\Meerkat\Core\Contracts\Threads\ThreadContextContract, null given

HTML as per the screenshot - basically a copy of whats in the docs.

Screenshot 2023-05-02 at 23 24 47

I've done a little code digging but cant see what the issue is.

Have I missed a step?

Statamic v3.4.7

JohnathonKoster commented 1 year ago

Hey there!

I typically see this if it can’t find an entry with the given ID. I’ll do some debugging later in the week to see if I can reproduce it and/or improve on this error

On Tue, May 2, 2023 at 5:26 PM Ryan Mitchell @.***> wrote:

I'm getting an error:

Stillat\Meerkat\Core\Storage\Drivers\Local\LocalThreadStorageManager::createForContext(): Argument #1 ($context) must be of type Stillat\Meerkat\Core\Contracts\Threads\ThreadContextContract, null given

HTML as per the screenshot - basically a copy of whats in the docs. [image: Screenshot 2023-05-02 at 23 24 47] https://user-images.githubusercontent.com/51899/235798789-a3735df7-4ed0-4d78-b4d2-98cfff88010d.png

I've done a little code digging but cant see what the issue is.

Have I missed a step?

Statamic v3.4.7

— Reply to this email directly, view it on GitHub https://github.com/Stillat/meerkat-statamic3/issues/230, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABH5R6SQ4LNSCTHWMK4W573XEGCXVANCNFSM6AAAAAAXTUPCVY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- John Koster

ryanmitchell commented 1 year ago

That was helpful thanks - it helped me find the cause of the error.

I had the comment form wrapped in a {{ user }} tag, so it was getting the user id not the entry id.

icemancast commented 8 months ago

FYI had this same issue but my reply form was inside the {{ comments }} loop so think the id was getting confused as well. I moved it outside of that and that worked.