In diesem Blog-Beitrag geht es um das Testen von Legacy-Anwendungen wie beispielsweise Magento 1 Shops. Als Magento Freelancer liegt mein Fokus insbesondere auf Testing-Strategien, die sehr einfach und kosteneffizient für meine Kunden umzusetzen sind.
Over the years I have collected several useful layout XML code snippets that you can e.g. insert into individual Magento CMS pages or into your layout xml code in the local.xml file. This offers several chances to improve your search engine optimization (SEO) for your Magento store like noindex or canonicals.
Im folgenden Blog-Post möchte ich die aus meiner Sicht wichtigsten Aspekte erläutern, warum für mich Magento 1 bzw. der Community-Nachfolger OpenMage nach wie vor eine absolut sinnvolle Lösung für Kunden sein kann. Außerdem zeige ich anhand meiner eigenen Website konkrete Implementierungsmöglichkeiten auf.
In my daily work I regularly take over legacy projects from customers that have a relatively old code base and shall be upgraded in order to be compatible with latest software versions, PHP versions and so on. Within those projects I always use several techniques to quickly get to work but at the same time carefully try to not introduce new defects.
In the following blog post I will take you through several tips when you take over legacy projects.
If you are maintaining several Magento instances or use features like AWS autoscaling, you have many different places to look for your Magento application logs. In these cases a central logging application is very helpful.
In this post we will examine how to use the ELK stack with Magento logs.
While tweaking your Magento 1 online shop for performance you might have come into try to remove the default Mage_GiftMessage extension.
Unfortunately like many other default extensions, this module cannot be removed so easily because of some errorneous, hidden dependencies in other modules.
So let’s have a look what needs to be done in order to remove the default Magento Gift Message Extension.
As we all know Magento 1 was using latest technologies at the time it has been published more than 10 years ago in 2008. In the meantime, of course, used libraries and development patterns have been outdated, so is the case with Prototype. This post is about how to start to remove the Prototype library from Magento 1 or OpenMage.
Especially for Magento 1 after its end of life but also for Magento 2 it is important that you secure the Magento instance as best as possible.
In the following I will list some tips of that I use for my clients to secure their Magento backends.
In the field of search engine optimization (SEO) everyone tries to write the content in best quality from a customer perspective and ultimately also for the search engine. One important aspect therein is to avoid duplicate content as this is a major problem for search engines.
In this post I will clarify what duplicate content is and show a common source of duplicate content in Magento.
After the official end of life of Magento in last June, I recommended two ways of continuing with Magento 1 to my clients: either use MageOne to take care of providing security patches and updates for the latest Magento Open Source version 1.9.4.5. Or use the community-driven OpenMage fork of Magento. In this post we will see how I did the migration of my own website from Magento 1.9.4.5 to OpenMage.
Recently I discovered a bug in the core Magento 1 PayPal Express extension that leads to the user being redirected to the home page after PayPal checkout with no error message.
As the investigation was a rather lengthy process, I’ll tell you the details and of course the easy fix in this post here.
In my recent blog post for our Recolize Recommendation Blog I highlight some of changes that browser vendors are implementing regarding the handling of cookies in 2020.
For a long time Apache has been the defacto standard for hosting PHP web applications like Magento 1 or WordPress. Then with the rise of the need for high-scaling applications hosted in the cloud webservers like nginx or full page caches like Varnish became popular in order to handle the enormous amounts of traffic pouring in. The LiteSpeed webserver for Magento 1 is the new cool kind in the block now.
Approximately in every third Magento project that I am doing I get the request to implement some kind of Dropshipping. That’s why I want to give a short overview of how to handle that with Magento.
Today I was asked by a client if he should upgrade his Magento 1.5.1.0 store to the latest Magento Community Edition 1.9.1.1.
Basically I recommend following the PSR-2 standard for Coding Style Guidelines in Magento projects. Verifying your coding styles makes sense in any case – whether you are working in a large team of developers or as a freelancer for several clients. Agreeing to one common coding standard and following the rules improves readability and comparability.
Yesterday I had an interesting problem in a Magento community installation of one of my clients:
A lot of my clients complain about the fact that they receive tons of spam messages via the Magento contact and review forms.
In Magento 1.9 there is a JavaScript error on the product page in the backend that prohibits adding links to downloadable products when using the default German localization that ships with this Magento version.
I am often asked by my clients which Magento Extensions I can recommend for their shop. Thats why I created a (probably incomplete) list of Magento 1 extensions that I regularly use in my Magento projects: