OXID eShop v6.0.0 RC2 is published

OXID eShop v6.0.0 release candidate 2 is publicly available. We explicitly want to express that you can from now on, start developing your projects on this release. You may find it tagged as https://github.com/OXID-eSales/oxideshop_ce/tree/v6.0.0-rc.2 on GitHub.

But why it is not called “stable” yet? We are concerned that also other points than just a software package belong to a „stable“ version like for example an update path from former versions, documentation for this series, content of OXID Academy etc. All this is planned to be released by the end of this year. OXID eShop v6.0.0 RC2 now has become to the state of feature freeze, no more important changes, just bug fixes.

With this version, you’ll get a fully featured “compilation” in a manner that all modules like PayPal, Paymorrow, Payone, VCMS (PE + EE), the new WYSIWYG editor “summernote” (for all editions) as well as templates will be included in this version.

Other changes in comparison to OXID eShop v6 RC1:

  • PayPal is completely adapted to OXID eShop v6. If you want to write your modules from scratch for OXID eShop v6 on, this would be a good template. We’ll shortly come up with a tutorial to explain how to write modules for OXID eShop v6.
  • The ERP/SOAP interface as well as the eVAT module are ready to be used with OXID eShop v6.
  • Unified namespaces where introduced. This is relevant for version independent development of OXID modules. We will shortly publish a blog post about this topic for more detailed information.
  • The admin panel got a slight face lift.

Please remember that the so called “dyn pages” were completely removed from the code base, please use appropriate modules instead such as for connecting OXID eShop with Trusted Shops.

We also announced earlier that some rarely used functions (guest book, statistics etc.) were removed from the shop core and bundled as modules. Partially, we will even not deliver the compilation with these modules. Some of them will still be maintained by the OXID core team, and some other really rarely used modules will be moved to OXIDprojects in the hope that those who need it can still find them here.

One more important information: We announced that the entire shop shall run in UTF-8 only mode. When testing that we saw that there might happen some “unpredictable side effects” in memory usage with the oxIDs in conjunction with joins, for example in modules. To prevent this, we still kept them in latin collation.

To see the entire change log, please turn to this page: https://github.com/OXID-eSales/oxideshop_ce/blob/master/CHANGELOG.md

Updating and installing OXID eShop v6.0.0 RC2

The most simple way to install the OXID eShop is to run the Composer command and create a project. Please make sure you have the latest version of composer installed by running composer self-update.

By default, Composer installs the OXID eShop compilation including the development ressources (e. g. OXID Testing Library, IDE helper, Codesniffer). If you are planning to install the OXID eShop Compilation on production environments, make sure to add the nodev flag.

  • For Community Edition run:

  • For Professional Edition run:

  • For Enterprise Edition run:

For updating OXID eShop from RC1 to RC2, please run the following steps:

  1. Update composer.json file according to these changes.
  2. In the project, run:

    for updating dependencies.
  3. In the project, run

    for executing all necessary scripts.

Please update on your own risk, we recommend installation from scratch.

If you have an older version then 6.0.0 RC1, you might be interested in installing the OXID development tools. In this case, check and add these changes to your root composer.json before running “update”.

Credits

In this release, some pull requests could be merged. We want to gratefully thank

  • @gerlweb for pull request #547
  • @alfredbez for pull request #557
  • @michaelkeiluweit for pull request #558

 

0.00 avg. rating (0% score) - 0 votes
0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *