Plugin is Breaking WooCommerce Product edit and also not syncing anymore

  • Resolved gmedel

    (@gmedel)


    4 years, 4 months ago

    Hi,
    The last (or maybe second-to-last) update has caused problems with my site. I cannot edit my WooCommerce products (all my products are normal products).

    Also, the plugin is not syncing at all with my Facebook and Instagram stores.

    Checking the “Programmed Actions” in the WooCommerce “Status” page, I realized that I have a lot of failed actions, and they are all from “wc_facebook_regenerate_feed”. They all say that “the action timed out after 300 seconds”. They all started a few days ago, so I’m assuming maybe after the last update or second to last update.

    I tried deleting the product catalog from Facebook, and re-connecting the plugin, but this also didn’t work, and now my Facebook and Instagram stores are not showing because they don’t have products.

    Bottom line, something is wrong with the catalog syncing, and it times out. This didn’t happened before with my settings, so it’s not a “not enough memory” problem.

    Here is the system status, as requested:

    
### WordPress Environment ###

WordPress address (URL): https://tercerplanetacomics.cl
Site address (URL): https://tercerplanetacomics.cl
WC Version: 4.6.2
REST API Version: ? 4.6.2
WC Blocks Version: ? 3.4.0
Action Scheduler Version: ? 3.1.6
WC Admin Version: ? 1.6.3
Log Directory Writable: ?
WP Version: 5.5.3
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: –
WP Cron: ?
Language: es_ES
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 7.2.26
PHP Post Max Size: 1 GB
PHP Time Limit: 600
PHP Max Input Vars: 1000
cURL Version: 7.48.0
OpenSSL/1.0.1e

SUHOSIN Installed: –
MySQL Version: 5.6.41-84.1
Max Upload Size: 1 GB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 4.6.2
WC Database Prefix: wpke_
Tama?o total de la base de datos: 129.78MB
Tama?o de los datos de la base de datos: 105.11MB
Tama?o del índice de la base de datos: 24.67MB
wpke_woocommerce_sessions: Datos: 0.01MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_api_keys: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wpke_woocommerce_attribute_taxonomies: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_downloadable_product_permissions: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_order_items: Datos: 0.01MB + índice: 0.01MB + Motor MyISAM
wpke_woocommerce_order_itemmeta: Datos: 0.06MB + índice: 0.04MB + Motor MyISAM
wpke_woocommerce_tax_rates: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_tax_rate_locations: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_shipping_zones: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_shipping_zone_locations: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_shipping_zone_methods: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_payment_tokens: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_payment_tokenmeta: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_woocommerce_log: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_actionscheduler_actions: Datos: 1.15MB + índice: 0.26MB + Motor MyISAM
wpke_actionscheduler_claims: Datos: 0.01MB + índice: 0.04MB + Motor MyISAM
wpke_actionscheduler_groups: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wpke_actionscheduler_logs: Datos: 0.56MB + índice: 0.36MB + Motor MyISAM
wpke_aiowps_events: Datos: 1.13MB + índice: 0.16MB + Motor MyISAM
wpke_aiowps_failed_logins: Datos: 0.20MB + índice: 0.07MB + Motor MyISAM
wpke_aiowps_global_meta: Datos: 5.62MB + índice: 0.00MB + Motor MyISAM
wpke_aiowps_login_activity: Datos: 0.02MB + índice: 0.01MB + Motor MyISAM
wpke_aiowps_login_lockdown: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_aiowps_permanent_block: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_b2s_posts: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wpke_b2s_posts_drafts: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_b2s_posts_favorites: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_b2s_posts_network_details: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_b2s_posts_sched_details: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_b2s_user: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wpke_b2s_user_contact: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_b2s_user_network_settings: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_cartflows_ca_cart_abandonment: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wpke_cartflows_ca_email_history: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wpke_cartflows_ca_email_templates: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_cartflows_ca_email_templates_meta: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wpke_commentmeta: Datos: 0.13MB + índice: 0.06MB + Motor MyISAM
wpke_comments: Datos: 0.19MB + índice: 0.06MB + Motor MyISAM
wpke_ewwwio_images: Datos: 2.72MB + índice: 0.95MB + Motor MyISAM
wpke_ewwwio_queue: Datos: 0.05MB + índice: 0.04MB + Motor MyISAM
wpke_failed_jobs: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_links: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_mailchimp_carts: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_mp_country: Datos: 0.01MB + índice: 0.00MB + Motor MyISAM
wpke_mp_feature_products: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_mp_orders: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_mp_order_items: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_mp_payment_methods: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_mp_withdraws: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_ms_snippets: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_options: Datos: 6.07MB + índice: 1.22MB + Motor MyISAM
wpke_postmeta: Datos: 6.25MB + índice: 1.43MB + Motor MyISAM
wpke_posts: Datos: 11.85MB + índice: 0.40MB + Motor MyISAM
wpke_queue: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_snippets: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_social_links: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_stock_log: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_addresses: Datos: 0.02MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_countries: Datos: 0.02MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_currencies: Datos: 0.01MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_orders: Datos: 0.93MB + índice: 0.03MB + Motor MyISAM
wpke_tcp_ordersmeta: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_orders_costs: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_orders_costsmeta: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_orders_details: Datos: 0.62MB + índice: 0.07MB + Motor MyISAM
wpke_tcp_orders_detailsmeta: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_rel_entities: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_taxes: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_tcp_tax_rates: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_termmeta: Datos: 0.01MB + índice: 0.01MB + Motor MyISAM
wpke_terms: Datos: 0.05MB + índice: 0.10MB + Motor MyISAM
wpke_term_relationships: Datos: 0.19MB + índice: 0.33MB + Motor MyISAM
wpke_term_taxonomy: Datos: 0.06MB + índice: 0.06MB + Motor MyISAM
wpke_toe_content_img: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_toe_img_status: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_toe_log: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_toe_options_categories: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_toe_product_files_types: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_toe_rating: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_usermeta: Datos: 0.42MB + índice: 0.25MB + Motor MyISAM
wpke_users: Datos: 0.05MB + índice: 0.05MB + Motor MyISAM
wpke_wc_admin_notes: Datos: 0.01MB + índice: 0.00MB + Motor MyISAM
wpke_wc_admin_note_actions: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wc_category_lookup: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wc_customer_lookup: Datos: 0.03MB + índice: 0.03MB + Motor MyISAM
wpke_wc_download_log: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wc_order_coupon_lookup: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wc_order_product_lookup: Datos: 0.01MB + índice: 0.01MB + Motor MyISAM
wpke_wc_order_stats: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wpke_wc_order_tax_lookup: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wc_product_meta_lookup: Datos: 0.01MB + índice: 0.03MB + Motor MyISAM
wpke_wc_reserved_stock: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wc_tax_rate_classes: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wpke_wc_webhooks: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_webpay: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wfblockediplog: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wfblocks7: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wpke_wfconfig: Datos: 4.39MB + índice: 0.01MB + Motor MyISAM
wpke_wfcrawlers: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wffilechanges: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_wffilemods: Datos: 2.89MB + índice: 0.56MB + Motor MyISAM
wpke_wfhits: Datos: 0.05MB + índice: 0.01MB + Motor MyISAM
wpke_wfhoover: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wfissues: Datos: 0.01MB + índice: 0.01MB + Motor MyISAM
wpke_wfknownfilelist: Datos: 1.56MB + índice: 0.18MB + Motor MyISAM
wpke_wflivetraffichuman: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wpke_wflocs: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wflogins: Datos: 0.15MB + índice: 0.04MB + Motor MyISAM
wpke_wfls_2fa_secrets: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wpke_wfls_settings: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_wfnotifications: Datos: 0.02MB + índice: 0.00MB + Motor MyISAM
wpke_wfpendingissues: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wfreversecache: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wfsnipcache: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wfstatus: Datos: 0.21MB + índice: 0.08MB + Motor MyISAM
wpke_wftrafficrates: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_wls_entries: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wls_logs: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wpmailsmtp_tasks_meta: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_wp_rp_tags: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_wsal_metadata: Datos: 50.85MB + índice: 13.25MB + Motor MyISAM
wpke_wsal_occurrences: Datos: 4.47MB + índice: 3.88MB + Motor MyISAM
wpke_wsal_options: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wpke_yoast_indexable: Datos: 1.65MB + índice: 0.28MB + Motor MyISAM
wpke_yoast_indexable_hierarchy: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wpke_yoast_migrations: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wpke_yoast_primary_term: Datos: 0.01MB + índice: 0.02MB + Motor MyISAM
wpke_yoast_seo_links: Datos: 0.08MB + índice: 0.02MB + Motor MyISAM
wpke_yoast_seo_meta: Datos: 0.01MB + índice: 0.02MB + Motor MyISAM

### Post Type Counts ###

attachment: 1673
custom_css: 4
et_body_layout: 4
et_pb_layout: 2
et_template: 5
et_theme_builder: 1
fa_slider: 1
feedback: 281
jetpack_migration: 2
jp_img_sitemap: 2
jp_sitemap: 2
jp_sitemap_master: 2
nav_menu_item: 112
oembed_cache: 2
options: 1
page: 13
post: 31
product: 229
revision: 1290
safecss: 1
shop_coupon: 3
shop_order: 54
shop_order_refund: 1
slidedeck2: 1
tcp_product: 954
wpmarketplace: 1

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?

### Active Plugins (40) ###

SSL Zen - Free SSL Certificate & HTTPS Redirect for WordPress: por SSL Zen – 3.0.9
Akismet Anti-Spam: por Automattic – 4.1.7
All-in-One WP Migration: por ServMask – 7.29
All In One WP Security: por Tips and Tricks HQ
Peter Petreski
Ruhul
Ivy – 4.4.4

AntiVirus: por pluginkollektiv – 1.3.10
Better Search Replace: por Delicious Brains – 1.3.3
Blog2Social: Social Media Auto Post & Scheduler: por Blog2Social
Adenion – 6.5.4

Classic Editor: por WordPress Contributors – 1.6
Code Snippets: por Code Snippets Pro – 2.14.0
Coming soon and Maintenance mode WpDevArt: por wpdevart – 3.2.0
Divi 100 Article Cards: por Elegant Themes – 0.0.3
Divi Booster: por Dan Mossop – 3.3.4
EWWW Image Optimizer: por Exactly WWW – 5.8.1
Facebook for WooCommerce: por Facebook – 2.1.4
Site Kit by Google: por Google – 1.20.0
Hide WooCommerce Categories On Shop Page: por Matix Web Designers – 1.1.0 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
Jetpack by WordPress.com: por Automattic – 9.0.2
Kadence WooCommerce Email Designer: por Kadence WP – 1.4.3 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
Official Facebook Pixel: por Facebook – 2.2.1
QuadMenu - Divi Mega Menu: por QuadMenu – 1.2.0
QuadMenu: por Mega Menu – 2.0.4
Regiones de Chile para WooCommerce: por melvisnap  – 0.4 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
SVG Segura: por Daryll Doyle – 1.9.9
WC Password Strength Settings: por Daniel Santoro – 2.2.1 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
wePOS - Point Of Sale (POS) for WooCommerce: por weDevs – 1.1.2
WooCommerce Cart Abandonment Recovery: por CartFlows Inc – 1.2.8 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
Checkout Field Editor for WooCommerce: por ThemeHigh – 1.4.4 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
WooCommerce Admin: por WooCommerce – 1.6.3 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
WooCommerce khipu: por khipu – 2.7.0 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
WooCommerce khipumanual: por khipu – 2.7.0 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
WooCommerce khipupayme: por khipu – 2.7.0 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
WooCommerce khipuwebpay: por khipu – 2.7.0 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
WooCommerce POS: por kilbot – 0.4.24 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2
WooCommerce Stock Manager: por StoreApps – 2.5.2
WooCommerce: por Automattic – 4.6.2
Wordfence Security: por Wordfence – 7.4.12
Yoast SEO: por Equipo Yoast – 15.2.1
WP Mail SMTP: por WPForms – 2.5.1
WP Activity Log: por WP White Security – 4.1.5
YITH Pre-Order for WooCommerce: por YITH – 1.2.12

### Inactive Plugins (2) ###

Google Analytics Dashboard for WP (GADWP): por ExactMetrics – 6.3.0
WooCommerce Deposits: por Webtomizer – 2.3.7 – Versión instalada no está probada con la versión activa de WooCommerce 4.6.2

### Settings ###

API Enabled: ?
Force SSL: –
Currency: CLP ($)
Currency Position: left
Thousand Separator: .
Decimal Separator: ,
Number of Decimals: 0
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: ?

### WC Pages ###

Base de la tienda: #4301 - /tienda/
Carrito: #4302 - /carrito/
Finalizar compra: #4303 - /finalizar-compra/
Mi cuenta: #4304 - /mi-cuenta/
Términos y condiciones: ? Página sin definir

### Theme ###

Name: Divi
Version: 4.6.6
Author URL: https://www.elegantthemes.com
Child Theme: ? – Si estás modificando WooCommerce en un tema padre que no has creado personalmente
te recomendamos utilizar un tema hijo. Ver: Cómo crear un tema hijo

WooCommerce Support: ?

### Templates ###

Overrides: –

### Action Scheduler ###

Completo: 2.357
Oldest: 2020-10-29 20:42:43 -0300
Newest: 2020-11-09 17:40:49 -0300

Fallida: 754
Oldest: 2020-11-06 03:19:54 -0300
Newest: 2020-11-09 20:11:59 -0300

En curso: 1
Oldest: –
Newest: –

Pendiente: 1
Oldest: 2020-11-16 16:48:10 -0300
Newest: 2020-11-16 16:48:10 -0300

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

Viewing 15 replies - 1 through 15 (of 19 total)

  • Hey @gmedel ,

    Thanks for reaching out to us. I’m sorry to hear you’ve encountered this issue! Happy to further investigate this with you!

    As a first step, I’m going to need a bit more information about the number of products you currently have. Do you encounter a specific error when trying to edit a product? Does the same issue persist if Facebook for WooCommerce is disabled temporarily?

    Lastly, you’ve mentioned that you tried re-connecting the plugin. Does that mean you disabled and re-enabled it? Or did you use the “Uninstall” button in the WooCommerce > Facebook > Connection page?

    Looking forward to your response.

    Best regards,
    Pit

    Thread Starter gmedel

    (@gmedel)

    Hi @pitbozionelos!

    Thanks for writing back.

    – I currently have 199 posted products on my site.
    – The error that appears when trying to edit any product is a server error 500.
    – When the plugin is disabled the error does not persist and I can edit products.
    – I’ve tried re-connecting by:
    – Using the “uninstall” button and following the process to connect again. No problem with the connection, it just didn’t sync up.
    – Then I completely deleted the Facebook catalog, and then again tried with the “uninstall” button, to see if the catalog would re-generate instead of just updating. It did not. I now don’t have anything on my Facebook, as it doesn’t sync up or re-generate the catalog.
    – Disabling and enabling the plugin doesn’t work either. It just allows me to edit products by having the plugin disabled.

    Also, checking out the WooCommerce -> Status -> Registers section, every day there’s a new “fatal error” register (that started with the plugin updates, and stops when the plugin is disabled). The register has a lot of these:

    2020-11-11T00:01:40+00:00 CRITICAL Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) en /home/tercerplanetacom/public_html/wp-includes/wp-db.php en la línea 1999

    Also, there’s already 1062 failed “programmed actions”, all the same: “wc_facebook_regenerate_feed”, which is being timed out after 300 seconds.

    I know this is not a problem with my site, as the plugin was working ok a few weeks ago, and we have made no other changes.

    Hope you can help out!

    Cheers!

    Hey @gmedel ,

    Thanks so much for sharing more information with me. I’m really sorry to hear that the latest update of our plugin has started causing these issues.

    The critical errors about the allocated memory could be affecting the sync process for the products to the Facebook Shop. Could you let me know if you’ve tried raising the memory limit of your site to a larger enemy to check if this is affecting the edit process?

    Also, the Facebook for WooCommerce plugin will try to sync a product to your Facebook Shop when making a change to a product and trying to update. So, if the syncing process doesn’t proceed as expected, it could interrupt the editing of the product.

    Would it be possible to make adjustments to your site’s memory limit and check if the performance is improved?

    Looking forward to your response.

    Best regards,
    Pit

    Thread Starter gmedel

    (@gmedel)

    Hi, for the moment, I’m not able to up the memory limit, as it is set by the hosting provider, and not by me.

    But, I would have thought that the memory limit of 256 mb shouldn’t be an issue, if the plugin worked ok before.

    I will try to get in contact with the hosting provider and see if something can be done about this.

    I don’t know how the plugin works, but I’m thinking that something maybe went wrong with the plugin update, as I’ve seen in the forum than I’m not the only one with this issue.

    Hey @gmedel ,

    Thanks for your response and providing me with more information regarding this case.

    Taking a step back regarding this case, this error seems to be caused by the generation of the product feed. This sometimes can be caused when the number of products is large. You did mention that your products are “normal” in one of your previous responses — does that mean that these are simple or variable products?

    Also, I’d be happy to guide you into disabling the feed generation for the plugin in order to work around this issue at the time being. Is this something that would interest you?

    Looking forward to your response.

    Best regards,
    Pit

    Thread Starter gmedel

    (@gmedel)

    Hi @pitbozionelos,

    All my products are simple. I have 199 products at the moment.

    I’m not sure what do you mean by “disabling the feed generation”. If I disable the plugin, or if I disconnect it from my Facebook account (via the uninstall button), the feed generation stops and I can edit my products.

    I don’t need that. I need that the plugin works again syncing my products up to my Facebook and Instagram stores, which are currently empty (with no products, as I deleted them, trying to fix the issue).

    I don’t know what I could do in order to fix this on my end.

    Best regards,
    Gonzalo.

    Hey Gonzalo ( @gmedel ),

    Thanks for your response and apologies for any confusion my previous message has caused. Let me provide you with a bit more information in order to better clarify this process.

    In the latest update of our plugin, there’s less of an importance to the feed file, as there have been some improvements in the last few versions that add additional product syncing via the API. Previously, the stock status would only be updated if a product was updated via an admin, or a manual sync performed. When a customer bought a product on your WooCommerce store, and if it then became out of stock, this would be caught by the feed file generation and sync instead. Now with our latest version, once the product has its stock changed, this will also trigger a sync via the API now too.

    There is still one useful case for the feed file generation, and that’s for when the catalog is edited manually, or for some other reason, gets out of sync with the WooCommerce store. As the sync is only one way, from the plugin to your catalog, any changes made by other third-party plugins or manual edits, are not synced back to your WooCommerce store. This can leave you with a bit of a mismatch in multiple ways depending on the actions performed. The feed file sync should be setup as a “replacement” update. What this means is that when the feed file is synced, any products not included in the feed file will be removed from your Facebook catalog. Essentially, it’s a bit like a reset, telling Facebook, this is the complete catalog and how it looks right now.

    That said, this of course only works if the feed file is able to be generated! So if it’s failing intermittently, like what seems to be happening in your case, then perhaps setting the interval to 24 hours and having it generate in quiet periods might be one option to keep this. Otherwise, we can remove it and rely solely on the API sync instead, which as I say, should be good enough with the most recent versions.

    Would you please let me know if this is something that you’d be willing to try to test if you can continue using our plugin with your site? I’m happy to provide you with more instructions on how to proceed.

    Looking forward to your response.

    Best regards,
    Pit

    Thread Starter gmedel

    (@gmedel)

    Hi @pitbozionelos

    I’m ok with testing anything you want in order to correct the issue. A few points though:

    1) The regeneration of the feed file is failing always. Not intermittently. If it would be failing intermittently, my facebook catalog would have products, but as I deleted it manually via Facebook, now it doesn’t have anything, and it has not been regenerated.

    2) I need to regenerate the catalog. I don’t know if the way you want to test will do it or not.

    3) What I want, is that my catalog is synced from the website to facebook. It will never be modified via facebook, as I have configured that the sales should be done directly in the website, so all changes in products (like descriptions or stock or sales) will come from the website.

    If the way you propose will help, let’s do it. But, will this change be erased if the plugin updates in the future?

    Best regards,
    Gonzalo Medel.

    Hey Gonzalo ( @gmedel ),

    Thanks so much for your detailed response and my apologies for my delayed reply.

    I’d like to consult with our team a bit more to ensure that disabling the product feed generation is the best step while moving forward. As previously mentioned, the catalog should continue being updated via a different method, but as your shop doesn’t have any connected catalogs connected, this could be a different issue that I’d like to further investigate.

    I’ll make sure to reach out to you as soon as possible with more information. In the meantime, don’t hesitate to reply here if there’s any more information you’d like to share.

    Best regards,
    Pit

    Hey Gonzalo ( @gmedel ),

    Thanks you very much for your patience while taking a closer look on this case on the back-end. I’d like to share a bit more information with you to ensure we’re making the best step moving forward.

    In one of your previous messages, you’ve mentioned that using the “Uninstall” button and then reconnecting the plugin to Facebook didn’t regenerate the catalog. That may be because one of the steps during the setup process is asking you to either use a catalog that you’ve already created or create a new one. Could you let me know if during that process, you used another catalog or tried to create a new one through our plugin?

    I’m asking the above since our plugin will need to connect to a catalog in order for the product feed to start generating and syncing the products. It’s possible that your products not being able to be edited and the catalog being deleted aren’t connected and may be two separate issues. However, I’d like to first confirm again that the catalog has been successfully created and connected to your site during the setup process.

    If you’d like to double-check if that’s the case, you can also try to navigate to the WooCommerce > Facebook > Connection page and then try the “Uninstall” button again. When you go through the setup process again, make sure that during this step, you click on the “Catalog” field and then either click on the “Create new” option or use a catalog that already has been created.

    Once again, this may not be connected to the regeneration feed issue, but as previously discussed, there are two ways to sync your products to your Facebook shop, and if the above doesn’t solve the issue, we can try disabling the product feed generation process and see if that works better for your site.

    Would you please let me know if uninstalling the connection and installing again by following the instructions above has changed the status of the products on your end?

    Looking forward to your response.

    Best regards,
    Pit

    Thread Starter gmedel

    (@gmedel)

    Hi @pitbozionelos,

    Today I tried what you asked for, I checked and the connection seemed to be ok, with a connected catalog, same one from Facebook.

    Even so, I tried to do it again. I uninstalled the connection (via the button), and then I started again.

    I clicked on the plugin button to start the configuration, and instead of using the same catalog, I created a new one. The plugin seemed to connect everything ok, but when it comes to syncing up the products, same thing. No products appeared on the new catalog (it says that it’s syncing but nothing else happens). The same errors are in the WooCommerce status registers (memory and time).

    I then tried again, connecting the plugin with the original catalog. Same thing. Same errors.

    I suppose it’s time to try the other way that you propose.

    Hope it helps!

    Best regards,
    Gonzalo.

    Hey Gonzalo ( @gmedel ),

    Thanks a lot for your response and going through the process again. Moving forward, I’ll share two methods you can follow as I’ve been taking some time working on this case on the back-end with some of my colleagues.

    It seems that a few other customers have encountered the same error with their products not being able to be updated due to memory limit being too low. As previously mentioned, in this case, there may be two different cases causing two issues, so I’d recommend first following the first option and then if needed the second. The reason for that is because the first method is less complicated and doesn’t change the functionality of the plugin per se.

    Method 1
    You’ll need to reach out to your hosting provider to raise the limit of your site from 256mb to 512mb. It seems that this method has worked for other merchants. You’ve mentioned in one of your previous messages that you were going to contact your hosting service about raising the memory limit. Would it be possible to let me know if you’ve been able to proceed with this request? If not, could you reach out to them and ask them to raise the memory limit to 512mb and let me know if this works?

    Method 2
    You can use the following custom code snippet a try to remove the current and all future actions for the feed file generation: https://gist.github.com/simonporter007/410a1f2787fed34e7d4f1b9430993526

    However, please be aware of a couple notes:

    • I’m afraid that customizations are not covered under our support policy, so implementing this directly or modifying it further isn’t something we can assist with.
    • Please be sure you know how to add custom code to your site. Personally, I like the free Code Snippets plugin method.

      • I would also recommend removing the schedule, if it exists, from your Facebook data feed so that there are no errors if it tries to retrieve a file that is no longer generated. You can do this by logging into Commerce Manager and then navigating to Catalog > Data Sources > select the WooCommerce data feed > Settings and using the three dot menu to delete any existing replacement schedule.

      https://cloud.skyver.ge/nOuDgZW5

      Could you please let me know if any (or both) of the methods above were able to help you with this issue? If not, I’ll make sure to ask one of our engineers to take another look in case I’ve missed anything.

      Looking forward to your response.

      Best regards,
      Pit

    Thread Starter gmedel

    (@gmedel)

    Hi @pitbozionelos!

    I’m happy to inform you that today I was finally able to get help from my hosting provider, and they have increased my memory limit to 512 mb, just like you suggested, and the problem was finally fixed!

    Now the catalog has been synced correctly and both my Facebook and Instagram stores have reappeared.

    Everything appear to be working perfectly, except for one little detail:

    Before, I had a few collections of products, selected automatically by category. This was made via the Facebook catalog, using the categories that were synced up in each product by the plugin.

    Now, the categories for each product are not synced correctly. Instead, every product has a number in the category field. All products with the same number “543543”.

    I bypassed this problem for now, as I was able to recreate the collections, selecting by product name that “contains” a key phrase.

    Was this “category” field changed by any chance in the latest updates of the plugin?

    Best regards,
    Gonzalo.

    Hey Gonzalo ( @gmedel ),

    I’m really happy to hear that raising the memory to 512mb seemed to do the trick! ?? Glad I was able to assist you with that.

    Regarding the new issue you’ve encountered, there are some new options that have been added in terms of category syncing through our plugin. In order to further investigate, would it be possible to navigate to one of the affected products and share a screenshot with me of the “Facebook” tab?

    You can use a service like Imgur or Snipboard to share a link of the screenshot with me.

    Looking forward to your response.

    Best regards,
    Pit

    Thread Starter gmedel

    (@gmedel)

    Hi Pit! (@pitbozionelos)

    All of my products have the Facebook tab with it’s default settings.

    As an example, I share here a screetshot of the Facebook tab for a specific product, a comicbook “Man Of Steel #6” (it’s all in spanish, but I suppose you’ll get that it’s all default):
    https://snipboard.io/y7ONGz.jpg

    You can look at the product categories and see that it has a few assigned:
    https://snipboard.io/s9elAN.jpg

    Also, if you look at the same product in the Facebook catalog, inspecting the product and clicking on the “show more fields” button, you can see that the category shown in facebook it’s a number:
    https://snipboard.io/JYpGzo.jpg

    I’m guessing that something is wrong. With the default settings, I assume that the synced product should have at least it’s principal category (it was like that, a couple of updates back).

    Maybe the plugin it’s syncing the category ID number instead of it’s name?

    Best regards,

    Gonzalo.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Plugin is Breaking WooCommerce Product edit and also not syncing anymore’ is closed to new replies.