PDA

View Full Version : Solved Can't go back to default language



MikeFara
04-12-10, 05:31
Clicking on the default language flag won't let me go back to English when a foreign language is chosen.

kamilkurczak
04-12-10, 09:58
I saw that on your forum, please paste here your all htaccess rules.
Thanks

MikeFara
04-12-10, 16:46
Started with 4.1 *MAYBE* but not sure.

Thank you so much



RewriteEngine On
RewriteRule ^((urllist|sitemap).*\.(xml|txt)(\.gz)?)$ vbseo_sitemap/vbseo_getsitemap.php?sitemap=$1 [L]
RewriteCond %{REQUEST_URI} !(admincp/|modcp/|cron|vbseo_sitemap)
#Start VBET Rewrite
RewriteRule ^/?(af|sq|ar|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|de|el|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|vi|cy|yi)/$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/ [L,QSA]
RewriteRule ^/?(af|sq|ar|be|bg|ca|zh-CN|hr|cs|da|nl|en|et|tl|fi|fr|gl|de|el|iw|hi|hu|is|id|ga|it|ja|ko|lv|lt|mk|ms|mt|no|fa|pl|pt|ro|ru|sr|sk|sl|es|sw|sv|zh-TW|th|tr|uk|vi|cy|yi)/(.*)?$ vbenterprisetranslator_seo.php?vbet_lang=$1&redirected=/$2 [L,QSA]
RewriteCond %{REQUEST_URI} !(admincp/|modcp/|vbseo_sitemap/|cron)
RewriteRule ^((archive/)?(.*\.php(/.*)?))$ vbenterprisetranslator_seo.php [L,QSA]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !^(admincp|modcp|clientscript|cpstyles|images)/
RewriteRule $ vbenterprisetranslator_seo.php [L,QSA]
#End VBET Rewrite
RewriteRule ^((archive/)?(.*\.php(/.*)?))$ vbseo.php [L,QSA]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !/(admincp|modcp|clientscript|cpstyles|images)/
RewriteRule ^(.+)$ vbseo.php [L,QSA]

kamilkurczak
06-12-10, 10:34
yours .htaccess looks Ok.
I was on your site and I saw that you change a flag image to U.S. flag.
So You've changed a vbenterprisetranslator_flags template.

vBET use cookies to remember forum language. I can't see in your site source this code:

onclick="document.cookie = 'vbet_language=; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/'; return true;"
Please, restore the old vBET template (vbenterprisetranslator_flags or only this code) and it will be work good.

scottct1
06-12-10, 17:17
I am having the same issue on my vBulletin 4.1 install, that you installed with the default templates.

MikeFara
07-12-10, 01:45
yours .htaccess looks Ok.
I was on your site and I saw that you change a flag image to U.S. flag.
So You've changed a vbenterprisetranslator_flags template.


Well thanks for the idea, but no this file was not changed. The images were.

MikeFara
07-12-10, 01:47
vBET use cookies to remember forum language. I can't see in your site source this code:

onclick="document.cookie = 'vbet_language=; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/'; return true;"
Please, restore the old vBET template (vbenterprisetranslator_flags or only this code) and it will be work good.

To explain: It doesn't work and the template was never changed.



<div class="shade footer_copyright" align="center">
{vb:raw linkstitle}
<!--vBET_SNTA--><!--vBET_NRE-->
<div class="vbetflagsbox">
<vb:each from="flags" value="flag">
<a rel="novbseo" href="{vb:var flag.url}" <vb:if condition="$flag['code']==$vbulletin->options['vbenterprisetranslator_forumlanguage']">onclick="document.cookie = 'vbet_language=; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/'; return true;"</vb:if>><img class="vbet-flag vbet-{vb:raw flag.code}" width="16" height="11" src="images/vbet/flags/clear.gif" alt="{vb:var flag.name}" <vb:if condition="$vbulletin->options['vbenterprisetranslator_flags_noborder'] && !$flag['highlight']">border="0"</vb:if><vb:if condition="$flag['highlight']">style="border-style: solid; border-width: 1px; border-color: yellow;"</vb:if>/></a>
</vb:each>
</div><!--vBET_ENTA-->
</div>

MikeFara
07-12-10, 02:12
You may not have been aware of this problem



vBulletin 4.1.0 PL2 Released
There was an issue identified in vBulletin 4.1.0 and 4.1.0 PL1 that may potentially break a number of 3rd party plugins and modifications.
Please note, this issue does not affect the core vBulletin product, but changes that were made to the core vBulletin product may potentially break 3rd party plugins and modifications.

As part of our inclusion of the mobile APIÂ’s, the vBulletin templates were re-factored in how they are rendered to support the API.
The $vbulletin variable was placed so that it was not part of the eval process, and subsequently out of scope for the templates of 3rd party plugins and modifications templates.
Here is an example template conditional that would be affected:

Code:

in group 5, 6 or 7

We have released a patch which now exposes the $vbulletin variable to templates, and should enable such plugins/modifications to work as they did previously.


Patching to vBulletin 4.1 PL2 apparently fixes the problem entirely.

kamilkurczak
07-12-10, 08:38
so , now is fixed?

scottct1
07-12-10, 15:53
It fixed mine. :)

kamilkurczak
07-12-10, 16:08
ok thanks for confirmation

AfrikaansAlbanianArabicBelarusianBulgarianCatalanChineseCroatianCzechDanishDutchEnglishEstonianFilipinoFinnishFrenchGalicianGermanGreekHaitian CreoleHebrewHindiHungarianIcelandicIndonesianIrishItalianJapaneseKoreanLatvianLithuanianMacedonianMalayMalteseNorwegianPersianPolishPortugueseRomanianRussianSerbianSlovakSlovenianSpanishSwahiliSwedishTaiwaneseThaiTurkishUkrainianVietnameseWelshYiddish
Translations supported by vBET 4.9.2