Invalid Argument Error
-
Hi guys, when creating a new feed, we get the following error:
Warning: fputcsv(): delimiter must be a character in /home/clients/edb42069f8/sites/DOMAINNAME.COM/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php on line 2063
The feed then never refreshes nor our other existing ones.
-
Hi,
Thanks for using our plugin and reaching out to us.
Looks like you are trying to create a CSV feed but did not choose a delimiter for it?
I am simply trying to create a new feed that’s all. Once it saves, i beg a ton of error lines showing that. Also for some reason our original feed, that was there for months is not refreshing anymore.
We migrated to a new server and after that, nothing refreshes…
Would a premium subscription allow you guys to fix it?
We migrated to a new server and after that, nothing refreshes…
–> Changes are big that that actually caused the problem at hand. As there are lots of things that could go wrong during such a migration it would be hard to determine where things have gone wrong. I suspect the best option you might have is to start from scratch by completely re-installing the plugin and start all feeds from scratch too.
Yes but when creating a new feed and saving it, we initially get that error. Then when clicking on refresh it is always stuck at 0. I tried all sorts of things with cron related but same thing. If we go on elite would your support team be able to fix it for us?
Did you do a clean install of the plugin already?
Upgrading to our paid version won’t make any difference. Unfortunately, per the WordPress forum guidelines, we’re not allowed to discuss our paid Elite plugin here so for any questions about our paid plugins, please contact our support team directly when you would like to discuss the paid version of our plugin.
I tried to uninstall it yes, and same thing. I noticed that if we uninstall and install again, all our feeds remain there so they are not delete. Is there a way to uninstall and remove all DB and other settings as well so we can build the feeds fresh?
I create a new feed and get this error:
Fatal error: Maximum execution time of 60 seconds exceeded in /home/clients/IDHERE/sites/DOMAIN.COM/wp-includes/class-wp-post.php on line 254
Updated: Just changed max execution time to 300 secs. The new feed created is stuck at processing 0%… I checked various cron related posts, etc. but doesn’t seem to fix anything. We are running php 7.4 i could push it to 8 but not sure if that helps. We cannot get our feeds refreshed…
Should I share with you the logs?
-
This reply was modified 4 years, 7 months ago by
antanast.
Update: Now our feed refresh is stuck at 31% instead of 0%.
Did you already check the WooCommerce fatal error logs of today? This is where you can find them: https://docs.woocommerce.com/document/finding-php-error-logs/
Yes, I see lots of CRITICAL Maximum execution time of 60 seconds exceeded but none for the plugin. I increased the time on the server plus now on the wp-config.
The critical errors can come from other plugins as well when our runs and needs those plugins (like discount or shipping plugins). You can test this by deleting today’s fatal error log and then manually kick of a feed. If within a few minutes after the fatal error log is back than you know it is initiated by the refreshing of a feed.
Actually those errors were from several days ago. The latest update is that the feed update is stuck to about 38% for more than 12 hours now.
And you are no longer seeing the ones you reported earlier? This one:
Warning: fputcsv(): delimiter must be a character in /home/clients/edb42069f8/sites/DOMAINNAME.COM/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php on line 2063
Can you stop the processing of the feed. Delete today’s fatal error log and than manually restart a feed again and when it gets stuck share the complete content of todays fatal error log with us?
Still stuck, now at about 25. No fatal errors recorded for today’s date…
Question: Our server runs memcached, does that play a role?What’s next?
-
This reply was modified 4 years, 7 months ago by
The topic ‘Invalid Argument Error’ is closed to new replies.