Issue fix

At work this week I was updating the deployment scripts for one of our projects
when I realised that Hyva wasn’t generating the app/etc/hyva-themes.json
file on deployment which then caused the pipeline to fail.

In a local development environment, all images from the live system are usually missing. You can solve this problem by downloading images from a live server on-the-fly. Here's how to pull it off.

Ever feel like you're on a wild goose chase trying to track down missing products in your Magento 2 collections? I think we’ve all been there before. It's frustrating when you're sure a product exists, but it's nowhere to be found in your foreach loop.

This issue crops up more often than you might think. I've seen countless developers scratch their heads, wondering if they've gone crazy… or if Magento is playing tricks on them.

Server errors are among the most common Magento errors, especially of the Magento 500 variety. Wrangling up with an HTTP 500 internal server error can eat away at your precious time and resources. In light of that, let’s dive into the most likely causes behind these errors, and the solutions that developers should use to overcome these.

This extension aims to solve the problem of discrepancies between Magento revenue reports and the revenue reports in Google Analytics.

That problem arises due to the fact that a certain number of people close the browser window before returning to Magento's success page. Since Google Analytics is Javascript based, and thus client based, the GA Purchase Event will not be fired and the order will not be registered in Analytics.