đđ Greetings, fellow Mage aficionados! Brace yourselves for the magical unveiling of our latest release for this great 2023: OpenMage 20.3.0! đđĒŠ
This release isn’t just another update; it’s a recipe for the end of the year ecommerce party, with great ingredients like bugfixes, security enhancements, components and subsystems upgrades with a sprinkle of performance improvements.
OpenMage continues its remarkable journey with an important new release!
Among the numerous pull requests, one truly stands out. After months of development, we are thrilled to announce a significant upgrade to a core component of the OpenMage backend:
The TinyMCE rich text editor skyrockets from its “more than 10-years-old” version 3 to the new and shining version 6.7!
After the colossal 20.1.0 2 release just a few weeks back, it’s time for a little “smooth the edges” update, but don’t be fooled, it’s as important as your morning coffee!
When working on OpenMage or any complex PHP project, you might come across issues that require patches to be applied to third-party packages or libraries. These patches may be fixes or features for core code that you need to use immediately but have not yet been merged or formally released for any number of reasons.
In this blog post, we’ll explore the benefits of using privately maintained patches and how to use Composer and the cweagans/composer-patches dependency to maintain your own set of patches as well as how to generate patches.
Since the approval of our second RFC - release schedule OpenMage 19.x enters and “patch only” state, it will be maintained for two more years as promised but only significant security patches or regression fixes will be ported to v19, every other development (and we have many) will be focused on v20+.
We encourage everybody to upgrade to v20, it is our latest and greatest and deserves the bit of work necessary for the upgrade (ask your developer/agency, don’t do it yourself).
With this security update a single issue was fixed.
This important security update includes six security issues:
In backend > Catalog > Manage Categories, we can configure a category page and put it on the main menu. The page contents are rendered in
app\design\frontend\base\default\template\catalog\category\view.phtml
If we want to render an HTML table in which its data are taken from the database, we would follow these steps: