In order to improve the performance of parsing in oik-shortcodes we introduced the storing of strings representing a post meta value rather than the post_id. This then required queries to be written using meta_query. For oik-ajax to be able to request the next page, the meta_query information must be passed to the client and back again. This needs to get back to the query that is run when the shortcode is executed. We need to find a solution that's fairly transparent to the shortcode that's being invoked.
This needs to work for [bw_navi] when it's being called to page through the lists displayed for Called by, Invoked by, Call and Call hooks.
If no easy solution can be found we'll have to revert to storing the post ID and/or remove the need for meta_query.
In order to improve the performance of parsing in oik-shortcodes we introduced the storing of strings representing a post meta value rather than the post_id. This then required queries to be written using
meta_query
. For oik-ajax to be able to request the next page, themeta_query
information must be passed to the client and back again. This needs to get back to the query that is run when the shortcode is executed. We need to find a solution that's fairly transparent to the shortcode that's being invoked.This needs to work for
[bw_navi]
when it's being called to page through the lists displayed for Called by, Invoked by, Call and Call hooks.If no easy solution can be found we'll have to revert to storing the post ID and/or remove the need for meta_query.