Hi,
Thanks for using our plugin and reaching out to us.
The warning indicates that our plugin had problems updating one of your (tmp) product feeds because it could not open the feed itself. Since you mention it is filling up your errors logs this seems to be a consistent problem on your website.
I am going to assume that the file is not actually called filename_tmp.xml in your error log but has a different file name that you changed because of security reasons?
Are you running a security/permission plugin that is setting restrictions on this directory somehow: wp-content/uploads/woo-product-feed-pro/ or are you or a plugin deleting files from that directory?
Yes, thats correct. I renamed the reference file in this post.
I looked at the folder woo-product-feed-pro and it has the permissions as 755. The xml file ‘I can see filename.xml’ is there with permissions 644. But not ‘filename_tmp.xml’ is on the server.
I also noticed this similar error message:
[23-Nov-2022 07:52:36 UTC] PHP Warning: copy(/home/customer/www/mysite/public_html/wp-content/uploads/woo-product-feed-pro/xml/filename_tmp.xml): Failed to open stream: No such file or directory in /home/customer/www/mysite/public_html/wp-content/plugins/woo-product-feed-pro/classes/class-get-products.php on line 5100
Should I make a filename_tmp.xml for it to have a file that exists on the server to write to?
The filename_tmp.xml file is created by our plugin every time a feed update or creation starts. The plugin will then first create/update the filename_tmp.xml file and once it is done it will copy the filename_tmp.xml file to the final feed URL and delete the filename_tmp.xml file. This is done because you don’t want Google or Facebook fetch your final feed when it is being updated by our plugin, that could result in lots of products not making it to Google or Facebook when the feed is not done processing or updating yet.
Now for some reason when the plugin is updating the feeds at your end it cannot find or open the filename_tmp.xml file anymore. We can’t really tell why it is not there or cannot be opened, usually these kind of things do happen because of permission issues or overactive security plugins.
Usually this also results in feeds not getting updated at all. Is this also the case for you?
I will have to check with client and get back to you on that.
Only recent changes to site where plugin updates and switching to PHP8. Hosted with Siteground with cloudflare and iThemes security pro if that helps.
Ok tested and using regenerate feed is not working and hanging on 50%. What else can I be testing? The plugin had been working wonderfully for months.
I also tried creating a new feed as a test and that gave a 404 error and could not create the new feed.
Did you check the WooCommerce fatal error log of yesterday? Can you share its content with us? This is where you can find those logs: https://woocommerce.com/document/finding-php-error-logs/
Assuming the issue at hand has been resolved and our support is no longer required I will close this topic for housekeeping reasons now.
Do not hesitate to reach out to us again in-case you need our help again.
