Message of the day:
Hey! This is the big channel for the big, next major release of SilverStripe! https://www.silverstripe.org/blog/update-on-silverstripe-5-x/
Talking about upcoming feature development for 5.x and 6.x
I've inferred there's some major changes coming up to Member passwords and general security changes, just based on what's happening with the silverstripe/mfa recipe. Way too early to speculate otherwise 🙂
I haven't found the code things super challenging. Just unforeseen things that make the upgrade time add up. The most challenging thing I think I've found is being able to sell the upgrade to clients from v3 to v4 despite the time it can take and the unknowns with the upgrade. Moreover, reassuring them SS is the right framework and CMS to use when they're thinking about having to upgrade from v4 to v5 in the future.
Things that can creep into their mind is, "would this be more cost effective on another platform". For example WordPress which is a extremely simple upgrade process. Saying to a client "Yeah, but WP is junk though" isn't the greatest selling technique.
Thanks for sharing. Are you able to elaborate on what "unforeseen things" might entail? e.g. Are they mostly project related, to do with upgrade path on custom modules, or...?
Each website is unique and there are many many things to know about SilverStripe. The unknown things I refer to are custom coded things for a given website that may not have a heap of documentation and so during scoping phase may have aspects which aren't taken into consideration. Also, API changes that just simply aren't known. For me, I found a number of things caught me out. An example is form fields don't take html content in v4. Figured that out only when loading an in progress ss4 site to find html displaying as text on a page. Another around fields was default values in a DateField which get populated different in ss4 compared to ss3. Just a number of things like that. In another way of saying, unless one is to know every single change from v3 to v4, and they also know a website intimately enough to be able to scope with enough granularity to accommodate every little change, the scoping phase of an upgrade project comes down to a degree of guess work.
Does that answer your question @nightjarnz?
Yes that is helpful, thanks :)
I can say with certainty that getting over namespaces and how they work won't be a thing again :P
What did you find most challenging?
(I'm asking for feedback here)
depends on what you percieved as "big tasks"
that’s the wish
remains to be seen ¯_(ツ)_/¯
Lol fair play. It won't be as big of a task to upgrade from v4 to v5 as it was going from v3 to v4 though, right?
It's a tactic to have changes first.