sf-webdesign Posted September 1, 2013 Share Posted September 1, 2013 (edited) Hi all! After upgrading to Prestashop 1.5.5.0 I got a problem with the translations. I am not able anymore to manage the translations of the front end. This means that i cant edit them. (See attachment). It states that there are no expressions.. However, it is still possible to manage/edit the translations of the backend. Anyone with a solution? or is this a bug? Thanks! Edited September 1, 2013 by sf-webdesign (see edit history) Link to comment Share on other sites More sharing options...
misterpink Posted September 4, 2013 Share Posted September 4, 2013 Hi, sorry for my bad english, i have the same problem, have you resolved this probleme?? Thanks Link to comment Share on other sites More sharing options...
sf-webdesign Posted September 5, 2013 Author Share Posted September 5, 2013 Hi, No I didn't yet.. I have no idea why this error occur. I just used the new version of 1-click upgrade. The weird thing is that the back end translations do show up. Anyone an idea? Or should I put this issue at the issue tracker? Thanks! Link to comment Share on other sites More sharing options...
benjamin utterback Posted September 17, 2013 Share Posted September 17, 2013 Hello all, we have released a new version of the 1-click upgrade module. Feel free to download it and see if the error persists. but FIRST Read these upgrade tips here, http://www.prestasho...0-upgrade-tips/ you can download the new module on our Addons store here http://addons.presta...utoupgrade.html Thank you! Link to comment Share on other sites More sharing options...
sf-webdesign Posted September 25, 2013 Author Share Posted September 25, 2013 Hi! I discovered that I have the same problem when doing a fresh installation. Anyone a solution for this? Or experiencing the same? Thanks! Link to comment Share on other sites More sharing options...
benjamin utterback Posted September 26, 2013 Share Posted September 26, 2013 Can you try to do a Fresh installation in English and then change your language preferences to your language after installation. Your translation fields should show correctly then. Link to comment Share on other sites More sharing options...
sf-webdesign Posted September 29, 2013 Author Share Posted September 29, 2013 I have tried a fresh installation in English and now the problem does not occur. So its a little bug, but there is also a way to bypass Thanks alot! Link to comment Share on other sites More sharing options...
Barzi Posted October 3, 2013 Share Posted October 3, 2013 (edited) Hi , please I have a similar problem which is there are less expressions than it should be for example in the front office header fieldset there are only 4 expressions can anyone help ? Edited October 3, 2013 by Barzi (see edit history) Link to comment Share on other sites More sharing options...
Eduardo Vilar Posted October 4, 2013 Share Posted October 4, 2013 Hi all! After upgrading to Prestashop 1.5.5.0 I got a problem with the translations. I am not able anymore to manage the translations of the front end. This means that i cant edit them. (See attachment). It states that there are no expressions.. However, it is still possible to manage/edit the translations of the backend. Anyone with a solution? or is this a bug? Thanks! I have the same problem after updating to V 1.5.5.0 "stable" I am Unable to do a fresh install since my shop is in production. I'll try the process again manually WITHOUT Module 1-click. But any help to fix this bug is welcome! I have 2 stores in the same situation. WebRep Classificação geral Este site não tem classificação (número de votos insuficientes) Link to comment Share on other sites More sharing options...
benjamin utterback Posted October 4, 2013 Share Posted October 4, 2013 Hi , please I have a similar problem which is there are less expressions than it should be for example in the front office header fieldset there are only 4 expressions can anyone help ? I have the same problem after updating to V 1.5.5.0 "stable" I am Unable to do a fresh install since my shop is in production. I'll try the process again manually WITHOUT Module 1-click. But any help to fix this bug is welcome! I have 2 stores in the same situation. WebRep Classificação geral Este site não tem classificação (número de votos insuficientes) Hello all, please turn on error reporting and let me know what errors you see. I can help you from there. Thank you! Read how to here, http://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-500-error-or-blank-page/ Always make sure to have a backup! 1 Link to comment Share on other sites More sharing options...
Eduardo Vilar Posted October 4, 2013 Share Posted October 4, 2013 Hello all, please turn on error reporting and let me know what errors you see. I can help you from there. Thank you! Read how to here, http://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-500-error-or-blank-page/ Always make sure to have a backup! Hi there! these errors are displayed: Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1104 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1624 Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1104 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1624 Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1104 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1624 Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1104 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1624 Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1104 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1624 Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1104 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1624 Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1104 Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/armazemcruz.com.br/httpdocs/loja/controllers/admin/AdminTranslationsController.php on line 1624 Thank you for your help Eduardo Link to comment Share on other sites More sharing options...
chrasty Posted October 8, 2013 Share Posted October 8, 2013 (edited) Hi,in Prestashop 1.5.6.0 same problem. I can not change language for site and can not translate front office.Multistore is activated PHP: 5.2.17 Warning: preg_match_all() [function.preg-match-all]: Compilation failed: unrecognized character after (? at offset 10 in /var/www/clients/client3/web51/web/controllers/admin/AdminTranslationsController.php on line 1108Warning: Invalid argument supplied for foreach() in /var/www/clients/client3/web51/web/controllers/admin/AdminTranslationsController.php on line 1628 anyone know how to fix it? Thank you Edited October 8, 2013 by chrasty (see edit history) Link to comment Share on other sites More sharing options...
sf-webdesign Posted October 8, 2013 Author Share Posted October 8, 2013 Try install it in the English language. This solved the problem for me. Later you can change to the language you prefer. Let us know of this works Link to comment Share on other sites More sharing options...
chrasty Posted October 8, 2013 Share Posted October 8, 2013 I tried it, but does not work. In 1.5.4.1 it work fine, but 1.5.5.0 and 1.5.6.0 does not work. Link to comment Share on other sites More sharing options...
Azimov Posted October 10, 2013 Share Posted October 10, 2013 I fixed it in 1.5.6.0 Open /controllers/admin/AdminTranslationsController.php on line 1070 change : case 'front': // Parsing file in Front office $regex = '/\{l\s*s=(?|\'('._PS_TRANS_PATTERN_.')\'|"('._PS_TRANS_PATTERN_.')")(\s*sprintf=.*)?(\s*js=1)?\s*\}/U'; break; case 'back': // Parsing file in Back office if ($type_file == 'php') $regex = '/this->l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else if ($type_file == 'specific') $regex = '/Translate::getAdminTranslation\(\''._PS_TRANS_PATTERN_.'\'\)/U'; else $regex = '/\{l\s*s\s*=(?|\''._PS_TRANS_PATTERN_.'\'|"'._PS_TRANS_PATTERN_.'")(\s*sprintf=.*)?(\s*js=1)?(\s*slashes=1)?\s*\}/U'; break; case 'errors': // Parsing file for all errors syntax $regex = '/Tools::displayError\(\''._PS_TRANS_PATTERN_.'\'(,\s*(.+))?\)/U'; break; case 'modules': // Parsing modules file if ($type_file == 'php') $regex = '/->l\(\''._PS_TRANS_PATTERN_.'\'(, ?\'(.+)\')?(, ?(.+))?\)/U'; else // In tpl file look for something that should contain mod='module_name' according to the documentation $regex = '/\{l\s*s=(?|\''._PS_TRANS_PATTERN_.'\'|"'._PS_TRANS_PATTERN_.'").*\s+mod=\''.$module_name.'\'.*\}/U'; break; case 'pdf': // Parsing PDF file if ($type_file == 'php') $regex = '/HTMLTemplate.*::l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else $regex = '/\{l\s*s=(?|\''._PS_TRANS_PATTERN_.'\'|"'._PS_TRANS_PATTERN_.'")(\s*sprintf=.*)?(\s*js=1)?(\s*pdf=\'true\')?\s*\}/U'; break; for : case 'front': // Parsing file in Front office $regex = '/\{l\s*s=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"](\s*sprintf=.*)?(\s*js=1)?\}/U'; break; case 'back': // Parsing file in Back office if ($type_file == 'php') $regex = '/this->l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else if ($type_file == 'specific') $regex = '/Translate::getAdminTranslation\(\''._PS_TRANS_PATTERN_.'\'\)/U'; else $regex = '/\{l\s*s\s*=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"](\s*sprintf=.*)?(\s*js=1)?(\s*slashes=1)?\s*\}/U'; break; case 'errors': // Parsing file for all errors syntax $regex = '/\{l\s*s=[\'\"]'.PS_TRANS_PATTERN_.'[\'\"].*\s+mod=\''.$module_name.'\'.*\}/U'; break; case 'modules': // Parsing modules file if ($type_file == 'php') $regex = '/->l\(\''._PS_TRANS_PATTERN_.'\'(, ?\'(.+)\')?(, ?(.+))?\)/U'; else // In tpl file look for something that should contain mod='module_name' according to the documentation $regex = '/\{l\s*s=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"].*\s+mod=\''.$module_name.'\'.*\}/U'; break; case 'pdf': // Parsing PDF file if ($type_file == 'php') $regex = '/HTMLTemplate.*::l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else $regex = '/\{l\s*s=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"](\s*sprintf=.*)?(\s*js=1)?(\s*pdf=\'true\')?\s*\}/U'; break; Link to comment Share on other sites More sharing options...
chrasty Posted October 10, 2013 Share Posted October 10, 2013 Great Azimov, work fine. Thank you very much Link to comment Share on other sites More sharing options...
Eduardo Vilar Posted October 10, 2013 Share Posted October 10, 2013 I fixed it in 1.5.6.0 Open /controllers/admin/AdminTranslationsController.php on line 1070 change : case 'front': // Parsing file in Front office $regex = '/\{l\s*s=(?|\'('._PS_TRANS_PATTERN_.')\'|"('._PS_TRANS_PATTERN_.')")(\s*sprintf=.*)?(\s*js=1)?\s*\}/U'; break; case 'back': // Parsing file in Back office if ($type_file == 'php') $regex = '/this->l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else if ($type_file == 'specific') $regex = '/Translate::getAdminTranslation\(\''._PS_TRANS_PATTERN_.'\'\)/U'; else $regex = '/\{l\s*s\s*=(?|\''._PS_TRANS_PATTERN_.'\'|"'._PS_TRANS_PATTERN_.'")(\s*sprintf=.*)?(\s*js=1)?(\s*slashes=1)?\s*\}/U'; break; case 'errors': // Parsing file for all errors syntax $regex = '/Tools::displayError\(\''._PS_TRANS_PATTERN_.'\'(,\s*(.+))?\)/U'; break; case 'modules': // Parsing modules file if ($type_file == 'php') $regex = '/->l\(\''._PS_TRANS_PATTERN_.'\'(, ?\'(.+)\')?(, ?(.+))?\)/U'; else // In tpl file look for something that should contain mod='module_name' according to the documentation $regex = '/\{l\s*s=(?|\''._PS_TRANS_PATTERN_.'\'|"'._PS_TRANS_PATTERN_.'").*\s+mod=\''.$module_name.'\'.*\}/U'; break; case 'pdf': // Parsing PDF file if ($type_file == 'php') $regex = '/HTMLTemplate.*::l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else $regex = '/\{l\s*s=(?|\''._PS_TRANS_PATTERN_.'\'|"'._PS_TRANS_PATTERN_.'")(\s*sprintf=.*)?(\s*js=1)?(\s*pdf=\'true\')?\s*\}/U'; break; for : case 'front': // Parsing file in Front office $regex = '/\{l\s*s=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"](\s*sprintf=.*)?(\s*js=1)?\}/U'; break; case 'back': // Parsing file in Back office if ($type_file == 'php') $regex = '/this->l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else if ($type_file == 'specific') $regex = '/Translate::getAdminTranslation\(\''._PS_TRANS_PATTERN_.'\'\)/U'; else $regex = '/\{l\s*s\s*=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"](\s*sprintf=.*)?(\s*js=1)?(\s*slashes=1)?\s*\}/U'; break; case 'errors': // Parsing file for all errors syntax $regex = '/\{l\s*s=[\'\"]'.PS_TRANS_PATTERN_.'[\'\"].*\s+mod=\''.$module_name.'\'.*\}/U'; break; case 'modules': // Parsing modules file if ($type_file == 'php') $regex = '/->l\(\''._PS_TRANS_PATTERN_.'\'(, ?\'(.+)\')?(, ?(.+))?\)/U'; else // In tpl file look for something that should contain mod='module_name' according to the documentation $regex = '/\{l\s*s=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"].*\s+mod=\''.$module_name.'\'.*\}/U'; break; case 'pdf': // Parsing PDF file if ($type_file == 'php') $regex = '/HTMLTemplate.*::l\(\''._PS_TRANS_PATTERN_.'\'[\)|\,]/U'; else $regex = '/\{l\s*s=[\'\"]'._PS_TRANS_PATTERN_.'[\'\"](\s*sprintf=.*)?(\s*js=1)?(\s*pdf=\'true\')?\s*\}/U'; break; Resolved. THANK YOU FOR HELP! Link to comment Share on other sites More sharing options...
benjamin utterback Posted October 10, 2013 Share Posted October 10, 2013 Hey guys, I took the time to make a Pull Request on our GitHub regarding this fix. Our development team got together and saw an issue with Azimov's fix because > .*\s+mod= can crash in certain conditions . Our Development team came up with a more stable fix and I have attached the file here. Please make a backup as you need and replace your classes/admin/AdminTranslationsController.php with this file attached. Let me know if it still works for you. Please make sure to backup AdminTranslationsController.php Link to comment Share on other sites More sharing options...
chrasty Posted October 10, 2013 Share Posted October 10, 2013 Path is: controllers/admin/AdminTranslationsController.php Benjamin your file work fine in 1.5.6.0 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now