-
Notifications
You must be signed in to change notification settings - Fork 108
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
offset not found issue on add_column #125
Comments
Is this fixed after latest code release? |
no, I am using the latest version |
I updated it a minute ago, please check if you have 1.4.2 |
Works for me anyway... Can't reproduce your error. |
ok, I will check it later, thanks! |
so if you are using addColumn which has ordering enabled, does your search works without errors? BTW. I have server side processing enabled |
I just tested it and it works as expected - if you try to search or sort on virtual column the search/sort is not executed. This may be changed in future releases but this involves changing large amount of code to make it work other way. |
(please reopen this issue if you find it working other way than above) |
sure, thanks, I'll soon take a look again and post screenshots with version names and code if you would need any more information |
OK, thanks |
after an upgrade, I get the error message when doing global search on virtually added column with add_column
the problem is in Databases.php file line 560 - index is being requested which should not!
somebody has to override
if ($this->input['columns'][$i]['orderable'] == "true") when using add_column function and not using the ordering, or offsets must be calculated correctly and filtering not used on them
bug dissapears when explicitely initializing
The text was updated successfully, but these errors were encountered: