https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails Gravity Support Forums Topic: Multilingual site with qtranslate error handling fails en-US Sat, 04 Apr 2026 08:27:11 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-39073 Thu, 27 Oct 2011 04:31:22 +0000 mauricenaef 39073@https://legacy.forums.gravityhelp.com/ <p>Hi Carl</p> <p>Did you manage to have a look into this with your developer? Any change we will get the forms to work with Qtranslate. I know about WPML, but just as Gfdd, the Sites are already running with the Plugin and I would like them to use this Forms in Translation to!</p> <p>Thanks and regards </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-36093 Fri, 23 Sep 2011 17:55:58 +0000 Carl Hancock 36093@https://legacy.forums.gravityhelp.com/ <p>That is going to be the problem. The URL isn't the same. qTranslate is changing how URL Rewriting functions which causes problems with the form submission process and the form action which uses the current URL. </p> <p>The function above was one a user had posted, we aren't familiar with it and can't reproduce this issue locally because our server environment is different. So it's not something we've been able to recreate in order to test. But I can have our lead developer take another look. </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-36091 Fri, 23 Sep 2011 17:43:16 +0000 Capstone 36091@https://legacy.forums.gravityhelp.com/ <p>Thanks... the site I'm working on was done before WPML was an option, and at this point switching to it isn't a practical solution. qTranslate appends the URL with a language code to handle the language selection. For example, to display the content in Spanish, the URL <a href="http://www.mysite.com/mypage" rel="nofollow">http://www.mysite.com/mypage</a> is changed to <a href="http://www.mysite.com/es/mypage" rel="nofollow">http://www.mysite.com/es/mypage</a>. Is the code snippet above the correct place to add some logic to check the current language and change the URL if needed? </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-36086 Fri, 23 Sep 2011 16:33:32 +0000 Carl Hancock 36086@https://legacy.forums.gravityhelp.com/ <p>I am not aware of any solution. But I know WPML (<a href="http://www.wpml.org" rel="nofollow">http://www.wpml.org</a>) doesn't have this issue so the issue is going to be how qTranslate handles page translations and manipulates/changes WordPress. </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-36084 Fri, 23 Sep 2011 16:29:52 +0000 Capstone 36084@https://legacy.forums.gravityhelp.com/ <p>I'm looking for a solution to this as well. My PHP skills are decidedly lacking, but in looking at kevinfilteau's suggestion above, I wonder if some logic could be added to this function to detect the current language and adjust the URL accordingly:</p> <pre><code>public function get_current_page_url() { $pageURL = &#39;http&#39;; if (RGForms::get(&quot;HTTPS&quot;,$_SERVER) == &quot;on&quot;) $pageURL .= &quot;s&quot;; $pageURL .= &quot;://&quot;; $pageURL .= RGForms::get(&quot;HTTP_HOST&quot;, $_SERVER) . rgget(&quot;REQUEST_URI&quot;, $_SERVER); return $pageURL; }</code></pre> <p>Has anyone else made any progress on a work-around? I'm desperate to resolve this issue. </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-29330 Thu, 07 Jul 2011 12:15:12 +0000 Carl Hancock 29330@https://legacy.forums.gravityhelp.com/ <p>This is an issue on the qTranslate end and how they integrate with WordPress. You would need to notify the qTranslate developers, it would benefit them to fix whatever the problem is because currently we recommend users use the WPML plugin (<a href="http://wpml.org" rel="nofollow">http://wpml.org</a>) for translations specifically because it works with Gravity Forms and they provide an Add-On for translating your forms as well as your pages so you can use one form in multiple languages. </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-29307 Thu, 07 Jul 2011 10:32:45 +0000 mauricenaef 29307@https://legacy.forums.gravityhelp.com/ <p>Any update on this? I get a blank page when a form gets submitted in a non default language to... any help is highly appreciated!</p> <p>regards marcel </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-25671 Tue, 17 May 2011 07:00:37 +0000 Jevgenijs 25671@https://legacy.forums.gravityhelp.com/ <p>I also use qTranslate for WP sites I make. I will look into the issues if they will arise.<br /> Generally, qTranslate uses fairly simple hooks, so I do not really expect any problems.<br /> Will tell you how it goes. </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-25626 Mon, 16 May 2011 16:13:28 +0000 Carl Hancock 25626@https://legacy.forums.gravityhelp.com/ <p>Gravity Forms was working with qtranslate, however that was a year ago and qtranslate may have been updated since then. I would suggest getting in touch with the qtranslate developer as they are going to know their product better than we do in order to debug what is going on. </p> https://legacy.forums.gravityhelp.com/topic/multilingual-site-with-qtranslate-error-handling-fails#post-25621 Mon, 16 May 2011 15:23:23 +0000 gfdd 25621@https://legacy.forums.gravityhelp.com/ <p>Sorry if I sounded rude, I know this is probably not Gravity's fault, but when I bought the license for Gravity Forms last year, you did not report any incompatibilities with Qtranslate nor did the WPML integration exist back then.</p> <p>Now the site we bought Gravity for is finished and developed with Qtranslate and we cannot start from scratch. Still, the forms are not working, which is why I'm asking for some help in debugging/working around the issue right here. </p>