Daniil S.
Forum Replies Created
-
Seems the developers are not that active…
Hi again! The correct metafield name is “_wc_gla_availabilityDate”, with this corrected in the latest code snippet everything works flawlessly. A big thanks to you!
Hay, thank you for your reply! Tried it now, unfortunately not doing anything – also no errors in the server PHP logs or anything. Just silently not doing anything ?? Tried to run the CRON task manually, no luck as well. Trying to debug now, but can’t seem to find where it actually fails.
Regarding your code, can i add it to the child theme “functions.php” or does it have to go to “themes.php”?
Awesome, thanks a lot! This looks brilliant!
Hi, thanks a lot for the hint! We normally use a bulk editing plugin “PW Bulk Edit” but unfortunately it can’t see the atteibutes of the “Google Listing & Ads” plugin. I will try the plugin suggested by you, if we get a “NO” from the devs in this topic.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 messes translations up@takayukister Maybe you could add the possibility to change the locale of each contact form from the admin page even after creation of the form?
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 messes translations up@vr2008 Could you kindly point me to the right location in the database to change my forms locale? Thanks in advance!
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 messes translations upDear Takayuki,
thank you for your confirmation, but i don’t quite understand the question. As from your reply i see that you supposedly found the cart and saw that partially the cart is shown in Englisch, partially in German. The problem is, it should all be German – which it is, if i disable CF7. The problem seems to be exactly what the commenters “astronim” and “vr2008” described which from my point of view is a terrible design decision – no plugin, especially one that has actually nothing to do with translations, should be allowed to mess with the front end language in any way.
To “astronim” and “vr2008”, thank you guys, this was of huge help!
Best Regards
Dan.Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 messes translations upHi, please follow the steps below to see the effect. I will enable CF7 (temporary) so the translations are get affected by the problem.
1. Visit: Wechselstrom-Labornetzger?t 0 … 300Vrms 0 … 25A 3kVA – DF-S5103 (laborance.de)
2. Add the product to cart.
3. Go to cart and follow to cheack-out.
4. You will see that some texts are German, while some are Englisch.
The website’s original language is German, and as i said if i disable CF7 everything is in German, while if i enable CF7 some terms are translated to Englisch. This is not affected by any other plugins or themes, as i tried disabling them all except for WooCommerce and CF7.
If you have any questions, please contact me!Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 messes translations upHi, in the Cart and Checkout process pages mainly.
Br. Dan
Hello @amagsumov,
thank you for your reply.
In my case i disabled the plugin in the database, so now it is listed as “disabled” in the plugin directory. I have now updated all websites manually, thank you any way.Hi Safronik,
thank you for your reply.
Maybe you could still issue an update with a higher version just for all users to update ? We have just disabled the faulty plugin version 5.126 on all of our websites, and we would like to update automatically to the fixed version on all of our websites so it would be great if you could issue a technical update of the fixed version with a version number 5.127.Best
Dan.
Forum: Plugins
In reply to: [W3 Total Cache] Minify JS file Exclusion not working on IISHi,
wanted to say thank you again for the quick reply, the 500 failure was not relate to your fix – was a different plugin which updated to a faulty version exactly when i tested your edit.
Best
Dan.
Hi,
as far as i understand the originally released version 5.126 was faulty (crashed 5 of our WP shops), and you rolled it back to 5.125. Then you released a fix, with the same version number 5.126 – from my point of view this is a critical failure because those who updated to the faulty version 5.126 do not receive the new fix, until they manually remove the plugin and re-install. The correct way of issuing the fix would be to update it to a higher version, for example 5.127 so it gets updated automatically on the affected wp sites.
Best
Dan.
- This reply was modified 5 years, 6 months ago by Daniil S..