boltzmann_gt Posted April 9, 2020 Share Posted April 9, 2020 Hello, I have a multilingual store, languages are English and Romanian. Default is Romanian. In some places of the backend, the default language inputs won't hide when i select the other language. Like in the screenshots, look at the product title input and the summary textarea: When EN is selected, both inputs are shown (EN and RO). When selecting RO (the default locale) it behaves normal Link to comment Share on other sites More sharing options...
JBW Posted April 21, 2020 Share Posted April 21, 2020 Whats your PHP Version? Link to comment Share on other sites More sharing options...
boltzmann_gt Posted April 23, 2020 Author Share Posted April 23, 2020 PHP Version is 7.2. But i don't see how this is relevant for the problem. It seems to me that is a frontend issue, javascript related. Link to comment Share on other sites More sharing options...
JBW Posted April 23, 2020 Share Posted April 23, 2020 4 minutes ago, boltzmann_gt said: But i don't see how this is relevant for the problem. Because PHP 7.3/7.4 is causing multiple display issues - but seems not relevant for you with 7.2 4 minutes ago, boltzmann_gt said: javascript related. Any errors in the Javascript console? Link to comment Share on other sites More sharing options...
boltzmann_gt Posted April 23, 2020 Author Share Posted April 23, 2020 No errors in the console. The default locale translation input has a class "visible", and this class is defined in theme.css (admin123/themes/new-theme/public/theme.css) ".translation-field{display:none}.translation-field.visible{display:block}" However, since this class is not set at page render, because it's not in the file that seems to me it's responsible for this render (src/PrestaShopBundle/Resources/views/admin/TwigTemplateForm/bootstrap_4_layout.html.twig) i can only assume it's added after by some javascript. Link to comment Share on other sites More sharing options...
boltzmann_gt Posted April 23, 2020 Author Share Posted April 23, 2020 Found the culprit. A module that was installed together with the front end theme was creating this problem. I disabled the module, cause i wasn't using it anyway and now it works fine 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