jayhybrid
Forum Replies Created
-
Forum: Developing with WordPress
In reply to: How to escape wp_send_json?Jacob, thank you!
I can’t believe I haven’t considered this, I should have payed more attention to the documentation.
Regards
JayForum: Reviews
In reply to: [Prevent Browser Caching] Thank youHey Kostya
Thank you for the quick fix, really appreciate it! Everything seems to be working just fine now. I have edited my review accordingly.
Regards
JayAh I see, translating a Form does not copy the conditions? Should this be a feature request rather than a bug report?
I actually just updated Contact Form 7 Multilingual to 1.0.2 and checked the conditional Fields for the German version of my Contact Form and they are entirely missing.
There is also no JS error anymore.
Unfortunately, I could not notice a change after replacing the code.
I’m no developer, but it seemed to be a JS related issue to me, since I am getting the above mentioned error on page load of the translated (German) page.
TypeError: conditions.filter is not a function scripts.js:678:44/cf7-conditional-fields/js/scripts.js?ver=1.7.9
Alright, I have set up a fresh WP Installation here (http://debug.hybridsupply.de) and installed
- Contact Form 7
- Contact Form 7 Conditional Fields
- Contact Form 7 Multilingual
- WPML Multilingual CMS
- WPML String Translation
- WPML Translation Management
There is a contact Form with a single field on the first page (which works, as it should): Entering something into the field, triggers some condition and a second field appears.
Using WPML and Contact Form 7 Multilingual (WPML Extension) I have translated the Form, the WPML way and it can be seen in the German Version of the page, yet the conditional logic is not working.
Hi Jules
I just updated to version 1.7.9 and also updated my Contact Form Translation and the issue seems to persist.
Is there anything I can do to help you with this issue?
Thanks
JayHey Marc
In case in helps, here is a list of messages currently in my log:
<!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: WordPress login cookies were detected, In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: WordPress login cookies were detected --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), WordPress login cookies were detected --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The file path is unsuitable for caching (/robots.txt) --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (OPTIONS), In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request extension is not suitable for caching --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST) --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), The request extension is not suitable for caching --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request extension is not suitable for caching, In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD) --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (POST), In the settings, caching is disabled for matches for one of the current request's GET parameters --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD), The request extension is not suitable for caching --> <!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: The request method was not GET (HEAD), The request extension is not suitable for caching, In the settings, caching is disabled for matches for one of the current request's GET parameters -->and many more for various sitemaps
Regards
JayHi David,
seems to be gone now.
Regards
JayHi,
I am using WP 5.3 and WPO Version 3.0.13 and can not confirm this. I am still receiving plenty of messages in my debug.log
<!-- WP Optimize page cache - https://getwpo.com - page not served from cache because: In the settings, caching is disabled for matches for one of the current request's GET parameters -->is one of many messages that are currently flooding my log. I could not find anything in the settings do disable this, what am I missing?
Regards
JayThe automatic upgrade to WordPress 5.2.1 seemed to have fixed the issue for me.