nadine
Forum Replies Created
-
Awesome! I just bought the Pro version some days ago and it works now.
Ok, thanks for the information. Then I will buy the Pro version. It’s an amazing plugin. Thanks for all your work! ??
Thanks for all your suggestions. Atm I use the following:
- YOOtheme 4.1.5 (there is a newer version 4.2.6 available)
- Essentials YOOtheme Pro 2.0.19 (there is a newer version 2.1.0 available)
- Falang for YOOtheme 1.11 (there is a newer version 1.12 available)
So, first I will update everything and they try again. Unfortunately, I don’t have a video software available atm. If it still doesn’t work after the updates I will contact YOOessentials support. Thanks.
Edit: I just updated Essentials YOOtheme Pro to the latest version 2.1.0 and Falang for YOOtheme to the latest version 1.1.2 . Still the same. Will update the theme this evening.
- This reply was modified 1 year ago by nadine.
The option was unchecked and I checked it in Falang settings. However, the behavior is still the same. This is the AJAX request: https://link.storjshare.io/s/jvg2smsk26z46lm3ddba7fexdx5q/demo-bucket%2FAJAX%20req.PNG
As you can see in the screenshot the English message is still displayed although it’s sent from the German page.
Yes, here are the screenshots:
FA languages: https://link.storjshare.io/s/juv5ffkt2flhrllw67hk2dmybeuq/demo-bucket%2FFA%20languages.PNG
After submit actions:
https://link.storjshare.io/s/jvz4nerwsua3upt3qeg33c62hgmq/demo-bucket%2FAfter%20submit%20actions.PNGFA condition EN:
https://link.storjshare.io/s/jwbn4rgruce4kkkwkkrjyekqmhja/demo-bucket%2FFA%20condition%20EN.PNGFA condition DE:
https://link.storjshare.io/s/jurmge5gsg3fshl5vebae2eh7x4q/demo-bucket%2FFA%20condition%20DE.PNGAh thank you. I watched the instructions on your page and used the language conditions. English for the English message and German for the German message. Still, the English message is always displayed even if the contact form was sent from the German site. Any advice on that?
Forum: Plugins
In reply to: [Falang multilanguage for WordPress] Compatibility with PHP 8.2I can confirm the warnings disappeared when updating. Thanks a lot for your great work!
Forum: Plugins
In reply to: [Falang multilanguage for WordPress] Compatibility with PHP 8.2Awesome! ?? I just spotted some further deprecation notices I didn’t mention in my initial post. Just wanted to add them here, so that you can catch them too. ??
Deprecated: Creation of dynamic property Falang\Core\Language::$term_group is deprecated in /var/www/wordpress__4/wp-content/plugins/falang/src/Falang/Core/Language.php on line 53
Deprecated: Creation of dynamic property Falang\Core\Language::$parent is deprecated in /var/www/wordpress__4/wp-content/plugins/falang/src/Falang/Core/Language.php on line 53
Deprecated: Creation of dynamic property Falang\Core\Language::$count is deprecated in /var/www/wordpress__4/wp-content/plugins/falang/src/Falang/Core/Language.php on line 53
Deprecated: Creation of dynamic property Falang\Core\Language::$filter is deprecated in /var/www/wordpress__4/wp-content/plugins/falang/src/Falang/Core/Language.php on line 53
Deprecated: Creation of dynamic property Falang\Core\Language::$flag_code is deprecated in?/var/www/wordpress__4/wp-content/plugins/falang/src/Falang/Core/Language.php?on line?63
Deprecated: Creation of dynamic property Falang_Public::$nav_menu is deprecated in /var/www/wordpress__4/wp-content/plugins/falang/public/class-falang-public.php on line 2795
Deprecated: Creation of dynamic property Falang_Public::$user_profile is deprecated in /var/www/wordpress__4/wp-content/plugins/falang/public/class-falang-public.php on line 2795
Deprecated: Creation of dynamic property Falang_Public::$widget_pages is deprecated in /var/www/wordpress__4/wp-content/plugins/falang/public/class-falang-public.php on line 2795
Deprecated: Creation of dynamic property Falang_Public::$woocommerce is deprecated in?/var/www/wordpress__4/wp-content/plugins/falang/public/class-falang-public.php?on line?2800
Hi @bojankatusic ,
Thank you for your reply. While the mentioned deprecation seems to be fixed, there are still some other deprecations. Can you please make sure that these deprecations will be fixed too?
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/wordpress__4/wp-content/plugins/mainwp-child/class/class-mainwp-child-updraft-plus-backups.php on line 1900
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/wordpress__4/wp-content/plugins/mainwp-child/class/class-mainwp-child-updraft-plus-backups.php on line 3361
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/wordpress__4/wp-content/plugins/mainwp-child/class/class-mainwp-child-updraft-plus-backups.php on line 3362
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/wordpress__4/wp-content/plugins/mainwp-child/class/class-mainwp-child-updraft-plus-backups.php on line 3511
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /var/www/wordpress__4/wp-content/plugins/mainwp-child/class/class-mainwp-child-updraft-plus-backups.php on line 3512
Deprecated: Using ${var} in strings is deprecated, use {$var} instead in?/var/www/wordpress__4/wp-content/plugins/mainwp-child/class/class-mainwp-child-updraft-plus-backups.php?on line?3512
Thank you and best
Forum: Plugins
In reply to: [Falang multilanguage for WordPress] Compatibility with PHP 8.2Awesome, thank you! ?? Do you already have a time frame when the next version will be released?
Forum: Plugins
In reply to: [Broken Link Checker] Instagram and YouTube links falsely reported brokenHi Patrick,
Thanks for getting back to me. Yes, we use the local broken link detection. No, haven’t tested Cloud engine yet. Would you recommend this? And we have no YouTube API Key saved. Should we add one?
Thanks and best
NadineForum: Plugins
In reply to: [Wise Chat] Chat not working (HTTP 400 error messages)Hello @marcinlawrowski ,
Thank you for your answer. I just did a brief plugin analysis and temporarily deactivated the following plugins and deleted cache.
- Borlabs Cookie
- Autopimize
These seemed to be the most suspicious ones to potentially interfere with Wise Chat. However, the error was still the same. I read the article you posted and I want to point out that I receive HTTP 400 which means “Bad request”. So, it’s unlikely to be a permission issue as implied in the post.
Also worth mentioning that Wise chat has worked on the same site with the same theme and plugins in the past. What else could be the cause for the HTTP 400 errors?
Thank you and best
NadineOk, thank you. Waiting for your feedback on this.
Ok, I just raised a ticket on your website.