(e.g the page has a has_one with another page, and it has several fields in the DB array, and the functionality of that page is being changed so that they’re not used anymore, can I just remove them from the arrays?)
you could, knowing that if something disappears it's likely from that change... the data should be retained (the columns don't get removed), so if you need to re-add them it shouldn't be an issue
db/has_one is retained...
many_many should retain the joint table as well (I think)
Yeps, removal of fields/relations are never actively destroyed in the database
Also, are there any repercussions of removing fields from a pagetype?
I can’t find anywhere that it’s actually applicable though 😞 The class is used in a few other packages that have already been namespaced and are using it correctly.
I’m a bit stuck on where to start debugging.
👋 has anyone ever had
ReflectionException: Class VersionedDataObject does not exist before?
I’m trying to upgrade from version 1.5.0 of https://github.com/heyday/silverstripe-versioneddataobjects to version 2.0.5 (while upgrading php to 7.3 from 5.6 and silverstripe to 3.7.3)
There’s a custom trait on those
“work” meaning that they don’t force you to manually publish the image.