craighobson

Getting this error as well,

PHP Fatal error: Uncaught Error: Attempt to assign property "timestamp" on null in /www/public/wp-content/plugins/wp-accessibility/wp-accessibility-stats.php:100

It’s not easy to see right away, but under the WP Accessibility settings > scroll down to the “Testing & Admin Experience” section > then the “Page Statistics Tracking” options > None

That will turn off the Tracking.

• This reply was modified 10 months, 3 weeks ago by craighobson. Reason: spelling

Just reach out to Kinsta’s support and they’ll enable the “save_comments” option for you. This is exactly what they need to do: https://woocommerce.com/document/woocommerce-square/#section-43

Simple fix!

Nice! That worked. Thank you!!

That worked. Thanks!

Thanks Robert,

Too bad. It was a handy tool.

All the best!

Nope, that’s not it. I purchased the premium version and still having the same issue.

I’m stumped.

Bingo. The “Add to Wishlist” button only works if logged in.

Of course, as we were troubleshooting, we were all logged into the WordPress admin area on only one browser… and it worked fine. When checking another browser, we were not logged in to WordPress and so we saw the error. Ha!

For the “Add to Wishlist” button to work for “guests and customers”, it seems we would need to purchase the premium version. That explains it.

Whew!

Same here! One more clue I can add to this thread,

• I am now having this issue with a website that was recently moved over from Bluehost to WP Engine for hosting.

This plugin worked before but now throws this error; and only on Safari and Firefox. WP Engine has an aggressive caching platform… @robperry4 seems to be on to the root of the problem.

Looking forward to a fix?

Looks like the latest WooCommerce 2.4.2 release resolved the issue.

I’m having the same issue.

The “Stock Qty” input field adds a bunch of decimal places after I input my single number and then update the product. It seems that stock quantity then doesn’t get reflected on the front end when selecting a variation… strange.

I’ve got the same problem.

For those using Rackspace Cloud Sites, this solved the problem for me: https://www.rackspace.com/knowledge_center/article/php-sessions-state-servers-on-cloud-sites-and-how-to-fix-non-working-php-sessions

I was working for a client who had an outdated version of WordPress installed. Updating to the most recent version of WordPress solved it for me.

I have the same problem… Any luck finding a solution?