OXID eShop v6.0.0 Beta3 is published
OXID eShop v6.0.0-beta.3 is publicly available as from now.
Information about changes
- Some 3rd party components have been updated to a newer version. These alterations can be found here.
- The routing of controllers is now compatible back and forth. Please see the details in these documents: namespaces in modules page and modules metadata v2.0 page.
- It is possible now to use virtual namespaces everywhere via instanceof, and type hints and exception catching are backwards as well as forwards compatible.
- A new security improvement (related to security bulletin 2016-001) has been added . Previously, in the source code, there was a so called “black list” of fields defined, forbidding user updates. This means that all new fields appearing in oxuser and oxaddress tables could have been updated by a signed-in user. In OXID eShop v6.0.0-beta.3, these fields were “white listed”, meaning that only fields described can be updated, but all new fields can’t. If there will be a need to add additional fields for updating user or address information via user forms in the storefront, you’ll have to extend this class:
OxidEsales\EshopCommunity\Application\Model\User\UserUpdatableFields
For the shipping address please use this class:
OxidEsales\EshopCommunity\Application\Model\User\UserShippingAddressUpdatableFields
Please read more about “Modify white listed fields” in this document. An example on how to extend an UpdatableFields class can be found in these module commit changes.
Please find the entire change log (comparison the former version beta 2) on GitHub, and the list of fixed bugs in this version in the bug tracker.
Updating and installing OXID eShop v6.0.0-beta.3
If you run the installation like described in the blog post “OXID eShop v6.0.0 Beta: Installation” you will now automatically install the new beta version.
For updating from a former v6 version, edit the file my_oxid_eshop_project/composer.json and replace OXID eShop metapackage entry with “^v6.0-beta.3”. Then run:
$ composer update --no-dev
In case you’d like to install development dependencies please add the changes into your project specific my_oxid_eshop_project/composer.json file.
Then run:
$ composer updateInformation how to run OXID eShop tests can be found in OXID eShop installation documentation page, section “Project with development components”.
Flow Theme version 2.1.0
A new version of the Flow theme was released within the compilation. It contains several fixes and improvements together with:
- newly created block: checkout_order_btn_submit_bottom in page/checkout/order.tpl
- renamed block: from dd_widget_header_categorylist_navbar_list to dd_widget_header_categorylist_navbar in widget/header/categorylist.tpl as two blocks has had the same name.
Please see all alterations made compared to v2.0.0 on GitHub as well as a list of the fixed bugs in the bug tracker.
I’m very interested to see how oxid 6 stacks up. Oxid has felt very old for a while now but namespaces should help modernize things quite a lot.
Chris, you saw this blog post as well, didn’t you? https://oxidforge.org/en/oxid-eshop-v6-0-0-beta1-released.html
Has someone tried the EE Vesion? I’m getting stuck on step 5 of Installation:
“..
Fehler beim Ausführen des Kommandos ‘/home/mhostdbo/mydomain.de/vendor//bin/oe-eshop-facts oe-eshop-db_migrate’. Returncode: ‘127’.
Das Kommando gibt folgende Meldung zurück:
Impossible to execute the command.
..”
Did i miss something?
Kann ich bestätigen, sowohl bei der PE als auch bei der EE:
Fehler beim Ausführen des Kommandos ‘/home/mhostdbo/mydomain.de/vendor//bin/oe-eshop-facts oe-eshop-db_migrate’. Returncode: ‘127’.
Returncode: ‘127’ means “If a command is not found, the child process created to execute it returns a status of 127”.
Could you please describe the following:
* File listing of “/home/mhostdbo/mydomain.de/vendor//bin/”
* Details about your environment (OS, installed PHP and library versions)
* Steps which were used to install the eShop
* Does the installation fail only with beta 3? Have you tried beta 2/1 previously?
Could you also please provide output from:
cd /home/mhostdbo/mydomain.de/
VERBOSE=1 vendor/bin/oe-eshop-facts oe-eshop-db_migrate
This will expose all the variables which were used in order to proceed with migrations.
-bash-4.1$ VERBOSE=1 vendor/bin/oe-eshop-facts oe-eshop-db_migrate
“..
CMD: /home/mhostdbo/mydomain.de/vendor/doctrine/migrations/bin/doctrine-migrations “–ansi” :migrate -n –configuration=”/home/mhostdbo/mydomain.de/vendor/oxid-esales/oxideshop-pe/migration/migrations.yml” –db-configuration=”/home/mhostdbo/mydomain.de/vendor/oxid-esales/eshop-doctrine-migration-wrapper/migrations-db.php”
X-Powered-By: PHP/4.4.9
Content-type: text/html
Parse error: syntax error, unexpected ‘[‘ in /home/mhostdbo/mydomain.de/vendor/doctrine/migrations/bin/doctrine-migrations.php on line 21
..”
Guest because of wrong PHP Version $(which php)
* File listing of “/home/mhostdbo/mydomain.de/vendor//bin/”
doctrine-dbal -> ../doctrine/dbal/bin/doctrine-dbal
doctrine-migrations -> ../doctrine/migrations/bin/doctrine-migrations
oe-eshop-db_generate_migration -> ../oxid-esales/eshop-db-migration-wrapper/oe-eshop-db_generate_migration
oe-eshop-db_migrate -> ../oxid-esales/eshop-db-migration-wrapper/oe-eshop-db_migrate
oe-eshop-db_migration_facts -> ../oxid-esales/eshop-db-migration-wrapper/oe-eshop-db_migration_facts
oe-eshop-db_views_regenerate -> ../oxid-esales/eshop-db-views-regenerator/oe-eshop-db_views_regenerate
oe-eshop-demodata_install -> ../oxid-esales/eshop-demodata-installer/oe-eshop-demodata_install
oe-eshop-doctrine_migration -> ../oxid-esales/eshop-doctrine-migration-wrapper/oe-eshop-doctrine_migration
oe-eshop-doctrine_migration_facts -> ../oxid-esales/eshop-doctrine-migration-wrapper/oe-eshop-doctrine_migration_facts
oe-eshop-edition -> ../oxid-esales/eshop-edition-facts/oe-eshop-edition
oe-eshop-edition_facts -> ../oxid-esales/eshop-edition-facts/oe-eshop-edition_facts
oe-eshop-facts -> ../oxid-esales/eshop-facts/oe-eshop-facts
oe-eshop-facts_helper -> ../oxid-esales/eshop-facts/oe-eshop-facts_helper
oe-eshop-migration_facts -> ../oxid-esales/eshop-migration-facts/oe-eshop-migration_facts
* Details about your environment (OS, installed PHP and library versions)
CentOS 6.8 64-bit with pd-admin v4.26
PHP 5.6.23
MySQL 5.5
This is the first time I’ve test OXID eShop v6, never test beta 2 an 1 before.
First thing before starting the setup wizard, I have to change PHP path in:
/vendor/oxid-esales/eshop-facts/oe-eshop-facts
instead
: ${ESHOP_PHP_BIN_PATH:=$(which php)}
to
: ${ESHOP_PHP_BIN_PATH:=/usr/local/pd-admin2/php5-5.6.23/bin/php-cli}
pd-admin default bash php path (which php) is
/usr/local/pd-admin2/bin/php (PHP Version 4)
Indeed, the migrations will not work with PHP Version 4. ATM it assumes that the system has one PHP installation, and it will use it as default. The PHP version which is picked by ‘which’ will be the one which is found first in the “PATH” environment variable. Other work-around was found by you already by changing one of the facts.
From your perspective, what would be the best way to resolve the issue? Do we need to provide you with a way to change the default PHP executable? Or can we delegate these issues to system operators?
Hi Edvinas,
I’ve test it again today. After we have make custom path of user bash, where (which php) is now to:
~/bin/php
and
~/bin/php is a symbolic link to
/usr/local/pd-admin2/bin/php5-5.6.23
Create new fresh project with composer, go to setup wizard:
Same issue in step 5
“..
Fehler beim Ausführen des Kommandos ‘/home/mhostdbo/mydomain.de/vendor//bin/oe-eshop-facts oe-eshop-db_migrate’. Returncode: ‘127’.
..”
I think, we should deligate these issues to system operators.
Typically during setup that user is ‘www-data’. And environment variables such as ‘PATH’ can be different for different users.
It would be strange though if you indeed changed the `PATH` variable for `www-data` and it still didn’t work out.
Hi there,
running the command
user@box:~/shared_folder/oxidBeta$ VERBOSE=1 vendor/bin/oe-eshop-facts oe-eshop-db_migrate
does output the following:
Variables from: “oe-eshop-facts”
ESHOP_PHP_BIN_PATH: /home/vagrant/phpfarm/inst/current-bin/php
ESHOP_FACT_BIN_PATH: /home/vagrant/shared_folder/oxidBeta/vendor/oxid-esales/eshop-facts/oe-eshop-facts
ESHOP_FACT_BASEDIR: /home/vagrant/shared_folder/oxidBeta/vendor/oxid-esales/eshop-facts
ESHOP_SOURCE_PATH:
ESHOP_BOOTSTRAP_PATH:
ESHOP_CONFIG_PATH:
ESHOP_VENDOR_PATH:
ESHOP_VENDOR_BIN_PATH: /bin
ESHOP_VENDOR_NAME: oxid-esales
ESHOP_OXID_VENDOR_PATH:
Script “oe-eshop-db_migrate” was not found. Possible candidates:
The path to the vendor/bin folder could not be determined correctly.
Could you please provide more information about the environment you’re using? Host and guest if possible.
Host is Windows 7 and Guest is Ubuntu Trusty.
Looks like same issue: https://github.com/OXID-eSales/oxvm_eshop/issues/32
Thank you for the link, but it did not solve the problem.
I did a little bit of digging:
File oe-eshop-facts
The variable ESHOP_SOURCE_PATH consits of ESHOP_FACT_BASEDIR and the SOURCE_PATH_SUFFIX.
Which translates to the path
/home/vagrant/shared_folder/oxidBeta/vendor/oxid-esales/eshop-facts/../../source/
Needless to say, it does not exist.
Could there be something wrong with the SOURCE_PATH_SUFFIX variable?
I have opened an issue on GitHub:
https://github.com/OXID-eSales/oxvm_eshop/issues/37