islamtamanna
Forum Replies Created
-
Hola @crammarc,
To do so you can select “Two decimal points” in the output filter. For reference: Screenshot
Let me know if it solves your issue.
Best Regards,
Hi @shanbagakumar,
It is unfortunate to hear that.
Can you please give me your feed link and screenshots of your feed attributes, feed filter, and the feed settings section here?
Let me know.
Best Regards,
Hi @kfwebmaster,
You’re most welcome!
If you’re enjoying using our plugin and liking our support, would you mind leaving us a positive feedback?
Your feedback is important to us and motivates us to improve our services.
Best Regards,
Hi @kfwebmaster,
Yes, it is possible to activate a test or sandbox mode on staging and development environments to avoid polluting your Google Shopping feed with unnecessary data.
?
For staging sites, as long as you don’t upload the feed URL to your merchant account or send the feed to Google Merchant Center using the Content API, your production Google Shopping feed won’t be affected.?For development environments, you should not use the existing feed that is already connected to your Google Merchant Center. However, you can create a new feed specifically for testing and development purposes to keep your production feed clean and accurate.
?
This way, you can ensure that your Google Shopping feed remains unaffected by your staging and development activities while you work on testing and improvements.I hope this informations clears your confusion.
Best Regards,
Hi @shanbagakumar,
If you created that product after you created the feed, it could potentially cause the issue. The reason is that your feed settings were not set to auto-update, so any newly added products might not be included in the feed until you manually regenerate it.
Now that you’ve set the feed to update daily at 11 AM, it should resolve this problem going forward.
Let me know If the issue persists.
Best Regards,
Hi @shanbagakumar,
It can be a reason that you are facing this issue because you’ve set the Auto-Generate Your Feed settings as “No Interval.” In this configuration, your feed will not update automatically, which can lead to missing products in your feed.
To resolve this issue, you might consider setting a regular interval for your feed generation, such as daily or hourly, depending on how often your product data changes. This will ensure that your feed is updated regularly without the need for manual intervention.
If the issue persists even after setting a regular interval, please let me know, and we can further investigate the problem.
Best Regards,
Hi @keksdestodes,
I’m glad to hear that you were able to solve the issue! Thank you for sharing your approach here. This will undoubtedly be helpful for anyone who might encounter a similar problem.
If you’re pleased with our help, we’d be glad if you could consider leaving a review to let others know about your experience.
Wishing you all the best with your project, and don’t hesitate to contact us if you need anything else.
Best regards,
- This reply was modified 1 year, 3 months ago by islamtamanna.
Hi @keksdestodes,
Thank you for providing the details and the URL of the page. The error message you’re encountering, “The file xxx could not be accessed,” is likely due to a CORS (Cross-Origin Resource Sharing) policy restriction.
The problem is arising because your website is trying to access an image file hosted on a different domain (“<u>https://cdn-5f7884d3c1ac190fbc5749c6.closte.com</u>“) from your own domain (“<u>https://camperstyle.de</u>“), and the server where the image is hosted hasn’t been configured to allow such cross-origin requests.
To resolve this, you’ll need to add the necessary headers to your server to enable cross-origin requests from your domain. I recommend following the instructions in the link you provided: https://biglinden.com/support/how-to-enable-cors-in-wordpress/. This guide will help you set up the required headers to allow your website to access the images hosted on a different domain without any issues.
Once you’ve implemented the CORS headers, your users, whether logged in or not, should be able to access the images without encountering the “The file xxx could not be accessed” error.
Let me know if you are able to solve the issue.
Best regards,Hi @keksdestodes,
The image the tour URL is loading from Closte CDN but in the backend it is loading from the wp-content. This could be the issue.
We are looking into this. We’ll get back to you very soon.
Best Regards,
Hi @keksdestodes,
Thank you for providing the URL. However, I’ll need the URL of the image path in your backend that you’re trying to display in your feed.
Looking forward to helping you further.
Best regards,
Hi @keksdestodes ,
Since you’ve mentioned that the issue is related to not logged-in users, it might also be helpful to try clearing your browser cache and cookies before accessing the page again. This could potentially resolve any cached data causing the issue.
To better assist you, could you kindly provide us with the specific page URL where you’re encountering this issue?
Once we have the page URL, we’ll be able to take a closer look and provide you with a more accurate solution.
Thank you for your cooperation!
Best Regards,
Hi @yakatech2021,
Thank you for getting in touch with us. I’d like to clarify that our plugin, Product Feed Manager for WooCommerce, currently does not have direct compatibility with Advanced Custom Fields (ACF). As a result, you might experience issues with ACF fields in the feed.
While our plugin supports many WooCommerce product attributes and custom fields, compatibility with specific third-party plugins like ACF might be limited.
If you have further questions or need assistance, feel free to reach out.
Best regards,
Hi @yakatech2021,
I’m glad to inform you that we have already released a fix for this issue you’re facing with the CSV Custom Feed changing back to XML after saving or updating.
Could you please give it a try, if the problem has been resolved on your end?
Let me know.
Best regards,
Hello @yakatech2021,
We are aware of the issue you mentioned. We are currently working on resolving this, and we expect to release an update to address this problem within this week.
Just to clarify, even though it may display as XML, the feed is actually being generated as a CSV, and it is stored as CSV in the backend as well.
We appreciate your understanding and patience while we work on resolving this.
Thank you for using our plugin.
Best regards,