morvy
Forum Replies Created
-
Seems like the BETA is an older version of the plugin, but it does work correctly and also the other issue with missing QR function in Settings is fixed.
Mailer: phpmailer
HostName: XXX
cURL Version: 8.14.1
OpenSSL Version: OpenSSL/1.1.1w
OS: Linux 4.18.0-553.77.1.lve.el8.x86_64 #1 SMP Wed Oct 8 14:21:00 UTC 2025 x86_64
PHP: Linux 8.2.29 C.UTF-8
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
WordPress: 6.8.3 sk_SK UTF-8
WordPress Theme: Blocksy
WordPress Plugins: WPCodeBox 2, Blocksy Companion (Premium), Advanced Custom Fields PRO, GTM4WP - A Google Tag Manager (GTM) plugin for WordPress, LiteSpeed Cache, Post SMTP, Sequential Order Numbers for WooCommerce, WooCommerce, Wordfence Security, SEOPress PRO, SEOPress, WPS Hide Login
WordPress wp_mail Owner: /var/www/html/wp-includes/pluggable.php
WordPress wp_mail Filter(s): PostsmtpMailer->get_mail_args
WordPress wp_mail_from Filter(s): wordfence::fixWPMailFromAddress
WordPress phpmailer_init Action(s): PostsmtpMailer->phpmailer_smtp_init
Postman: 3.6.1
Postman Sender Domain (Envelope|Message): XXX | XXX
Postman Prevent Message Sender Override (Email|Name): Yes | Yes
Postman Active Transport: Other SMTP (smtp:tls:login://XXX:587)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 72440 | 241
Postman Email Log (Enabled|Limit|Transcript Size): Yes | 500 | 128
Postman Run Mode: log_only
Postman Stealth Mode: YesMailer: phpmailer
HostName: XXX
cURL Version: 8.14.1
OpenSSL Version: OpenSSL/1.1.1w
OS: Linux 4.18.0-553.77.1.lve.el8.x86_64 #1 SMP Wed Oct 8 14:21:00 UTC 2025 x86_64
PHP: Linux 8.2.29 C.UTF-8
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
WordPress: 6.8.3 sk_SK UTF-8
WordPress Theme: Blocksy
WordPress Plugins: WPCodeBox 2, Blocksy Companion (Premium), Advanced Custom Fields PRO, GTM4WP - A Google Tag Manager (GTM) plugin for WordPress, LiteSpeed Cache, Post SMTP, Sequential Order Numbers for WooCommerce, WooCommerce, Wordfence Security, SEOPress PRO, SEOPress, WPS Hide Login
WordPress wp_mail Owner: /var/www/html/wp-includes/pluggable.php
WordPress wp_mail Filter(s): PostsmtpMailer->get_mail_args
WordPress wp_mail_from Filter(s): wordfence::fixWPMailFromAddress
WordPress phpmailer_init Action(s): PostsmtpMailer->phpmailer_smtp_init
Postman: 3.6.1
Postman Sender Domain (Envelope|Message): XXX | XXX
Postman Prevent Message Sender Override (Email|Name): Yes | Yes
Postman Active Transport: Other SMTP (smtp:tls:login://XXX:587)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 72440 | 241
Postman Email Log (Enabled|Limit|Transcript Size): Yes | 500 | 128
Postman Run Mode: log_only
Postman Stealth Mode: YesForum: Plugins
In reply to: [Ecomail] Možnosť nastaviť rozdielne List ID pre rôzne jazyky/krajiny@kristianfilo je to super nápad, ale pozri, aký prístup k užívateľom zvolil Ecomail/WPify .. absolútne nikto to tu nekontroluje. Autodeploy do repozitára a tým to hasne. Ak s tým potrebuješ pohnúť, napíš WPify na support mail, vtedy ti ochotne pomôžu, ak je to niečo, čo im Ecomail odklepne, inak zabudni.
Forum: Plugins
In reply to: [Sentry for WordPress] Sentry LogsThanks for your reply!
During the weekend I put something together, when it’s at least staging ready I’ll put a comment with a link to the repo. My approach is to extend Woo loggers and allow user to select Sentry instead of files/mails/db. Most of the stuff works, but I need to double-check ..
Of course I’ll keep only one plugin active, but keep in mind, that by having Lite version here, you may get customers who want to upgrade to Pro later and if taxonomies and everything is different, are you going to have a migration tool, that needs to be kept updated as well? My client has a Pro license, but having Lite version would be better for him as it’s less cluttered and maybe it’s less resource heavy. The features he needs are all covered in the Lite version now, but he needs to stay on Pro because he can’t downgrade.
Forum: Plugins
In reply to: [Ecomail] Prečo ste zmenili checkout opt in na opt out?Presne o tom píšem v mojej otázke spred týždňa..
https://wordpress.org/support/topic/strata-nastaveni-po-update/
Odpoveď od supportu na ich webe, že toto rieši WPify a mám im napísať e-mail. Z troch klientov, pre ktorých riešim ecomail už dvaja kvôli podobným “sračkám” odišli. Je neakceptovateľné, aby jediný možný spôsob komunikácie so supportom bol e-mail, ktorý je na vývojára, ktorý pri svojom vlastnom plugine komunikuje normálne, ale pre pluginy, ktoré outsourcuje mal úplne na háku. A fakt čerešnička, keď sa niečo buď pokazí alebo zmení logiku.
Tiež je smutné, že základná vec – newsletter form, ktorú som žiadal už dosť dávno je stále v nedohľadne, aj keď technicky je to aj pre menej skúseného programátora otázka 4 hodín aj s testovaním.
Forum: Plugins
In reply to: [Packeta] Nefunkčné CRONyPozeral som to aj na aktuálnej verzii 2.0.3, ale nakoniec čo pomohlo, bolo zmazanie všetkých zlyhaných akcií a teraz čo pribudli nové, už sú vybavené bez chyby.
Forum: Plugins
In reply to: [Packeta] Nefunkčné CRONyZdravím,
predpokladám, že sa to deje od starších verzií až po tú aktuálnu. V podstate som v logoch nenašiel jednu success akciu
LIKE "%packetery%"Forum: Plugins
In reply to: [WPify Woo Czech] Nefunkčný preklad WooDobrý deň,
predpokladám, že preklad cez woocommerce.mo využíva len minimum ľudí, no je to najefektívnejší spôsob, ako upraviť niektoré stringy v rámci oficiálneho Woo prekladu. Na čistej inštalácii sa načítavajú v poradí
1. /wp-content/languages/woocommerce/woocommerce-xx_XX.mo
2. /wp-content/languages/plugins/woocommerce-xx_XX.moPo aktivácii WPify Woo sa ale toto poradie zmení a to spôsobuje, že síce sa preklad zo zložky woocommerce načíta, ale nepoužije. Teda nie je to o tom, že by Váš plugin zasahoval do textdomain alebo nejakým spôsobom prepisoval originál preklad, ale problém je, že sa zmení poradie prekladov a tým sa tie custom nepoužijú.
Ak to spravím cez Loco, samozrejme viem tento problém “vyriešiť”, ale za cenu oveľa vyššej záťaže a času načítania, keďže potom sa vkladajú Loco preklady pre všetko. Pri Loco sa ale /wp-content/languages/logo/plugins/ načítava ako prvé aj keď je váš plugin aktívny, preto to dokáže použiť preložené stringy.
Forum: Plugins
In reply to: [WooCommerce] Custom translations overwritten by default stringsHello,
I’ve created a new install on my local machine to check the behavior and found out that:
- WP 6.6.2 + Woo 9.6 + Loco load all files in correct order, translation works
- WP 6.7 + Woo 9.6 + Loco load all files in correct order, translation works
- WP 6.6.2 / 6.7 + Woo load only woocommerce folder file, so custom translation works, but the default one is skipped
- After installing WPify Woo plugin, the order of files is different and because of that the translation is not applied. I’ve opened ticket with them, so I’ll add the response here. There may be more plugins that cause this behavior.
It’s really strange that after clean install the translation worked, then upgrading to 6.7 it stopped working and returning back to 6.6.2 it didn’t recover. Only way to keep plugins and woocommerce folders loaded is to keep Loco enabled. Please note that I’m only talking about default locations of Woo, not /wp-content/languages/loco/plugins location, which is empty.
Forum: Plugins
In reply to: [WooCommerce] Custom translations overwritten by default stringsSorry but custom translations are supported by Woo by default. It’s not something I hacked in to make it work. It’s a built-in feature that stopped working with the release of 9.4.
I do believe it’s a bug and I believe it’s not outside of support scope as it’s a core issue of Woo
Forum: Plugins
In reply to: [WooCommerce] Custom translations overwritten by default stringsI’ve checked with Loco disabled as well on WP 6.6.2 and the translation is not used. It’s loaded, but not applied, so this has to do something with changes introduced in 9.4 release
Forum: Plugins
In reply to: [WooCommerce] Custom translations overwritten by default stringsTranslations don’t work on WP6.6.2 with Woo 9.6 either, only with Loco, but the default woocommerce.po/mo/php won’t change strings even when loaded.
If Woo wasn’t using the /wp-content/languages/plugins/ it wouldn’t be hard to use custom translations, that’s why the languages/woocommerce was introduced I believe. But if that doesn’t work anymore, I don’t think this is something for “professional” help. I can think of many ways to force my translations, but we’re trying to do things the WP way with WP coding standards etc, so if something like this needs to be “hacked”, it’s probably a bug, isn’t it?
Lastly, this has nothing to do with custom coding. Custom translations are mentioned in official Woo documentation as a way to change strings when needed, because default location for translations is used by Woo.
- This reply was modified 11 months, 1 week ago by morvy.
Forum: Plugins
In reply to: [Packeta] Odstranit druhé logo Packety@aleksandreeu ked mate custom pridane ikony, bol by problem skryt to logo len cez CSS? Inak, nechcem rypat, ale logo na bielom pozadi nie je v sulade s brand manualom 🙂
