alex2693
Forum Replies Created
-
@simowp forget about CRON. You should everything immediatelly, without queue or cron.
You did it once for the product, then you need to do the same for image importer.
Find in the same code the code which means to dispatch ($process->save()->dispatch()) and change with ($process->task()).By one word, do the same you dod for product – for image now
- This reply was modified 4 years, 6 months ago by alex2693.
@simowp @smashinghats @kimvt1991
The simplest way to fix the import – do not send the product to the queue, but post immediately.
Find the line:
$process->save()->dispatch()and replace with$process->task($product_data)It will increase the importing process by 2-3 sec, but will work.
The problem related with async queries in backend, cron, etc.
I’m not sure if it’s the best way to fix it, but I spent on it more then a week.This problem could be related with proxy based connections, external SSL tunnels (Cloudflare), etc.
@kimvt1991 are there any other cURL/queue actions in the plugin?
The issue wasn’t related with your plugin. I had a wrong configuration in my SSL apache V. host.
The server refused the connection to the 443 port, which was used to send a POST request.
After two days debugging I found how to see the error message.
1. Go here: wp-content/plugins/woo-alidropship/admin/settings.php
2. Find the line:$process->save()->dispatch()
3. Wrap into var_dump:var_dump($process->save()->dispatch());die;
4. Open: wp-content/plugins/woo-alidropship/includes/wp-async-request.php
5. Find the line and comment it:'blocking' => false,
6. Open the developers toolbar in your browser
7. Import product again and see the error message.The problem is NOT related with this plugin, but with the async tool this plugin uses.
Reference:
https://github.com/deliciousbrains/wp-background-processing/issues/24#issuecomment-412409391Hello, @simowp
Can we have a chat somewhere? I dont except the help from the author.I have the same problem in my website, so let me know how and where can we chat.