I’ve been asked several times how to run OXID eShop in a subdirectory like https://myluvelydomain.com/shop/. Actually, there are several methods to achieve this goal including the adaption of your apache vhost or via .htaccess forwarding. In this blog post I will describe how to use unix symlinks to resolve the situation as it is a very smart solution that can even be used to roll out and back between several versions of your project without any downtime.
About Clemens Scholz
My first job: "Magic Coder", from 2000 forward the main focus always was PHP. Joined OXID as DevOps Engineer in the end of 2017.
Besides the fascination IT, my other passion is to write trashy SciFi stories.
Entries by Clemens Scholz
We’ve experienced requests concerning the “Right to data portability” (Art. 20 GDPR) on several channels. The legal text states someat like ” … receive the personal data … in a structured, commonly used and machine-readable format…”. As this is not a clear specification, provide an SQL script for reading out all relevant information from the database. Get the script from this blog post.
This patch update was extraordinarily pushed up to give you a proper time frame to establish the GDPR compliance with OXID eShop. Additionally, we started to introduce new principles of code writing in order to become more flexible, agile and innovative when changing the core. Anyway, this patch update contains bug fixes as well as loads of pull requests.
Would it not be grand to to automatically generate the source code documentation for your own project, no matter what OXID eShop edition is used? Learn in this blog post how to do it.