dimitrisv

What I will do first is to upgrade an 8.7 eshop to the 8.8.1 version.
If the error does not occur… (it first occurs during installation) then we are on the right track. If not I will have to try (in another store going to version 8.8.0 etc).

In our case, I have to point out that, version 8.8 and 8.8.1 never appeared as updates!

Only just yesterday we were notified to update from version 8.7.0 o the latest version.

I guess you have to ask the Woocommerce team to release a version that 8.8.3 to make up for this for most eshops.

In our case we have over 10 eshops that we are supporting and doing triple installs to all of them is a bit of a pain – thanks to this bug we noticed in the first one, all the others have stayed in 8.7.
I will only do this for the one that got corrupted. But what if I need also version 8.8.0 ?

Correct! After disabling YOUR plugin the errors ceased.

That means our site does not offer Paypalpayments since yesterday night.

We didnt know that Woocommerce offers native support of paypal – we are only using yor plugin for paypal.

I guess you have to speak to them.

I opted to write here because it is your service that it is impacted, for Woocommerce support, you are merely of one their functionalities. So, I presumed, here is the best place to sort this out ASAP, as you may have other back channels with the Woocommerce core team.

Am I clear now?

• This reply was modified 10 months, 2 weeks ago by dimitrisv.

Hello,

The crashes stopped as soon as disabled your plugin. As the error log suggests the error is due to changes in the logging of woocommerce that your gateway does not adhere to.

Please create the ticket yourselves because it is your gateway that is impacted.

Our free, open sourced troubleshooting has to have some limit you see, as this benefits YOUR business.

We can live for a few days without paypal.

Best regards,

Dimitris.

• This reply was modified 10 months, 2 weeks ago by dimitrisv.
• This reply was modified 10 months, 2 weeks ago by dimitrisv.

Thank you! This one did the trick!

Thank you but, this is probably because we are using Pixel Your Site Pro as well.

The thing is that right now I am getting this lovely empty screen in both options of the sitekit!!!

It is not due to a plugin conflict.

Please see this loom here:
https://www.loom.com/share/6d1fca85f8ca41baab6e687c91065181?sid=d6ebf7ba-69da-4410-a58d-198e4ab7daae

I submitted the form.

Included are the js errors that we get in the console as you rightly pointed out

Just to add, that in my case not even the settings page is loading, so I do not even have the option to “reset” the installation

I have exactly the same issue.
Cloudways hosting, PHP 8.2, WP 6.4.3, Woo 8.5.2. – It stopped working in all my sites.

I am affraid the issue was not solved completely.

[Thu Aug 31 15:15:41.170453 2023] [proxy_fcgi:error] [pid 18742:tid 140601475438336] [client 157.55.39.215:0] AH01071: Got error ‘PHP message: PHP Warning: ?Undefined property: wpdb::$wc_orders in public_html/wp-includes/class-wpdb.php on line 789PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘WHERE payment_method = ‘ppec_paypal” at line 1 for query SELECT 1 FROM ?WHERE payment_method = ‘ppec_paypal’ made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce\\PayPalCommerce\\{closure}, WooCommerce\\PayPalCommerce\\init, {closure}, WooCommerce\\PayPalCommerce\\Compat\\CompatModule->run, WooCommerce\\PayPalCommerce\\Compat\\CompatModule->initialize_ppec_compat_layer, WooCommerce\\PayPalCommerce\\Compat\\PPEC\\SubscriptionsHandler->maybe_hook, WooCommerce\\PayPalCommerce\\Compat\\PPEC\\PPECHelper::use_ppec_compat_layer_for_subscriptions, WooCommerce\\PayPalCommerce\\Compat\\PPEC\\PPECHelper::site_has_ppec_subscriptions’

You are unbelievable!

Just installed it, it is looking good! ??

Thank you so much!

Thank you Joost. In my case I switched back to 2.2.0. (going back to non-HPOS will add about 2million records in my postmeta and I am happy with the speed we enjoy due to HPOS).

Please be so kind to post in this thread as soon as you release with the fix.

This is correct. It has been resolved.

In our case, because we wanted to move ASAP to HPOS, we replaced both with custom code. One that adds a flat fee on Cash On Delivery, and another that adds a checkbox for a Phone Order in the Orders Admin section.

Thus we did away with both plugins that seemed to have superfluous functionality for our needs (plus the HPOS incompatibility).

We have already done away with the Local Pick Up plus and now the only thing that remains is to have the Pods team make their Order entity extension compatible with the HPOS based Orders page.

It is saddening the fact that there is this innovation (HPOS) that delivers tramendous improvement on performance and plugins that are dealing with Orders just have to wait for the time that their compatibility will be compulsory, in order to make them compatible.

Another issue is this:



When you go to an order (new or existing) you do not get any of the options for this order.

For example we have custom fields (via Pods framework) that do not show, nor can be hidden.

Also Phone Orders and Payments – WooCommerce remains incompatible.

Having done without the incompatible
– Local Pickup Plus and
– WP All Import/Export

Should we have interoperability with
– Pods
– Phone Orders and Payments
– Payment Gateway Based Fees

We could have migrated to HPOS “yesterday”.