Backoffice partially in English after Update to 1.1.0

[RabbitZzZ]

Hi,

after updating a shop to 1.1.0 parts of the backoffice now only appear in English despite all the expressions are filled in the translations section (and have the translations in there).
For example the order page and the translations page itself are only shown in English.
I also already tried updating the translations and clearing the cache without success.

Any idea how this could be resolved? Is it a bug?

[Occam]

Seems to be even worse. If you clear cache and even import the latest translation files, you will face this issue that the translations are perhaps nearly complete while the whole BO is in English. This even happens for a language like German that provides apart from some minor lacks a full translated thirty bees. This bug is new and first appeared with TB 1.0.1.

[Occam]

No fix, but a bypass:

• If bigger than 49 Bytes save file /translations/<yourlanguage>/admin.php
• Import the English language
• Go to Employees
• Change BO language to English and save
• Change BO language back to your language and save
• Clear cache and recompile
• If this does not help, check length of /translations/<yourlanguage>/admin.php
• If it is now (emptied to) 49 bytes, replace it with the formerly saved file

This should do the trick, provided that your language is fully translated. Check this at Crowdin.

Edited August 29, 2019 by Occam

[Traumflug]

https://github.com/thirtybees/thirtybees/issues/1031

[RabbitZzZ]

This didn't change anything for me. The admin.php has the same size before and after.

[Occam]

Just for the record:

• What language are we talking about?
• Do parts show up or is everything English in BO?
• Considering other weird mistakes you've posted lately:
  What PHP version do you have?
  Are all minimum requirements for thirtybees/Prestashop met?

[RabbitZzZ]

• German
• most parts show up, but for instance translation page and order editing page are in English (haven't checked evrything)
• running on PHP 7.1.3 (also tested on 7.0 -> same), minimum requirements are met

 

Edited September 3, 2019 by RabbitZzZ

[Occam]

 

On 8/29/2019 at 11:37 PM, Traumflug said:

https://github.com/thirtybees/thirtybees/issues/1031

This is not about the size of the admin.php. As the BO is fully translated the admin.php is complete. So why don't you just apply the fix that Karlo Šimunović has proposed in the above topic at Github. Though this does not help cure the strange behavior of AEUC under 1.1.0, it's a step in the right direction. Anyway, I currently wouldn't recommend 1.1.0 in Germany in production mode.

Edited September 3, 2019 by Occam

[RabbitZzZ]

I'm sorry, I didn't actually see that solution. But I tried it and it worked. Thanks!

What's the strange behaviour of AEUC? This shop is in production already. Would it be wise to downgrade? On the other hand the update also fixed some stuff that was wrong before...

Edited September 3, 2019 by RabbitZzZ

[wakabayashi]

18 hours ago, RabbitZzZ said:

most parts show up, but for instance translation page and order editing page are in English (haven't checked evrything)

I can confirm that with german. We have the same issues...

[Occam]

Like I already told @RabbitZzZ you need to apply the the fix proposed by Karlo Šimunović. However, this alone does not solve the cache error which may happen to AEUC from time to time. The hookDisplayProductPriceBlock.tpl will not show up when the Smarty cache is enabled. This is why I patched smarty.config.inc.php, too. In some parts it is a rollback of some improvements by @datakick, who totally dropped assigning variables by reference. Regardless of advices at Stackoverflow like i.e. this one, that assigning variables (with an ampersand prefix) as reference are deprecated in PHP 7 it seems that it still makes a difference. These changes didn't allow my AEUC module to correctly display the hook for tax and delivery costs.

I attach both patched files here: Fix_translations_&_avoid cache_bug for AEUC.zip (removed following the moderator's suggestion)

Edited September 7, 2019 by Occam

[wakabayashi]

@Occam Thanks for your answer. I have seen the fix already before, but I guess this will soon be included in the bleeding edge anyway.

[Occam]

Hmmh ... bleeding what? I'm not so familiar with this kind of insider tb-speak.  I suppose you mean some kind of development version. A link would be fine.

[wakabayashi]

Bleeding edge is a term from the new core updater. It basically means, that the shop will update to the point of all github commits. 

[Traumflug]

On 9/4/2019 at 4:10 PM, Occam said:

bleeding what?

"Blutige Liebe". That's how it got translated to German 🙂