Error database – Latest post doesn't show

Hello,

I’m back with the same issue 🙂

I’m checking your plugin code and try to understand why is appearing a database error in the log.

$results = $wpdb->get_results( “
SELECT
posts.ID, posts.post_date_gmt AS date
FROM
" . $wpdb->base_prefix . ($blog_id > 1 ? $blog_id . '_' : '') . "posts AS posts
$only_podcasts_sql_from
WHERE
posts.post_type = ‘post’
$only_podcasts_sql_where
AND posts.post_status = ‘publish’
AND posts.post_password = ”
AND posts.post_date_gmt < ‘” . gmdate( “Y-m-d H:i:s” ) . “‘
$only_podcasts_sql
ORDER BY
posts.post_date_gmt DESC
LIMIT 0,”
. (int) $max_entries_per_site
);

This line (at plugin.php), $wpdb->base_prefix . ($blog_id > 1 ? $blog_id . ‘_’ : ”) , throw the error, because for the main blog (id = 1) id is ommited . But id 1 does exist, and wp_posts doesn’t exist for multisite, it must be prefixtable_1_posts

Now, moreover, when I publish a post in network: it is showed at feed page, but not at widget.

If I try to disable cache, also the last post published doens’t appear.

Can you help me, please?

It is a good plugin, but doesn’t work well yet.

Hi Frank,

$wpdb->base_prefix . ($blog_id > 1 ? $blog_id . ‘_’ : ”)

in my case, the main blog is: baseprefixtable_1_posts

So, as blog_id = 1, the result is: baseprefixtable_ posts (which doesn’t exist), and then it is threw the following database error:

WordPress database error Table ‘database.baseprefixtable_posts’ doesn’t exist for query

Thank you,

Okay, I didn’t know that other multisite installations there is no id = 1 (my wp multisite is older than 4 years)

In fact, there are some constants, where you can define the default.

define (‘SITE_ID_CURRENT_SITE’, 1);
define (‘BLOGID_CURRENT_SITE’, ‘1 ‘);

From what I’ve seen, the majority is 1.

I don’t quite understand, but the fact is that you can not omit the id 1, whether or not the main blog.

Don’t you think?

Thanks a lot,

Hello Frank,

When will you update your plugin in order to solve this bug?

thanks!!!!

Hello Frank,

I have tested it and now it works correctly. The log error dissapeared.

Thanks a lot for your work!