• Resolved wpguillaume

    (@wpguillaume)


    Hello,

    First of all, thank you for this very useful plugin. Having a free version for small shops is very nice.

    I set up a Facebook feed on both WP and Facebook ends, which works fine if I manually update the feed. But if I modify a product and do nothing else, the change won’t appear on Facebook.

    Feed is set up to update hourly.

    Here is my debug.log file: https://fichiers.ouvaton.coop/f.php?h=0JFncO8A&p=1

    Feed URL is linked to this post.

    If I read the debug.log file correctly, it seems the automatic update has never worked.

    WooCommerce test-log.log is empty. Planified tasks show other tasks that seem to have performed fine, does that mean wp-cron is enabled? I can’t see anything cron-related in my wp-config.p?p file.

    Thank you for any pointers, please ask if I can give you more information.

    The page I need help with: [log in to see the link]

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

    Thanks for using our plugin and reaching out to us.

    When your WP-cron is disabled there should be a notification on top of our manage feeds page saying that the WP-cron has been disabled and that our plugin needs it to function properly.

    Is there such a notification?

    Thread Starter wpguillaume

    (@wpguillaume)

    Hello,

    There isn’t any notification on this page.

    Also, I seem to remember I read somewhere on these boards that manual refresh also needed WP-Cron. Is that so? Because manual refresh does work, I see the effects of modifying, say, a product’s description, on the Facebook catalogue.

    Thank you.

    Hi,

    That depends, when there are over 750 products in your website than indeed the WP-cron is also needed for manual refreshes of your feed. Since however your manual refreshes do work I suspect you have less than 750 products.

    Did you install a WP-cron plugin? If so, can you tell what cron events you are seeing that start with “woosea”?

    Thread Starter wpguillaume

    (@wpguillaume)

    Indeed, we have less than a hundred products.

    WP-Crontrol finds one woosea_cron_hook event, with no arguments, set to run hourly, with woosea_create_all_feeds() action.

    I modified a product, then clicked on “Run now” for this event. It gets added on top of the queue, set at 1st January 1970, then a few seconds later a notification tells me events queue has changed. On reload, the event is gone, looking like is has run. But the XML feed hasn’t changed. If I then refresh it manually, the XML feed indeed changes.

    Though, I also notice two notifications on clicking “Run now”. One says the event has been set to run now, not altering the previous schedule which remains unchanged. The other notification says that one or several events have missed their schedule, without further precisions.

    I tried disabling All-In-One WP Security plugin for these tests, but it wasn’t the culprit.

    Thank you.

    Hi,

    I don’t think it should be doing this “set at 1st January 1970” to be honest. When you hit the “run now” link it should start executing the cron event immediately. That combined with the notification that one or several events have missed their schedule makes me believe the cron event did not get executed at all for some reason.

    Since you mention that the plugin does update fine when you do a manual update makes me believe there is something off/wrong with your WP-cron.

    Can you try disabling and re-enabling our plugin (do not delete it) as that will reset all cron events needed by our plugin. Maybe that solves the issue at hand.

    Thread Starter wpguillaume

    (@wpguillaume)

    Hi,

    According to the first answer of this post https://www.ads-software.com/support/topic/run-now-button-duplicate-job-with-01-01-1970-date/, the 1970 date setting is the way WordPress ensures the next event in the queue is the one you clicked on “Run now”.

    Disabling and re-enabling your plugin didn’t solve the issue.

    I’ll be asking my web host, see if it could be something on their end.

    Thread Starter wpguillaume

    (@wpguillaume)

    Hi @supportadtribes,

    I asked my webhost to run a cron task on their end and to disable WP-Cron, but it doesn’t look like it solved the issue, the feed still doesn’t upload automatically. (It’s only after that, that I read you don’t recommend disabling WP-Cron. I wondered because it’s a slow traffic website that maybe the cron tasks weren’t updated often enough. It is now set to a five minutes interval, and as mentioned earlier, there are less than a hundred products. Please tell me if this is indeed bad practice.)

    WooCommerce’s test-log.log is empty, but I searched /logs/error_log through FTP and it’s filled with woosea-related errors, such as (from oldest to latest):

    [Wed Jun 22 21:18:38.633686 2022] [proxy_fcgi:error] [pid 21092:tid 139761649968896] [client 10.0.20.15:45042] AH01071: Got error 'PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre

    [Sat Apr 22 13:49:42.220434 2023] [proxy_fcgi:error] [pid 20185:tid 140141776172800] [client 10.0.20.16:47180] AH01071: Got error 'ect_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: id was called incorrectly. Les propri\xc3\xa9t\xc3\xa9s du produit ne doivent pas \xc3\xaatre accessible directement. Backtrace: do_action('wp_ajax_woosea_project_refresh'), WP_Hook->do_action, WP_Hook->apply_filters, woosea_project_refresh, woosea_continue_batch, WooSEA_Get_Products->woosea_get_products, do_shortcode, preg_replace_callback, do_shortcode_tag, cm_insert_page_content, apply_filters('the_content'), WP_Hook->apply_filters, cm_filter_description, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.', referer: https://creamaga.com/wp-admin/admin.php?page=woosea_manage_feed

    Do you see what is wrong here?

    Thank you very much!

    Thread Starter wpguillaume

    (@wpguillaume)

    Hi @supportadtribes,

    Did you have a chance to take a look at my previous questions and log error quotes?

    Thank you very much.

    The error logs you shared are not entirely clear to use but it seems to be referring to some legacy plugins installed. Did you make sure to be on the latest version of WooCommerce and WordPress?

    Thread Starter wpguillaume

    (@wpguillaume)

    Hi @supportadtribes,

    I’m currently on WooCommerce 7.7.2 and WordPress 6.2.2, with your plugin on 12.6.7. There hasn’t been any new woosea-related errors since the once from 22 April 2023 that I pasted in my previous post.

    Is there any debug mode that I can enable, to check whether the cron tasks are indeed called? Or some code I could temporarily insert to do the same checks?

    I can go back to using wp-cron instead of the cron task ran every 5 minutes by my webhost. The rest of the website seems to work fine (basket, payments, mailings, etc.) in both cases. But I just noticed that I reported here on April 22 about disabling wp-cron, and it’s also the last time an error was logged, as I mentioned above.

    Meanwhile, I have to manually refresh my Facebook feed. Is there a way to allow access to this button in “Manage feeds” for shop owners? For now it seems you have to be an admin to access the “Manage feeds”page.

    Thank you very much for the support you provide.

    Hi,

    Can you check your cron events and list the ones that start with “woosea_”?

    Thread Starter wpguillaume

    (@wpguillaume)

    Hi @supportadtribes,

    WP-Crontrol finds two woosea_cron_hook event, with no arguments, set to run hourly, with woosea_create_all_feeds() action.

    Thank you.

    Thanks for this, there should be only one but two should not be causing issues.

    I tried opening your debug.log URL again but it no longer seems to work? Can you share a new debug.log URL with us? This is how you can create/retrieve it: https://adtribes.io/send-your-debug-log-to-support/

    Thread Starter wpguillaume

    (@wpguillaume)

    Hi @supportadtribes,

    Here is an up-to-date debug.log file: https://fichiers.ouvaton.coop/f.php?h=04TkvcBE&d=1

    Thank you.

    According to the debug log you have this option enabled: https://www.dropbox.com/s/srnic5rkayoe9ju/Screenshot%202023-06-13%20at%2008.34.53.png?dl=0

    Can you disable it? That should make your feed update on the set refresh intervals again.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Facebook feed updating *only* manually’ is closed to new replies.