« Changelog History


PrestaShop v1.7.6.1 Release Notes

Release Date: 2019-08-26 // over 4 years ago

  • 🛠 Main fixes

    • In some circumstances prices would appear with 6 decimal digits (#14640)
    • The “convert a guest into a customer” feature wasn’t working (#14639)
    • It was possible to circumvent the BO token in some circumstances (Thanks Guillaume Lictevout) (#14671)
    • 🔊 The “erase all” button in the logs page wasn’t working (#14686)
    • Mails weren’t completely translated/translatable (#14633)
    • 🔗 Links pointing to edit/view customers weren’t working on legacy pages like Quick Search (#14672)
    • Prices in Czech would sometimes be displayed using the wrong formatting (#14657)
    • 🔊 Applying filters in the logs page would result in an error (#14785)
    • 🌐 Importing a theme would fail it if contained a translations directory with no files (#14960)
    • 🌐 The translation interface wasn’t working when using a theme other than classic (#14733 and #15133)
    • 🌐 Module translations edited through the new back office interface were being ignored by the module (#14932)
    • Disabled categories were not being shown in the parent category tree when editing categories, resulting in an error (#14790)
    • Accessing the suppliers page after an import would result in an error (#14908)
    • Following steps in the checkout process were being disabled even when the theme didn’t include a “continue” button (#14846)
    • Errors would occur when manipulating orders in some circumstances when working on a multishop environment (#14595 and #15144)

    Important changes

    ⚡️ Following #15173 we had to modify CurrencyDataProviderInterface::findAll and add an optional parameter to be able to fetch all currencies regardless of the current shop context. This doesn’t break any previous use of the method since the parameter is optional, but it requires to update any class that implemented that interface.

    🌐 Following #15139, module translations are no longer attached to the currently active theme. If you want a different translation for each theme, you will have to edit the theme translations; this requires the specific wording to be physically present in the theme's templates or else it won't appear in the translation interface. Only theme translations are attached to a theme now, all other translations are now global.

    Full Changelog