Scopey

But we won't do that without releasing an upgrade tool to assist

Scopey

It is possible that we might move to strict typing in SS5 - mayyyybe. That might be a little annoying.

thats4shaw

Magento 1.x to 2.x was a significant jump.

💯 (2)
taoceanz
taoceanz in #ss5 2019-05-15 23:52:11 (edited) (deleted)

Tools get upgraded as the tools our tools use evolve. PHP has evolved, and so SilverStripe has developed to accommodate new features and better ways of doing things. It makes sense there's going to be big changes from time to time that take a lot of effort to accommodate but yield good rewards.

taoceanz

@thats4shaw yes used the upgrader and it did a lot, but left a lot to be done, too. Also followed the ss4 upgrade article on the silverstripe website.

@Scopey I think the namespacing was a big one and the changes to the code base to accommodate that. I'm coming at this from not being super fluent with SS4 and I guess not grasping all of the changes that had been made between the two versions and so not being able to completely plan the upgrade through not enough detailed knowledge.

I more or less want to be able to sell what it takes to upgrade SilverStripe between versions to a client who may be thinking Joomla, Magento, WordPress, OctoberCMS etc would be more straight forward to upgrade.

Tools get upgraded as the tools our tools use evolve. PHP has evolved, and so SilverStripe has developed to accommodate new features and better ways of doing things. It makes sense there's going to be big changes from time to time that take a lot of effort to accommodate but yield good rewards.

thats4shaw

Regardless of what CMS/Framework you choose, you’ll face similar problems 🤷‍♂️.

Scopey

Namespacing & file rewrite were pretty hard hitting for sure

👍 (1)
Scopey

SS5 is not likely to remove anything that's not deprecated in SS4.

thats4shaw

Did you use the upgrader tool? It does most of the heavy work for you.

taoceanz

As it seems, upgrading from ss3 to ss4 is a relative mission where the majority of project files need to be updated many breaking api changes are introduced, and even server configuration needs to change. When ss5 is released, is upgrading from ss4 to ss5 going to be the same sort of massive breaking api changes the update from 3 to 4 is? I love SilverStripe and from a dev perspective it's the best CMS/Framework I've worked with so far and want to continuing using and contributing for many years to come, but it's a difficult sell to clients informing them an upgrade between major versions—for security and performance reasons—could take weeks to months in re-development and testing in a couple years time when it's necessary to upgrade again.