Title: Florent's Replies | WordPress.org --- # Florent [ ](https://wordpress.org/support/users/flowebpro/) * [Profile](https://wordpress.org/support/users/flowebpro/) * [Topics Started](https://wordpress.org/support/users/flowebpro/topics/) * [Replies Created](https://wordpress.org/support/users/flowebpro/replies/) * [Reviews Written](https://wordpress.org/support/users/flowebpro/reviews/) * [Topics Replied To](https://wordpress.org/support/users/flowebpro/replied-to/) * [Engagements](https://wordpress.org/support/users/flowebpro/engagements/) * [Favorites](https://wordpress.org/support/users/flowebpro/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 31 total) 1 [2](https://wordpress.org/support/users/flowebpro/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/flowebpro/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/flowebpro/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Tracktastic: Free Matomo Integration for WooCommerce] Fatal Error on Product pages](https://wordpress.org/support/topic/fatal-error-on-product-pages-4/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 months, 3 weeks ago](https://wordpress.org/support/topic/fatal-error-on-product-pages-4/#post-18762130) * Hi, I encounter the exact same issue_`PHP Fatal error:  Uncaught Error: Call to a member function get\_sku() on string`_ * “Matomo WordPress plugin is installed, activated and track visits already. Matomo WordPress plugin is installed, activated and track visits already.I’m using the“ auto” tracking method in Matomo settings (from wordpress back-office).I also tried to switch to “Manual” mode, uninstalled tracktastic, installed it again = Still get the fatal error. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] WP-OPTIMIZE KILLED ALL MY WEBSITES](https://wordpress.org/support/topic/wp-optimize-killed-all-my-websites/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [1 year, 6 months ago](https://wordpress.org/support/topic/wp-optimize-killed-all-my-websites/page/3/#post-18132813) * In my previous message, I mentionned that the cache preloader was calling URL too many times. It’s the reason we get high php-fpm usage. In our case, the preloader call every URL more than 10 times ! Support ([@vupdraft](https://wordpress.org/support/users/vupdraft/)) answered that it was because of the “user specific” cache function. But It’s a premium function, we don’t use this function.So the preloader generate 10X more request that it should makes. * ```wp-block-code 172.71.102.188 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"172.71.118.215 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"172.71.127.111 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"172.71.183.58 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"172.71.127.26 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"172.71.127.26 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"172.71.119.23 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"172.71.99.34 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32378 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"172.69.223.181 - - [13/Nov/2024:17:02:07 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"172.71.118.186 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"172.70.46.109 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"172.71.130.143 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36" ``` - This reply was modified 1 year, 6 months ago by [Florent](https://wordpress.org/support/users/flowebpro/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] WP-OPTIMIZE KILLED ALL MY WEBSITES](https://wordpress.org/support/topic/wp-optimize-killed-all-my-websites/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [2 years, 3 months ago](https://wordpress.org/support/topic/wp-optimize-killed-all-my-websites/page/2/#post-17352206) * [@vupdraft](https://wordpress.org/support/users/vupdraft/) Thanks ! This seems to be a Premium Upgrade function, but the concerned website use the free version( 3.2.22), and don’t have this option listed.Thanks * ![](https://i0.wp.com/i.ibb.co/NFdqYJN/image.png?ssl=1) - This reply was modified 2 years, 3 months ago by [Florent](https://wordpress.org/support/users/flowebpro/). - This reply was modified 2 years, 3 months ago by [Florent](https://wordpress.org/support/users/flowebpro/). - This reply was modified 2 years, 3 months ago by [Florent](https://wordpress.org/support/users/flowebpro/). - This reply was modified 2 years, 3 months ago by [Florent](https://wordpress.org/support/users/flowebpro/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance] WP-OPTIMIZE KILLED ALL MY WEBSITES](https://wordpress.org/support/topic/wp-optimize-killed-all-my-websites/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [2 years, 3 months ago](https://wordpress.org/support/topic/wp-optimize-killed-all-my-websites/page/2/#post-17351861) * Hi, * I’m hosting the website of a clients. I noticed a very high load on his website everyday, same hour.It is because of the cache preloading.For an unknown Reason, WP-Optimize perform 9 Query for each URL, instead of one. My client use the “ cache a different version for mobile” so we end with… 18 query by SECOND for ONE url!!!!!Checked at WordPress cron, didn’t find duplicates cron jobs….Cron:_“ wpo\_use\_cache\_lifespan” 1 day interval – “Same as cache lifespan: 1 days”_Cron:_“ wpo\_purge\_old\_cache” 1 day interval – “Every time after the cache has expired”_( don’t look at IP, it’s Cloudflare IP. legit traffic from the website itself)Using php8.1 (php-fpm). * ![](https://i0.wp.com/i.ibb.co/nfXKQQN/wtfisthat.png?ssl=1) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Fatal Error qui traine depuis plus d’un an.](https://wordpress.org/support/topic/fatal-error-qui-traine-depuis-plus-dun-an/) * Thread Starter [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [2 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-qui-traine-depuis-plus-dun-an/#post-16831438) * Je ne sais pas quelle solution vous avez choisi, je vais tester ça. * Effectivement, dans le cas d’un envoi international, le bordereau douanes précise le poids de chaque article. Mais pas pour le national + Europe… Déclarez un poids de 0 si l’article n’existe plus, et fini les problèmes. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Produit supprimé = WordPress cassé](https://wordpress.org/support/topic/produit-supprime-wordpress-casse/) * Thread Starter [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 years, 1 month ago](https://wordpress.org/support/topic/produit-supprime-wordpress-casse/#post-15506420) * Hello, Visiblement ce problème n’a pas encore été corrigé. C’est assez embetant… * Bonne journée, Florent * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Message d’erreur WP](https://wordpress.org/support/topic/message-derreur-wp/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 years, 3 months ago](https://wordpress.org/support/topic/message-derreur-wp/#post-15274719) * Ca doit être le même problème qu’ici : [https://wordpress.org/support/topic/produit-supprime-wordpress-casse/](https://wordpress.org/support/topic/produit-supprime-wordpress-casse/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] CURL error: (400) 30401 : Le code point de retrait est incorrect](https://wordpress.org/support/topic/curl-error-400-30401-le-code-point-de-retrait-est-incorrect/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 years, 5 months ago](https://wordpress.org/support/topic/curl-error-400-30401-le-code-point-de-retrait-est-incorrect/#post-15170669) * J’ai eu le même problème. J’en suis arrivé à la conclusion que le client avait choisi un point retrait lors de sa commande, qui n’existe plus, et n’est plus accepté par la poste, au moment de la génération de l’étiquette. * (le retour de l’api de la poste indiquait bien une erreur du type Code point relais invalide) - This reply was modified 4 years, 5 months ago by [Florent](https://wordpress.org/support/users/flowebpro/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Génération de plusieurs étiquettes pour une commande](https://wordpress.org/support/topic/generation-de-plusieurs-etiquettes-pour-une-commande/) * Thread Starter [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 years, 6 months ago](https://wordpress.org/support/topic/generation-de-plusieurs-etiquettes-pour-une-commande/#post-15070887) * Petite précison : Car à +30kg, l’étiquette ne pouvait pas se générer. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] L’extension n’a pas pu être activée](https://wordpress.org/support/topic/lextension-na-pas-pu-etre-activee/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 years, 6 months ago](https://wordpress.org/support/topic/lextension-na-pas-pu-etre-activee/#post-15070116) * Vous avez un problème avec votre installation de PHP, rien à voir avec le plugin Colissimo. Vous devriez avoir le module php_soap installé et activé dans votre configuration PHP. * Vous pouvez poster le résultat d’un phpinfo(); si c’est pas clair pour vous. ( Créer un fichier xxxxx.php, avec pour contenu : `` ) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Message d’erreur de la part de WordPress](https://wordpress.org/support/topic/message-derreur-de-la-part-de-wordpress/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 years, 6 months ago](https://wordpress.org/support/topic/message-derreur-de-la-part-de-wordpress/#post-15035082) * Ne serait-ce pas le bug du poids incalculable du fait que le produit a été supprimé depuis ? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Erreur carte des points colissimo relais](https://wordpress.org/support/topic/erreur-carte-des-points-colissimo-relais/) * [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [4 years, 6 months ago](https://wordpress.org/support/topic/erreur-carte-des-points-colissimo-relais/#post-15035074) * J’ai, moi aussi, un problème de double inclusion des scripts de Google map. Cela n’entraine pas le même dysfonctionnement, mais j’ai tout de même une erreur Javascript (qui semblerait occasionner un conflit avec Paypal, qui tout comme Colissimo, modifie la valeur du bouton de validation de la commande (Payer avec paypal /VS/ Veuillez choisir un point relais)) * Dans mon cas, la double inclusion est signalée dès lors qu’un point de retrait est sélectionné. le module colissimo recharge le script google map une deuxième fois lorsqu’il rafraichit le panier avec les infos du point relais. * A mon sens il faudrait s’assurer que le module Google map est chargé au niveau de la page panier, et non du module d’expédition, qui recharge les scripts google map une seconde fois dès lors qu’il s’actualise. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Sécurité Tel relais : Probleme !](https://wordpress.org/support/topic/securite-tel-relais-probleme/) * Thread Starter [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [5 years, 2 months ago](https://wordpress.org/support/topic/securite-tel-relais-probleme/#post-14107397) * Je suggérait une piste, pour pouvoir palier au manquement du ws concernant ce cas spécifique, et gérer en front l’affichage d’un message plus équivoque. * Il n’y a pas de problème de numéro, c’est un problème de règle Pays/indicatif, CF vos précédents messages. * Je clos le ticket. Merci. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Sécurité Tel relais : Probleme !](https://wordpress.org/support/topic/securite-tel-relais-probleme/) * Thread Starter [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [5 years, 2 months ago](https://wordpress.org/support/topic/securite-tel-relais-probleme/#post-14106756) * Hum… Si réponse du ws “veuillez définir un numéro” ET champ téléphone = pas vide, avec des chiffres > Numéro de portable non valide pour le pays de destination. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Colissimo Officiel : Méthodes de livraison pour WooCommerce] Génération étiquette / Fatal Error](https://wordpress.org/support/topic/generation-etiquette-fatal-error/) * Thread Starter [Florent](https://wordpress.org/support/users/flowebpro/) * (@flowebpro) * [5 years, 2 months ago](https://wordpress.org/support/topic/generation-etiquette-fatal-error/#post-14106726) * Impossible à mettre en place dans la pratique, pour le suivi logistique (ce sont des produits faits sur mesure expédiés plusieurs semaines après commande) il nous est indispensable de garder le produit dans la commande. Nous ne pouvons pas nous permettre de le supprimer et de ne plus savoir quel article a été commandé. * Car le produit a été supprimé de Woocommerce, mais il reste néanmoins enregistré dans la commande. * Nous avons une trentaine de commandes pour lesquels nous allons créer les étiquettes manuellement. Viewing 15 replies - 1 through 15 (of 31 total) 1 [2](https://wordpress.org/support/users/flowebpro/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/flowebpro/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/flowebpro/replies/page/2/?output_format=md)