You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I cannot make datatables to work with columns in blade views. All works ok for regular columns, but not for relations. All these columns will print "[object Object]" in table ({} in json return). This happens only with blade files like "columns.user.login". In all files I have only "test" text (I can put exact same path in every column, and it will be error only in these with relation in it anyway).
If I remove rawColumns() or escapeColumns([]) then all works OK (but without rendering HTML of course).
What is weird - if I replace 'columns.user.login' with 'test' then again it works. Only not with separate blade files. Why?
I found similar problem here: #1151 It should be fixed, but no :(
I tried to test this with my old Laravel 5.5 instalation and datatables 8, and also same problem.
Fix Issue yajra#2062
Column with blade file is rendered by view() but it cannot be converted to json response. render() will return just HTML code.
Also without render if we try to debug $data inside DT source by Log or var_dump it will result with "Allowed memory size of xxx bytes exhausted".
Summary of problem or feature request
Hi. I cannot make datatables to work with columns in blade views. All works ok for regular columns, but not for relations. All these columns will print "[object Object]" in table ({} in json return). This happens only with blade files like "columns.user.login". In all files I have only "test" text (I can put exact same path in every column, and it will be error only in these with relation in it anyway).
If I remove rawColumns() or escapeColumns([]) then all works OK (but without rendering HTML of course).
What is weird - if I replace 'columns.user.login' with 'test' then again it works. Only not with separate blade files. Why?
I found similar problem here: #1151 It should be fixed, but no :(
I tried to test this with my old Laravel 5.5 instalation and datatables 8, and also same problem.
Is this bug? Any ideas? I
Code snippet of problem
System details
The text was updated successfully, but these errors were encountered: