Hi,

I upgraded from 2.1.2 to 2.1.3 and now I get this error on ajax call. In version 2.1.2 I haven’t encunetered this error.

I know this is csrf and if I turned it off it works. Any ideas why?

If you think this is a bug.
Post it here,
http://ellislab.com/forums/viewforum/51/

Community Auth, which has a few ajax calls, has stopped working when csrf_protection is enabled. So, there is for sure a bug. I’ll try to see if I can fix it later. I don’t have time right now.

UPDATE: It was my code. There’s nothing wrong with CodeIgniter.

Thanks for anwsers. Where can I see when bug is gonna to be fiexed?

valuk - 09 October 2012 02:27 AM

Thanks for anwsers. Where can I see when bug is gonna to be fiexed?

What I was saying is that there is no bug. In my case, it was my code. I wasn’t properly sending the CI CSRF token along with my ajax request, but fixed the instances where that was the problem, and everything is working fine. There’s nothing wrong with CI 2.1.3.

Ok sorry and thanks.

I placed a bug report as I’m having the same issue and want to just double check. I’d hate to be forced to find a new jquery plugin because of a CI bug, especially when a decent grid plugin is a royal pain to find.

elite-board - 17 October 2012 07:29 PM

I placed a bug report as I’m having the same issue and want to just double check. I’d hate to be forced to find a new jquery plugin because of a CI bug, especially when a decent grid plugin is a royal pain to find.

What jquery plugin are you using, and how are you using it? Does it fire off multiple requests at once? Can you reproduce the problem using a siimple code?

I’m using jTables(http://www.jtable.org/), its a grid plugin.

all it does is call a controller action that has a sql command (which is in a model). it uses GET to handle things like paging, sorting, etc. which I use $this->input->get() to get those values.

the code itself is simple.

I have other ajax code that works fine, but its also homebrewed so I built it to handle CI’s CSRF.

I’m willing to use another grid plugin if i have to, but I’d really prefer not to as this suit my needs the best out of the limited choices out there. I probably go through the plugin’s code tonight and see if I can tweak it.

I fixed the problem.

the script’s author says the load is in GET, but the code has it fixed to do POST no matter what. I altered the ajax call to go one or the other depending on what its doing and now its working again

so it seems to not be a bug, just poor plugin documentation lol.