Quantcast
Channel: PrestaShop Developers' blog
Viewing all 939 articles
Browse latest View live
↧

PrestaShop Core Weekly - Week 21 of 2021

June 1, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 24th to Sunday 30th of May 2021.

Core Weekly banner

General messages

Dear Developers,

In case you missed it, 1.7.8 beta has been released yesterday! Please read the Release Note then help us testing it. We are looking for all kind of feedback, especially from module developers to find out if their modules behavior is correct with this new version. Docker images are also available for this beta version.

Another PrestaShop release is also making its way to the stage: PrestaShop 1.7.7.5 patch version has been delivered to QA team who is running the standard patch release test campaign to validate it.

In the meantime, in the PHP ecosystem, Symfony released Symfony 5.3.0. What a great week for releases!

Releases

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

Back office

  • #24649: Remove irrelevant “todo” reminder. Thank you @zuk3975
  • #24628: Add router to defined javascript components. Thank you @zuk3975
  • #24555: Fix for product combination quantity change in RTL panel . Thank you @samberrry

Front office

  • #16138: Fixed the bad discount amount for specific prices. Thank you @levyn

Installer

Tests

Code changes in the ‘1.7.7.x’ branch

Back office

  • #24576: BO - New Order - Empty gift message is not a null value, by @Progi1984
  • #24565: Order View - Discount Modal - Disable submit until name is filled, by @Progi1984

Code changes in modules, themes & tools

Core Weekly Generator tool

Customer reassurance block module

Faceted search module

User documentation landing page

Changes in developer documentation

Buy button lite module

QA nightly results

Wishlist block module

Stylelint browser compatibility plugin

stylelint configuration

OnBoarding module

Example modules

DocToolsBundle

Product Comments module

  • #102: Fix duplicated id for review tables. Thank you @SD1982

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @NeOMakinG, @jolelievre, @Progi1984, @dependabot[bot], @kpodemski, @PierreRambaud, @GabrieleMartini, @zuk3975, @nesrineabdmouleh, @PululuK, @mvorisek, @boubkerbribri, @JevgenijVisockij, @okom3pom, @samberrry, @SD1982, @arouiadib, @eternoendless, @matthieu-rolland, @atomiix, @levyn!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧
Search

Do you speak PrestaShop? – May 2021 edition

June 2, 2021, 5:00 pm
$
0
0

Contributing to PrestaShop is not only about the code, it is also about taking part in the PrestaShop translation project! This report will tell you how the translations of the software evolved in May!

Crowdin Monthly banner

Project news

New 1.7.8 strings are available for translation

The catalog of 1.7.8 translations has recently been added to Crowdin. This means that the completion rate for all projects has slightly decreased. Some projects that used to be 100% translated and validated are no longer complete. Translators, proofreaders… your project needs you! Feel free to take a look at the new translations and help your language reach 100%!

The reward program is back

In 2020, because of the sanitary crisis, our headquarters were closed and we were not able to send gifts to the top translators. But after a year, it was time to bring this reward program back to life! We also took the opportunity to reset the counters. From now on, we will only take into account the words translated from January 1, 2020. Last week, we sent about 20 packages to the top translators of the year 2020. Don’t forget to check your mailbox if this is your case. :mailbox:

Jiří VALT already received his package, and sent us a picture of the gift with a nice message! Thank you again for your involvement in the Czech project Jirka!

Jirka's goodies reward program

:two_hearts: Special thanks to newcomers

Many people subscribe to the project(s) of their choice each month, but not so many start translating straight away. For that reason, we would like to thank R0b3rt020 who rushed into the effort immediately! Thank you very much Robert!

A few stats

  • 16 members were active on the project this month.
  • A total of 5,592 words have been translated and 5,775 validated.
  • All this in 14 different languages.

Thank you for your involvement!

Top contributors

A lot of you are working every day on Crowdin to have PrestaShop available in many languages, and PrestaShop cannot thank you enough for your dedication! Here are the most active translators and proofreaders for May 2021.

Top 10 translators in May:

 TranslatorLanguage# Words
1.‫‬ Girdman.com (anargaragezov)Azerbaijani1,516
2.SNor42Hungarian1,119
3.Lauri Lepik (laurilllepik)Estonian1,010
4.mirmalEsperanto384
5.Begi Ganellari (begiganellari1997)Albanian349
6.Сергій Мацапура (mazapura)Ukrainian272
7.M. Mirena (mmirena)Albanian232
8.A. L (roynsdx)Arabic210
9.Ahmad Abu Ashour (gpsarab)Arabic110
10.Gabriel Tenita (ggedamed)Romanian109

Top 5 proofreaders in May:

 ProofreaderLanguage# Words
1.SNor42Hungarian3,134
2.Girdman.com (anargaragezov)Azerbaijani1,665
3.M. Mirena (mmirena)Albanian414
4.A. L (roynsdx)Arabic344
5.Gabriel Tenita (ggedamed)Romanian94

Congrats, and welcome to our new top contributors! :clap:

Remember, you can see who has been contributing to our translation project thanks to the Translators page.

Complete translations

Fully available languages

At the end of May, PrestaShop 1.7.7 was fully available (= 100% translated and validated) in 18 languages:

BosnianChinese traditionalDanishEnglish
FinnishFrenchGreekHebrew
ItalianLithuanianPersianPortuguese, Brazil
RomanianSerbianSlovakSlovene
Spanish, SpainSwedish  

Thank you all for your contribution!

Almost fully translated languages

Korean, Polish, and Czech are 99% translated. Almost there! :muscle: If you would like to contribute to these projects, do not hesitate to join us on Crowdin.

Note that Turkish, that appeared in this category last month, was 100% translated at the end of May. That is great, thank you to all the Turkish translators!

Languages with the best evolution

The following languages had the best progress thanks to the translation community:

  • Hungarian (+6% to reach 83% validated)
  • Azerbaijani (+2% to reach 36% validated)
  • Estonian (+2% to reach 100% translated :tada: )

Congratulations! :muscle:

Best translation progress in May 2021

A huge thank you to all the contributors!

Of course, this is highlighting the languages that made some progress with new translations; but it does not mean that the languages that are not mentioned here are not active. Indeed, some editing and rewriting could be going on, but the percentage of translation would not be modified (since it is working on strings that are already translated). So let’s not forget about the work of other contributors! Thanks to you too!

If you have not joined us on Crowdin yet, it is never too late! :wink:

If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let me know: I will include a word about it in the next monthly report.

↧
↧

PrestaShop Core Weekly - Week 22 of 2021

June 6, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 31th of May to Sunday 6th of June 2021.

Core Weekly banner

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

  • #24782: Check that $session is set before using it. Thank you @tswfi
  • #24760: Drop leftover code, /tools/http_build_url/ was removed. Thank you @mvorisek
  • #24757: Make getValue more strict to avoid false negative. Thank you @RomainMazB
  • #24701: Deprecate Tools::safePostVars method. Thank you @mvorisek

Back office

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

  • #24771: Build assets, by @Progi1984
  • #24679: Fix free shipping cart rule should not be recomputed when PS_ORDER_RECALCULATE_SHIPPING is false, by @atomiix

Code changes in modules, themes & tools

Core Weekly Generator tool

Product Comments module

Changes in developer documentation

User documentation landing page

PrestaShop Specifications

OnBoarding module

Docker images

Gamification module

Customer reassurance block module

Faceted search module

Email Alerts module

Wishlist block module

Image slider module

Google Sitemap module

Example modules

  • #65: Bump dns-packet from 1.3.1 to 1.3.4 in /example_module_mailtheme. Built by @dependabot[bot]
  • #63: Add JavaScript example of ‘how to manage custom grid action’ in demoextendgrid module . Thank you @zuk3975

MJML Theme Converter

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @dependabot[bot], @NeOMakinG, @Progi1984, @matthieu-rolland, @boubkerbribri, @prestaforum, @tswfi, @kpodemski, @mvorisek, @RomainMazB, @marionf, @jolelievre, @atomiix, @sowbiba, @zuk3975, @micka-fdz, @PierreRambaud, @SD1982, @GabrieleMartini, @nesrineabdmouleh, @PululuK, @MatShir, @okom3pom, @Quetzacoalt91!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧

1.7.8 is ready for translation

June 10, 2021, 12:00 pm
$
0
0

1.7.8 strings are available for translation

As you probably noticed with the announcement of the beta release a few days ago, PrestaShop 1.7.8 is on its way! While it brings new features, this new version also means new strings. A file containing all 1.7.8 strings has been pushed to Crowdin, and is ready for translation!

Translators, proofreaders… your project needs you! Feel free to take a look at those new strings and help your language reach 100% translation. :muscle:

In this article, I will address the key elements of the translation process of this new catalog.

Help us translate PrestaShop 1.7.8

New strings & completion rates

If you visited Crowdin in the last few days, you probably noticed that the completion rates for all projects have slightly decreased and that the projects that used to be 100% translated and validated are no longer complete. Don’t worry, that’s completely normal as new untranslated and unapproved strings were added to the project. In order to get back to a 100% completion rate, all the new strings should be translated and validated.

Mistakes in the source strings

Even though the wording is always reviewed when a pull request is submitted, some mistakes could have been missed. So, don’t hesitate to let us know if you notice something wrong so that we can correct it. Note that, despite the string freeze, we will wait about 2 or 3 more weeks before adding the corrections to Crowdin. After that, we won’t be able to add any new wording. If you spot a mistake, please tag me (@Julievrz) in the “Comments” section of the string, or contact me directly!

Context

As the 1.7.8 version has not been released yet, some strings may appear a bit unclear because of the lack of context. If this is the case, please don’t hesitate to ask for help! You can open an issue in the “Comments” section of a string and I will do my best to answer your questions. In any case, don’t forget that you will still be able to modify the translations when the new version is released.

A note on plural form

In the software copywriting, (s) used to be added at the end of a word to indicate that it could be both singular and plural. For example: “There are %NbItems% item(s) in your cart”. We realized this was not the best option, as some languages have more than one plural form and therefore complicates the translation work. For the 1.7.8 catalog, we decided to improve the way plural is handled on PrestaShop.

You will see strings that contain both the singular and the plural forms, separated by a vertical line. The appropriate string will be selected depending on the number of items, for example:

Are you sure you want to delete the selected image?|Are you sure you want to delete the %filesNb% selected images?

When translating these strings, you should always start with the singular form and then the plural form, separated by a vertical line, without space, just like this:

singular|plural

Sometimes, it can also look like this:

0|singular|plural

For instance, in English we would say 0 items, 1 item, some items:

items|item|%NbItems% items

Let’s keep in touch on Slack! :email:

Until now, to exchange with the community, we used the “Discussions” tab on Crowdin. But this option seemed a bit limited as it is not possible to share images, and there is little interaction. That’s why we decided to open a Slack channel dedicated to the PrestaShop translators. On this channel, I will share information about the translation project. You will also be informed about the publication of the Crowdin monthly report. Of course, you will also be able to ask questions, suggest ideas, or get in touch with other translators.

I think the publication of the new 1.7.8 strings is the perfect time to start a discussion, so don’t hesitate to join us on the PrestaShop Open Source Slack! When you’re in, you will be able to join the #translation channel.

↧

Release of PrestaShop 1.7.7.5

June 14, 2021, 5:00 am
$
0
0

PrestaShop 1.7.7.5 is now available. This maintenance release fixes 19 regressions reported since the 1.7.7.0.

1.7.7.5 is available!

We suggest upgrading your shop quickly in order to benefit from these fixes. Of course, don’t forget to backup before.

Main fixes

Back-office

Front-office

Core

Acknowledgements

Contributors to this patch version, from both the Core team and the community at large:

Progi1984, boubkerbribri, PierreRambaud, SD1982, dali-rajab, atomiix, IcarusSosie and NeOMakinG

Thank you!

Download PrestaShop 1.7.7.5 now!

For any upgrades problems or PrestaShop’s bugs, please create a new issue here.

If you have questions or need help, do not hesitate to take a look at our community platforms or support plans.

Since version 1.7.7.5 is a “patch” update to version 1.7.7, upgrading from any 1.7.7 version will be easy: features will work better, and modules & themes which worked fine on 1.7.7.x will work just as well with 1.7.7.5. Upgrades from a standard 1.7.x version should work just as well.

↧
↧

PrestaShop Core Weekly - Week 23 of 2021

June 14, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 31th of May to Sunday 6th of June 2021.

Core Weekly banner

General messages

Dear developers,

PrestaShop 1.7.7.5 was released on June 14, 2021. This maintenance release fixes 19 bugs reported on previous 1.7.7 versions.

We also celebrate two other notable releases from past week: Linklist module v5.0.0 and… PHP 8.1 Alpha 1!

By the way, PrestaShop 1.7.8.0 beta was released 2 weeks ago now. Have you tested it yet? Remember that only two weeks are left in the beta phase. The next step is the Release Candidate (RC) – any bugs found at RC stage will delay the final release date. Now is the best time to look for issues!

Releases

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

  • #24854: Fix typo in comments of class Mail. Thank you @comxd
  • #24834: Check if regeneration is wanted before checking filesystem. Thank you @RomainMazB
  • #24634: Remove _PS_SMARTY_DIR_ pointing to no longer existing directory. Thank you @mvorisek

Back office

Front office

  • #24846: Remove extracted comments from webpack config of core JavaScript, by @NeOMakinG
  • #24792: If the product has no combinations then the specific_references must be filled in. Thank you @levyn
  • #24738: Add a hook ‘actionValidateOrderAfter’, This hook is called after the complete creation of an order. Thank you @olecorre
  • #24730: Add product page link and move download in order details. Thank you @marekjedrzejewski

Code changes in modules, themes & tools

Quality Assurance module

Example modules

Customer reassurance block module

Faceted search module

Changes in developer documentation

  • #1034: Explain how deprecate a service, by @Progi1984
  • #1033: Add note about use of underscores in module’s main class name. Thank you @muyncky
  • #1030: Fix services decoration doc. Thank you @PululuK
  • #999: Document CLI Context loader Console, by @matks
  • #996: Add Router Dispatcher component, by @matks
  • #988: Explain collapsable right sidebar that contains documentation , by @matks
  • #835: Integrate CQRS commands and queries references, by @jolelievre

Translation Files repository

Stylelint browser compatibility plugin

stylelint configuration

OnBoarding module

User documentation landing page

PrestaShop Specifications

Product Comments module

Issues Bot

  • #21: Add label topwatchers if number of comments or positive reactions >= 5, by @sowbiba

The PrestaShop open source project

  • #43: Add ip right policies for PrestaShop open source user groups, by @ttoine

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @PierreRambaud, @NeOMakinG, @dependabot[bot], @Prestaworks, @Progi1984, @micka-fdz, @boubkerbribri, @jolelievre, @nesrineabdmouleh, @matthieu-rolland, @matks, @muyncky, @atomiix, @juraj1000, @sowbiba, @PululuK, @comxd, @RomainMazB, @kpodemski, @jf-viguier, @levyn, @olecorre, @marekjedrzejewski, @mvorisek, @Shagshag, @eternoendless, @ttoine!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧

Multistore feature in PrestaShop 1.7.8: What’s new?

June 16, 2021, 2:00 am
$
0
0

With the release of the new version 1.7.8 which is in progress, this article details one of the main features revamps of this version: the multistore.

The multistore feature allows merchants to manage several front offices through a single back office. It’s frequently used by merchants who sell in different countries and therefore have different languages and/or currencies. It is also used by merchants who do both B2B and B2C. And it is more rarely used by merchants who have several brands.

We are thrilled to introduce you to the new features and changes around the multistore feature. But before jumping into the features awaiting our users in this new version, we would like to share our research and conception process.

Firstly, why rethinking this feature?

The multistore feature was introduced in PrestaShop 1.5 and had not been reworked for many years. In addition, some features of the multistore having disappeared with the Symfony migration, this feature was becoming particularly unattractive. It was also hard to use in the back office because of its old interface that led to misunderstanding and configuration errors for users.

In late 2019, the PrestaShop Product team decided to revamp the multistore feature in the back office. At the origins of this project was a thorough investigation to understand the main pain points.

This decision opened an opportunity to revamp the multistore feature which would be more understandable and easier to use.

A long process to ensure the full success of the revamp.

First, to have a better understanding of our users’ pain points, we interviewed merchants with a different number of shops and different business activities such as B2B / B2C, selling in different countries. We also interviewed web agencies of different sizes.

Secondly, we made a competitive analysis to identify opportunities and threats.

Then, once the pain points were well understood and with better knowledge of the market, the Product team and Product designers organized mockup tests to present different solutions to users.

Finally, pain points encountered were addressed with a new user interface, new features, and more information messages.

Now, let’s present these changes.

I. The new color system and multistore header

One of the main difficulties for the merchants was to know which store they were configuring in the back office and this was bringing a lot of configuration errors.

To solve this problem, a color picker was added to choose a color for each group and shop. The color can be configured while creating or editing the group or the shop (in the back-office > Advanced parameters > Multistore).

The new multistore colorpicker

Once configured, the color is displayed in the new multistore header, when a group or a shop is selected, making it easy for the user to know what shop he/she is working on.

The new multistore header

If you have existing groups and shops without colors, the default color is light grey. We highly recommend editing them to add a personalized color. By the way, it’s possible to change it by clicking directly on the color icon, before the name of each group and shop in the drop-down of the header.

The new multistore drop-down context

Edit color

Please note, the “all shops” context is blue by default and this color can’t be changed.

Multistore all shops context

The new header

The new multistore header is displayed on Symfony pages and is more visible than the old shop context selector, still present on legacy pages. Merchants can find in this header everything related to the multistore feature and can perform several actions:

  • Changing context through the drop-down: Select “All shops” context to apply a change to all stores, select a group of shops to apply changes to all the stores of this group, or select a specific store.
  • Changing context through the search bar with autocompletion: allows you to search and select a shop or a group quickly, this is particularly helpful if you have a lot of shops.
  • Configure URL: This link is displayed if no URL has been configured, it redirects to the shop URL edition page and allows to add the URL of the shop.
  • View my shop: This link is displayed if an URL has been configured and opens the shop front office to quickly have access to your store.

II. Checkboxes

Checkboxes are displayed in a specific shop context and a group context. They are displayed before each field/toggle/parameter and allow merchants to apply specific settings to a store or a group of shops. Merchants just need to select the parameter to modify, bring their modifications, and then save.

When checkboxes are not selected, the fields or toggles are disabled.

Checkboxes allow:

  • to select one or many fields/toggles
  • to enable selected fields/toggles
  • to apply a different configuration for the selected store or group
  • the merchant to see which parameters have a different value for the selected store or group

Multistore checkboxes

For now, they have been implemented only on the Maintenance page of the back office. It will be implemented on the pages not yet migrated during the Symfony migration. For the pages already migrated in Symfony, we are looking for developers to implement it, so if you are willing to do this, please let us know in a comment :)

III. Specific settings drop-down

This drop-down is displayed in the “all shops” context and group contexts. It allows you to see which settings have been customized in one or several specific shops. And therefore, the settings that will not be overridden following a change made in “all shops” or in a group context.

For now, it has been implemented only on the Maintenance page of the back office. It will be implemented on the pages not yet migrated during the Symfony migration. For the pages already migrated in Symfony, we are looking for developers to implement it, so if you are willing to do this, please let us know in a comment :)

Search bar

In the specific settings drop-down, there is a search bar with auto-completion allowing you to search and select a shop or a group quickly. If the user chooses one of the listed results, it is automatically selected as context.

In the specific settings drop-down there are:

  • The shop groups’ names with a link to select them as context
  • The shops’ names with a link to select them as context

Next to each shop name, there is a mention:

  • “Inherited” if the parameter has the same value as in the “all shops” context
  • “Customized” if the parameter has a different value in a specific shop

Multistore specific settings dropdown

IV. Information messages

Many information messages have been added on different pages and in different locations of the back office to provide better assistance, to inform of some behaviors as early as possible, and to avoid misunderstandings.

For example, some pages are available only in the “all shops” context, and consequently, when you arrive on these pages, the context automatically switches to “all shops”. To prevent any issue, an information message has been added: “Note that this page is available in all shops context only, this is why your context has just switched.”

V. Modules

Another pain identified during the user research step, was the difficulty of knowing whether a module is compatible with the multistore or not.

To solve this problem the first thing to do was to define the notion of compatibility. A module can be :

  • compatible,
  • partially compatible,
  • incompatible
  • or not concerned with the multistore compatibility.

A module is considered compatible with the multistore feature when it can be either:

  • configured differently from one store to another;
  • configured quickly in the same way on all stores thanks to the “All shops” context or the group of shops;
  • or even activated for one store and deactivated for another.

A partially compatible module means that some of its options may not be available or may not work in a multistore context.

An incompatible module means that its configuration applies to all stores.

A module may also not be concerned with multistore compatibility. For example, a captcha module will have the same configuration for all stores.

The second thing was to indicate for each module their compatibility or not with the multistore.

For native modules’, we have indicated the multistore compatibility in the readme.md of each module.

Modules developers can now indicate the multistore compatibility in the source code of their module, by declaring a multistoreCompatibility attribute, and give it one of the following constants as a value: MULTISTORE_COMPATIBILITY_YES, MULTISTORE_COMPATIBILITY_PARTIAL, MULTISTORE_COMPATIBILITY_NO, or MULTISTORE_COMPATIBILITY_NOT_CONCERNED. Example: public $multistoreCompatibility = self:: MULTISTORE_COMPATIBILITY_YES

This way, the multistore compatibility is indicated for merchants in their back office for the installed modules. This information is displayed when clicking on the “read more” link of installed modules in the Module Manager section.

Multistore module compatibility

The third thing was to help contributors to develop & make their modules compatible with multistore. For this, an example module has been developed and the multistore developer documentation has been updated.

VI. Linklist module

The linklist module allows displaying links such as Terms & conditions, new products, contact, sitemap … in the footer.

Many users complained about the fact that the linklist module wasn’t compatible with the multistore feature, as it was quite annoying for their activity, not being able to have different links in their footer.

This is why we decided to make this module compatible with the multistore and this was made possible thanks to the great work of Krystian Podemski :pray:

To do so, a feature has been added, and you must already know it because it is present on other pages. It’s the shop association block. You know, this block allows you to choose which shop(s) the element will be associated with while creating or editing it?

Multistore shop association block

The new multistore header has also been added to the linklist module.

The linklist module version 5.0.0 is now 100% compatible with the multistore feature and can be used for shops using PrestaShop 1.7.8 version and above.

Closing notes

Over the last few months, PrestaShop has been working hard to deliver these new features and changes. Overall, the multistore feature revamp ensures a better usage and understanding, and a better global user experience by addressing the main pain points.

As you may know, big technical changes are not possible in a minor version because we must avoid backward compatibility breaks. We had to make choices, to bring value to users of this feature while maintaining backward compatibility.

We encourage you to try out the features on the beta version and share any feedback here. Your opinion is important to us. We are counting on you to share your feedback and new ideas with us so that we can continue to improve the multistore feature that you need.

This iterative process was made possible thanks to the contribution of many merchants and web agencies who gave their time to participate in interviews, surveys, and test prototypes, which resulted in useful feedback. We are super grateful to them! That’s the open-source spirit and that’s how we can build the software that our users need.

↧

PrestaShop Core Weekly - Week 24 of 2021

June 20, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 7th to Sunday 13th of June 2021.

Core Weekly banner

General messages

Dear developers,

A lot of efforts are being directed on fixing the last known bugs in PrestaShop 1.7.8 in order to deliver soon a first Release Candidate. If you have not tested the beta yet, please be aware that only one week remains for the beta phase.

In the meantime, work continues on develop branch for next version. Two major Pull Requests have been merged this week for the next version: the upgrade of Symfony framework to version 4 and the removal of Addons modules being installed from the installer. These two items are part of the 1.7.9 draft roadmap that should soon be completed.

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

Back office

Front office

Installer

  • #24970: Remove useless static cache and make sure CI exit in status 1 when installation failed, by @PierreRambaud
  • #24676: Remove addons modules on install and add postinstall execution, by @PierreRambaud

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

Front office

Installer

Tests

Code changes in modules, themes & tools

PrestaShop test scenarios

Customer reassurance block module

Faceted search module

The PrestaShop open source project

Example modules

  • #69: Bump postcss from 7.0.17 to 7.0.36 in /example_module_mailtheme. Built by @dependabot[bot]

Pages not found module

  • #15: Use defined() with quotes is not optional. Thank you @lmeyer1

stylelint configuration

Changes in developer documentation

Suppliers list module

  • #8: Update composer setting License, by @atomiix
  • #7: The link of suppliers list is incorrect when using an array as parameter. Thank you @okom3pom
  • #3: Uninstall module used on PS 1.6 before using this one, by @Quetzacoalt91

Wishlist block module

User documentation landing page

PrestonBot

  • #120: Add PR available when editing PR too, by @atomiix
  • #119: Update symfony v3.4.35 to v3.4.49, by @atomiix
  • #118: Add “PR available” label to the issue marked as solved in the PR description, by @atomiix

Docker images

PrestaShop Specifications

Prestashop UI Kit

Core Weekly Generator tool

OnBoarding module

PHP Developer Tools

  • #63: Add autoindex lib to php-dev-tools (v4 branch), by @Quetzacoalt91
  • #59: Defines _THEME_NAME_& __PS_BASE_URI__ early to avoid warnings.. Thank you @SebSept

Product details statistics module

Google Analytics module

Theme customization module

  • #44: Remove enable/disable mobile when module is disabled, by @Progi1984

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Progi1984, @matks, @dependabot[bot], @eternoendless, @lmeyer1, @nesrineabdmouleh, @atomiix, @boubkerbribri, @PierreRambaud, @kpodemski, @micka-fdz, @tswfi, @PululuK, @jf-viguier, @Julievrz, @NeOMakinG, @mrAKAR, @olecorre, @okom3pom, @jolelievre, @sowbiba, @Quetzacoalt91, @amaury-hanser, @juraj1000, @daresh, @matthieu-rolland, @Socrapop, @samberrry, @SebSept, @ks129!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧
Search

PrestaShop Core Weekly - Week 25 of 2021

June 27, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 21th to Sunday 27th of June 2021.

Core Weekly banner

General messages

Dear developers,

There is still a lot of effort focused on 1.7.8 in order to deliver a first Release Candidate.

In the meantime, here are some news about what’s going on in the PrestaShop project:

An interesting discussion opened in issue #24954 about a change in terminology: it is about replacing “product combination” with “product variation”.

The wording “combination” has been used for a long time in the Back Office, so changing it might create confusion. We would love to hear your feedback about this topic! To do so, feel free to complete this survey and share it with other PrestaShop users in your network.

You can also tell them about the incoming public demo on YouTube that will happen next Wednesday, June 30, 2021 at 2pm CEST.

Finally, you might have noticed a change on the Developer Documentation website. The search bar is now being powered by DocSearch which is a free tool provided by Algolia for developer documentation websites.

Releases

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

Back office

Front office

  • #24940: Refactor cartPresenter to reflect the real business need. Thank you @arouiadib

Tests

Code changes in the ‘1.7.7.x’ branch

Front office

Code changes in modules, themes & tools

Changes in developer documentation

Customer reassurance block module

Faceted search module

OnBoarding module

Update prestashop/php-dev-tools from 3.15.1 to 3.16.0

Product Comments module

User documentation landing page

The PrestaShop open source project

Issues Bot

QA nightly results

PrestaShop Specifications

PHP Developer Tools

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @eternoendless, @sowbiba, @jolelievre, @kpodemski, @boubkerbribri, @dependabot[bot], @nsorosac, @atomiix, @matks, @nesrineabdmouleh, @zuk3975, @jf-viguier, @Progi1984, @Hlavtox, @WebHelpersPau, @matthieu-rolland, @PierreRambaud, @NeOMakinG, @unlocomqx, @marionf, @arouiadib, @davidglezz, @micka-fdz, @okom3pom, @Quetzacoalt91!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧
↧

PrestaShop Public OSS Demo - June 2021 session

June 30, 2021, 5:00 pm
$
0
0

The project’s sixth monthly public demo session was held and streamed live on June 30, 2021.

The session’s agenda was as follows:

You can use the timestamps to jump directly to the parts you want to watch.

Watch the replay on YouTube

Special thanks to @Hlavtox who is a regular contributor of the PrestaShop project and joined us today to present his work!

Next session in July

We noticed that 2pm CEST was a little early in the morning for people watching us live from the Americas, so we decided that future sessions will start two hours later — at 4pm. We hope this will encourage our American community to watch the demo live and discuss with us :)

The next session will be streamed live on Wednesday, July 28, 2021 at 4pm CEST. See you then!

↧

Do you speak PrestaShop? – June 2021 edition

July 1, 2021, 9:00 am
$
0
0

Contributing to PrestaShop is not only about the code, it is also about taking part in the PrestaShop translation project! This report will tell you how the translations of the software evolved in June!

Crowdin Monthly banner

Project news

New 1.7.8 strings are available for translation

The new 1.7.8 strings were added to Crowdin for the first time at the end of May. Since then, some of you have reported a few mistakes in the source strings, that we were able to correct and add on Crowdin, on June 24. Thank you very much for your help! That was the last push, so no new strings should be added to the 1.7.8 catalog from now on. In order to get back to a 100% completion rate, all the new strings should be translated and validated… Your project needs you! :muscle:

Let’s keep in touch on Slack

Until now, to exchange with the community, we used the “Discussions” tab on Crowdin. But this option seemed a bit limited as it is not possible to share images, and there is little interaction. That’s why we decided to open a Slack channel dedicated to the PrestaShop translators. On this channel, I will share information about the translation project. You will also be informed about the publication of the Crowdin monthly report. Of course, you will also be able to ask questions, suggest ideas, or get in touch with other translators.

Join us on Slack

Join us on the PrestaShop Open Source Slack! When you’re in, you will be able to join the #translation channel.

Share your thoughts on a wording issue

It was suggested in the issue #24954 to replace “product combination” with “product variation” in the back office. As this wording has been used for some time in the back office, we wouldn’t want to create confusion. So, in order to get merchants’ thoughts on this topic, we created a quick survey. So, if you are reading this and you are a merchant using PrestaShop, feel free to complete this survey and share it with merchants in your network. :pray: Thank you very much in advance for your feedback!

Your pictures of the reward program

SeongHyeon Cho received his package a month ago and sent us a picture of the gift with a nice message! Thank you again for your involvement in the Korean project!

SeongHyeon Cho's goodies reward program

If you received your gift as well, feel free to send us a picture so that we can share it here! It’s always nice to know that you received our package. :innocent:

:two_hearts: Special thanks to newcomers

Many people subscribe to the project(s) of their choice each month, but not so many start translating straight away. For that reason, we would like to thank the ones who rushed into the effort immediately! So lots of love to the dedicated whenwesober, hakan esen, Antonio Festa, EchoBilisim, and jugman!

A few stats

  • 53 members were active on the project this month.
  • A total of 93,763 words have been translated and 88,542 validated.
  • All this in 32 different languages.

Thank you very much for your involvement!

Top contributors

A lot of you are working every day on Crowdin to have PrestaShop available in many languages, and PrestaShop cannot thank you enough for your dedication! Here are the most active translators and proofreaders for June 2021.

Top 10 translators in June:

 TranslatorLanguage# Words
1.‫‬ Zoran Tejic (zotamal)Serbian (Latin)44,389
2.SNor42Hungarian5,671
3.SeongHyeon Cho (jaymz9634)Korean3,067
4.Lauri Lepik (laurilllepik)Estonian2,903
5.Cha (cafetango)Chinese Traditional2,852
6.Stamatis (breezer)Greek2,810
7.Patrik Lindblom (extendus)Swedish2,792
8.Daniel Hlavacek (Hlavtox)Czech2,666
9.David Gonzalez (davidglezz)Spanish,2,310
10.Enzo Ferrara (ferribbotte)Italian2,012

Top 10 proofreaders in June:

 ProofreaderLanguage# Words
1.Zoran Tejic (zotamal)Serbian (Latin)44,080
2.SNor42Hungarian6,325
3.Lauri Lepik (laurilllepik)Estonian5,703
4.SeongHyeon Cho (jaymz9634)Korean3,224
5.Cha (cafetango)Chinese Traditional2,900
6.Enzo Ferrara (ferribbotte)Italian2,827
7.Stamatis (breezer)Greek2,810
8.Patrik Lindblom (extendus)Swedish2,807
9.David Gonzalez (davidglezz)Spanish2,666
10.Rodrigo Laurindo (rblaurin)Portuguese, Brazilian2,545

Congrats, and welcome to our new top contributors! :clap:

Remember, you can see who has been contributing to our translation project thanks to the Translators page.

Complete translations

Fully available languages

At the end of June, just a few days after the new strings were added to Crowdin, PrestaShop 1.7.8 was already fully available (= 100% translated and validated) in 7 languages. That’s great! Thank you for your involvement. :tada:

Chinese traditionalEnglishEstonianFrench
GreekPortuguese, BrazilSwedish 

Thank you all for your contribution!

Languages with the best evolution

The following languages had the best progress thanks to the translation community:

  • Serbian (Latin) (+36% to reach 97% translated and validated)
  • Czech (+5% to reach 99% translated)
  • Greek (+5% to reach 100% translated and validated)

Congratulations! And special thanks to Zoran Tejic who worked a lot on the Serbian project lately. Only 3% left before the language is fully available, almost there! Feel free to contact me if you want to help the Serbian translators reach 100%.

Best translation progress in June 2021

A huge thank you to all the contributors!

Of course, this is highlighting the languages that made some progress with new translations; but it does not mean that the languages that are not mentioned here are not active. Indeed, some editing and rewriting could be going on, but the percentage of translation would not be modified (since the work happens on strings that are already translated). So let’s not forget about the work of other contributors! Thanks to you too!

If you have not joined us on Crowdin yet, it is never too late! :wink:

If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let me know: I will include a word about it in the next monthly report.

↧

PrestaShop Core Weekly - Week 26 of 2021

July 4, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 28th of June to Sunday 4th of July 2021.

Core Weekly banner

Releases

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

Back office

  • #25153: Make color picker global in back office, by @matthieu-rolland
  • #25152: Fix selectors map not being set in experimental product combinations page. Thank you @zuk3975
  • #25089: Fixed replaced image in product page. Thank you @NoZTurn
  • #25087: Fix form label alignment, switch precision and alignment. Thank you @Hlavtox
  • #25085: Kick border radius of the middle button of search bar, by @NeOMakinG
  • #25072: BO: Product Form V2 : Show inactive categories in the category tree. Thank you @e-gaulue
  • #24982: Fix getting products count on category list. Thank you @kpodemski
  • #24658: Deprecate Domain\SpecificPrice namespace. Thank you @zuk3975

Front office

  • #25151: Remove useless 50x.html pages in classic. Thank you @jf-viguier
  • #24656: Introduce ability to version Media. Thank you @samberrry
  • #24437: Add “recycled packaging” in order_conf and new_order mail and on order summary page and order confirmation page. Thank you @okom3pom

Web services

  • #22969: Fixed API inconsistent return format of JSON. Thank you @Kyaary

Tests

Code changes in modules, themes & tools

Changes in developer documentation

Customer reassurance block module

User documentation landing page

Email subscription module

Faceted search module

presthubot

Prestashop UI Kit

LocalizationFiles

Product details statistics module

  • #23: Missing deleteds attributes names in product stats module . Thank you @PululuK

Example modules

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @matthieu-rolland, @Progi1984, @PierreRambaud, @dependabot[bot], @Sinepel, @atomiix, @eternoendless, @Hlavtox, @zuk3975, @jf-viguier, @sadeqush, @okom3pom, @sowbiba, @matks, @nesrineabdmouleh, @NeOMakinG, @NoZTurn, @e-gaulue, @lmeyer1, @kpodemski, @micka-fdz, @PululuK, @samberrry, @Kyaary, @Quetzacoalt91!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧

PrestaShop Core Weekly - Week 27 of 2021

July 19, 2021, 6:55 am
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 5th to Sunday 11th of July 2021.

Core Weekly banner

Releases

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

Back office

  • #24932: Fix unexpected condition in country-state-selection-toggler. Thank you @davidglezz

Tests

  • #25266: Fix develop tests crashing because of outdated translation wordings, by @atomiix
  • #25238: Migrated some Legacy Tests to Integration/Unit Tests, by @Progi1984
  • #25146: Separate functional tests to BO and FO and Add regression campaign to the actual run, by @boubkerbribri

Code changes in the ‘1.7.7.x’ branch

Back office

Front office

Tests

  • #25281: Rise Apache Travis timeout to workaround addons module install issues, by @matks

Code changes in modules, themes & tools

User documentation landing page

Customer reassurance block module

Faceted search module

Changes in developer documentation

Prestashop UI Kit

Example modules

Search Bar module

Wishlist block module

  • #125: Add TS-loader and fix webpack configuration to support next version, by @NeOMakinG
  • #124: Fix RTL issues on add to wishlist button on FO, by @NeOMakinG

Email subscription module

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @matks, @okom3pom, @Progi1984, @dependabot[bot], @atomiix, @eternoendless, @NeOMakinG, @marionf, @boubkerbribri, @davidglezz!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧
↧

PrestaShop Core Weekly - Week 28 of 2021

July 19, 2021, 6:58 am
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 12th to Sunday 18th of July 2021.

Core Weekly banner

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

  • #25268: Fix isCatalogMode condition and Remove the price-drop link from the the best seller display condition. Thank you @Sinepel
  • #25267: Replace getsupplierlink with getSupplierLink. Thank you @Sinepel
  • #25242: Minor code refacto Order.php. Thank you @PululuK

Back office

Front office

  • #25067: Added clickable phone number on navbar and footer. Thank you @henri9813
  • #24080: Improve complexity of CategoryController::getCanonicalURL and Add doc to the parent function. Thank you @Sinepel
  • #23698: Can’t show module on the Left Column. Thank you @nenes25

Tests

Code changes in the ‘1.7.7.x’ branch

Back office

Code changes in modules, themes & tools

Customer reassurance block module

Faceted search module

Changes in developer documentation

Email Alerts module

  • #85: Send email when the number in stock matches the minimum. Thank you @okom3pom

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @dependabot[bot], @matks, @boubkerbribri, @eternoendless, @matthieu-rolland, @Sinepel, @PululuK, @Arman-Hosseini, @NeOMakinG, @henri9813, @PierreRambaud, @jolelievre, @yildizib, @okom3pom, @nenes25, @JevgenijVisockij!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧

PrestaShop Core Weekly - Week 29 of 2021

July 26, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 19th to Sunday 25th of July 2021.

Core Weekly banner

General messages

Dear developers,

In case you missed it, we moved the next Public OSS Demo session date to Wednesday, August 4, 2021 at 4pm CEST. We noticed that 2pm CEST was a little early in the morning for people watching us live from the Americas, so we decided that future sessions will start two hours later — at 4pm. We hope this will encourage more of our community to watch the demo live and discuss with us :smile:

Also we are really proud to announce that PrestaShop Core is compatible with PHP 8.0 in the develop branch thanks to @atomiix. The full project is not entirely compliant with PHP 8 yet (some modules need dependencies updates) but this is a major milestone for PrestaShop, just in time to greet the first beta of PHP 8.1 that was released on July 22!

Releases

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

Back office

  • #25295: Allow enable/disable selection for customers in Customer Groups, by @Progi1984
  • #25169: Cart rule category selection : display categories in a hierarchical way. Thank you @jf-viguier

Front office

  • #25210: Add download link when an order have 2 product type virtual and normal. Thank you @okom3pom

Tests

Code changes in the ‘1.7.8.x’ branch

Back office

Front office

Tests

Code changes in the ‘1.7.7.x’ branch

Back office

  • #25378: Order Product Search: Limit only if the search phrase length is greater than 2 characters and HTTP Code Error become a 400, by @Progi1984
  • #25375: In Order view, set the lang of the order for order messages, by @Progi1984
  • #25326: Create empty Customer when the customer or the guest has been deleted, by @PierreRambaud

Installer

Code changes in modules, themes & tools

Changes in developer documentation

Customer reassurance block module

Faceted search module

Contextual Help Api

  • #3: Update license headers and install extension http, by @sowbiba
  • #1: Initial commit - Functional App, by @sowbiba

Core Weekly Generator tool

  • #91: Handle years that start with different week numbers, by @matks

User documentation landing page

stylelint configuration

TranslationTools Bundle

Contact Form module

  • #56: Added WebP as authorized extension in Attachment, by @Progi1984

Social Follow module

  • #40: Deprecate variable for logged in customer. Thank you @Hlavtox

Wishlist block module

Auto Upgrade module

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Progi1984, @PierreRambaud, @dependabot[bot], @sowbiba, @matks, @atomiix, @eternoendless, @jolelievre, @nesrineabdmouleh, @kpodemski, @Seb33300, @boubkerbribri, @Arnaud104, @okom3pom, @lmeyer1, @jf-viguier, @Hlavtox, @NeOMakinG, @Oksydan, @Sinepel, @Quetzacoalt91!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧
Search

Towards a more mobile-friendly back office

July 28, 2021, 9:25 am
$
0
0

Until now, PrestaShop always relied on a desktop-first responsive design strategy. Indeed, there are few use cases on mobile. But you can’t prevent users from checking their store’s back office on their mobile!

Why work on responsive design?

They were some issues that affected the user experience on mobile:

  • Difficulties in accessing important store information
  • Hidden content because of overlapping components
  • Text readability issues
  • Bugs and lack of consistency on display (e.g. not the same padding)

All of these issues make it difficult for users to use PrestaShop on mobile devices. Also, they cause a bad reputation for the PrestaShop open source project.

First steps: quick wins 💪🏻

Valentin (front-end developer), and I, Scott (product designer), had a limited bandwidth to work on this project due to others features to work on. In order to avoid breaking changes, we only scoped small fixes on the mobile version of the backoffice a.k.a. quick wins.

A quick win is a small change, that is quick and easy to implement but that has a big and visible impact for the user.

Process

Maintainers first explored PrestaShop issues about responsive design on GitHub and centralized them by creating a single Epic.

In parallel, we analyzed all back office pages on mobile version and discussed responsive strategies to mitigate problems. For each problem, a specific issue was created and added to the Epic.

The Epic was organized into 3 different categories:

  • Remove components - components that aren’t important or used in mobile version
  • Improvements - optimizing navigation, optimizing space, etc
  • Bugs - display adjustments, broken pages, etc

What has changed?

Removing components

Some components are available on mobile version but aren’t necessarily useful during the mobile experience and become easily annoying on a small screen device.

  • The “Recommended Modules and Services” button has been removed thanks of the work being done on the PrestaShop open source project. It’s not available anymore.
  • The “Import” and “Export” buttons have been removed for tables because importing or exporting .csv files is useless on mobile phones because of the file system and the lack of software to process them.
  • Breadcrumbs have been removed because of the limited depth of the menus.
  • In the header, “View my shop” text has been removed to shorten the button and save space in the header/top bar. Only the icon was kept.
  • The “Merchant Expertise” button has been removed because mobile users are firstly looking for order updates from their shop. We gained some space on the top bar for more important features.

Before: "View my shop” text

header-before

After: "View my shop" text and "Merchant Expertise" button removed

header-after

Display optimization

  • Some components were too close to the edges of the mobile screen, and some weren’t. In order to keep consistency, a minimum of 16 px padding left and right has been added on the mobile version.
  • Font size used for the navigation drawer was too big, it was reduced. Less scroll, means more content displayed on screen and on the left menu.
  • The header and the KPIs container on the mobile version took up half of the screen space, hiding essential containers. For that reason, KPIs containers were turn into cards to optimize the space. Users can now access other KPIs cards by simply horizontally scrolling on their screen.

Feature

  • According to Google Material Design’s definition: “A floating action button (FAB) represents the primary action of a screen”. Maintainers created this component exclusively on mobile version to make primary buttons easier to reach by placing it on the bottom right corner of the screen, and also to save space.

Before: less reachability for buttons and header was quite big

reachability-before

After: primary and secondary actions in the FAB

reachability-after

Navigation optimization

The accessibility and reachability issues of the navigation drawer and the header’s content have been solved on the mobile version.

  • When users clicked on the hamburger menu to access the navigation drawer, the header was sticky and prevented users from viewing the first items. Users couldn’t access the Dashboard page and could barely tap on the Orders tab. The header stickiness was removed to make the menu accessible again.

Before: the header is overylaying the navigation drawer

navigation-drawer-before

After: the header isn't sticky anymore

navigation-drawer-after
  • Notifications and profile weren’t accessible and it was difficult to quit the pop-in once clicked because it was almost in full page and the space to exit the pop-up was too small. The Design team redesigned the pop-in and placed it just under the selected icon to easily understand which icon the pop-in is related to. Also, a highlight was added to the selected icon to ease up identification of the selected tab. You can notice that the icon used for the profile editing button has been replaced by a more representative icon. An icon was added to the sign out link for faster identification and the use of the red color makes it stand out from the rest.

Before: difficult to quit the pop-in

popin-before

After: easy to quit the notifications pop-in

popin-notifications-after

After: easy to quit the profile pop-in

popin-profile-after

Broken pages examples

A lot of pages were not displayed properly: text overlapping, making the content unreadable. Because of the lack of structure, it was also difficult to understand which group was associated with each button. In UX, this law is called the “Law of Common Region” which stipulates that “Elements tend to be perceived into groups if they are sharing an area with a clearly defined boundary”.

  • The stock management page was considered as a broken page and it was redesigned by applying the previous rules (removing import/export buttons, removing the help button, maintaining a minimum of 16 px padding left and right).

Before: stock management page completely broken

broken-page-before

After: display fixes

broken-page-after

What’s next? 🚀

After the quick wins, it’s time for bigger changes! Maintainers will work on more complex issues involving breaking changes such as tables. Usability tests will be performed in order to make sure that the back office will be completely usable.

↧

Announcing August PrestaShop Public OSS Demo

July 28, 2021, 5:00 pm
$
0
0

Friendly reminder, the next session of public demonstration from the maintainers team will happen Wednesday, August 4, 2021 at 4pm CEST!

We expect to present 2 topics:

  • First a focus on 1.7.8.0 Release candidate process and timeline by @marionf
  • Then a Focus on some 1.7.8.0 RC1 most interesting bug fixes:
    • bug #25332: a display issue for product details when using a specific layout, presented by @matthieu-rolland
    • bug #24103: adding payment with comma would fail in Order Back office page, presented by @matks
    • bug #24143: a error happened when visting a disabled category page, presented by @matks

Join us on YouTube!

The session will be kept in record on YouTube, so that even if you can’t attend to the live stream, you will still be able to catch up later.

See you then!

↧
↧

PrestaShop Core Weekly - Week 30 of 2021

August 1, 2021, 5:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 26th of July to Sunday 1st of August 2021.

Core Weekly banner

General messages

Dear developers,

Release patch 1.7.7.6 is close to being delivered while Release Candidate 1.7.8.0 is also approaching the launchpad.

We are also preparing a new format for the incoming Public OSS Demo.

You might have noticed some heavy work being done on the developer documentation. We will soon have to maintain multiple versions of the documentation, this requires changes in how we build the site: the content will stay in the Docs repository, while the site itself has been moved to an independent DevDocs site repository. Also, the DevDocs’ theme has also been moved to an independent repository so it can be reused in the near future.

Releases

A quick update about PrestaShop’s GitHub issues and pull requests:

Code changes in the ‘develop’ branch

Core

Back office

Front office

Code changes in the ‘1.7.7.x’ branch

Core

Back office

  • #25428: Don’t recalculate total when PS_ORDER_RECALCULATE_SHIPPING is 0 and editing a carrier, by @Progi1984
  • #24991: Fix combination ecotax display and edition, by @jolelievre

Code changes in modules, themes & tools

Changes in developer documentation

Customer reassurance block module

Faceted search module

Core Weekly Generator tool

Developer documentation Hugo Theme

Social Follow module

OnBoarding module

MJML Theme Converter

Auto Upgrade module

Example modules

  • #62: Publish Demo SymfonyForm 1.1.0 : add other and choice form types to example form. Thank you @JevgenijVisockij
  • #58: Publish Example module demonstrating Javascript router component usage. Thank you @zuk3975

Google Analytics module

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @jf-viguier, @Progi1984, @matthieu-rolland, @kpodemski, @dependabot[bot], @matks, @eternoendless, @atomiix, @jolelievre, @MaximeMichaud, @lukaslau, @PierreRambaud, @okom3pom, @NeOMakinG, @Hlavtox, @tups, @JevgenijVisockij, @zuk3975!

Thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with issues and comments on GitHub!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use GitHub to report an issue. Thank you!

Happy contributin’ everyone!

↧

Do you speak PrestaShop? – July 2021 edition

August 3, 2021, 3:00 am
$
0
0

Contributing to PrestaShop is not only about the code, it is also about taking part in the PrestaShop translation project! This report will tell you how the translations of the software evolved in July!

Crowdin Monthly banner

Project news

:two_hearts: Special thanks to newcomers

Many people subscribe to the project(s) of their choice each month, but not so many start translating straight away, let alone become top translators! For that reason, we would like to thank the ones who rushed into the effort immediately! So lots of love to the dedicated Lessandro Kalmykoff, and Gabriel Schwardy.

A few stats

  • 18 members were active on the project this month.
  • A total of 21,300 words have been translated and 50,962 validated.
  • All this in 16 different languages.

Thank you very much for your involvement!

Top contributors

A lot of you are working every day on Crowdin to have PrestaShop available in many languages, and PrestaShop cannot thank you enough for your dedication! Here are the most active translators and proofreaders for July 2021.

Top 10 translators in July:

 TranslatorLanguage# Words
1.‫‬ Enrique García Cruz (quiquegarcia)Spanish, Mexico8,112
2.Girdman.com (anargaragezov)Azerbaijani7,002
3.Monika (monikaraciunaite)Lithuanian1,764
4.Daniel P. (danielpatilea)Romanian1,491
5.Lessandro Kalmykoff (l.kalmykoff)Ukrainian866
6.Gabriel Schwardy (Caleydon)Slovak495
7.mirmalEsperanto326
8.SNor42Hungarian209
9.Daniel HlavtoxCzech208
10.v88Russian196

Top 8 proofreaders in July:

 ProofreaderLanguage# Words
1.Enrique García Cruz (quiquegarcia)Spanish, Mexico40,160
2.Girdman.com (anargaragezov)Azerbaijani7,250
3.Monika (monikaraciunaite)Lithuanian2,171
4.Marcin Orzechowski (Martinovy)Polish655
5.SNor42Hungarian289
6.David Gonzalez (davidglezz)Spanish208
7.Benjamin Gantikow (bbbenjie)German114
8.Zoran Tejic (zotamal)Serbian (Latin)105

Congrats, and welcome to our new top contributors! :clap:

Remember, you can see who has been contributing to our translation project thanks to the Translators page.

Complete translations

Fully available languages

At the end of July, a month after the new strings were added to Crowdin, PrestaShop 1.7.8 was already fully available (= 100% translated and validated) in 9 languages. That’s great! Thank you for your involvement. :tada:

Chinese traditionalEnglishEstonianFrench
GreekPortuguese, BrazilSpanishSpanish, Mexico
Swedish   

Thank you all for your contribution! And remember, in order to get back to a 100% completion rate, all the new 1.7.8 strings should be translated and validated… Your project needs you! :muscle:

Languages with the best evolution

The following languages had the best progress in July thanks to the translation community:

  • Spanish, Mexico (+38% to reach 100% validated)
  • Azerbaijani (+7% to reach 41% validated)
  • Lithuanian (+4% to reach 99% validated)

Congratulations! And special thanks to Enrique García Cruz who worked a lot on the Spanish, Mexico project lately. The language is now completely translated and validated! :muscle:

Best translation progress in July 2021

A huge thank you to all the contributors!

Of course, this is highlighting the languages that made some progress with new translations; but it does not mean that the languages that are not mentioned here are not active. Indeed, some editing and rewriting could be going on, but the percentage of translation would not be modified (since the work happens on strings that are already translated). So let’s not forget about the work of other contributors! Thanks to you too!

Let’s keep in touch!

If you have not joined us on Crowdin yet, it is never too late! :wink:

You can also join the #translation channel of the PrestaShop open source Slack. On this channel, I share information about the translation project. You will also be informed about the publication of the Crowdin monthly report. Of course, you will also be able to ask questions, suggest ideas, or get in touch with other translators.

Join us on Slack

↧

PrestaShop Public OSS Demo - July 2021 session

August 4, 2021, 5:00 pm
$
0
0

The project’s seventh monthly public demo session was held and streamed live on August 4, 2021.

The session’s agenda was as follows:

  • 01:17 Beginning of the session, introduction
  • 04:02 Presentation of the agenda
  • 05:05 Event rules
  • 06:02 Focus on 1.7.8.0 Release candidate process and timeline by @marionf
  • 09:56 Bug #24103 Adding payment with comma does not work in Order Back office page by @matks
  • 15:12 Bug #24145 Missing 404 for category page that does not exist by @matks
  • 19:50 Closure

You can use the timestamps to jump directly to the parts you want to watch.

Watch the replay on YouTube

Next session in September

The next session will be streamed live on Wednesday, September 1, 2021 at 4pm CEST. See you then!

↧
Viewing all 939 articles
Browse latest View live
Search