Categories are not in use in this blog. Please use the tags or other elements to navigate.
On 15th of February 2018, E-commerce Berlin EXPO will take place again at STATION. I attended already in the last year and was surprised to see other faces than usually on events in this line of business. No wonder: E-commerce Berlin EXPO is much more multinational than other events usually are. Surprisingly, e-commerce vendors are not the majority, online merchants will cover a high percentage of [Read more...]
A while ago, OXID officially announced the availability of a unified development environment OXID Developer VM, based on Ansible and Vagrant. To be honest, I quarreled with it a long time and put hours and hours to understand the concept behind (by trial and error). Finally, I made it with some help of my dear friends and colleagues to get the basic principles and to have it up and running a [Read more...]
Today, I want to inform you about some personnel changes and re-structuring at the OXID core development department. By 1st of June, Benjamin Jörger will take over the job as Head of Development. Benjamin studied Business Informatics, used to work as a software developer in different branches and switched over from the Java/Oracle world. In 2012, he started working as a Project Manager at our [Read more...]
Going over this January's IT and e-commerce news, it was dominated by evil tidings about security issues in this or that web based system. In quick succession, different web applications were on the "security advisory" news: PHPMailer, Magento and Shopware. In a matter of fact, none of the software vendors (not talking about delivering commercial or open source software) is immune to security [Read more...]
This is a quick note to let you know that OXID eShop versions 4.8.11 Professional and Community Edition (5.1.11 Enterprise Edition) as well as OXID eShop versions 4.10.0 beta PE and CE (5.3.0 beta EE) have been published. Please note that, due to O'Brians law ("Murphy was an optimist"), the release of OXID eShop version 4.9.8 PE and CE (5.2.8) has to be postponed until next week. Here are [Read more...]
Most likely you already know that, if you want to send a pull request to one of the OXID public repositories, it is policy to agree to a contributor license agreement (CLA) before. Please read more about the why and what in OXID's FAQ on this topic. When we started accepting contributions, it was still necessary to sign a paper manually and to send it back to us; later we found a service that [Read more...]
A couple of days ago we were surprised by an unusual pull request on GitHub. The contributor, @Haehnchen, simply requested to remove the file .phpstorm.meta.php because of a native PhpStorm plugin. Indeed, Daniel Espendiller, the real name behind @Haehnchen, wrote and distributed a well working native OXID plugin for JetBrains PhpStorm under MIT open source license. As he describes, this plugin [Read more...]
The German portal onlinemarketing.de recently published a guest blog post by Herbert Buchhorn of clicks.de. The author used a checklist of SEO specific built-in features, but omitted significant advantages OXID is offering. I will adapt the same check list to show what OXID eShop can deliver from a SEO perspective. As I'm frequently asked about SEO topics anyway, I hope you will enjoy the post, [Read more...]
A couple of days ago, on 7th July, OXID was awarded with the PayPal Partner Award 2015. For this reason, our CEO Roland Fesenmayr went to Berlin for PayPal partner day, received the accolade and suddenly disappeared from one second to another. He popped up back home in Freiburg explaining that he simply used the time machine app, whew! However, I personally don't believe in that stuff. [Read more...]
If you want to send a pull request to a certain project on GitHub, you first have to fork it to your own repository and then - in the most cases - clone it to your local machine. If you're contributing to a very active project with many commits, the size of this download will grow over the time. This is because the entire commit history of the project will be cloned to your machine as [Read more...]