Documentation says ajaxSettings specifies the ajax default behavior. In short, if ajax calls are going to be using GET or POST (refers to jQuery documentation at this point).
That's ok. The default setting is POST. Perfect. But many ajax calls made by jTable are based in GET, don't use ajaxSettings configuration and it looks like there is no other chance to make it use POST than modifying the library file (something that should be avoided).
Calls like reloadTable, and many more (just check the library file). How should I proceed if I want all ajax calls to use ajaxSettings ? or is there a reason to have the current behavior in the library?
RoelDeveloper
commented
10 years ago
Documentation says ajaxSettings specifies the ajax default behavior. In short, if ajax calls are going to be using GET or POST (refers to jQuery documentation at this point).
That's ok. The default setting is POST. Perfect. But many ajax calls made by jTable are based in GET, don't use ajaxSettings configuration and it looks like there is no other chance to make it use POST than modifying the library file (something that should be avoided).
Calls like reloadTable, and many more (just check the library file). How should I proceed if I want all ajax calls to use ajaxSettings ? or is there a reason to have the current behavior in the library?
Congratulations for such a good library.
Thanks for your time.
Regards, Herman Gomez