Watched 1 video

Watched 1 Video from start to finish

Subscribed for 1 month

Learning and showing your support for 1 Month

Spread the word 1 time

Referred 1 Member to Drifting Ruby


10 times Chatter Box

Make 10 comments to videos or replies to other comments

Share the love 1 time

Liked 1 episode


Welcome back 3 times

You've visited Drifting Ruby on 3 different days

Suggested 1 episode

Helped the community by suggesting 1 episode

Vote Suggestion 1 time

Helped the community by voting on suggestions 1 time

1 time Chatter Box

Make 1 comment to videos or replies to other comments

Earned on 3/4/2019

# Name
afonso.pimentel said over 1 year ago on DataTables :

Hi. I found your post very helpful and I thank you very much for taking time to build such clear and helpful posts.
I have an issue that only started to happen after I modified my datatable to server side processing following the instructions in your video.
What started to happen was this.
I have a webapp with a header with some menu options. One of the options is a link to the users index page.
If I create or update a user, my application redirects to that user show page - let's assume I just created user #10. So after the creation I'm at url /users/10.
This is fine up until this point. When I click on the users index link to see all the users is when the issue happens.
I can see in the logs that the correct controller and method is called - users controller and index method.
The page starts to load, I see the title of the page and the columns headers, but then I get and error - the JSON response is not what it was expected.
In the logs, after the call for the index page, another request was made (same url as the detail of the user with some extra params: ?draw=1....). So it starts a GET to /users/10?draw=1...
I do not know where this call is made. I have no idea what to do and it would be great if you could provide some help about this.
Thanks in advance.
Afonso Pimentel