View Issue Details

Jump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0006646OXID eShop (all versions)6. ------ Setup -------public2017-06-01 13:422017-06-23 13:46
Reporterrmaekeler Assigned To 
PrioritylowSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
Product Version6.0.0-rc.1 
Summary0006646: Error while generating view during setup
DescriptionWhen trying to install the Oxid-EE I get an error while views are being generated during setup.

After tracing the error a bit, my guess is that the scripts that add new database-fields for the upgrade to EE get executed AFTER setup tries to generating views which causes it to fail.
Steps To Reproduce1. composer create-project --no-dev oxid-esales/oxideshop-project my_oxid_eshop_project dev-b-6.0-beta-ee
...into web-folder of developement-vm

2. start setup process

3. click through until step 5 and error is thrown
TagsNo tags attached.
Attached Files
Bildschirmfoto 2017-06-01 um 12.11.06.png (26,797 bytes)   
Bildschirmfoto 2017-06-01 um 12.11.06.png (26,797 bytes)   
Bildschirmfoto 2017-06-01 um 12.11.37.png (225,107 bytes)   
Bildschirmfoto 2017-06-01 um 12.11.37.png (225,107 bytes)   
ThemeNot defined
BrowserGoogle Chrome
PHP VersionOther
Database Version5.6

Activities

QA

2017-06-02 08:47

administrator   ~0012106

You can see from the exception message that the field "oxserial" does not yet exist in the "oxshops" table and therefore the setup can not be completed successfully. Because the Community Edition is the base, the field is not in the database.

So the migration of CE -> PE -> EE has not yet been executed yet. This suggests that the bash scripts are not running properly.

The statement to execute the migration scripts is in the file composer.json:
 
"Scripts": {
    [...]
    "Oe: migration: run": "oe-eshop-facts oe-eshop-db_migrate"
    "Oe: migration: new": "oe-eshop-facts oe-eshop-db_generate_migration"
    "Oe: views: regenerate": "oe-eshop-facts oe-eshop-db_views_regenerate"
}
 
The files containing the SQL changes are located at the following location:
 
vendor / oxide esales / oxides shop-pe / migration / data / Version20160919103142_ce_to_pe.php
vendor / oxide esales / oxides shop-ee / migration / data / Version20160919103142_pe_to_ee.php
 
Since the queries execute the SQL command "Alter table", the database user should be checked for sufficient rights. This might have been rejected by the database when you changed the table. Corresponding notes should be found in the activated MySQL log.