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?
From now on you can additionally use Telegram to receive breaking news such as release notes and security bulletins when working with OXID. Read more about the Telegram integration in this blog post.
https://oxidforge.org/wp-content/uploads/2018/09/t_logo.png236236Marco Steinhäuserhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngMarco Steinhäuser2018-10-29 12:03:012018-10-29 12:03:01Use Telegram to receive breaking OXID dev news
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
CVE Identifier: CVE-2018-14020: An attacker is able to change the delivery address by bypassing the checkout process when using Paymorrow payment method.
OXID eShop 6.1.0 compilation contains two new modules (GDPR Opt-in + Klarna), monolog implementation, form field configuration, possibility to overwrite Smarty plugins with your own modules and is ready for the Personalization Option (EE). oxchkversion was removed from the admin panel.
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äuser2018-07-31 14:32:082018-08-02 15:53:16OXID eShop version 6.1.0
This patch update contains bug fixes (incl. security issues 2018-002 as well as 2018-003), GUI changes have been done. Furthermore, the modules Klarna and GDPR Opt-in were added to the compilation. See details in this listing.
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äuser2018-07-31 14:31:402018-08-02 15:56:18OXID eShop version 6.0.3
OXID eShop 6 introduced several improvements to the OXID eShop environment. These changes also have reached the module system, which leads to some new features for developers.
https://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.png00Steven Pfündlinhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngSteven Pfündlin2018-06-01 12:43:162018-06-01 12:49:39Module development in OXID eShop 6 – benefit from the new features
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.
https://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.png00Clemens Scholzhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngClemens Scholz2018-05-29 11:21:352018-05-29 11:21:35How we temporarily handle the right to data portability (Art. 20 GDPR)
Geo-blocking Regulation: how to configure OXID eShop to be compliant?
0 Comments/in blog English pll_5c004d9eea6a3 benjamin.joerger / Benjamin JörgerEU, geo-blocking, News, Regulations
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.
OXID eShop version 6.1.1
0 Comments/in blog English RBlank / Robert BlankNews, oxid6, Releases
OXID eShop version 6.1.1 is published and contains mostly bug fixes, no storefront changes.
Use Telegram to receive breaking OXID dev news
0 Comments/in blog English marco.steinhaeuser / Marco Steinhäuserannouncements, dev, messenger, News, telegram
From now on you can additionally use Telegram to receive breaking news such as release notes and security bulletins when working with OXID. Read more about the Telegram integration in this blog post.
Running OXID eShop in a subdirectory
0 Comments/in blog English clemens.scholz / Clemens Scholzdev, Infrastructure, Installation, oxid6, symlinks
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.
Security Bulletin 2018-003
0 Comments/in blog English OXID Security Team / OXID Security TeamNews, Security
CVE Identifier: CVE-2018-14020: An attacker is able to change the delivery address by bypassing the checkout process when using Paymorrow payment method.
Security Bulletin 2018-002
0 Comments/in blog English OXID Security Team / OXID Security TeamNews, Security
CVE Identifier: CVE-2018-12579: An attacker is able to take over an access to user account.
Summer releases 2018: OXID eShop 6.1.0, 6.0.3 and 4.10.8/5.3.8
0 Comments/in blog English benjamin.joerger / Benjamin JörgerNews, Releases
Two days ago we published three releases, OXID eShop 6.0.1, 6.0.3 and 4.10.8/5.3.8. Please read this blog post for a summary of the changes.
OXID eShop version 6.1.0
0 Comments/in blog English marco.steinhaeuser / Marco SteinhäuserNews, oxid6, Releases
OXID eShop 6.1.0 compilation contains two new modules (GDPR Opt-in + Klarna), monolog implementation, form field configuration, possibility to overwrite Smarty plugins with your own modules and is ready for the Personalization Option (EE). oxchkversion was removed from the admin panel.
OXID eShop version 6.0.3
0 Comments/in blog English marco.steinhaeuser / Marco SteinhäuserNews, oxid6, Releases
This patch update contains bug fixes (incl. security issues 2018-002 as well as 2018-003), GUI changes have been done. Furthermore, the modules Klarna and GDPR Opt-in were added to the compilation. See details in this listing.
OXID eShop version 4.10.8 (CE + PE) & 5.3.8 (EE)
0 Comments/in blog English marco.steinhaeuser / Marco SteinhäuserNews, Releases
No GUI changes, no other bugs fixed but security issues 2018-002 and 2018-003, EoL release of OXID eShop series 4.10.
Module development in OXID eShop 6 – benefit from the new features
0 Comments/in blog English steven.pfuendlin / Steven PfündlinAPIs, module development, Modules backend, Modules frontend
OXID eShop 6 introduced several improvements to the OXID eShop environment. These changes also have reached the module system, which leads to some new features for developers.
How we temporarily handle the right to data portability (Art. 20 GDPR)
0 Comments/in blog English clemens.scholz / Clemens ScholzGDPR, right to data portability
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.