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

PrestaShop Core Weekly - Week 3 of 2021

January 24, 2021, 4:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 18th to Sunday 24th of January 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

Front office

Installer

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

  • #22909: BO - Create Order - Updated product list when adresses changed, by @Progi1984
  • #22863: Fix reference in Shopping carts view. Thank you @kpodemski
  • #22805: BO - Orders page - Cannot delete a product restricted by a cart rule, by @Progi1984

Tests

Code changes in modules, themes & tools

Customer reassurance block module

PHP Developer Tools

  • #49: Update PHP Syntax linter github action to use standard GA instead of prestashop/github-action-php-lint@master, by @matks
  • #48: Update PHP CS Fixer github action to use standard GA instead of prestashopcorp/github-action-php-cs-fixer, by @matks
  • #46: Add stub for Module::getInstanceByName always returning true, by @Quetzacoalt91

QA nightly results

Nightly board

Changes in developer documentation

User documentation landing page

Faceted search module

PrestaShop Specifications

Example modules

  • #37: Homogenize composer.json authors, by @matks
  • #36: Add logos for all modules, by @matks
  • #33: Copy demoextendsymfonyform1 into demoextendsymfonyform3, by @matks
  • #31: Demonstrate displayOrderPreview. Thank you @kpodemski

Search Bar module

Shopping cart module

Simple HTML table display module

OnBoarding module

Check payment module

Custom text module

Product Comments module

Theme customization module

Order Notifications on the Favicon module

PrestaShop PHPStan extension

MJML Theme Converter

  • #10: Update dependencies to be compatible with PHP 7.3, by @jolelievre

Product details statistics module

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @PierreRambaud, @dependabot[bot], @matks, @atomiix, @boubkerbribri, @kpodemski, @Progi1984, @nesrineabdmouleh, @justeen35, @NeOMakinG, @davidglezz, @Prestaworks, @Quetzacoalt91, @github-actions[bot], @dpatou, @LouiseBonnard, @marionf, @jolelievre, @MatShir, @PrestanceDesign, @Kioob, @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!

↧
Search

PrestaShop Core Weekly - Week 4 of 2021

January 31, 2021, 4:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 25th to Sunday 31th of January 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

Front office

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

Front office

Tests

Code changes in modules, themes & tools

Customer reassurance block module

Changes in developer documentation

Prestashop UI Kit

  • #134: Fix behavior of switch button if yes is checked and switch disabled, by @NeOMakinG
  • #131: Fix focus and active on select2 group, by @NeOMakinG

Translation Files repository

Faceted search module

User documentation landing page

PrestaShop-modules

Eslint configuration

Core Weekly Generator tool

  • #72: Add phpstan extension to coreteam.py listing, by @matks

PrestaShop Specifications

PHP Developer Tools

  • #47: Remove PrettyCI configuration file and references, by @matks

Auto Upgrade module

  • #377: Add more upgrade tests and switch to Github actions, by @atomiix

Wishlist block module

Product details statistics module

Email subscription module

Search Bar module

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @nesrineabdmouleh, @dependabot[bot], @jolelievre, @NeOMakinG, @kpodemski, @Progi1984, @Julievrz, @Quetzacoalt91, @Seb33300, @matks, @eternoendless, @PierreRambaud, @zuk3975, @mvorisek, @moncef-essid, @itsvahid, @atomiix, @pablopolyte, @LouiseBonnard, @okom3pom, @marionf, @tswfi, @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!

↧
↧

PHP, scalability & filesystems

February 4, 2021, 7:50 am
$
0
0

In this third article in the performance series we started last year, we’ll talk about PHP, scalability and its impact on the filesystem!

Also, we’re glad to announce that our White Paper about PrestaShop Performance is now published. So, if you’re interested by performance in general and PrestaShop in particular, have a look at it and let us know what you think!

Without further ado, let’s dive into PHP, filetystem and scalability!

Scalabilities

First thing first, let’s talk about scalability a little and check this definition provided by André Bondi:

Scalability is the property of a system to handle a growing amount of work by adding resources to the system.

So, in simplest terms, if I want more clients, or customers, or visitors, I need to add resources to my system. Which seems fair, does it not?

Of course, talking about performance here, we could argue that tuning the system’s configuration and its different parts should achieve the same result. Still, once the fine tuning part is done, we should add resources to the system all the same in order to handle more load, so let’s play along.

Let’s review together the two main levers to enable scalability - and keep in mind those are not exclusive, you often mix them up in Real Life™️.

Vertical

The simpliest and most efficient way to add some resources to your system if often to add some RAM, or CPU, or storage, or all of those at the same time.

Here with a simple stack with a webserver (let’s use Apache2), your favorite PHP application and a database (here MySQL):

Vertical ScalingWe require more minerals

In a modern world made of cloud computing instances, vertical scaling can be done in a few mouse clicks by upgrading the instance type and releasing new resources. It can be a bit more tricky if you manage the hardware yourself, but it’s still feasible.

Though, keep in mind some potential limitations:

  • It tends to be less and less true, but pricing is not linear and 64GB of RAM may not cost twice 32GB
  • There may come a point where you can NOT add more resources verticaly and you’ll just hit the limit
  • If you’re managing your own infrastructure, you already know it takes time to upgrade or replace instances (buying, receiving and installing new parts can take weeks)
  • If you’re managing your own infrastructure, what will you do with the old hardware?
  • Finally, if you’ve not already mixed a bit of horizontal scaling, your system will be unavailable during the upgrade!

Nonetheless, vertical scaling remains the most efficient way to scale a system or an application, as very little resources are wasted (either in networking, or scheduling, processing, etc..).

Last but not least, vertical scaling usually requires no configuration change (either at the system’s or application’s level), keeping complexity to its minimum.

Horizontal

As you may have guessed, horizontal scaling is all about adding more instances of your system or application, whichever infrastructure you are using (either some docker, virtual machines or physical servers, the concept is similar):

Horizontal ScalingJust keep swimming, just keep swimming!

Still, depending on your ecosystem, it may require some more work, at least a way to load balance traffic between the instances.

And probably a way to distribute the application’s files, especially for application like PrestaShop.

Hence, the most simple architecture schema you will come with looks a lot like this (either load balancing with your kubernetes service through an ingress or just setting up your F5 BigIP appliance):

Horizontal Scaling ExpandedI’ve a feeling we’re not in Kansas anymore.

And we are not even mentioning the redundancy systems that could be setup for the load balancing and the shared filesystem parts.

Of course, if you can avoid a shared filesystem, please do - it is a lot of constraints, technical complexity and performances issues to resolve. But sometimes you can’t, because your application or system requires it, and it becomes a new challenge to manage. Wich is fine!

Let’s face it : even with cloud computing within reach of our keyboards, horizontal scaling remains more complicated to setup than vertical scaling. It may even require some configuration (but more on that later) and, in some rare cases, code adaptation.

So, why should we even consider horizontal scaling?

  • A more linear pricing when adding instances and resources
  • More granularity as well (you can size each instance as needed)
  • If you’re managing your own infrastructure, you’re not wasting resources when adding a new server
  • Uptime : with several instances running simultaneously, you can update and upgrade your system seamlessly!
  • Once setup, it can enable some new deployment methods, facilitating rollout, rollbacks, and so on

PHP & Filesystems

So, now that we’re all on the same page about our scalability options, we all want some uptime, some performance and some fine PHP.

Thing is, the first thing we see when running PHP on a shared filesystem is some performance issues. It can be expected with some network overhead due to the shared filesystem, but PHP inner workings are taking it up to another level.

System calls

On an unix system, when you want to access a file, one way or another, the kernel has to resolve it. Because everything is a file on a Unix system, this mechanism is used wether your target is a directory, a socket, a link or a plain file - the main difference being the file type.

It does this by calling stat, which is a bit heavy on the system, not only because it requires disks metadata but also because of context switching.

PHP filesystem usage

PHP not being a compiled language, it does use several files.

Even more today, with Composer enabling package management, adding plenty of modules and files.

Just a quick example here, a standard PrestaShop installation, just the modules directory contains around 10k files:

$ ll -R|wc -l
10775

And this is not limited, or specific, to PrestaShop. Here’s the vendor directory of a custom application:

$ ll -R vendor/|wc -l
40539

And we’ve not even seen the application’s files at this point.

Of course, your mileage may vary, but that remains something to take into account when developing and designing your application, because faster storages will only mitigate this: context switching will remain, metadata will still be required, and so on.

As stated before, PHP will resolve those files, requiring the kernel to do so, calling stat for each of them, each time.

Optimizations

Of course, there are ways to attenuate PHP’s behaviour regarding the filesystem usage. Though, as you’ll see, those solutions could impact the way you manage your system.

Caching may not always be easy, but it’s always efficient.

realpath cache

First configuration directive to keep in mind when dealing with PHP and performance is realpath cache. As mentionned earlier, PHP does scan the directories for files and subdirectories, which takes some system resources and introduces even more latency in a distributed system with a shared storage.

But PHP allowing us to cache those calls and their responses since version 5.3, we’ll make good use of this option and enable it as such:

realpath_cache_size = 4096K
realpath_cache_ttl = 600

As usual, you may need to adjust those values depending on your own system and application (path length, number of files, etc..).

The open_basedir dilemma

Don’t forget that the real path cache directives are incompatible with the open_basedir one. Hence, you won’t be able to enable both of them. Which could be a conundrum as one directive enables performance when the other enforces security.

Our best advice would be to work on both sides by:

  • Either with containers (at PHP or kernel level), or Virtual Machines or whichever technology you’re the most confortable with, working on security by minimizing the directories and contents the application can access to
  • Enabling the realpath cache directive in order to improve the application’s or system’s performances

As always, we’re aware our advice can not take several parameters into account - such as the security requirements of your application or system, your access to different platform architectures types or the resources at your disposal.

Security is always a trade-off (performance, accessibility, ease of use: you name it).

opcache

Opcache is another cache system available to us through PHP.

This time we are not caching the filesystem paths, files and directories but the files contents themselves. And more precisely: the compiled files’ contents, stored in memory. Which will minimize as much as possible the filesystem’s accesses.

This is a real booster for your system and/or application, here are some suggested configuration parameters:

[opcache]
opcache.enable=1
opcache.enable_cli=0
opcache.memory_consumption=256
opcache.interned_strings_buffer=32
opcache.max_accelerated_files=16229
opcache.max_wasted_percentage=10
opcache.revalidate_freq=10
opcache.fast_shutdown=1
opcache.enable_file_override=0
opcache.max_file_size=0

If you can manage it, here are few options you could also configure:

opcache.validate_timestamps=0
opcache.revalidate_path=0

Keep in mind that, if you deactivate validate_timestamps, OPCache will never update your code, unless you trigger it (either through internal functions or by restarting the web server). Which will impact your deployment method if you’re dealing with VMs and physical servers - but be irrelevant when working with containers.

Results

So, what can you expect from a bit of caching, when trying to minimize the filesystem impact on PHP?

Well, we’re glad you ask!

Users per hour count graphAs usual, the more the merrier

As you can see, even with a small instance with a single vCPU and standard disks, we see a huge performance improvement.

Something that you will be able to reproduce, whatever your environment and setup is.

Just in case you were wondering about the filesystem and disks impact, here is another test with SSD disks on the same instance type:

User per hour count with SSD graphAgain, the more the merrier

Let’s have a quick look at the CPU usage before wrapping up:

CPU Usages graphMore CPU usage means less bottlenecks

We do hope this article helped to shine some light on some PHP mechanics, their intrications with performance and how to alleviate them.

If you wonder about other parameters that could fasten your PHP application and PrestaShop specifically, plenty of them can be found in our devdocs.

About the series

Here are the topics that have currently been covered during this series:

  1. Performance (& PrestaShop)
  2. Apache Vs. NGINX : Match Of The Millennium
  3. PHP, scalability & filesystems
↧

PrestaShop Core Weekly - Week 5 of 2021

February 7, 2021, 4:00 pm
$
0
0

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

Core Weekly banner

General messages

Dear developers,

Have you read “PHP, Scalability & Filesystems” that was published last week on this blog?

This is the third article of the performance series started in 2020 by @djodjo3 who is Lead DevOps at PrestaShop company. This article is about PHP, scalability and its impact on the filesystem.

In the meantime, the Pull Request for a new multishop header search mechanism by @matthieu-rolland has been merged, it’s one important milestone for the new multishop header for migrated pages project for PrestaShop 1.7.8.

Also a v5.0.0 version is beingprepared for module autoupgrade with some fixes related to upgrades from PrestaShop 1.6 to PrestaShop 1.7.7.

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

Front office

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

  • #22980: Replaced hooks displayAdminList<Before|After> with displayAdminGridTable<Before|After>, by @Progi1984

Tests

Code changes in modules, themes & tools

Customer reassurance block module

Faceted search module

  • #32: Bump version to 2.0.4 and add badge in README, by @matks

Search Bar module

  • #29: Bump version to 2.1.1 and add badge in README, by @matks
  • #27: Add latest github version badge in readme, by @matks
  • #26: Bump version to v2.1.1 and add prepend-autoloader false, by @matks

Gamification module

  • #78: Fixed path for badge images on migrated pages, by @Progi1984

QA nightly results

Traces

Prestashop UI Kit

User documentation landing page

Changes in developer documentation

PrestaShop-modules

Auto Upgrade module

Wishlist block module

PrestonBot

OnBoarding module

Example modules

  • #41: Fix composer autoloader configuration for demosymfonyform, by @matks
  • #35: Rewrite demoextendsymfonyform1 module without CQRS, by @matks

Google Analytics module

Customer data privacy block module

Theme customization module

Where to start contributing?

What about redirecting the customer to Product page after he created an account on Front Office? This is a feature request submitted last year by a contributor, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @morgoth6, @dependabot[bot], @nesrineabdmouleh, @matks, @Progi1984, @PululuK, @Amin-Hosseini, @NeOMakinG, @PierreRambaud, @jolelievre, @kpodemski, @zuk3975, @atomiix, @Hlavtox, @pablopolyte, @Shoprunners, @nenes25, @matthieu-rolland!

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? – January 2021 edition

February 10, 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 January!

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. For that reason, we would like to thank the ones who rushed into the effort immediately! So lots of love to the dedicated Laimonas Matukas, Jussi Lahtinen, Arman Hosseini, Zafer ÖZTÜRK, jordipagano, 8i11y, and Armand.

A few stats

  • 33 members were active on the project this month.
  • A total of 14,139 words have been translated and 5,860 validated.
  • All this in 23 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 10 most active translators and proofreaders for January 2021.

Top 10 translators in January:

 TranslatorLanguage# Words
1.‫דניאל שפירא‬‎ (danielshapiro9)Hebrew4,264
2.mirmalEsperanto3,598
3.jbonelloMaltese1,565
4.8i11yGerman989
5.Valerij Ivashchenko (likemusic)Russian721
6.Armand (Rubujeto)Esperanto655
7.Oleg (metacreo)Russian, Lithuanian546
8.Tatu Wikman (tswfi)Finnish324
9.A. L (roynsdx)Arabic248
10.Çocuk Saatleri (cocuksaatleri)Turkish218

Top 10 proofreaders in January:

 ProofreaderLanguage# Words
1.‫דניאל שפירא‬‎ (danielshapiro9)Hebrew4,346
2.A. L (roynsdx)Arabic462
3.Rauno Riikman (weaver)Finnish348
4.Monika (monikaraciunaite)Lithuanian161
5.David Gonzalez (davidglezz)Spanish149
6.Gabriel Tenita (ggedamed)Romanian137
7.Arman Hosseini (Arman-Hosseini)Persian102
8.webdvl (megashopba)Czech56
9.Zoran Tejic (zotamal)Serbian30
10.P.V. (MARK-APP)Dutch21

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 January, PrestaShop 1.7.7 was fully available (= 100% translated and validated) in 14 languages:

BosnianChinese traditionalDanishEnglish
FrenchGreekItalianPortuguese, Brazil
RomanianSerbianSlovakSlovene
Spanish, SpainSwedish  

Languages with the best evolution

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

  • Hebrew (+8% to reach 95% translated)
  • Esperanto (+8% to reach 69% translated)
  • Russian (+3% to reach 97% translated)

Congratulations! :muscle:

Best translation progress for January 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 proofreaders! Thanks to you too!

Languages that need (more) proofreaders

A translated string will not be available in PrestaShop as long as it is not validated. For this reason, it is important to keep a high level of validated strings vs. translated strings, to make sure everyone benefits from the latest translations!

At the end of January, some languages would still benefit from some proofreading:

  • Spanish, Argentina (100% translated vs 13% validated).
  • Esperanto (69% translated vs 19% validated).
  • Galician (98% translated vs 58% validated).
  • Spanish, Venezuela (51% translated vs 11% validated).
  • Spanish, Mexico (91% translated vs 56% validated).

Languages that need proofreading

If you wish to help to proofread what has been translated, please contact PrestaShop with the language you would like to proofread: just send an email to translation@prestashop.com. Your help is needed!

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.

Do you have a question, a remark? Do not hesitate to leave a comment. See you next month! :raising_hand:

↧
↧

PrestaShop Core Weekly - Week 6 of 2021

February 14, 2021, 4:00 pm
$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 8th to Sunday 14th of February 2021.

Core Weekly banner

General messages

Dear developers,

Last Friday maintainer @pululuk, helped by @sowbiba and many others built the ZIP archive for PrestaShop 1.7.7.2 and delivered it to QA team for validation. This is the second time a PrestaShop release is built by someone who is not an employee of PrestaShop company! Congratulations @pululuk!

Another interesting news: thanks to the awesome work of @atomiix, the upgrades between PrestaShop versions using the autoupgrade module are now being run every night and results can be looked at in the Nightly build dashboard

In the meantime, @NeOMakinG also upgraded the jQuery version to v3.5 for Classic Theme and default Back Office theme.

The next step for release 1.7.7.2 is now QA validation. Release is expected to happen at the latest on next Monday (22th of February).

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

Front office

Web services

  • #23081: Fix the combination’s disappearance from Cart when it’s updated by WS. Thank you @fabiovannini

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

Front office

Tests

Code changes in modules, themes & tools

Changes in developer documentation

  • #865: Fix link to testing introduction. Thank you @Paddimir
  • #862: Update information on displayCarrierExtraContent hook. Thank you @Hlavtox
  • #860: Fix return error in execute method. Thank you @jf-viguier
  • #855: Add page about users, login and secure_key, by @matks

PrestaShop PHPStan extension

  • #8: Add PrestaShop as author in composer.json, by @matks
  • #5: Add ClassConstantsMustHaveVisibilityRule, by @matks

Auto Upgrade module

Customer reassurance block module

Faceted search module

Search Bar module

Dashboard Activity module

  • #24: Bump version to v2.1.0, update min core compatibility, by @matks

User documentation landing page

Core Weekly Generator tool

Wishlist block module

Prestashop UI Kit

Shopping cart module

LocalizationFiles

  • #5: Translate Ukrainian locale from Russian to Ukrainian. Thank you @rakvium

Where to start contributing?

What about fixing a success message that is incorrect and is displayed when a search alias is created from the Back Office? This is a bug report submitted three months ago, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Paddimir, @matks, @Hlavtox, @jf-viguier, @atomiix, @dependabot[bot], @PierreRambaud, @zuk3975, @github-actions[bot], @NeOMakinG, @pablopolyte, @eternoendless, @nesrineabdmouleh, @fabiovannini, @Progi1984, @sowbiba, @boubkerbribri, @JevgenijVisockij, @rakvium, @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!

↧

Announcing public demos from the maintainers team

February 19, 2021, 8:00 am
$
0
0

Last month, the maintainers team held a special event for the open source project: a public demonstrations session. To better understand what this is about, let’s provide some context.

Demonstrations at PrestaShop

Historically, the maintainers team of the PrestaShop open source project was only composed of employees from the PrestaShop company, developers assigned by the company to work on the project. This team used many forms of organizations over years, the most recent being a mix of Scrum rituals and Kanban method. One of the Scrum rituals being followed by the team is the demo session.

Scrum’s demo is a regularly held event that takes place at the end of each development cycle (called sprint), where the team demonstrates what has been built. This helps stakeholders, inside and outside the team, to witness the outcome, what has been delivered, and provide feedback. For years, this event happened regularly, but only employees of the PrestaShop company were invited.

Since 2020, the PrestaShop project is becoming increasingly independent from the PrestaShop company. One of the major milestone of this evolution has been the introduction of community maintainers@kpodemski and @pululuk.

As the project becomes more open, transparency is key. During 2020, we published the Maintainer’s Guide. Next step: making the demo meetings public, and streamed live!

We hope that this event will become a regular rendez-vous for the maintainers and the PrestaShop community to share information, feedback, and ideas.

The first Public open source demonstrations

The first online session of what we call for now “Public PrestaShop open source demonstrations” was held last month on the 28th of January.

Since this was our very first attempt to this type of meeting, in English, and including people from outside the PrestaShop company, this first session was open for maintainers but not for community. The objective was to give the concept a shot before going fully public. We have already identified multiple areas for improvement, but we were globally satisfied with the result.

Next session, however, will be public and streamed live on the PrestaShop project’s new YouTube channel.

Attendees will be able to ask questions in the chat that will be read and answered live.

Each 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.

This first session agenda

The first session agenda was as follows:

  • 00:00 Introduction
  • 02:23 Presentation of the agenda
  • 03:06 Event rules
  • 04:20 Project announcements
  • 06:04 First demonstration - Multishop support for Symfony BO pages by @matthieu-rolland
  • 18:40 Second demonstration - Enhanced module capacities to customize Symfony thanks to form simplification by @matks
  • 29:51 Questions & Answers
  • 38:30 Closure

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

Watch the replay on YouTube

Next step, second session on the 25th of February

The next session of “public PrestaShop open source demonstrations” is scheduled for the 25th of February at 2pm CET– that’s next Thursday! If you want to learn more about the PrestaShop project… see you there!

↧

Release of PrestaShop 1.7.7.2

February 22, 2021, 6:00 am
$
0
0

After a few weeks dedicated to fixing upgrades problems, regressions and security issues found on the previous 1.7.7 versions, PrestaShop 1.7.7.2 is finally available!

1.7.7.2 is available!

This patch release fixes 21 regressions reported on version 1.7.7.0 and 1.7.7.1 and 2 security issues.

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

Reminder: the 1-Click Upgrade module’s latest version is v4.12.0, don’t forget to upgrade it before using it.

Main fixes

Below are listed some main regressions we fixed in this version:

Upgrade

SEO

Order page

Shopping Cart

Others

Read the full changelog here

Security fixes

2 security fixes have been included in this patch version:

Acknowledgments

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

Ali Shareei, Boubker Bribri, Franck Lefèvre, Ibrahima Sow, Krystian Podemski, Mathieu Ferment, Nesrine Abdmouleh, Pierre Rambaud, Simon Garny, Thomas Baccelli and Valentin Szczupak

Thank you!

A special version co-released by our maintainer Pululu Kinanga (@Pululuk) from l’Agence123 and the PrestaShop team. They helped us to deliver this patch version. This is a new step towards the independence of the open-source project.

Download PrestaShop 1.7.7.2 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.2 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.2. Upgrades from a standard 1.7.x version should work just as well.

↧
Search

PrestaShop Core Weekly - Week 7 of 2021

February 22, 2021, 4:00 pm
$
0
0

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

Core Weekly banner

General messages

Dear developers,

Last week the maintainers team focused on delivering PrestaShop 1.7.7.2 which was achieved on time, on this Monday 22nd of February 2021! We are very happy of this outcome.

Did you also notice our Public Online Demonstrations announcement? If you want to attend the next one, it will be at 2pm CET on Thursday, 25th of February, streamed live on our newly created YouTube channel!

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

  • #23289: Use default currency when supplier currency setting is incorrect, by @atomiix

Code changes in modules, themes & tools

Changes in developer documentation

Example modules

Faceted search module

Customer reassurance block module

User documentation landing page

Wishlist block module

  • #99: Fix ‘is same’ smarty function for stats template. Thank you @pablopolyte

PrestaShop PHPStan extension

Share Buttons module

Where to start contributing?

What about updating the Order Confirmation email template to remove the gift line when gift option is disabled? This is a bug report submitted one month ago, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Progi1984, @dependabot[bot], @nesrineabdmouleh, @pablopolyte, @atomiix, @NeOMakinG, @RomainMazB, @jolelievre, @matks, @Hlavtox, @jf-viguier, @zuk3975, @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!

↧
↧

Second public demo from the maintainers team

February 24, 2021, 5:00 am
$
0
0

As announced previously, the next session of public demonstration from the maintainers team will happen tomorrow, Thursday 25th of February, at 2 pm CET!

It will be streamed live on our newly created YouTube channel. Please find the link to join us below:

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 tomorrow!

↧

PrestaShop Public OSS Demo - February 2021 session

March 1, 2021, 2:00 am
$
0
0

Last week, the maintainers team held again a video conferencing for the project public demonstrations session, streamed live on YouTube.

The second Public open source demonstrations setup

This was our second attempt to this type of meeting, in English.

After exploring the different setups and tools capacities to host this event, we found that a suitable solution would be to host the session on Jitsi while streaming the video into a YouTube channel.

This setup was a compromise between the capacities of the tools, the quality of the video and the flexibility for maintainers.

Attendees were able to ask questions in the chat that could be read and answered live. The streaming event has been recorded by YouTube and can be watched by the people who could not attend to the live stream.

This session agenda

The session agenda was as follows:

  • 00:00 Waiting for everybody to join
  • 02:34 Beginning of the session, introduction
  • 04:48 Presentation of the agenda
  • 05:23 Event rules
  • 06:12 Project announcements
  • 07:19 First demonstration - Product Page BO architecture by @jolelievre
  • 33:39 Second demonstration - Multiple fixes for upgrade from PS 1.6 to PS 1.7.7 by @atomiix
  • 45:40 Questions & Answers
  • 54:08 Closure

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

Watch the replay on YouTube

Next session in March

The next session of public PrestaShop open source demonstrations will happen in end of March. We’ll communicate as soon as the time and day are decided.

Note: we have noticed that some of the slides being used in the event were very slow to be loaded, this issue seems to be related to the use of Google Chrome while sharing the screen on Jitsi and streaming to YouTube. Our apologies for the issue, we will make sure to fix it for next time.

↧

PrestaShop Core Weekly - Week 8 of 2021

March 1, 2021, 4:00 pm
$
0
0

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

Core Weekly banner

General messages

Dear developers,

Last week, the maintainers team held again a video conferencing for the project public demonstrations session, streamed live on YouTube.

The version 2.0.0 of module blockwishlist is now complete. This is a wide rework of the module capacities and codebase, and it will be compatible with PrestaShop 1.7.6 and newer versions.

The release has not been done yet and should follow soon.

Finally the kanban for 1.7.7 branch is not empty yet, it still contains unresolved regressions reported on versions 1.7.7.0 and 1.7.7.1. The next batch of bugfixes for 1.7.7 will be delivered in patch version 1.7.7.3, which is scheduled to be delivered within the next 6 weeks.

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

Code changes in the ‘develop’ branch

Core

  • #23310: Remove unusable code in OrderSlip::getOrdersSlipProducts(). Thank you @PululuK
  • #23295: Update Smarty to v3.1.39, by @matks
  • #23269: Fix nightly autoupgrade - issue with Cookie destruction, by @atomiix

Back office

Front office

  • #23353: Fix classic theme images width, accessibilty and some lighthouse improvements, by @NeOMakinG
  • #23309: Add ID field in global template vars. Thank you @PululuK

Installer

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Back office

  • #23142: Check if an order status has the same name in Add/Edit, by @Progi1984
  • #23040: Fixed missing DNI Number in BackOffice Order View, by @Progi1984
  • #22920: Prevent adding out of stock products in Create order page, by @Progi1984
  • #22791: BO - Order Page - Set an error message when the payment method is invalid, by @Progi1984

Tests

Code changes in modules, themes & tools

Changes in developer documentation

Customer reassurance block module

Faceted search module

PrestaShop PHPStan extension

Product Comments module

User documentation landing page

Docker images

PrestaShop modules registry

Decimal

Prestashop UI Kit

Custom text module

  • #53: Implement call to hook filterHtmlContent on modules HTML. Thank you @elburgl69

PrestaShop Specifications

GDPR module

Wishlist block module

  • #77: Introduce new version of blockwishlist module compatible with PS 1.7, by @Quetzacoalt91

Where to start contributing?

What about improving how notifications in the Back Office are marked ‘read’ ? This is a bug report submitted three years ago, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Progi1984, @dependabot[bot], @nesrineabdmouleh, @boubkerbribri, @matks, @PierreRambaud, @idnovate, @zuk3975, @NeOMakinG, @atomiix, @PululuK, @SD1982, @JevgenijVisockij, @elburgl69, @MatShir, @eternoendless, @Quetzacoalt91, @mikayilsrt, @lolath-presta!

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!

↧

Focusing on essential modules

March 2, 2021, 6:00 am
$
0
0

Over the years, the PrestaShop project became host and maintainer for a very large number of open source modules. Last year, over 160 of them were present in our GitHub organization. As you probably know already, maintaining them requires a lot of work, and the maintainer team’s resources are limited. Proof of this is that some of these modules have not been updated in years.

For this reason, the product team recently did a survey of almost 600 PrestaShop users to find out which modules were essential for their business and which ones they used the least.

As a result of this survey, the teams have decided to focus their efforts where it really matters. Rather than keeping hundreds of sparsely updated modules, starting this year, the PrestaShop Project will only commit to maintaining a smaller set of them – the ones that are really important for users.

This is why the following set of modules, reported in the survey amongst the least often used, have been abandoned and their repositories archived:

The following modules have also been abandoned and archived because they were still not compatible with 1.7 stores:

Abandoning these projects and archiving their repositories means that they will no longer be available in back-offices, but they will still available on GitHub. These modules will no longer receive any updates, nor accept contributions. Developers, however, can and will still be able to use them, fork them, improve them and redistribute them as derivative projects, following the AFL 3.0 license.

PrestaShop is an open source, community project. If the PrestaShop Project stops maintaining a repository, it does not mean this project is gone. What the project cannot do by itself, the community can do it, as long as people are willing to continue working on it. We hope to see contributors fork these modules and build newer, better versions of them.

Of course, you can also take a look at the Addons Marketplace, where you can find modules with similar features to the archived ones.

That said, the PrestaShop Project will continue to maintain and freely provide the modules identified as essential by users in the survey, including Faceted search, New products block, Mail alerts, and many more.

If you think an important feature is missing from the project, please create a feature request.

The list of project modules will be regularly analyzed to make it up-to-date with the what users need the most.

↧
↧

Do you speak PrestaShop? – February 2021 edition

March 9, 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 February!

Crowdin Monthly banner

Project news

Esperanto is finally available in the back office :tada:

A few weeks ago, Esperanto was not available in PrestaShop’s back office. I’m glad to announce that this issue has been solved! In your back office, go to International > Translations > Add/Update a language and select ‘Esperanto’ in the dropdown list.

Please note that not all translated strings have been validated yet. Therefore, these strings won’t be available in the back office. If you would like to help with proofreading, do not hesitate to contact me.

: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 Jonas Kriaučiūnas, Begi Ganellari, Robin Pokorný, Thommas, Sevindj, u50, and Mohamed Ali Rajab.

A few stats

  • 35 members were active on the project this month.
  • A total of 12,443 words have been translated and 9,468 validated.
  • All this in 25 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 10 most active translators and proofreaders for February 2021.

Top 10 translators in February:

 TranslatorLanguage# Words
1.‫‬ mirmalEsperanto3,750
2.AmirRzdPersian2,176
3.Enrique García (quiquegarcia)Spanish, Mexico1,416
4.8i11yGerman879
5.Armand (Rubujeto)Esperanto729
6.Szymon Tondowski (stdeykun)Polish657
7.Ilyasov Ivan (tRACE)Russian545
8.u-50Ukrainian364
9.unbandaraSinhala310
10.Benjamin Gantikow (bbbenjie)German297

Top 10 proofreaders in February:

 ProofreaderLanguage# Words
1.Enrique García (quiquegarcia)Spanish, Mexico5,200
2.AmirRzdPersian2,312
3.8i11yGerman756
4.Benjamin Gantikow (bbbenjie)German360
5.‫דניאל שפירא‬ (danielshapiro9)Hebrew238
6.Rauno Riikman (weaver)Finnish265
7.Marcin Orzechowski (Martinovy)Polish112
8.Girdman.com (anargaragezov)Azerbaijani69
9.Monika (monikaraciunaite)Lithuanian66
10.Gabriel Tenita (ggedamed)Romanian52

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 February, PrestaShop 1.7.7 was fully available (= 100% translated and validated) in 16 languages:

BosnianChinese traditionalDanishEnglish
FrenchGreekItalianLithuanian
PersianPortuguese, BrazilRomanianSerbian
SlovakSloveneSpanish, SpainSwedish

Languages with the best evolution

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

  • Spanish, Mexico (+11% to reach 67% validated)
  • Esperanto (+9% to reach 78% translated)
  • Persian (+5% to reach 100% translated :tada:)

Congratulations! :muscle:

Best translation progress for February 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 proofreaders! 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 9 of 2021

March 7, 2021, 4:00 pm
$
0
0

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

Core Weekly banner

General messages

Dear developers,

We enter the month of March, and this is the last month before April when we expect the feature freeze to happen!

Multiple projects for 1.7.8 have delivered major milestones last week:

Virtual product files are now managed in the new Product Page being built, as well as improvements for handling suppliers for product with combinations.

The Back Office maintenance page is now the first Symfony Back Office page using the new Multistore checkboxes interface to manage multistore settings.

We also would like to applause the merge of PR #20288 which is the Back Office page “Customers > Outstanding” migrated to Symfony by contributor @ks129!

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

Front office

Tests

  • #23539: Disable temporarily phpstan extension, by @matks
  • #23522: Introduce phpstan for prestashop v1.1 with 3 new Rules: ClassConstantsMustHaveVisibilityRule, UseTypeHintForNewMethodsRule, UseTypedReturnForNewMethodsRule, by @matks
  • #23494: Fix click on toggles on nightly develop, by @boubkerbribri
  • #23490: Use GA ubuntu 18.04 for sanity and integration tests, by @matks
  • #23489: Improve integration.yml GA file name, by @matks
  • #23463: Rename PHPStan exclude class list, by @matks

Code changes in the ‘1.7.7.x’ branch

Front office

Tests

Code changes in modules, themes & tools

Circuit breaker

Wishlist block module

PrestaShop on Docker

PrestonBot

Changes in developer documentation

  • #877: Fix module send example directory. Thank you @nenes25
  • #876: Fix typo in contribution guidelines, by @matks

Customer reassurance block module

Faceted search module

PrestaShop PHPStan extension

  • #14: Handle multiple loads of same file through PHPConfigurationFileLoader, by @matks
  • #13: Fix extension.neon indentation, by @matks
  • #12: Improve documentation for UseTypedReturnForNewMethodsRule, by @matks
  • #11: Introduce UseTypeHintForNewMethodsRule, by @matks
  • #9: Introduce UseTypedReturnForNewMethodsRule, by @matks

User documentation landing page

GDPR module

  • #138: Modify GitHub Action PHP CS Fixer to not depend on prestashopcorp, by @matks
  • #137: Apply license headers from native modules, by @matks
  • #134: Bump prestashop/php-dev-tools from 3.4 to 3.14. Built by @dependabot[bot]

PrestaShop Specifications

Prestashop UI Kit

Decimal

  • #15: Migrate to Coveralls & Added support versions, by @Progi1984

PrestaShop English User Documentation

  • #2: Delete duplicate content to clean user-documentation-en repository . Thank you @Julievrz

Prestashop Shop Creator tool

  • #5: Add composer 2 compatibility and use new faker lib. Thank you @davidglezz

Where to start contributing?

What about fixing a label incorrectly displayed in the Back Office Create an order page ? This is a bug report submitted last month, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @Progi1984, @NeOMakinG, @matks, @PierreRambaud, @nenes25, @boubkerbribri, @dependabot[bot], @nesrineabdmouleh, @kpodemski, @agostinofiscale, @marionf, @Quetzacoalt91, @Julievrz, @zuk3975, @sowbiba, @davidglezz, @matthieu-rolland, @JevgenijVisockij, @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 10 of 2021

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

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 8th to Sunday 14th of March 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

Front office

Installer

Tests

Code changes in the ‘1.7.7.x’ branch

Tests

Code changes in modules, themes & tools

Changes in developer documentation

TranslationTools Bundle

  • #84: Migrated from Travis CI to Github Actions & Added PHPCSFixer, by @Progi1984

Docker internal images

PrestaShop on Docker

GDPR module

Search Bar module

Shopping cart module

Simple HTML table display module

Custom text module

Faceted search module

OnBoarding module

Check payment module

Product Comments module

Theme customization module

Order Notifications on the Favicon module

PHP Developer Tools

Customer reassurance block module

User documentation landing page

Email Alerts module

Core Weekly Generator tool

PrestaShop PHPStan extension

  • #19: Fix configuration file - mismatch parameters, by @matks
  • #18: Exclude class methods with inheritdoc for Type rules, by @matks
  • #17: Exclude for rules magic methods, by @matks
  • #16: Add interface test usecases, by @matks

Wishlist block module

Buy button lite module

Prestashop UI Kit

Auto Upgrade module

  • #386: Add more nightly tests and re-enable 1.6 migration test, by @atomiix

PrestaShop Specifications

  • #206: Add multistore specs for maintenance page, by @marionf
  • #204: Multistore - Add specs for add/edit employees, by @marionf
  • #203: Multistore specify behavior when unchecking a box, by @marionf

PrestaShop user documentation

PrestaShop user documentation (FR)

  • #2: Delete duplicates following Gitbook synchronisation . Thank you @Julievrz

PrestaShop user documentation (ES)

  • #1: Delete duplicate content following GitBook synchronization. Thank you @Julievrz

PrestaShop user documentation (Farsi)

  • #1: Delete duplicate content after GitBook/Github synchronization failed. Thank you @Julievrz

PrestaShop user documentation (Dutch)

  • #1: Delete duplicate content in the Dutch user documentation. Thank you @Julievrz

PrestaShop user documentation (Italian)

Where to start contributing?

What about adding a button to remove supplier or brand logos in the Back Office page ? This is a feature request submitted six months ago, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @boubkerbribri, @okom3pom, @Progi1984, @dependabot[bot], @Quetzacoalt91, @matks, @nesrineabdmouleh, @NeOMakinG, @PierreRambaud, @jolelievre, @tswfi, @Julievrz, @ent47, @sowbiba, @JevgenijVisockij, @eternoendless, @jf-viguier, @atomiix, @zuk3975, @marionf, @Prestaworks!

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 - Choosing the pace

March 22, 2021, 3:00 am
$
0
0

Following the February session of the open source project’s public demo, we now feel confident to set a pace for these events.

PrestaShop open source project’s public demo every month

We aim to host open source project’s public demos the last Wednesday of each month at 2pm CET.

That means that the March session will happen on Wednesday 31st of March 2021, 2pm CET.

The session will be kept in record on YouTube, so it can be watched later if this timeslot is not suitable for you.

Sessions agenda

For now we stick to the current content of these sessions, which means in each session we

  • present the event
  • present latest announcements for the project
  • present some of the topics achieved this month
  • host a Q&A session

By the way, the Q&A session does not need to be about the demonstrations content! It can be any question related to the open source project, be it the scope, the documentation, the process or the content of the project.

If you have suggestions or feedbacks about previous demo sessions or upcoming sessions, feel free to tell us in the comment section

↧
↧

PrestaShop Core Weekly - Week 11 of 2021

March 22, 2021, 9:00 am
$
0
0

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

Core Weekly banner

Releases

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

Code changes in the ‘develop’ branch

Core

  • #23650: Introduce Experimental Feature data model, by @matks

Back office

Front office

  • #8738: FO Don’t display shipping method for virtual cart. Thank you @timactive

Code changes in the ‘1.7.7.x’ branch

Back office

Tests

Code changes in modules, themes & tools

Faceted search module

eslint configuration

  • #5: Migrated from Travis CI to Github Actions, by @Progi1984

Decimal

circuit-breaker

TranslationTools Bundle

Auto Upgrade module

Changes in developer documentation

Customer reassurance block module

PrestonBot

Prestashop UI Kit

PrestaShop Virtual Machine

PrestaShop PHPStan extension

  • #22: Introduce acceptance tests with phpstan PHAR, by @matks

PrestaShop Specifications

Core Weekly Generator tool

User documentation landing page

Email Alerts module

Where to start contributing?

What about adding the missing discount label in Front Office for products with attributes? This is a bug report submitted 1 year ago, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @PierreRambaud, @Progi1984, @atomiix, @boubkerbribri, @industria01, @dependabot[bot], @matks, @NeOMakinG, @jolelievre, @eternoendless, @okom3pom, @sowbiba, @ks129, @nesrineabdmouleh, @micka-fdz, @jf-viguier, @JevgenijVisockij, @timactive!

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 12 of 2021

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

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

Core Weekly banner

General messages

Dear developers,

PrestaShop 1.7.7.3 is currently being validated by QA team.

Other releases are also expected to happen soon! Email Alerts module v2.3.0 and Share Buttons module v2.1.1.

And the next public open source demo is going to happen on next Wednesday 31st of March 2021, at 2pm CET.

The session will be kept in record on YouTube, so it can be watched later if this timeslot is not suitable for you.

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

Code changes in the ‘develop’ branch

Core

Back office

Front office

  • #23151: Remove microdata in html flow and replace by JSON-LD for classic theme. Thank you @fdonnet

Installer

Tests

Code changes in the ‘1.7.7.x’ branch

Core

Front office

  • #23688: Fix display of color section on the add to cart modal on FO, by @NeOMakinG

Tests

Code changes in modules, themes & tools

Changes in developer documentation

Currency selector

Customer data privacy block module

Faceted search module

User documentation landing page

Share Buttons module

Customer reassurance block module

Issues Bot

User documentation (Italian)

Email Alerts module

Cross-selling module

Auto Upgrade module

  • #391: Wait For page to reload before putting it under maintenance on e2e tests, by @boubkerbribri

PrestaShop PHPStan extension

  • #23: Add extension into acceptance tests, by @matks

PrestaShop Specifications

Where to start contributing?

What about redirect a customer to product page or checkout after a successfull account creation? This is a feature idea submitted 1 year ago, and it is one of our good first issues.

Good first issues are a list of all beginner-friendly improvements and bugs to fix in the project. You can read more about this label on our article about it.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @eternoendless, @Progi1984, @dependabot[bot], @github-actions[bot], @kpodemski, @sowbiba, @Julievrz, @JevgenijVisockij, @matks, @boubkerbribri, @PierreRambaud, @jolelievre, @okom3pom, @NeOMakinG, @marionf, @zuk3975, @SD1982, @matthieu-rolland, @fdonnet!

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!

↧

Release of PrestaShop 1.7.7.3

March 30, 2021, 7:00 am
$
0
0

PrestaShop 1.7.7.3 is now available. This maintenance release fixes 10 bugs reported on previous 1.7.7 versions, as well as one security issue.

1.7.7.3 is available!

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

Reminder: the 1-Click Upgrade module’s latest version is v4.12.0, don’t forget to upgrade it before using it.

Main fixes

Below are listed some main regressions we fixed in this version:

Back Office

Front office

Read the full changelog here.

Security fixes

One security fix have been included in this patch version:

Acknowledgments

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

Boubker Bribri, Franck Lefèvre, Mathieu Ferment, Nesrine Abdmouleh, Pablo Borowicz, Pierre Rambaud, Thomas Baccelli, Valentin Szczupak

Thank you!

Download PrestaShop 1.7.7.3 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.3 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.3. Upgrades from a standard 1.7.x version should work just as well.

↧
Viewing all 939 articles
Browse latest View live
Search