bilzone
Forum Replies Created
-
Hello,
I encountered the same problem. After version 3.4.6 the Purchase event is no longer triggered. I even tried on a new version of wordpress/woocommerce + default Storefront theme but without any results. Initially I thought it was something I was doing wrong but it seems there are others as well. Do you have any idea when it will be resolved?
Thank you
Forum: Plugins
In reply to: [TikTok] Pixel without eventsI also activated Enable Advanced Matching within the plugin but still did not display any events.
I read somewhere that this plugin is not a browser based event pixel so it will not show up if I’m using the TikTok Pixel Helper but shouldn’t it show me something in Test Events? How do I know if it works or not?Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelIn the meantime I solved it.
The solution is the following:
– in the theme files, in hedear.php, before the < / body> the following code must be inserted:<?php
do_action( ‘woocommerce_after_single_product’ );
?>In the meantime I solved it.
I had already tried everything you wrote above but without any result.The solution is the following:
– in the theme files, in hedear.php, before the < / body> the following code must be inserted:<?php
do_action( ‘woocommerce_after_single_product’ );
?>Thanks for the answer
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelI resolved those errors but the ViewContent event still doesn’t fire when I select the Elementor Full Width template.
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelAs I said in the last update, the problem is with the Elementor Full Width template.
If I change to the Default Template or Template template, it loads, so the problem is definitely with the template. The problem is that the entire site is built around that template and it’s almost impossible for me to change all.
All tests are done with cache disabled.
In the console I have the following errors:
- Scroll util from “/dev/js/frontend/utils/scroll”
is hard deprecated since 3.1.0 - UseelementorModules.utils.Scroll` [email protected]?ver=3.27.1:2</li> </ol> <p>2. elementorCommon.helpers.softDeprecated()<code>is hard deprecated since 3.7.0 – Use</code>elementorDevTools.deprecation.deprecated()` insteadI have another question. How do I know that the Conversion Api is working?
Thank you
- This reply was modified 1 year, 4 months ago by bilzone.
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelI researched further and found that it is not compatible with the Elementor Full Width template. This is where I am stuck and I really don’t know what else to do to solve the problem.
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelI found out where the problem was but I don’t know how to solve it. One of the plugins used is Elementor. When I disable it, the ViewContent event appears instantly. So that’s where the problem lies.
Now I don’t know how to solve it because I can’t do without this plugin (Elementor)
Do you have any idea?
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelHello,
I uploaded the report to dropbox:
I will make a brief recap of the problems encountered:
- The ViewContent event appears only after I configure it manually, using the Event Setup Tool. After manually configuring it at Setup Method in Test Events it showed “Event setup tool” but shortly after it changed to Partner integration, although I had manually configured this event.
But if I delete the event that I created manually earlier and surprisingly it was still displayed, only that in a maximum of 30 minutes it disappeared again. This means that the Facebook for Woocommerce plugin does not transmit this event (ViewContent).
2. Another thing. In Test Events, under Received From, there shouldn’t be Server? From what I understand, this plugin also knows Conversion Api.
How do I know that the Conversion Api is working? Shouldn’t both browser and server appear in Received from? For me, only browser appears.
How do I make this event active by default, without having to configure it using the Event Setup Tool.
I am interested in having the ViewContent event pass the following information:
– content_ids
– content_name
– content_type
– contents
– currently
– valueCurrently I have it configured manually but I don’t know if it’s ok to leave it like this because I’m interested in using the Conversion Api as well.
I tried all these tests with the cache disabled and the StoreFront theme active.
Waiting your response
Thank you
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelIs there any chance I can send it to you privately? I don’t want to share here.
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelI’m a little desperate to solve the problem. Why isn’t the ViewContent event firing?
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelDo you have any idea why it doesn’t appear by default? I’m also interested in sending content_ids
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in Pixel` WordPress Environment</p> <p>WordPress address (URL):<br>Site address (URL): <br>WC Version: 9.5.1<br>Legacy REST API Package Version: Modulul Legacy REST API nu este instalat pe acest site.<br>Action Scheduler Version: ✔ 3.8.2<br>Log Directory Writable: ✔<br>WP Version: 6.7.1<br>WP Multisite: –<br>WP Memory Limit: 2 Go<br>WP Debug Mode: –<br>WP Cron: ✔<br>Language: ro_RO<br>External object cache: – Server Environment</p> <p>Server Info: LiteSpeed<br>PHP Version: 8.0.30<br>PHP Post Max Size: 512 Mo<br>PHP Time Limit: 300<br>PHP Max Input Vars: 10000<br>cURL Version: 8.11.0<br>OpenSSL/1.1.1w</p> <p>SUHOSIN Installed: –<br>MySQL Version: 10.6.14-MariaDB<br>Max Upload Size: 512 Mo<br>Default Timezone is UTC: ✔<br>fsockopen/cURL: ✔<br>SoapClient: ✔<br>DOMDocument: ✔<br>GZip: ✔<br>Multibyte String: ✔<br>Remote Post: ✔<br>Remote Get: ✔ Database</p> <p>WC Database Version: 9.5.1<br>WC Database Prefix: wpvq_<br>Dimensiune totală bază de date: 77.17MB<br>Dimensiune date bază de date: 51.17MB<br>Dimensiune index bază de date: 26.00MB<br>wpvq_woocommerce_sessions: Date: 1.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_woocommerce_api_keys: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_woocommerce_attribute_taxonomies: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_woocommerce_downloadable_product_permissions: Date: 0.02 MO + Index: 0.06 MO + Motor InnoDB<br>wpvq_woocommerce_order_items: Date: 1.52 MO + Index: 0.13 MO + Motor InnoDB<br>wpvq_woocommerce_order_itemmeta: Date: 3.52 MO + Index: 3.03 MO + Motor InnoDB<br>wpvq_woocommerce_tax_rates: Date: 0.02 MO + Index: 0.06 MO + Motor InnoDB<br>wpvq_woocommerce_tax_rate_locations: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_woocommerce_shipping_zones: Date: 0.02 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_woocommerce_shipping_zone_locations: Date: 0.02 MO + Index: 0.05 MO + Motor InnoDB<br>wpvq_woocommerce_shipping_zone_methods: Date: 0.02 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_woocommerce_payment_tokens: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_woocommerce_payment_tokenmeta: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_woocommerce_log: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_actionscheduler_actions: Date: 2.52 MO + Index: 1.30 MO + Motor InnoDB<br>wpvq_actionscheduler_claims: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_actionscheduler_groups: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_actionscheduler_logs: Date: 1.31 MO + Index: 0.64 MO + Motor InnoDB<br>wpvq_commentmeta: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_comments: Date: 1.52 MO + Index: 0.77 MO + Motor InnoDB<br>wpvq_curiero_localities: Date: 1.52 MO + Index: 2.77 MO + Motor InnoDB<br>wpvq_curiero_mygls_awb_data: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_curiero_zipcodes: Date: 4.52 MO + Index: 4.52 MO + Motor InnoDB<br>wpvq_cuw_campaigns: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_cuw_campaign_engine: Date: 0.02 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_cuw_engines: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_cuw_offers: Date: 0.06 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_cuw_stats: Date: 0.05 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_e_events: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_e_submissions: Date: 0.09 MO + Index: 0.27 MO + Motor InnoDB<br>wpvq_e_submissions_actions_log: Date: 0.02 MO + Index: 0.11 MO + Motor InnoDB<br>wpvq_e_submissions_values: Date: 0.34 MO + Index: 0.09 MO + Motor InnoDB<br>wpvq_jetpack_sync_queue: Date: 0.02 MO + Index: 0.06 MO + Motor InnoDB<br>wpvq_jetpack_waf_blocklog: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_links: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_litespeed_avatar: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_litespeed_img_optming: Date: 0.02 MO + Index: 0.05 MO + Motor InnoDB<br>wpvq_litespeed_url: Date: 0.06 MO + Index: 0.08 MO + Motor InnoDB<br>wpvq_litespeed_url_file: Date: 0.08 MO + Index: 0.19 MO + Motor InnoDB<br>wpvq_loginizer_logs: Date: 0.02 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_options: Date: 5.09 MO + Index: 0.30 MO + Motor InnoDB<br>wpvq_postmeta: Date: 15.52 MO + Index: 9.03 MO + Motor InnoDB<br>wpvq_posts: Date: 10.39 MO + Index: 0.63 MO + Motor InnoDB<br>wpvq_termmeta: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_terms: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_term_relationships: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_term_taxonomy: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_usermeta: Date: 0.09 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_users: Date: 0.02 MO + Index: 0.05 MO + Motor InnoDB<br>wpvq_wc_admin_notes: Date: 0.05 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_wc_admin_note_actions: Date: 0.05 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_wc_category_lookup: Date: 0.02 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_wc_customer_lookup: Date: 0.20 MO + Index: 0.13 MO + Motor InnoDB<br>wpvq_wc_download_log: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_wc_orders: Date: 0.02 MO + Index: 0.11 MO + Motor InnoDB<br>wpvq_wc_orders_meta: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_wc_order_addresses: Date: 0.02 MO + Index: 0.06 MO + Motor InnoDB<br>wpvq_wc_order_coupon_lookup: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_wc_order_operational_data: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_wc_order_product_lookup: Date: 0.34 MO + Index: 0.31 MO + Motor InnoDB<br>wpvq_wc_order_stats: Date: 0.36 MO + Index: 0.27 MO + Motor InnoDB<br>wpvq_wc_order_tax_lookup: Date: 0.02 MO + Index: 0.03 MO + Motor InnoDB<br>wpvq_wc_product_attributes_lookup: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_wc_product_download_directories: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_wc_product_meta_lookup: Date: 0.03 MO + Index: 0.11 MO + Motor InnoDB<br>wpvq_wc_rate_limits: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_wc_reserved_stock: Date: 0.02 MO + Index: 0.00 MO + Motor InnoDB<br>wpvq_wc_tax_rate_classes: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_wc_webhooks: Date: 0.02 MO + Index: 0.02 MO + Motor InnoDB<br>wpvq_yith_wcmc_register: Date: 0.02 MO + Index: 0.00 MO + Motor InnoDB Post Type Counts</p> <p>attachment: 514<br>custom_css: 3<br>customize_changeset: 1<br>e-landing-page: 2<br>elementor_library: 10<br>elementor_snippet: 4<br>nav_menu_item: 14<br>page: 11<br>post: 1<br>product: 25<br>product_variation: 58<br>revision: 30<br>shop_order: 3105<br>slick_slider: 2<br>wp_global_styles: 1<br>wp_navigation: 1<br>wp_template: 2 Security</p> <p>Secure connection (HTTPS): ✔<br>Hide errors from visitors: ✔ Active Plugins (12)<br>wpformation – 1.9.17.1 Inactive Plugins (3)</p> <p></p> <p>Legacy API Enabled: –<br>Force SSL: –<br>Currency: RON (lei)<br>Currency Position: right_space<br>Thousand Separator: ,<br>Decimal Separator: .<br>Number of Decimals: 2<br>Taxonomies: Product Types: external (external)<br>grouped (grouped)<br>simple (simple)<br>variable (variable)</p> <p>Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)<br>exclude-from-search (exclude-from-search)<br>featured (featured)<br>outofstock (outofstock)<br>rated-1 (rated-1)<br>rated-2 (rated-2)<br>rated-3 (rated-3)<br>rated-4 (rated-4)<br>rated-5 (rated-5)</p> <p>Connected to WooCommerce.com: –<br>Enforce Approved Product Download Directories: ✔<br>HPOS feature enabled: –<br>Order datastore: WC_Order_Data_Store_CPT<br>HPOS data sync enabled: – Logging</p> <p>Enabled: ✔<br>Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2<br>Retention period: 30 de zile<br>Level threshold: –<br>Log directory size: 3 Mo WC Pages</p> <p>Bază magazin: ❌ Pagină nesetată<br>Coș: ❌ Pagina nu conține scurtcodul [woocommerce_cart] sau blocul woocommerce/cart.<br>Finalizare: #9 – /checkout/ – Conține scurt-codul [woocommerce_checkout]<br>Contul meu: #10 – /my-account/<br>Termeni și condiții: ❌ Pagină nesetată Theme</p> <p>Name: Best Shop<br>Version: 1.4.5 (este disponibilă actualizarea la versiunea 1.5.1)<br>Author URL: https://gradientthemes.com/<br>Child Theme: ❌ – Dacă modifici WooCommerce într-o temă părinte pe care nu ai construit-o personal recomandăm folosirea unei teme copil. Vezi: Cum creezi o temă copil<br>Theme type: Temă clasică<br>WooCommerce Support: ✔ Templates</p> <p>Archive Template: Tema ta are un fișier woocommerce.php<br>nu vei putea să contramandezi șablonul personalizat woocommerce/archive-product.php deoarece woocommerce.php are prioritate față de archive-product.php. Acest lucru are ca scop prevenirea problemelor de afișare.</p> <p>Overrides: Versiunea best-shop/woocommerce/content-product.php a 3.6.0 este depășită. Versiunea nucleu este 9.4.0<br>Outdated Templates: ❌</p> <pre class=”wp-block-code”><code> Află cum să actualizezi | Șterge cache-ul din starea sistemului cu informații despre temă</code></pre> <p>Admin</p> <p>Enabled Features: activity-panels<br>analytics<br>product-block-editor<br>coupons<br>core-profiler<br>customize-store<br>customer-effort-score-tracks<br>import-products-task<br>experimental-fashion-sample-products<br>shipping-smart-defaults<br>shipping-setting-tour<br>homescreen<br>marketing<br>mobile-app-banner<br>onboarding<br>onboarding-tasks<br>pattern-toolkit-full-composability<br>product-custom-fields<br>remote-inbox-notifications<br>remote-free-extensions<br>payment-gateway-suggestions<br>printful<br>shipping-label-banner<br>subscriptions<br>store-alerts<br>transient-notices<br>woo-mobile-welcome<br>wc-pay-promotion<br>wc-pay-welcome-page<br>launch-your-store</p> <p>Disabled Features: product-data-views<br>experimental-blocks<br>coming-soon-newsletter-template<br>minified-js<br>product-pre-publish-modal<br>settings<br>async-product-editor-category-field<br>product-editor-template-system<br>blueprint<br>reactify-classic-payments-settings<br>use-wp-horizon<br>add-to-cart-with-options-stepper-layout</p> <p>Daily Cron: ✔ Next scheduled: 2025-01-22 16:26:30 +02:00<br>Options: ✔<br>Notes: 54<br>Onboarding: completed Action Scheduler</p> <p>Finalizează: 2.984<br>Oldest: 2024-12-22 08:27:17 +0000<br>Newest: 2025-01-22 08:19:19 +0000</p> <p>Eșuată: 841<br>Oldest: 2023-08-18 17:07:35 +0000<br>Newest: 2025-01-21 19:48:02 +0000</p> <p>În așteptare: 4<br>Oldest: 2025-01-22 17:53:21 +0000<br>Newest: 2025-01-23 04:27:49 +0000 Status report information</p> <p>Generated at: 2025-01-22 10:19:21 +02:00<br>`
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelAnybody?
And I also noted in content_ids that it displays the product name instead of the numeric ID.
Forum: Plugins
In reply to: [Meta for WooCommerce] Missing ViewContent event in PixelHello,
676605977865936
- Scroll util from “/dev/js/frontend/utils/scroll”