daheadcracker

Ok, Thanks for taking care of this. In the meantime I had to do some other adjustments:

1. Whenever one of the variations in the bundle was changed, the other bundle products lost their selected product addons, therefore I needed to filter for the attribute of the variations.

        // Variation dependencies

        jQuery(‘.bundled_product’).on(‘found_variation’, (function (e, variation) {

            if( variation.attributes[‘attribute_pa_attr1’] || variation.attributes[‘attribute_pa_attr2’] ){

                this.selectedVariation = variation[‘variation_id’];

                this.triggerConditionalRules();

            }

        }).bind(this));

2. When I made a bundle product optional, clicking the checkbox lead to also loose the selected addons of the other products in the bundle. Therefore I needed to check if the variation of that product is actually set when the reset_data event triggers:

        jQuery(document).on(‘reset_data’, (function (e, variation) {

            if(variation != undefined){

                this.selectedVariation = 0;

                this.triggerConditionalRules();

            }

        }).bind(this));

Hope this helps you with the new release.

• This reply was modified 1 year, 8 months ago by daheadcracker.

Hey @christian1983

the hook “wc_amazon_async_polling” is being used for checking the status of Amazon charges and charge permissions async.

But why is it that the hook with the same args ([“BXX-XXXXXXX-XXXXXXX”,”CHARGE_PERMISSION”])/ for the same order needs to run almost 10 times a day for every day?

	public function schedule_hook( $id, $type ) {
		$args = array( $id, $type );
		// Schedule action to check pending order next hour.
		if ( false === $this->is_next_scheduled( 'wc_amazon_async_polling', $args, 'wc_amazon_async_polling' ) ) {
			wc_apa()->log( sprintf( 'Scheduling check for %s %s', $type, $id ) );
			as_schedule_single_action( strtotime( '+10 minutes' ), 'wc_amazon_async_polling', $args, 'wc_amazon_async_polling' );
		}
	}

According to “wp-content/plugins/woocommerce-gateway-amazon-payments-advanced/includes/class-wc-amazon-payments-advanced-ipn-handler.php:542” it seems to me as after an event “wc_amazon_async_polling” has run, the next one is beenig scheduled in 10 Minutes?
Why does this plugin need to run a polling functionality in the first place? e.g. the Stripe and Paypal plugins don’t need that and are running code only when it’s necessary e.g. while loading the order edit page in backend or while processing scheduled payments.

The removal of the completed actions in the database should be handled by Action Scheduler itself after 30 days of their completion. Do you have completed actions older than that? In the article, there is also an example to use a filter and change the 30 days settings period.

Yes there are older completed entries for this hook. For whatever reason the automated cleanup seems to work for hooks like ‘wc-admin_import_orders’ or ‘woocommerce_scheduled_subscription_payment’ but not for the ‘wc_amazon_async_polling’ hook.

I have lowered the cleanup schedule already to 7 days.

So I guess I can also delete the ‘complete’ and ‘failed’ together with the matching log entries manually, right?

Thanks
Regards

• This reply was modified 2 years, 11 months ago by daheadcracker.

Finally with the release of Version 2.1.0 this issue got fixed by setting a transient for 3 month if the query for the ppec subscriptions returns no results. Thanks.

Hi,

I reset the status to not resolved, as it is still not resolved. Still frequently (often even without initiating an update of the plugin manually / auto updates disabled) my commented code gets overritten and the plugin decides to spam the processlist of our DB that much, that the site goes down. Here again what is beeing spammed by the site_has_ppec_subscriptions method:

SELECT 1 FROM posts p
JOIN postmeta pm ON pm.post_id = p.ID
WHERE p.post_type = 'shop_subscription'
AND p.post_status != 'trash'
AND pm.meta_key = '_payment_method'
AND pm.meta_value = 'ppec_paypal'
LIMIT 1

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