I’ve ended up with many SS3 websites that use the old DOAP Module for better or worse. Kinda wishing I hadn’t used any modules what so ever now though.
The backed of DOAP used a Gridfield which you could customise nicely for end users. I’m struggling to re-create the usability once I’ve fandango’d the DOAP SiteTree split back over to normal Page Classes in SS4.
It’s a massive manual database ID matching nightmare to move from DOAP back to SiteTree. Especially if you have a lot of data to deal with.
- Make new Page Classes to mimic your old DOAP setup. Same field names, etc. Get the DB working and the Templates up and running under a new temporary Parent menu Item.
- Copy DOAP and NewsItem (example) and SiteTree tables over to a new temporary database for modding. Add all of the unique fileds from NewItem into DOAP table then use a JOIN Update to bring in all the data from NewsItem into DOAP so it’s all on one ROW as you’re going to need to reindex the IDs.
- Find the last SiteTree ID.
- Reindex the DOAP table ID field starting from the next ID from SiteTree.
- Copy across the new NewsPage table from the new setup.
- Now carefully INSERT the fields from DOAP that match field names in NewsPage and to the same into SiteTree.
- Copy that all into SiteTree_Live as well.
- Don’t forget to manually set the new ParentID for the new NewsHolder page.
- Test it out in the CMS on SS4.
If the SiteTree is now huge. I have 180 News pages to deal with.
I have installed Lumberjack but I can’t figure out how to customise the CMS part to be more friendly to use. There doesn’t seem to be many options.
Is there a better way to customise the backend of the CMS in SS4?
Maybe a custom ModelAdmin for the NewsPage class? I’m off to try that now.