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)
The behaviour of the PHP function __isset was changed with PHP version 7.0.6. OXID eShop makes use of this function __isset for lazy loading, and because of these changes lazy loading might behave unexpectedly in OXID eShop. Please read this blog post to avoid this unexpected behaviour in your projects and/or modules.
https://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.png00Igor Iegupovhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngIgor Iegupov2018-05-18 13:58:332019-02-16 22:23:08Function __isset and model lazy loading with different behaviour in PHP version 7.0.6 or newer
In order to improve the OXID eShop core code we are going to change some main principles of overwriting classes and methods when changing OXID eShop functionality with modules: methods may now be marked as private. This is not to cut away possibilities; there’ll be other means to catch up with what you want to achieve.
https://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.png00Koltanhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngKoltan2018-04-09 12:21:532018-04-09 12:21:53Announcing new principles in the OXID core and how you will benefit from them
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.
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-04-09 12:21:092018-04-25 01:00:46OXID eShop version 6.0.2
We recently released OXID eShop 6.0.2 including some changes in preparation of the upcoming European Data Protection Regulation (GDPR) that will be applicable as of May 25th, 2018 in all member states to harmonize data privacy laws across Europe.
https://oxidforge.org/wp-content/uploads/2018/04/2390666040_5a9d52b896_o-1.jpg597797Benjamin Jörgerhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngBenjamin Jörger2018-04-09 12:20:212018-04-25 01:00:55GDPR compliance with OXID eShop version 6.0.2
CVE Identifier: CVE-2018-5763: An attacker is able to bring servers to standstill by calling specially crafted URLs if OXID High Performance Option is activated and Varnish is used (denial of service/DoS).
Nice thing about OXID eShop, they provide a development environment. Without big effort you can get have the shop up and running on a virtual machine. The current blog post will give some hints for how to run the shop tests that come with the shop. We will cover how to run module tests in a follow up post.
https://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.png00Heike Reuterhttps://oxidforge.org/wp-content/uploads/2018/01/OXID_forge_sub.pngHeike Reuter2017-12-16 00:59:002018-01-23 18:03:02Run tests for OXID eShop 6