Message of the day:
Design: https://projects.invisionapp.com/dsm/silver-stripe/silver-stripe/folder/components/5b42ca0dc1ba8c001a91b69b Background: https://docs.google.com/document/d/1hffZFknysYi6tp55eOk4DzON4pjoEt7Xq4GGD-ZGah0/edit
Discuss the future of content editing in SilverStripe via content blocks
setting table name to old class name fixes that :)
well 'lose' - still in DB, just not 'found' because it'll check a new table (with nothing in it) instead.
otherwise you'll lose all data :>
If these are classes you control (part of your project) then please also don't forget to add
table_name config to them.
@SilentDesigns if the files you're needing to alter have an accompanying
.upgrade.yml in the module root, you can essentially copy the lines out for classes that extend DataObject - this is basically the legacy.yml file (sans a few headers - see above about an example).
migratefiletask is for migrating uploaded files in
assets/ between v3 and v4 of CMS
Cool, thanks and then I need to run the
MigrateFileTask ? Or just flush?
(because elemental doesn't have one)