Please no more open-heart surgery in your productive environment! Use composer on your local dev machine instead after equalizing it with your server environment.
https://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.png00Marco Steinhäuserhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngMarco Steinhäuser2019-03-01 22:55:592019-03-01 23:12:20Using composer in your local dev environment
In the context of the new geo-blocking Regulation, it will become necessary to ensure that potential customers from across the EU internal market have access to and buy from your online shop. However, no online merchant is obliged to deliver, but has to create possibilities that the shipments can be picked up e.g. in the countries of delivery specified by you, if the purchaser gives a delivery address in this country and organizes the onward transport himself. In this tutorial we will show you how to configure the shop so that you comply with the new regulation on 3rd of December.
https://oxidforge.org/wp-content/uploads/2018/11/Selection_999005.png550618Benjamin Jörgerhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngBenjamin Jörger2018-11-29 21:32:572018-12-03 19:41:37Geo-blocking Regulation: how to configure OXID eShop to be compliant?
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.
https://oxidforge.org/wp-content/uploads/2018/09/Selection_962.png200290Clemens Scholzhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngClemens Scholz2018-10-01 10:41:492018-10-01 10:41:49Running OXID eShop in a subdirectory