Since i do a lot of coding with symfony besides OXID i was very exited about this new version. So i gave it a try and updated one of the shops i maintain. (Its not public yet, i will update this post once we launch, Its launched by now, yay: https://www.cafelehmitz-photobooks.com/).

I basically followed this upgrade guide: https://docs.oxid-esales.com/eshop/de/6.2/installation/update/von-6.1.x-auf-6.2.0-aktualisieren.html

So here is my experience updating OXID eShop 6.1.5 to 6.2.0:

0. Update the Shop to latest 6.1 version and and also update all used modules to their latest version.
Since some sloppy things that were tolerated in modules before are now not tolerated anymore, we need to update the modules.
OXID 6.2. will throw errors when your modules metadata.php uses non strict code like constrains/contraints typo or wrong version number, which was tolerated before 6.2.

So to avoid errors like:
Module directory of /var/www/html/source/modules/ab/htmlmin could not be installed due to Metadata version 2 is not supported

…upgrade your modules and contact the maintainers if this issues are not fixed yet in their modules.

1. Update the composer.json
"require": {
"oxid-esales/oxideshop-metapackage-ce": "v6.2.0"
},
"require-dev": {
"oxid-esales/testing-library": "^v7.0.1",
"incenteev/composer-parameter-handler": "^v2.0.0",
"oxid-esales/oxideshop-ide-helper": "^v3.1.2",
"oxid-esales/azure-theme": "^v1.4.2"
}

2. Clear tmp dir:
rm -rf source/tmp/*

3. Run composer update
composer update --no-plugins --no-scripts --no-dev

4. Copy overridablefunctions.php
cp vendor/oxid-esales/oxideshop-ce/source/overridablefunctions.php source/

5. Run the composer scripts
composer update --no-dev

6. Run DB migrations
…there were no migrations in my case, tough.
vendor/bin/oe-eshop-db_migrate migrations:migrate

7. Migrate or update the modules
Require the module update helper component:
composer require --no-update oxid-esales/oxideshop-update-component
And run update:
composer update --no-dev --no-interaction
However this wasnt working and it removed all dev libraries and led to this error:
PHP Warning: Uncaught ErrorException: require(/var/www/html/vendor/composer/../ralouphie/getallheaders/src/getallheaders.php): failed to open stream: No such file or directory in /var/www/html/vendor/composer/autoload_real.php:73

So i had to adjust the command and omit the –no-dev option.
composer update --no-interaction

8. Run creation of standard module yaml configuration
vendor/bin/oe-console oe:oxideshop-update-component:install-all-modules

9. Transfer module data from DB into new yaml configuration
vendor/bin/oe-console oe:oxideshop-update-component:transfer-module-data

10. Delete module configuration from DB
vendor/bin/oe-console oe:oxideshop-update-component:delete-module-data-from-database

11. Activate module with new configuration
vendor/bin/oe-console oe:module:apply-configuration

12. Remove module Updater again
composer remove --no-update oxid-esales/oxideshop-update-component
composer update --no-interaction
Same here: this worked only by omitting the –no-dev option.

13. Remove xd_receiver.htm
rm source/xd_receiver.htm

14. Once all was done clear the cache again
rm -rf source/tmp/*
You might experience an error with oxid-community/ocbcleartmp module.
[2020-04-14 17:40:16] OXID Logger.ERROR: Function 'isEEVersion' does not exist or is not accessible! (OxidEsales\Eshop\Application\Controller\Admin\NavigationController)

So clear tmp and deactivate the module and reactivate it again, solved this.
The module was still using not exisiting code from cache.

Thats it. Nice!
Upgrading went almost smooth.
Now im looking forward to use DependencyInjection, Custom Commands and Doctrine QueryBuilder in this updated shop.

url.shop/nach-hersteller/hersteller-xyz

Möchte man “Nach Hersteller” umnennen in zB “Marken” muss man folgendes machen:

1. Im Code:

• Ändere die Translation Konstante BY_MANUFACTURER:
  source/Application/translations/de/lang.php:755
  source/Application/translations/en/lang.php:755
  

in ZB:

 'BY_MANUFACTURER' => 'Marken',

2. Im Shop Admin Bereich:

• Stammdaten -> Grundeinstellungen -> SEO
• Seo URLs neu berechnen
• Cache leeren

Magento has a config value: eu_countries that lists all Countries of the EU.

You can find it in the backend under:
Configuration -> General -> Country Options.

Against this list you can validate your country code, f.e. that you got in an billing or shipping address of an order.

$address = $order->getBillingAddress()->getData();
$eu_countries = Mage::getStoreConfig('general/country/eu_countries');
$eu_countries_array = explode(',',$eu_countries);
if(in_array($address['country_id'], $eu_countries_array)){
//do something useful:
//for example show a tax hint like this german one: 'steuerfreie innergemeinschaftliche Lieferung'
}

Pretty simple, once you know!

Do you know any other way?

Let me know!

OXIDs MVC, well thats some kind of different naming and you have to get used to:

the M (Model) you find in /core
the V you find in in your templates in /out, there the main view is called the same as your controller, given the controller has a render() method.
/views/details => /out/[templatename]/page/details.tpl
the C (Controller) you find in /views (what? oyerywell!)
like /views/details.php

The routing itself is like so:

?cl = controller

in /views

?anid = productID 

(that means the hash from the OXID field) or uid if you busy with users or any other relevant id

?fnc = myfunction

the method in the controller in /views

So this ends up in something like this:

<br />
theshop.de?cl=details&amp;anid=05848170643ab0deb9914566391c0c63&amp;fnc=myfunction<br />

This is unmasked routing, normally OXID has this covered in SEO URLs with prettier slugs.

To use custom methods in the controller you have to extend it, the OXID module way, check this here.

Apropos OXID module way: actually its not so bad, i like the emulation of multiple overloading for the models and controllers.
The module registry in the database however is something id rather have in the code, that would be easier to maintain over environments.
Also some better cascading for templates, assets, lang files etc in the modules would be cool. That “copy here copy there” installations can be quite annoying.
But anyway: i can deal with that.

Anyway: In the footer of my magento shop we might have a summary of the shopping cart,
which i simply put in the footer.phtml template file:

<?php if (Mage::getModel('checkout/cart')->getItemsCount() > 0): ?>
  <div class="footer_cart_widget">
    <a href="/checkout/cart" class="cart">
      <?php echo $this->__('Warenkorb') ?>:<br />
      <span class="cart_meta">
        <?php echo Mage::getModel('checkout/cart')->getItemsCount() ?>
        <?php if (Mage::getModel('checkout/cart')->getItemsCount() == 1): ?>
          Produkt: 
        <?php else: ?>
          Produkte: 
        <?php endif; ?>
        <?php echo $this->helper('checkout')->formatPrice(Mage::getSingleton('checkout/cart')->getQuote()->getGrandTotal()); ?>
      </span>
    </a>
  </div>
<?php endif; ?>

This means we might need to disable the caching for the footer HTML block,
so that my cart summary will stay dynamically generated.

This is how you can do it:

copy

app/code/core/Mage/Page/Block/Html/Footer.php

to

app/code/local/Mage/Page/Block/Html/Footer.php

and just comment out the following lines:

//$this->addData(array(
//    'cache_lifetime'=> false,
//    'cache_tags'    => array(Mage_Core_Model_Store::CACHE_TAG, Mage_Cms_Model_Block::CACHE_TAG)
//));

you could also put the cart values in the getCacheKeyInfo() method, but as this would result in caching a footer for any state of the shopping cart from my understanding, i don’t think it’s necessarily a good idea.

In this scenario development is done on two local machines while products and pages beeing already edited on the “Live”-Web-Server.
Git is used for version control and deployment. Also FTP SSH.

Magento is quite nice when it comes to deployment, as most config stuff is stored in XML files.
Those files are kept locally and ignored from version control.

So this is what my .gitignore looks like:

#cache, sessions, logs
/var/cache/*
/var/session/*
/var/locks/*
/var/report/*
/var/log/*
#media folder - images etc...
/media/*

#local config files
/app/etc/local.xml
.htaccess

#database dump
/database.sql

So i got a copy of the repository in each environment with a local .htaccess and local.xml file.

Theres a few things stored in DB by magento, though.
The most obvious is the “web/secure/base_url” and “web/unsecure/base_url” which both reside in the “core_config_data” table.
Those have to be set to the name of the host you’re working on.

This can be done with a shell script like this:

#create a dupm of the live DB on the server
ssh user@server.com 'mysqldump -u[username] -p[password] > ~/db_dump.sql'

#copy DB dump to local machine
scp user@server.com:~/db_dump.sql ./database.sql

#import SQL
mysql -u[local_mysql_user] -p[local_mysql_pw] [local_db_name] < ./database.sql

#update config settings in the DB
mysql -u[local_mysql_user] -p[local_mysql_pw] [local_db_name]<UPDATE
core_config_data
SET value='http://local.server.com/'
WHERE value ='http://server.com';
EOFMYSQL

This way all CMS and products  can be edited on the server, while the local machines can be easily synched.
For me this works fine, as we are working only in the file system in the local environment.
In case you can’t use the online Server as “database master” this might be not that simple.

As we most likely don’t want the whole /media folder under version control we might want to have another shell script to copy the media files to the local machine (via SCP in this case):

#remove local media folder
rm -rf ./media/*
#fetch media files
scp -r ssh_user@server.com:~/magento_folder/media/* ./media

I guess this could be done more efficiently with maybe ant or something.
But for the moment this works fine for me.

So now i can update my local environment with one line on the console:

git pull; sh sync_db.sh; sh sync_media.sh

This comes just as a normal textarea, as usual in OXID CE.
If you would like to add an Richtext Editor, you can purchase the fck Editor module
and install it, if you did not already.

After you installed the fck module your textareas of the basic shop are rich text.

But since the manufacturer long description comes from the module, you have to teach the fck module the new field.

Unfortunatly we cant extend the fck module, due to some private vars & methods.
So we have to hack it, like so:

Edit modules/tc_fckeditor/tc_fck_editor.php

Add:
line38+:

const MANUFACTURERS_MAIN = 'oxmanufacturers__extlongdesc';

Add:
line52+:

self::MANUFACTURERS_MAIN => 'editor_oxmanufacturers__extlongdesc',

Add:
line153+:

           case self::MANUFACTURERS_MAIN:
                $editor->addCustomJavascript($this->modulePath . 'custom/oxid_categories.js');
                break;

Then enable the module for the manufacturer text in the modules section of the backend:
manufacturer_text => tc_fckeditor/tc_fckeditor

And you should be able to rich edit your manufacturer long description.