• Resolved webhk

    (@webhk)


    Hello

    We have changed field mapping. Although changes was made, after refresh in feed we have still old data. The same when we fetch in google merchant. What can be the reason and how to improve it?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hi,

    You are probably looking at an old cached version of your product feed. Make sure to clear the cache of your browser, server and caching plugins. You can also force your browser to retrieve an uncached version of your feed by adding a parameter to the feed URL, for example:

    ../woo-product-feed-pro/xml/lQRGDOP7eofNdyfi0SdKJsd0VZm7otdw.xml?webhk=123

    See the webhk=123 part. Make sure to randomly change the number every time you want to make sure you are looking at the most recent updated version of your feed.

    [ Signature deleted ]

    • This reply was modified 4 years, 8 months ago by Jan Dembowski.
    Thread Starter webhk

    (@webhk)

    I changed the end but still i see or version – I added ?webhk=123 on the end.

    I wonder if Cloudflare make problems because as i know it keeps also cache. Can i be right?

    Thread Starter webhk

    (@webhk)

    I have flushed cache on the server and Cloudflare, I also use this parameter on the end bu still feed keep old data.

    Hi,

    Cloudflare definitly caused caching problems with users before (search the forums for it). Unfortunately we are no Cloudflare experts so we don’t know if there are any settings in it that you can change to prevent this from happening.

    Easiest to find out if Cloudflare is causing the issue at hand is to just disable the plugin, try updating the product feed and see if the update worked. If it did then you know its being caused by Cloudflare.

    Alternatively you could also look at the WooCommerce fatal error logs of today to see if there is anything in the logs (such as timeouts or memory usage warnings) that could be causing this (https://docs.woocommerce.com/document/finding-php-error-logs/).

    [ Signature deleted ]

    • This reply was modified 4 years, 8 months ago by Jan Dembowski.
    Thread Starter webhk

    (@webhk)

    I flushed cache on Cloudflare, my server SiteGround and make changes in one product price but in feed is same.. I will wait tomorrow and try also. Can i also send to you a debug file?

    Regards

    Did you also check your WooCommerce fatal error logs to see if there was anything in there that could give us a clue as to what is happening (timeouts, memory usage issue, and so on).

    Sure you can also copy/paste the debug.log here so we can check. However most likely the configuration of your feed itself (which is the only thing the debug logs shops) is not the cause of this.

    [ Signature deleted ]

    • This reply was modified 4 years, 8 months ago by Jan Dembowski.
    Thread Starter webhk

    (@webhk)

    Hello,

    I have found some errors

    2020-03-11T19:00:43+00:00 CRITICAL Maximum execution time of 30 seconds exceeded in /home/xxxx/public_html/xxxx.ph/wp-content/plugins/site-reviews/plugin/Helpers/Str.php on line 162

    2020-03-11T19:14:22+00:00 CRITICAL Maximum execution time of 30 seconds exceeded in /home/xxxx/public_html/xxxx.ph/wp-content/plugins/site-reviews/plugin/Defaults/DefaultsAbstract.php on line 0

    I hide some private information using xxxx instead of some data

    What it means? Could I send you debug also to email? we have full version.

    Thread Starter webhk

    (@webhk)

    I even cannot generate the new feed because i got this error:

    Fatal error: Maximum execution time of 30 seconds exceeded in ….

    this was during new feed generation

    Thread Starter webhk

    (@webhk)

    Sorry.. I found solution.. I asked server admin for extend an execution time on SiteGround and after that is working ?? I just need to add parameter on the end as you said ?web=xx223 or other and new version appears.

    Thanks for help!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Although I made changes in feed it still generating old’ is closed to new replies.