I have a domain in two languages. The first works correctly, but when i am logging on the second language, it's redirects me on the white list. How can i fix it? site.com - first language site.com/ru - second language
Hi, Which version of OpenCart are you using? Just to clarify: this is the same OpenCart site, but configured with 2 languages? What do you mean by 'redirects me to the whitelist'?
@Fred_Pinel, i made a mistake. "white page", not "white list". in the second language "oneall sicial" redirects me on the white page. and nothing happens
yes, it's the same site, but in two languages. and second language has url as "site.com/ru"
Hi, How did you set up OpenCart for the other languages with a /ru or /uk URIs? Reason is that by default, the language choice is set in a cookie (and several languages work), while URIs do not change.
Do you have any URLs for your sites for us to check?
Also, we're soon releasing another version with better error handling when the login fails (instead of a white page...).
I noticed, that default (site.com) have page /index.php?route=module/oneall/register&oa_redirect=common/home after logging (and it's ok as i writed earlier)
So similarly what if I'll redirect from /uk/index.php?route=module/oneall&oa_redirect=common/home to this /uk/index.php?route=module/oneall/register&oa_redirect=common/home for example, using htaccess.
Hi, Thanks for mentioning the SeoPro extension. This extension probably interferes with our extension. Quickly browsing through the code: maybe you can try to modify the file: catalog/controller/common/seo_pro.php: comment (place a // at the beginning og the line) line 239: return $link; This is mentioned as a comment in the following line (// (if you want to pass all parameters on homepage as is, comment the line above: `// return $link;`))
You can also try your suggestion, but I think the SeoPro is removing needed parameters.
Finally, the next release of our extension will provide more information on login failures (in the admin log). If needed, I can send you by email the file to edit.
Answers
Which version of OpenCart are you using?
Just to clarify: this is the same OpenCart site, but configured with 2 languages?
What do you mean by 'redirects me to the whitelist'?
Sorry for the questions!
Thanks.
yes, it's the same site, but in two languages. and second language has url as "site.com/ru"
Version 2.1.0.2 (trs-2.1.0.0)
site.com and site.com/uk
The first link is ok,
but the second one stops at the white page with this url
site.com/uk/index.php?route=module/oneall&oa_redirect=common/home
OC ver. 2102 (trs-2.1.0.0)
How did you set up OpenCart for the other languages with a /ru or /uk URIs?
Reason is that by default, the language choice is set in a cookie (and several languages work), while URIs do not change.
Do you have any URLs for your sites for us to check?
Also, we're soon releasing another version with better error handling when the login fails (instead of a white page...).
Regards.
Thank you
I noticed, that default (site.com) have page
/index.php?route=module/oneall/register&oa_redirect=common/home
after logging (and it's ok as i writed earlier)
So similarly what if I'll redirect from
/uk/index.php?route=module/oneall&oa_redirect=common/home
to this
/uk/index.php?route=module/oneall/register&oa_redirect=common/home
for example, using htaccess.
will it work?
Thanks for mentioning the SeoPro extension.
This extension probably interferes with our extension.
Quickly browsing through the code: maybe you can try to modify the file: catalog/controller/common/seo_pro.php:
comment (place a // at the beginning og the line) line 239: return $link;
This is mentioned as a comment in the following line
(// (if you want to pass all parameters on homepage as is, comment the line above: `// return $link;`))
You can also try your suggestion, but I think the SeoPro is removing needed parameters.
Finally, the next release of our extension will provide more information on login failures (in the admin log).
If needed, I can send you by email the file to edit.
Regards
please send me on xxxx what i have to edit.
Thank you.
Thanks.
We sent you the update.
We solved the problem by another method.
in the catalog/controller/common/seo_pro.php
we add: