-
Notifications
You must be signed in to change notification settings - Fork 26
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
Issue with render function and modal details window #45
Comments
Can you add your render config and your modal definition ? |
Sure Render function: Modal definition: `
@include('components.loader_small')
×
` |
Why put you cellValue inside [[]] ? Are you try : Are you try to add a breakpoint inside your function showDetails to see what'a happen ? |
Why put you cellValue inside [[]] ? Because i'm using a template engine that use {} to render server side element Are you try : "render": "" ? Yes but no value printed it print click="showDetails(cellValue)" Are you try to add a breakpoint inside your function showDetails to see what'a happen ? Yes and all work fine ajax call return code 200 and details info |
See below the render used inside UDT to open an image inside a modal
I hope that's help you. |
Is it possible call a jquery click event instead an ng-click event? to move modal population logic outside angular. I have tryed changing the button code like this
But instead printing the cell value it print the string (cellValue) |
I don't known if it's possible to call JQuery from Angular. |
Hello, can you try |
You can also try
The code for this option is here Ultimate-DataTable/src/directives/udt-cell.js Line 234 in 5b3aad3
|
Hello
I have some problems to get modal window with details working with ultimate datatable.
In my tabel i have a details column that using render function to show a button that on click call an angular function that open a bootstrap modal with details.
The ng-click trigger work as aspected but modal content is empty.
Same logic using datatable.js directly working correctelly
The text was updated successfully, but these errors were encountered: