Pradip Shah’s Post

Most of the magento extensions 99% of them are garbage, and 90% of the performance issues are because of the 3-5 installed extensions. These extensions are usually harmful because they reuse broken Magento 2 core framework with performance issues (Collections, Repositories, Plugins, etc.). If you are removing those Amasty, Welt Pixel and other crap, you have a chance to have a good magento Store without re-platforming to Hyva. Anyway, Hyva will remove it because it doesn't support or the store will be slow anyway. Keep your store close to the core functionality. Think twice when adding 3-d part crap to your store.

How To Create Magento 2 Headless NextJs Setup? Magento 2 headless setup with Next.js involves several steps, including setting up the Magento backend, configuring GraphQL, and setting up the Next.js frontend. Here’s a step-by-step guide: 1) Magento 2 Rest And GraphQL APIs 2) Create A New Next.Js Project 3) Configure Apollo Client 4) Get Data From Magento  5) Styling And Additional Features  6) Deployment Read more: https://lnkd.in/dTwYA_Ym #magento #headless #nextjs #React

Check out our latest blog post on creating a custom admin theme in Magento 2!🛠️   Whether you're enhancing the usability of your admin panel or aligning it with your brand's look, this guide covers everything you need. Perfect for developers looking to streamline their Magento 2 backend. 👉Read the full article: https://lnkd.in/dK7bxJKF #Magento2 #Ecommerce #CustomAdminTheme #DevCommunity #TechTips #CapitalNumbers

How does Tightly coupled Magento 2 headless NextJs work? A tightly coupled headless solution with Magento 2 as the backend and Next.js as the front-end, allowing for efficient data fetching and rendering. Adjust and extend the architecture based on your specific requirements. Link: https://lnkd.in/d9-PRkH2 #nextjs #magento2 #graphql

Ever debug Magento without a toolbar? 😅 I don't always use a Magento dev toolbar, but when I do, it's QuickDevBar. Vincent Pietri's Developer Toolbar was recently revamped to play nice with FPC and comes with a few things that make it awesome: - Info panel shows you everything about your controllers and routes - Design panel lets you see your layout handles without digging through XML - Profile panel keeps track of observers, collections, and more - Query panel helps you find those slow database queries - Built-in log viewer saves you from jumping to the terminal - Catches all those dump() calls we forget to clean up And the best part is that you can even create your own custom panels and add them to the tool. Grab QuickDevBar on GitHub at https://lnkd.in/g4uzMydd

Struggling to keep your Magento indexer modes consistent across deployments? Wish you could lock them down more effectively? The element119 Indexer Deploy Config module for Magento 2 is here to help. This module allows developers to lock indexer modes via deployment config, ensuring consistency and control over your indexer settings. Here's why you'll love it: 🔒 Lock Indexer Modes: Selectively lock indexer modes via the app/etc/config.php file. 🔍 Validation & Import: Indexer configurations are validated and imported during app:config:import. 🔧 Custom Indexer Support: Works seamlessly with custom indexers. 📢 Admin Messaging: Admins are informed which indexers are locked and get alerts when attempting changes. 🌐 Broad Compatibility: Supports both Magento Open Source and Adobe Commerce, as well as Hyvä and Luma themes. ⚙️ Developer-Friendly: Designed for easy customization and integration. If you're ready to take control of your indexer modes and streamline your deployments, get the module on GitHub at https://lnkd.in/gsPGYFKf #magento #magento2 #php #ecommerce #opensource #github

In magento development if you follow proper development rule with some key thing in mind for CWV then we can get really Good performance even in magento default luma theme. #performace #magento

We have another great question from Isaac Phillips! You’re working on a Magento 2 project with a custom GraphQL-based frontend. During the checkout process, it's necessary to have some additional logic that happens when the qty changes or updates are made on the cart page. A plugin was added on Quote::save for that purpose, but, during testing, you notice that the plugin also runs during the shipping and payment steps, causing unintended side effects. What’s the best way to ensure the plugin doesn't get triggered on those additional steps? ℹ Comment with your answer and reasoning. #swiftotter #magento #magentodeveloper #adobecommerce #weeklypracticequestion

In my new Magento Code That Sucks course, we covered how to fix the N+1 query problem in Magento. There are many other solutions to this problem! We could pop an item onto a queue with RabbitMQ, or orchestrate a custom query in a few different ways. But one other solution to process a large dataset in a short amount of time is by using the Zepgram_MultiThreading module. This module allows you to define a callback within a custom processor for either a search criteria builder query, collection, array, store, or website. After writing your code, you'll go to the CLI and run the new "bin/magento thread:processor" command. Within that command you can specify a timeout, the number of iterations to run, any environment-specific variables, and whether or not to show a progress bar while executing the command. When the process is executed, child processes are created and run the callback function for each item within the resultset. Since each callback is executed in a separate process, it allows for much faster processing times over the built-in Magento methods. You could also by pass memory limit restrictions, because the mem limit will be reset when each child process is created. Get the module on GitHub at https://lnkd.in/gjUd-C_N

Okay, this Monday, I'd like to share a conversation I had with my team. How often do you debate with your team when it comes to Magento development, following standards, and aiming for performance? It was the day I shared my review with the Magento developer leading the Magento + hyva theme development project, where the client wanted to score 90+ and launch the store in 4 weeks! Knowing how destructive the code was was crucial, and it was a bit intimidating for me to manage this. So we went as a fresh development. Now, the time came when my dev asked to hold for a while, where he submitted the ticket for the vendor to resolve the conflict issues within their extensions. (YKIYK) I mean, common; I have built a team where I want them to groom themselves by taking a leap to manage everything in-house. What could be the reason for providing service and product simultaneously? You have to go to that level where you have to find the root cause and do it yourself to get the timeline fulfilled. That's where I have wished my team at Navigate Commerce should perform. Not like a standard developer, but to serve clients globally, you have to raise the bar that fulfills the international scope. And you have to think in that direction. By now, we are on track and will resolve those teething issues to have the 90+ score. 🚀