Warning: count(): Parameter must be an array or an object that implements Countable in /home/vhosts/theatersaanzee.com/httpdocs/wp-includes/post-template.php on line 316

Support
#1

Site

Site URL - https://theatersaanzee.com
Home URL - https://theatersaanzee.com

WordPress Environment

Version - 5.3.2
Debug is on - No
Language - nl_NL
Is Multisite - No
Memory Limit - 128M

Web Server Configuration

Software - Apache
PHP Version - 7.4.2
MySQL Version - 5.6.29

PHP Configuration

Post Max Size - 8M
Time Limit - 150s
Max Upload Size - 2M

Active Theme

Name - Pro – Child Theme
Version - 3.2.0
Folder - //home/vhosts/theatersaanzee.com/httpdocs/wp-content/themes/pro-child/
Parent Theme Name - Pro
Parent Theme Version - 3.2.0
Parent Theme Folder - /home/vhosts/theatersaanzee.com/httpdocs/wp-content/themes/pro

Active Plugins

  • AddToAny Share Buttons 1.7.39
  • Foyer - Digital Signage voor WordPress 1.7.4
  • Gwolle Gastenboek 3.1.9
  • ActiveTickets for Theater 1.4.5
  • Snapshot Pro 3.2.1.4
  • Theater 0.16.1
  • Defender Pro 2.2.6
  • Hummingbird Pro 2.4.0
  • Smush Pro 3.6.0
  • WPMU DEV Dashboard 4.7.5

CDN

Click this button to check what CDN this site is using. - Check CDN

Hi Team,

Since the theme update to Pro 3.2.0 I see below warning message. I tried enabling and disabling the WP debug mode & deactivating all plugins, but didn’t fix the issue. If I activate the default Wordpress Twenty Twenty theme, the message disappears. Therefore, it seems to be a Pro related issue. Can you please help out?

image

Regards,
Yannick

#2

In the meantime I have disabled the error with @ini_set( ‘display_errors’, 0 );, but issue is still present.

#3

Hello Yannick,

Thanks for writing in! You are seeing a PHP Warning. This could be related to your PHP Max Upload since it is quite too low. You need to increase it.

To get rid of the PHP Warning message, please disable the debug mode. You can do this by opening wp-config.php and adding:

define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

When you revisit the page, you should no longer be seeing the error message.

Hope this helps. Please let us know how it goes.

#5

Hi @Yannick_Mol,

We have confirmed this is a bug, and it has been corrected. It will be part of the next release which will be available soon.

#6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.