You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the "Action Scheduler - Disable Default Queue Runner" application. But "Pinterest for woocommerce" application does not work when this application is open. Unable to create feed. Pinterest works when I turn off "Action Scheduler".
I emailed Pinterest and they gave me this reply:
"Pinterest for WooCommerce" needs the Action Scheduler, so I suggest to use other plugins to Optimize the site or use Object caching "
Is it possible to add an option to not affect Pinterest with your application? All I want is for the pinterest app to work. I need the use this two plugin at the same time. Please give me a solution.
I am using the "Action Scheduler - Disable Default Queue Runner" application.
Why are you disabling the default runner? People use this to disable the default runner temporarily while they address some issue on their site. You can also use this if you set up a server cron job to run actions with WP CLI: https://actionscheduler.org/wp-cli/.
Hi there,
I am using the "Action Scheduler - Disable Default Queue Runner" application. But "Pinterest for woocommerce" application does not work when this application is open. Unable to create feed. Pinterest works when I turn off "Action Scheduler".
I emailed Pinterest and they gave me this reply:
"Pinterest for WooCommerce" needs the Action Scheduler, so I suggest to use other plugins to Optimize the site or use Object caching "
Is it possible to add an option to not affect Pinterest with your application? All I want is for the pinterest app to work. I need the use this two plugin at the same time. Please give me a solution.
When i open the "Action Scheduler";
https://prnt.sc/26k8o4n
when i close the "Action Scheduler";
https://prnt.sc/26k8k6q
I hope you answer. Thanks in advance!
Caitlyn
[email protected]
Cosmique Studio
The text was updated successfully, but these errors were encountered: