terzag
Forum Replies Created
-
Forum: Plugins
In reply to: [Out of the Block: OpenStreetMap] No wide/full align on frontIt seems to work, thanks.
Forum: Plugins
In reply to: [qTranslate X Cleanup and WPML Import] Lost content with the cleanup toolHey. I was trying to replicate the issue on the sandbox and at some point I ran the cleanup tool without issue, but then I tried to add other posts to try to cover some special cases but if I go to your plugin it says that the cleanup tool has already run, I can’t run it again for some reason. Is there a way to force it?
(BTW, there’s an issue with the theme you’re using regarding loading the textdomain; it shouldn’t cause issues beyond the error message in the domain AFAIK.)
Forum: Plugins
In reply to: [qTranslate X Cleanup and WPML Import] Lost content with the cleanup toolHello,
The thing is that I can’t set a language, it is done automatically depending on the content. Basically, the way that qTranslate (and its various derivatives) works is that if the content is the same in every language, it considers that the post doesn’t have a language and it doesn’t add the related tags. AFAIK, there is no way to force a language besides editing the posts and make it so that every language has different content (even a single char), and so qTranslate will consider them different and add the tags.
Thanks for the clarifications. I’ll see with Facebook support.
Correct. The products are synced to the FB catalog and all of them appear in it. They’re all added/listed and appear to be fine (no problem reported).
The issue is that they’re not automatically published anymore on the FB page or Instagram. I’m trying to understand what change we made could have triggered the issue (my wild guess is that it would be the addition of a proper store to the FB account where it only had the catalog setup without one before that).
So, if the plugin has done its job, it implies that it’s another plugin that was used so far to publish them (i.e. Jetpack Social)? or do you mean that it’s Facebook that was doing the job internally without any outside input (i.e. when something is added to the catalog, Facebook is supposed to automatically publish it on the page and the associated Instagram page)?
Forum: Plugins
In reply to: [WooCommerce] Enable WC Lightbox without zoom?Just tried and it has the same behavior. Which is weird, as its options offer to disable the lightbox, the zoom or both, so I assume it should be possible to disable the zoom and still have the lightbox.
So, still not sure if it’s an issue with my theme (which has a number of hacks to display the product page in a specific way) or a bug in WC.
EDIT: I’ve just tried things with a different store and it’s a mixed bag. The original issue comes from a different plugin I use in the original store (it disable links on images, that’s why the lightbox doesn’t open when clicking on the image itself) and either a bug in WC or a misunderstanding from me:
– it is indeed possible to enable the lightbox without the zoom;
– the magnifying glass icon only appears when the zoom feature is enabled.Now, that’s the second point that’s confusing me: is the magnifying glass icon supposed to show that the image can be clicked and should always appear when the lightbox is enabled (which is what I assumed); or is it displayed only to be able to open the lightbox when the zoom is active because the image can’t be clicked otherwise, and thus it’s normal that it isn’t displayed when there is no zoom?
Here it is (the website is in french):
### WordPress Environment ### WordPress address (URL): https://www.crolle-terzaghi.com Site address (URL): https://www.crolle-terzaghi.com WC Version: 4.4.1 REST API Version: ✔ 1.0.15 WC Blocks Version: ✔ 3.1.0 Action Scheduler Version: ✔ 3.1.6 WC Admin Version: ✔ 1.4.0 Log Directory Writable: ✔ WP Version: 5.5.1 WP Multisite: – WP Memory Limit: 512 Mo WP Debug Mode: – WP Cron: ✔ Language: fr_FR External object cache: – ### Server Environment ### Server Info: Apache PHP Version: 7.3.18 PHP Post Max Size: 130 Mo PHP Time Limit: 300 PHP Max Input Vars: 16000 cURL Version: 7.38.0 OpenSSL/1.0.1t SUHOSIN Installed: – MySQL Version: 5.6.48-log Max Upload Size: 128 Mo Default Timezone is UTC: ✔ fsockopen/cURL: ✔ SoapClient: ✔ DOMDocument: ✔ GZip: ✔ Multibyte String: ✔ Remote Post: ✔ Remote Get: ✔ ### Database ### WC Database Version: 4.4.1 WC Database Prefix: wp_ Taille totale de la base de données: 25.85MB Taille de la base de données: 23.58MB Taille de l’index: 2.27MB wp_woocommerce_sessions: Données : 1.02MB + Index : 0.02MB + Moteur InnoDB wp_woocommerce_api_keys: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_woocommerce_attribute_taxonomies: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB wp_woocommerce_downloadable_product_permissions: Données : 0.02MB + Index : 0.06MB + Moteur InnoDB wp_woocommerce_order_items: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB wp_woocommerce_order_itemmeta: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_woocommerce_tax_rates: Données : 0.02MB + Index : 0.06MB + Moteur InnoDB wp_woocommerce_tax_rate_locations: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_woocommerce_shipping_zones: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_woocommerce_shipping_zone_locations: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_woocommerce_shipping_zone_methods: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_woocommerce_payment_tokens: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB wp_woocommerce_payment_tokenmeta: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_woocommerce_log: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB dct_boulots: Données : 0.00MB + Index : 0.00MB + Moteur MyISAM dct_boulots_text: Données : 0.05MB + Index : 0.01MB + Moteur MyISAM dct_categboulots: Données : 0.00MB + Index : 0.00MB + Moteur MyISAM dct_categboulots_text: Données : 0.00MB + Index : 0.00MB + Moteur MyISAM wp_actionscheduler_actions: Données : 0.06MB + Index : 0.11MB + Moteur InnoDB wp_actionscheduler_claims: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB wp_actionscheduler_groups: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB wp_actionscheduler_logs: Données : 0.05MB + Index : 0.03MB + Moteur InnoDB wp_aiowps_events: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_aiowps_failed_logins: Données : 0.34MB + Index : 0.00MB + Moteur InnoDB wp_aiowps_global_meta: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_aiowps_login_activity: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_aiowps_login_lockdown: Données : 1.52MB + Index : 0.00MB + Moteur InnoDB wp_aiowps_permanent_block: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_commentmeta: Données : 0.06MB + Index : 0.01MB + Moteur MyISAM wp_comments: Données : 0.06MB + Index : 0.02MB + Moteur MyISAM wp_fblb: Données : 0.00MB + Index : 0.00MB + Moteur MyISAM wp_links: Données : 0.00MB + Index : 0.00MB + Moteur MyISAM wp_lpc_inward_label: Données : 0.02MB + Index : 0.05MB + Moteur InnoDB wp_lpc_label: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_lpc_outward_label: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_mailchimp_carts: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_mailchimp_jobs: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_options: Données : 1.08MB + Index : 0.22MB + Moteur MyISAM wp_postmeta: Données : 3.36MB + Index : 0.33MB + Moteur MyISAM wp_posts: Données : 15.11MB + Index : 0.46MB + Moteur MyISAM wp_termmeta: Données : 0.00MB + Index : 0.01MB + Moteur MyISAM wp_terms: Données : 0.02MB + Index : 0.05MB + Moteur MyISAM wp_term_relationships: Données : 0.05MB + Index : 0.11MB + Moteur MyISAM wp_term_taxonomy: Données : 0.03MB + Index : 0.02MB + Moteur MyISAM wp_toolset_post_guid_id: Données : 0.00MB + Index : 0.00MB + Moteur MyISAM wp_usermeta: Données : 0.01MB + Index : 0.01MB + Moteur MyISAM wp_users: Données : 0.00MB + Index : 0.01MB + Moteur MyISAM wp_wcpdf_invoice_number: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_wc_admin_notes: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_wc_admin_note_actions: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB wp_wc_category_lookup: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_wc_customer_lookup: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_wc_download_log: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_wc_order_coupon_lookup: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_wc_order_product_lookup: Données : 0.02MB + Index : 0.06MB + Moteur InnoDB wp_wc_order_stats: Données : 0.02MB + Index : 0.05MB + Moteur InnoDB wp_wc_order_tax_lookup: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB wp_wc_product_meta_lookup: Données : 0.02MB + Index : 0.09MB + Moteur InnoDB wp_wc_reserved_stock: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB wp_wc_tax_rate_classes: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB wp_wc_webhooks: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB ### Post Type Counts ### attachment: 1979 nav_menu_item: 16 page: 12 post: 364 product: 87 product_variation: 6 projet: 193 revision: 1867 shop_coupon: 1 shop_order: 1 wpcf7_contact_form: 2 ### Security ### Secure connection (HTTPS): ✔ Hide errors from visitors: ✔ ### Active Plugins (28) ### Le Typographe: par Jean-noël Lafargue – 0.01 Admin Menu Editor: par Janis Elsts – 1.9.7 Akismet Anti-Spam: par Automattic – 4.1.6 All In One WP Security: par Tips and Tricks HQ Peter Petreski Ruhul Ivy – 4.4.4 bürö CMS Amazon Affiliate links: par brice terzaghi – 1.1 bürö CMS Gallery: par brice terzaghi – 0.1.9 Classic Editor: par Contributeurs et contributrices WordPress – 1.6 Clean Image Filenames: par Upperdog – 1.2.1 Colissimo shipping methods for WooCommerce: par Colissimo – 1.3.3 Contact Form 7: par Takayuki Miyoshi – 5.2.2 Enable jQuery Migrate Helper: par The WordPress Team – 1.0.1 GA Google Analytics: par Jeff Starr – 20200815 Jetpack par WordPress.com: par Automattic – 8.9 Link Manager: par WordPress – 0.1-beta Mailchimp for WooCommerce: par Mailchimp – 2.4.5 qTranslate-X: par qTranslate Team – 3.4.6.8 Really Simple SSL: par Really Simple Plugins – 3.3.5 SumUp Payment Gateway For WooCommerce: par SumUp – 1.0.0 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.4.1 Taxonomy Images: par Michael Fields Ben Huson – 1.0 Visual Link Preview: par Bootstrapped Ventures – 2.1.0 WooCommerce PayPal Checkout Gateway: par WooCommerce – 2.0.3 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.4.1 WooCommerce Stripe Gateway: par WooCommerce – 4.5.2 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.4.1 WooCommerce PDF Invoices & Packing Slips: par Ewout Fernhout – 2.6.0 WooCommerce & qTranslate-X: par qTranslate Team – 1.3 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.4.1 WooCommerce Services: par Automattic – 1.24.1 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.4.1 WooCommerce: par Automattic – 4.4.1 wp tarteaucitron.js self Hosted: par Ricci Dorian – 1.1.0 WPC Variations Radio Buttons for WooCommerce: par WPClever.net – 2.2.1 ### Inactive Plugins (0) ### ### Settings ### API Enabled: – Force SSL: – Currency: EUR (€) Currency Position: right Thousand Separator: Decimal Separator: , Number of Decimals: 2 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 boutique: #5074 - /shop/ Panier: #5075 - /shop/cart/ Commander: #5076 - /shop/checkout/ Mon compte: #5077 - /shop/my-account/ Conditions générales de vente et d’utilisation: #5086 - /shop/cgv/ ### Theme ### Name: DCT Version: 1.7.1 Author URL: http://www.terzag.info/ Child Theme: ❌ – Si vous modifiez WooCommerce sur un thème parent que vous n’avez pas construit personnellement nous vous recommandons d’utiliser un thème enfant. Voir : Comment créer un thème enfant WooCommerce Support: ✔ ### Templates ### Archive Template: Votre thème a un fichier woocommerce.php vous ne serez pas en mesure de substituer le modèle personnalisé woocommerce/archive-product.php étant donné que woocommerce.php a la priorité sur archive-product.php. Ceci vise à prévenir les problèmes d’affichage. Overrides: dct/woocommerce/content-product.php dct/woocommerce/content-single-product.php dct/woocommerce/single-product/add-to-cart/variable.php dct/woocommerce/single-product/product-image.php ### Action Scheduler ### Terminé: 87 Oldest: 2020-08-05 07:15:55 +0000 Newest: 2020-09-01 20:13:11 +0000Forum: Plugins
In reply to: [Wishlist for WooCommerce] Support for variations?Ok. Looking forward to it. 🙂
Regards.
Forum: Plugins
In reply to: [Wishlist for WooCommerce] Support for variations?Let’s say I sell T-shirts. Each product is a specific design and on the product page I have color and size variations to choose. If I have 2 colors and 3 sizes for a design, that makes 6 possible variations combinations.
I’d need the wishlist button to be dependent of the variations combination, i.e. on the “Design #1” T-shirt, I’d need to be able to wishlist the “Red / XL version”, or the “Blue / S” version rather than the “Design #1” product itself. And in the wishlist page, to have a link to the specific variation.
Or, to say it differently, treating each variations combination as a different product when it comes to the wishlist.
I’m currently using a different wishlist plugin that allows this but yours seems more streamlined and maybe better for my case apart from that limitation.
Ok, I’ll let you know if something wrong happens.
I’ve tried to disconnect/reconnect from the dashboard and it still happens. Sometimes it’s fine and there’s no connection issue alert when accessing the dashboard (was already the case before I disconnected/reconnected) and I’m starting to wonder if it’s actually related to the PHP issue that I reported at the beginning.
I realize that I forgot a part of the message in my initial report: the mail mentioned that the issue was triggered on the wp-login.php page, so I would assume that it’s when initializing the plugin?
AFAIK (I’m not the direct recipient of the e-mail), there hasn’t been a new alert since the initial one that happened two days ago, so I’m currently assuming that it was due to a problem when updating Jetpack to the latest version (I reinstalled it manually just in case). I was concerned that there was a compatibility issue with WP 5.5 which would break the website.
If the connection issue in the dashboard is an unrelated issue and only happens when displaying the stats, it’s not a big deal.
The website is https://www.crolle-terzaghi.com/
I doubt it’s a cache issue as the message appears on a different computer than mine, from what I’ve been told. Anyway, I’ve just tried to clear the cache and also with a different browser on mine and it still happens.
Besides, the original alert about the issue was sent by e-mail from the WordPress autocheck functionality that has been introduced in 5.2.
Not sure if it’s related but the day before we got the e-mail, I upgraded WP to 5.5. Also, I’ve had to install the jQuery Migrate Helper (https://ww.wp.xz.cn/plugins/enable-jquery-migrate-helper/) for compatibility with another plugin, not sure if it might be related to the issue.
The weird thing is that Jetpack seems to work properly: the dashboard displays stats and I assume it works as expected. It seems to actually be connected to the related account, except that when I load the page, I get an alert at the top saying that it can’t connect to wordpress.com.
When I say I’m disconnected, it’s in the admin part and I can’t give you admin access to the website, obviously.
When I go in the Jetpack dashboard, I get a message saying that there was an issue logging at wordpress.com. I can login again and it seems to work but when I come back to the admin, I’m logged out again in the Jatpack dashboard.
Wordpress 5.5 and PHP 7.3.18 (newest version available at my hosting service, no PHP 7.4 yet).