The Cloud Library causes some Category pages to display a server error

Posted in: Newspaper
Post count: 9

Some Category pages load fine. Others display a ‘500’ server error page and throw the error below in the background. The page loads when the plugin is turned off.

Fatal error: Uncaught Error: Call to a member function the_post() on null
in ****/wp-includes/query.php on line 979

Call stack:

the_post()
wp-content/plugins/td-cloud-library/wp_templates/tdb_view_category.php:17
include()
wp-includes/template-loader.php:106
require_once()
wp-blog-header.php:19
require()
index.php:17

Post count: 35449

Hi hcm,
This is quite strange. Normally, most of users use one cloud category for most of category, so in case that this is causing some problem will be on all categories and not only for a few.
So what I can suggest is to set a different cloud template and see if the problem persist. If the problem is still there, please set a no template https://i.imgur.com/HTLpItw.png
Also, you can make some test using only tagDiv plugins.
Let me know the results!

Post count: 9

It does appear to only be an issue with the global default template. When I select ‘No Template’, the page displays without error.

It is still only an issue with some categories though (with a custom default template selected) and I don’t see what’s different about those particular categories. It is strange that some work fine and others don’t work at all. I created a brand new default template and set it to global(I used different elements as well), but it continues to cause errors on some category pages.

I tested with only TagDiv plugins enabled and the results are the same.

Post count: 35449

Hi,
In this case please make a full backup for your website and we’ll continue to investigate it via email, please contact us at contact@tagdiv.com and provide wp-admin and cPanel access. Also, please include the link of this topic to identify you. We’ll check it as soon as possible.
Thank you!

Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic.