Kooyaya

Thank you so much, @mrclayton ! I’ll give it a try.

Hi Peter,

I have 15 pages on Data Projects as of now and more will be added. It would be helpful if I can see the Seq# and sort them.

It’s not critical, but very helpful.

Best regards,
Kooyaya

Sure! You are the best!

Hi @mrclayton,

Thank you so much for your prompt response and even jumping in to help! I really appreciate it!

Best regards,
Kooyaya

Thank you!

How can re-installation help fix the bug? Have you check your code around the line in error message? It’s obvious!

The $table_data used at line 2086 and 2091 is not defined when the if-statement in line 1998 is false, since the $table_data is only defined within the if block. The code is as below:

if ('VIEW' != $table_type) {
  ......
  $table_data = ......
}

$next_page = (-1 == $process_pages || 0 == count($table_data)) ? 'finished' : (int) ($row_start / $row_increment);

If I read the code correctly, the plugin breaks if there is a view in the database

Hi Peter,

Thank you so much for the prompt response!

I realized that you already provided the filter to customize where-clause and you mentioned it to me before (https://wpdataaccess.com/2020/01/29/filter-wpda-construct-where-clause-to-add-custom-search-behaviour/). The subquery returns the list of items for the current user. I can add a filter to get the job done. I’ll give it a try.

It’s an important security improvement to remove the sql_where paramenter. Completely understood!

Thanks,
Kooyaya

Thank you, Peter! This really helps!

Yes, a fake unique key works for me! Thank you, Peter!

That works! Thanks Peter!