V6 to big metapackages, what about suggests?

Hi all, why do the meta-packages require a lot of optional stuff e.g. (demodata, amazon-pay-sdk, amazonpay4oxid, payone, …)? From a perspective of an EE user, it is not really handy to build a custom composer.json with all the OXID components along the whole hierarchy and dependencies

Re: EE 5.3.7 migration to EE 6.0.2 is buggy

instagram.com/closedofficial <https://www.instagram.com/closedofficial/> Amtsgericht Hamburg HRB 53868 | Umsatzsteuer-Ident.-Nr.: DE 164980577 GF: Gordon Giers, Til Nadler, Hans Redlefsen Von: Jens Trant <jens.tr...@closed.com> Datum: Dienstag, 10. April 2018 um 13:22 An: &quo

EE 5.3.7 migration to EE 6.0.2 is buggy

Hi guys, I spent yesterday only a few hours for a test migration from EE 5.3.7 to 6.0.2, which seems to be actually buggy. Maybe there is a newer/more compatible source for migrations which I have missed?! My source was the official documentation:

AGB / Terms and conditions checked does not work in checkout

Hey guys, kindly let you know that the built-in terms and conditions check in the checkout process does not work (always accepted) if you use the shipped PayOne module with OXID (EE, maybe also PE). The mistake is in the 'fcPayOneOrderView.php' which is shipped with in OXID EE (maybe also PE)

Re: [oxid-dev-general] Quick SOAP ERP Connector question

== => https://www.myeshopurl.de/modules/erp/oxerpservice.php?wsdl=2.14.0 is also not working. Mit freundlichen Grüßen | Warm Regards, Mirza Ahtasham Ahmad M +4917645387460 | Skype: ahtasham82 On Fri, Apr 29, 2016 at 11:14 AM, Jens Trant