- Category: Dev News
- Category: Dev News
Have you ever wondered who was hiding behind a GitHub username? It’s time to find out! Contributor interviews are a great way of getting to know the people who participate in the PrestaShop project. This month, meet Jonathan Danse, aka PrestaEdit.
Jonathan is a module developer. He’s also one of the first contributors to the PrestaShop project. It all started, somewhat by chance, during a job interview 12 years ago. In this article, Jonathan talks about his experience with PrestaShop, his work as a module developer, and his dedication to the open source project. And psst, Jonathan has some great news to share at the end…
Dear readers, meet Jonathan!
Hi Jonathan, can you tell us more about yourself?
I discovered PrestaShop in August 2010, during a job interview. I was still a student at the time. I didn’t know PrestaShop and I wasn’t prepared at all. They told me to install PrestaShop and do everything they asked… I didn’t even know where to download the file! This technical interview lasted 4 hours. It allowed me to discover PrestaShop. At the time, it was the 1.2.5 version.
So, my first job ever was to configure the multistore feature on a 1.2.5 store!
When did you get involved in contributing to the PrestaShop project?
Almost at the same time. I joined the forum in November of the same year. I started by asking questions. Then, I started answering questions from others. I saw this as an opportunity to learn.
In 2012, I also wrote two articles about PrestaShop for the “PHP Solution” magazine. It was a technical presentation of the 1.5 version.
At the time, we couldn’t contribute code as much as we do now. But as soon as PrestaShop moved from Forge to GitHub, I started submitting pull requests. I think I created the 7th or 8th pull request!
I was also one of the first people outside of the PrestaShop company to contribute to the User Documentation on Confluence.
So, as you can see, when I love something, I invest myself from start to finish!
What motivates you to contribute now?
It keeps me busy, I like it! I was a contributor before I was a module developer. So, even when an issue doesn’t benefit my business directly, I still contribute. Because I want to help others and help the project grow. It also allows me to learn and experiment.
Is there a pull request that you are particularly proud of, or that you want to tell us about?
Well, I’m going to talk about a pull request that I submitted in 2012 but that was never merged. I wanted to add combinations to virtual products. It was a big contribution, so it discouraged me a bit… But this pull request is really important to me as it made me realize that not everything could be included in the core software and that there wasn’t much missing to turn my pull request into a module. It took me 10 hours to create the pull request, and 2 hours to turn it into a module. It was my first module. I sold it on the PrestaShop Addons Marketplace and it became a best seller.
That was 10 years ago. The management of the project has evolved a lot since then. I think some people had a bad experience and didn’t try to contribute again. They should give it a second chance. And if they feel like something is blocking them, they should talk to the right people and get some help.
In your opinion, what benefits can module developers and agencies gain from contributing?
We often heard, and I agree, that agencies should contribute to the project instead of fixing the same bugs over and over. Some agencies say they need time. But, they have time because they have to do it for their clients anyway. But contributing can be considered a loss, as they charge their customers for the service. My opinion on this is that agencies’ value-added isn’t to fix the same bugs several times. It’s rather to do it once, so they can work on a functional tool, that will attract new merchants and retain customers.
But I’m not going to lie. At PrestaModule, we sell modules that can replace native modules. So of course, I’m not going to contribute to those native modules. I prefer to contribute to the core software, I think that’s where my added value is.
Do you have any advice for first-time contributors?
Try, simply try. A contribution, regardless of its size, its complexity, … is always important! If it’s important to you, it can be important to others as well. When I submitted my pull request to add variables to emails, I didn’t know so many people would use them! Even if you’re just adding a hook, this hook could help others as well! And it will prevent you from having to find a workaround.
Would you like to add anything?
Yes! I have great news! I’m going to publish a book about PrestaShop 8. I don’t know when it will be published exactly, but I’ll keep you posted! In this book, I’ll share my 10-year experience on PrestaShop with developers. It will be about modules and theme development. It’s really important to me!
That’s great news! Where can we follow you?
You can follow me on Twitter: https://twitter.com/prestaedit. That’s where I share my technical discoveries and tips!
Thank you, Jonathan!
If Jonathan’s experience has inspired you and you want to get more involved in the project, don’t hesitate to contribute!
🌞 Summer break for interviews
We’ll do a summer break and come back with new interviews in
September. In the meantime, if you would like to share your
experience and have your interview published on the blog, feel free
to send an email to:
- Category: Dev News
The post Log In Links for Your Laravel App During Development appeared first on Laravel News.
- Category: Dev News
Friendly reminder, after one month break the next session of the public PrestaShop demo from the maintainers team will happen this week, on Wednesday, June 1, 2022 at 4pm CEST!
We expect to share with you project news and present 4 topics:
- Update on the Horizontal migration by @matks and @tegbessou
- PHP 8.1 compatibility by @atomiix
- Improvements for Email alerts module by @marsaldev
- Update on the Hummingbird theme by @Hlavtox
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!
- Category: Dev News
This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 23rd to Sunday 29th of May 2022.
Last week @atomiix was able to deliver PHP8.1 compatibility for the Core! This is great news and it means PrestaShop 8 will be compatible with PHP8.1.
We will be able to explain more about this in the next session of the public PrestaShop demo that will happen this week on Wednesday at 4pm CET.
A quick update about PrestaShop’s GitHub issues and pull requests:
- 33 new issues have been created in the project repositories;
- 24 issues have been closed, including 3 fixed issues on the core;
- 62 pull requests have been opened in the project repositories;
- 47 pull requests have been closed, including 40 merged pull requests.
Code changes in the ‘develop’ branch
- #28559: Micro performance optimizations in Order class, by @kpodemski
- #28547: Remove use of Tools::stripslashes, by @kpodemski
- #28545: Remove deprecated in Cart model. Thank you @PrestaEdit
- #28402: PHP 8.1 compatibility, by @atomiix
- #26572: Add a button for disabling all non native-in modules in Performance page, by @Progi1984
- #28584: Product list bulk delete and duplicate actions. Thank you @zuk3975
- #28577: Combination list form inside product form, and combinations available labels, by @jolelievre
- #28561: Toggle “show price” and “delivery times” inputs visibility. Thank you @zuk3975
- #28558: Add fixed quantity update to bulk combination edition. Thank you @zuk3975
- #28533: Introduce SetDefaultCombinationCommand. Thank you @zuk3975
- #26004: Migrating product list part 2. Thank you @JevgenijVisockij
- #27755: Move registration logic to new controller. Thank you @Hlavtox
- #27187: Set country from browser language if option is set in customer address. Thank you @Amoifr
- #27952: Adding the PATCH method to the REST API (webservices) + API cache management FIX. Thank you @nsorosac
- #28575: Fix UI tests by selecting country on FO, by @boubkerbribri
- #28527: Functional Tests - Add test ‘Choose address’ in create order page. Thank you @nesrineabdmouleh
Code changes in modules, themes & tools
- #302: img responsive on modal shopingcart. Thank you @rodriciru
- #294: Improve quickview modal. Thank you @mparvazi
- #293: TypeScript types improvements, by @NeOMakinG
- #292: Add customization modal for product line. Thank you @mparvazi
- #288: Improve useQuantityInput and fix minor bug. Thank you @mparvazi
- #285: No Carousel on no image product. Thank you @rodriciru
Docker internal images
Customer reassurance block module
- #406: Bump @babel/eslint-parser from 7.17.0 to 7.18.2. Built by @dependabot[bot]
- #405: Bump eslint from 8.15.0 to 8.16.0. Built by @dependabot[bot]
- #38: Bump stylelint from 14.8.3 to 14.8.5. Built by @dependabot[bot]
- #35: Bump stylelint from 14.8.2 to 14.8.3. Built by @dependabot[bot]
Faceted search module
- #665: Bump @babel/eslint-parser from 7.17.0 to 7.18.2. Built by @dependabot[bot]
- #664: Bump @babel/preset-env from 7.18.0 to 7.18.2. Built by @dependabot[bot]
- #663: Bump @babel/core from 7.18.0 to 7.18.2. Built by @dependabot[bot]
- #662: Bump eslint from 8.15.0 to 8.16.0. Built by @dependabot[bot]
Wishlist block module
The PrestaShop open source project
Architecture Decision Records repository
Changes in developer documentation sources
- #1375: Explain what files does what in form themes, by @matks
- #1371: Update Faceted search doc, by @matks
Distribution API client
Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @rodriciru, @Quetzacoalt91, @dependabot[bot], @jolelievre, @mparvazi, @zuk3975, @NeOMakinG, @boubkerbribri, @kpodemski, @PrestaEdit, @nesrineabdmouleh, @matks, @tegbessou, @atomiix, @nsorosac, @Hlavtox, @Saimis777, @Amoifr, @Progi1984, @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!