New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
datatables warning ajax error 404 not found #717
Comments
Try inspecting the ajax response to get a better view of the error. You may also need to double check that your columns and your js match your table structure. This is probably a js issue. |
404 Not Found is an intermittent issue of dataTables due to environment issue when using |
@yajra . Yes. I am currently using xampp. Search continues |
Route definition has been reviewed. Intermittent 404 but ajax returns data. I think I have to agree on environment issue. |
Deployed the app live in heroku. 404 is gone. So this is confirmed environment issue. Closing this. @yajra Thank you for looking at the error. Your documentation also helped me with left join and view and edit button, Thank you. |
The solution given above works just transfer your project to the HTDOCS of your XAMPPor www of your WAMPP or run it live |
@Marker17 just make your javascript and web.php as follows
}); And in web.php Route::any('ajax/chapter/list','YourController@Method'); this code worked for me. |
save my day |
Summary of problem or feature request
I am new to laravel. I was able to run datatable using jquery plugin.
I would like the server side processing. I encountered error 404 the other day. Today I encountered
500 Internal Server Error. Call to undefined method Yajra\Datatables\Datatables:
An accession has categories and so need a join. **_How do you output data that comes from a join
in the columns? Can you provide simple example for join used in server side processing?
Thank you for looking at this.
Code snippet of problem
here is route..
index.blade.php
service provider
alias
then accession
public function index(Request $request){
System details
The text was updated successfully, but these errors were encountered: