The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.

The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Tumblr, and Blogger.

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 Julius Zukauskas, aka zuk3975.

image

Julius comes from Lithuania. He works at Invertus, an ecommerce agency with a Platinum partner status in the PrestaShop Agency Partner program. Half of his time is dedicated to the open source project, and more specifically to the Symfony migration.

So, why exactly would an agency contribute to the open source project? Julius answered this question and many more.

Dear readers, meet Julius!

Hi Julius, can you tell us more about yourself?

Yes, of course. My name is Julius and I come from Lithuania.

My career as a developer started 5 years ago. Before that, I was working in a completely different field.

I studied physical therapy in college. It was interesting but I quickly realized that I didn’t want to keep on working in this field. So I decided to take Web development courses. The Invertus agency first welcomed me as an apprentice, then hired me on a permanent contract.

About my hobbies, I love all kinds of sports, but I’m especially passionate about martial arts. I also like jogging, especially in forests and parks. I love nature!

When did you get involved in the PrestaShop project?

My story with PrestaShop also started at Invertus. The agency is a Platinum partner in PrestaShop’s Agency Partner program. Most of our clients use PrestaShop to build and manage their online stores. So, that’s how I first got involved in the project. Then, I was assigned to the Symfony migration and that’s how I started contributing. I got in touch with maintainers and contributors.

The Invertus agency works with many different clients. Do you find it different to work for an open source project, compared to a regular client?

Many of our customers use PrestaShop so I’m used to it, it’s the same environment. However, the main difference with other projects is longevity and backward compatibility. When a change is merged to the PrestaShop project, it’s going to stay there for a while. You can’t just delete something as if you were the only one using the solution. Many people are using it, and once something is added, it takes much longer to remove it than in “regular” projects. When something is removed, we need to create a depreciation notice and make sure there is a replacement for that method. But also explain why it was removed and provide information on how to use the new method, etc.

In your opinion, how could agencies be encouraged to contribute more to the open source project? What benefits can they get from it?

First of all, I think it’s important to understand why they don’t contribute. When agencies are developing modules for their customers, for example, they may find bugs. They could contribute to fixing these bugs but they wouldn’t be able to quickly benefit from the fix. So, even if they submit a pull request to fix the bug, agencies will still have to find a quick solution for their customers.

That said, I still think contributions are beneficial to agencies. If they fix issues in the core software directly, they won’t need to fix the same bug over and over each time they have a new customer.

So, if you’re an agency: help your future self and contribute to the project.

Do you have any advice for first-time contributors?

There are a lot of pull requests available on PrestaShop’s project repository that you can learn from. When you submit a pull request, be as specific as possible: explain your use case and give some examples. Adding a screenshot usually helps too. And when you open an issue, remember to answer the following questions: what is your use case and why is it important?

Also, don’t hesitate to join the community on Slack.

Would you like to add anything?

I’m glad to work on the PrestaShop project. The PrestaShop community allows the project to grow, but it also allows me to grow as a developer!

Thank you, Julius!

If Julius’s experience has inspired you and you want to get more involved in the project, don’t hesitate to contribute!

Read more

Details
Category: Dev News

image

Laravel Nova author David Hemphill released the Nova Log Viewer source code—a tool for viewing your application logs via the Nova UI

The post Nova Log Viewer Package appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

Read more

Details
Category: Dev News

image

Simple code execution monitoring, built for developers Identify bugs and bottlenecks in your server side code before your users do.

The post How Code Execution Monitoring can help you to identify bugs and bottlenecks in your application before your customers do appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

Read more

Details
Category: Dev News

image

Learn how to monitor your Laravel application by services and not by hostnames.

The post How to monitor your Laravel application by services (not by hostnames) appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

Read more

Details
Category: Dev News

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase from Monday 25th of April to Sunday 1st of May 2022.

Core Weekly banner

General messages

Dear developers,

The entire team is working hard on PrestaShop version 8, with a freeze date planned for second half of May - this is why we decided to cancel our May Public Demo to focus on the release, and then present the community with amazing demos in June.

Releases

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

Code changes in the ‘develop’ branch

Core

Back office

Front office

  • #27397: Add the minimum required to the error message, when trying to apply a cart rule with a minimum. Thank you @Prestaplugins

Installer

Tests

  • #28381: Fix error in title controller test, and fix a warning in module tests, by @jolelievre
  • #27055: Split integration workflows into two, get rid of processIsolation, by @jolelievre

Code changes in the ‘1.7.8.x’ branch

Core

  • #28347: Bump modules (blockwishlist to 2.1.0, ps_facetedsearch to 3.8.0, ps_imageslider to 3.1.1), by @Progi1984

Back office

Installer

  • #26951: Fix Dockerfile for local image generation in branch 1.7.8.x under Linux. Thank you @mpaolino

Tests

Code changes in modules, themes & tools

Hummingbird theme

Contextual Help API

  • #7: Adding preprod environment. Thank you @djodjo3

Changes in developer documentation sources

stylelint configuration

Email Alerts module

  • #115: Prevent compatibility issues with the future version of psgdpr, by @kpodemski
  • #112: Display of list of notifications in my account. Thank you @lmeyer1
  • #111: Remove class unused in classic theme, but breaking comp with BS4. Thank you @lmeyer1

GDPR module

Classic theme

Customer reassurance block module

Faceted search module

Auto Upgrade module

  • #480: Bump to 4.15.0, by @matks
  • #462: Add hooks displayAdminThemesListAfter and displayModuleConfigureExtraButtons for 8.0.0, by @sowbiba

Image slider module

Currency selector

  • #28: Replace deprecated ObjectPresenter namespace, by @kpodemski

Links list module

Search Bar module

Wishlist block module

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @jolelievre, @marsaldev, @djodjo3, @mparvazi, @NeOMakinG, @PululuK, @Progi1984, @nesrineabdmouleh, @carcam, @dependabot[bot], @kpodemski, @hibatallahAouadni, @matks, @Amit-Kumar-Tiwari-Webkul, @zuk3975, @atomiix, @lmeyer1, @PrestaEdit, @Hlavtox, @sowbiba, @SharakPL, @Prestaplugins, @PierreRambaud, @mpaolino!

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!

Read more

Details
Category: Dev News
  1. WordPress.com Favorites: The Pelikan’s Perch
  2. Livewire or Inertia.js?
  3. Laravel 9.10 Released
  4. Generate Documents in PHP With an Excel Template
  5. Handle SEO for Your Models With this Laravel Package
  6. PrestaShop Core Weekly - Week 16 of 2022
  7. Service Providers in Laravel: What They Are and How to Use Them

Page 9 of 1108

© 2022 Extly, CB - All rights reserved.