Search

good support in all modern browsers.

option and has three modes of operation:

has three different Editor modes: Primary editing

has three different Editor modes: Primary editing

has three different Editor modes: Primary editing

has three different Editor modes: Primary editing

the end user's conceptual model of the data. Categories

file saving features of modern browsers (IE10+, Chrome, Safari,

is resized. A relatively modern browser is required

Thanks, colin, that helped me. In the end, I did this here. https://editor.datatables.net/examples/simple/inTableControls Have it changed to a "show"-button.

Hi @fabioo7 , You can move the element with jQuery functions - something like this. Cheers, Colin

Hi @anakin59490 , You would get that error if the DataTables initialisation couldn't find the requested pagingType plugin, so it looks like your step 1 above isn't loading the file as expected. Cheers, Colin

After researching for many hours,i finally found a way to make it work. I pass the POST date as string and then format it with strtotime() and then date() as follows: $POST1 = $_POST["datevalue_from_datepicker1"] ; $POST1 = str_replace('/', '-', $POST1); $POST1 = date('Y-m-d', strtotime($POST1)); and in sql in Editor instance ->where( function ( $q ) use ( $POST1) { $q->where( 'start',$POST1,'>=' ); } ) Thanks for the help!

Hi @crackwood , At a glance your code looks ok - pretty much the same as this example here. Are your variables html and html2 formatted the same as the example? If no joy, would you be able to link to your page or create a test case? Cheers, Colin

Hi @KelvinDing , Glad all working, and thanks for reporting back! Cheers, Colin

Thank you Kevin and apologies for my delayed reply. I'm pretty sure that I am including the correct files but maybe some of my other plugin files are conflicting so I will need to test with a blank slate. I will get back to you. Thanks

Actually its the toggling of any of the other buttons except the output button that causes the issue since doing so causes the output window size to change and then fires the page resize event.

Hi @teojicd , Yep, you have control over how the children are displayed by responsive.details.renderer. There's an example of that here. Cheers, Colin

@colin thank you very much :) :) :)