ERROR: The current node list is empty after upgrading laracast to Intertia

[kossa]

Currently laracasts-downloader is not working after the latest upgrade of Laracast to intertia : https://laracasts.com/blog/the-best-of-both-worlds

Any update for this ?

[Lisendra]

I can confirm, I'm getting the same error:

Authenticating
====================================
ERROR: The current node list is empty.`

[MicroSystems]

I got the same issue ERROR: The current node list is empty

[willvincent]

So the problem, obviously, is that the code as it exists today depends on all the data existing in the dom. Which it doesn't now that Laracasts is using inertia.

The necessary data does, however, appear to be available either in the data-page attribute of the #app div, or via an xhr request made to the same route, that returns JSON.

tl;dr - Should be fixable.

[emilas44]

Same problem me too....

[MicroSystems]

@willvincent any progress fixing this issue ?

[willvincent]

@MicroSystems I haven't had any time to try.

[paolog22]

up

[hardikdangar]

is this fixed ?

[emilas44]

Unfortunately not. @willvincent is probably very busy.... Maybe he could try to explain what do we have to do? Maybe there is someone else who could fix this!?

[paolog22]

Upon investigating. saw that csrfToken is not in the dom and is now located in js which is the app is still looking at the dom. :), this is for the authentication only. already fix on my end but i am still trying with getting the series

[AmirRezaM75]

i'm already working to fix this, but having problem with authentication,any idea how should I log in? Non of these approaches works :(

$response = $this->client->post(LARACASTS_POST_LOGIN_PATH, [
    'cookies' => $this->cookie,
    'body'    => [
        'email'    => $email,
        'password' => $password,
        '_token' => $csrfToken,
        'remember' => 1,
    ],
    'verify' => false
]);

$response = $this->client->post(LARACASTS_POST_LOGIN_PATH, [
    'cookies' => $this->cookie,
    'headers' => [
        'X-CSRF-TOKEN'   => $csrfToken,
    ],
    'body'    => [
        'email'    => $email,
        'password' => $password,
        'remember' => 1,
    ],
    'verify' => false
]);

[willvincent]

Not sure why things keep getting addressed to me. All I've done is minor tweaks to this code. 🤣

[carlosflorencio]

@AmirRezaM75 , the login seems to have changed and the request now sends the payload in JSON format.

It's required to send the Request Header content-type: application/json and the body as {"email":"[email protected]","password":"efaewr34q5"}.