markisu72

Ok, will do, thanks!

Hi @afzalpansuvi,

thanks for your feedback.

Sure, this is not a consulting forum, but you already helped me with the info that category__not_in does not apply to WC cats.
I know now how to move on

Thx
Markus

Hi @inpsydekrystian,

thanks for your response and sorry for my late one ??

I checked the connectivity and web hooks can be received successfully.

Is there a retry with these web hooks in case the system is not available?
It might have interfered with me restarting the machine.

Regarding activating the log… right now, I don’t expect credit card payments for some time due to circumstances… I would consider the issue an accident for now and would reopen a ticket if it reoccurs and then also activate logging.

But it would be great to learn about the retry-mechanisms anyway.

Thanks

Markus

Hi @inpsydekrystian,

I think, this mystery is solved… I fumbled with the hooks

woocommerce_cart_ready_to_calc_shipping and woocommerce_cart_needs_shipping

to only let shopping cart calculation happen on the checkout page and for whatever reason, this interfered with the PayPal plugin.

I found a different solution for what I wanted to achieve and now, everything looks as expected.

Best
Markus

Hi @inpsydekrystian,

thanks for the info.

Markus

Hi @devsmip,
any feedback on this?
In general, the plugin seems to work ok, but these restrictions bind me to a provider, I don’t want be bound to (like many others).

I’d be glad to support you on getting more positive feedback.
Thx
Markus

Hi guys,

I checked your code and there are basically only two places, where they are being used.

Firstly, for checking whether a directory has the same user as the plugin user. This is not needed – if there is an issue with accessing the directory, you can just _test_ it and post the same message.
Anyway, this is an absolute corner case and in order to just write a more sophisticated error message, does not rectify using getmyuid.

Secondly, you use shell_exec to execute a shell-find-command in order to find files. This easily can be done (and every other plugin does that) *without* shell_exec and without running shell commands.

I thought, it might be more tricky, but it is not – you can easily get rid of these functions and thus become compatible with all hosters – especially with very security-focusing B2B hosters.

Kindly update your plugin, so that these functions are no longer needed and we can use dedicated machines, which have been properly hardened for security.

Thx
Markus

Hi @nigeljamesstevenson,

that’s great news! Thanks a lot for your support!

Markus

Hi @anastas10s & @nigeljamesstevenson,

I don’t feel comfortable to post the full system report here.
Is there a confident way to get it to you?

What I can share with you here is the following:

### WordPress Environment ###

WordPress address (URL): https://www.my-removed-url.de
Site address (URL): https://www.my-removed-url.de
WC Version: 8.5.2
REST API Version: ? 8.5.2
WC Blocks Version: ? 11.8.0-dev
Action Scheduler Version: ? 3.7.1
Log Directory Writable: ?
WP Version: 6.4.3
WP Multisite: –
WP Memory Limit: 768 MB
WP Debug Mode: –
WP Cron: –
Language: de_DE
External object cache: –

### Server Environment ###

Server Info: nginx/1.24.0
PHP Version: 8.1.26
PHP Post Max Size: 2 GB
PHP Time Limit: 300
PHP Max Input Vars: 10000
cURL Version: 7.81.0
OpenSSL/3.0.2

SUHOSIN Installed: –
MySQL Version: 10.11.6-MariaDB-1:10.11.6+maria~ubu2204
Max Upload Size: 2 GB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 8.5.2

###
Connected to Woo.com: ?
Enforce Approved Product Download Directories: –
HPOS feature screen enabled: ?
HPOS feature enabled: ?
Order datastore: Automattic\WooCommerce\Internal\DataStores\Orders\OrdersTableDataStore
HPOS data sync enabled: –

A new order just popped in and as you can see in the screenshots, the widget does show 2 orders in processing state, while there are 3 in processing state in the order overview (and 3 is the correct amount).

Widget: https://snipboard.io/zWkXfB.jpg

Order overview: https://snipboard.io/myg1Ix.jpg

I waited several minutes but the status did not change (external cron interval is 1 min).
After switching the HPOS data sync back to enabled, the widget correctly shows 3 orders in processing state.

It seems obvious that the widget does NOT rely on the HPOS tables.

Hope, that helps.
Thanks for your support!

Markus

• This reply was modified 10 months ago by markisu72.

Hi @anastas10s & @nigeljamesstevenson,

thanks for your feedback.
I need to deactivate the compatibility mode first and wait for new orders coming in, in order to show you the effect.

I will get back to you.
Best
Markus

• This reply was modified 10 months ago by markisu72.

Just to not let some formalism get into the way of solving the issue… I created a new thread ??

https://www.ads-software.com/support/topic/woocommerce-status-widget-shows-wrong-numbers-with-hpos-enabled-part-ii/

@ewerkstatt I checked the template provided at gtm4wp.com and it seems that the provided container is already the updated one.

So I suppose, that the correct step would be to remove the existing e-commerce container from Tag Manager and replace it with the new one.

But since there is the hint, that we can expect an upgrade of the tutorial with a much simplified approach, soon, I will wait until this is available.
https://gtm4wp.com/google-tag-manager-for-woocommerce/how-to-setup-enhanced-ecommerce-tracking-google-analytics-4-ga4-version

Best
Markus

• This reply was modified 11 months ago by markisu72.

Yes, please…
I’m also a bit lost here…

Hi Joost,

thanks for your answer!

The hint regarding the “architectural issue” was not meant to be offensive, nor did I mean that hooking into shutdown is an issue in general. And yes, BIS uses the same approach.

It is just like (I assume) because your plugin name starts with a ‘z’, your shutdown action is the last to be executed and then firing stock update hooks will hit all other plugins in their shut down state… it somehow inverts the natural execution order.

Sure, I will open a request.

Thanks,

Markus

PS: there seem to be multiple places where you register a shutdown action which process the queue, if I’m not mistaken. You should apply the fix to all of them, if these places could result in the same issue

• This reply was modified 1 year ago by markisu72.