Andreas

Thank you very much!

Hello, I have the same issue.

“E_ERROR was caused in line 260 of the file plugins/woocommerce/src/Packages.php. Error message: Uncaught Error: Call to a member function get_column_count() on null in plugins/woocommerce/src/Packages.php:260”

Any idea?

Hi Mr. Kandani, I’m very sorry for the confusion I had.. Sorry for bothering you, and thank you very much for your great, prompt reply!

Could you please kindly remove my post or at least, remove the website URL from my first post?

Thanks and Best Regards.

We have the same trouble. Whole the website is disappeared after update 6.9.0, just a PHP warning message like above on homepage. Any help?
PHP version: 8.0.20

• This reply was modified 2 years, 6 months ago by Andreas.

We have the same trouble. Whole the website is disappeared after update 6.9.0, just a PHP warning message like above on homepage. Any help?

PHP version: 8.0.20
WordPress version 6.0.2
Theme: Skybook 2.0

• This reply was modified 2 years, 6 months ago by Andreas.
• This reply was modified 2 years, 6 months ago by Andreas.
• This reply was modified 2 years, 6 months ago by Andreas.

Hi them.es, thanks very much for your reply and report. I wonder how come WooCommerce team didn’t notice such obvious warning messages before releasing new features/versions? No testing team?

Debugging is off.

It is impossible to downgrade PHP on our web server (hosting thousands of domains, and not really good for both security/performance reasons)

PHP 7.x is considered outdated, old and slow by PHP.
There is even PHP 8.1.x branch (which is listed as current stable)

Reviewing the code for PHP 8 compatibility shouldn’t be very hard thing for WooCommerce team. It is well known and well respected plugin, and it would help your users a lot.

Best wishes.
Thanks.

Hi again, Maykato.

I have disabled all plugins (don’t have much anyway) but the problem still persists.

Please take a look at that warning lines above, it might be incompatibility with PHP 8.0.

Thanks.

After upgrading from PHP7 to PHP8, almost all my plugins were giving such warning. I reported them and they all fixed it. However the author of this plugin insists to ignore it.

My environment was: FreeBSD 13, PHP 8.0.13, nginx and ImageMagick ver 7 (3.5.1)

And the plugin was working great.. (1.9.2)

I think I can now reproduce the warning,
A GET request like: /?author=1 doesn’t give any PHP warning.
but a GET request like: //?author=1 gives the PHP warning above.

So typing: mysite.com/ will not give any warning.
but typing: mysite.com// will give the warning.

“PHP message: PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/change-wp-admin-login/includes/class-change-wp-admin-login.php on line 282

PHP message: PHP Warning: Trying to access array offset on value of type bool in /wp-content/plugins/change-wp-admin-login/includes/class-change-wp-admin-login.php on line 290” server: mysite.com, request: “GET // HTTP/2.0”

Also; visiting: mysite.com//.env
gives such error: PHP Warning: Undefined array key “path” in /change-wp-admin-login/includes/class-change-wp-admin-login.php on line 282

Can this help?

Thanks.

• This reply was modified 3 years, 3 months ago by Andreas.
• This reply was modified 3 years, 3 months ago by Andreas.
• This reply was modified 3 years, 3 months ago by Andreas.

Now, trying again with different browsers and cleared browser cache, it seems, sometimes it doesn’t show up at all, from time to time. Could you please give me an e-mail address so that I could post you the link? (My site that fastcgi-cache enabled)
Thanks.

• This reply was modified 3 years, 3 months ago by Andreas.
• This reply was modified 3 years, 3 months ago by Andreas.

Thanks so much for your return, Lap.

Here it is: https://imgur.com/198f6sZ

Hi Nuno, thank you!

I’m on PHP 8.0.13. Please let me know if you need to know anything else on that matter.

Best.

• This reply was modified 3 years, 3 months ago by Andreas.

I mean, I’m aware and intentionally I do know that why that page of mine gives 404, that’s ok. But no idea why Koko throws that error.

It seems, Koko gives such errors on 404 errors of WordPress? Statistics do indeed show up. But I’m not sure if all the visitors are counted or not.