2/14/2024 0 Comments Im a lumberjack and im not ok![]() ![]() It’s as simple as adding two lines of code to the DataObject then deb/build then duplicate EventItem into EventItem_Live and set the version field to 1 in both for all records. This works fine for either a grid field or ModelAdmin implementation. I also then enabled versioning on the DataObjects. I was not using the direct ORM method to bring in the DataObjects on the page template because I was using embargo dates as a filter. One way is to simply not implement either end of the has_many link and then use the ModelAdmin in SS4. One is to use the SinglePageAdmin module (which does not work with the latest version of SS4.2.1) which happens to be how I’d structured things in SS3. No DataObject that is in a $has_many link with a Holding Page should be administered from ModelAdmin. I could re-visit it later to re-implement that but I’ll be trying to avoid a DOAP style use where I is absolutely correct. I haven’t re-implemented custom URLSegment management so just using ID for a /show/ID link to the page but it works fine. I converted the DOAP back into a normal DataObject and brought in the Content and Title fields via SQL. I have implemented a version of Uncle Cheese’s Lesson about DOAP around the old News Page Item data from a DOAP. Maybe a custom ModelAdmin for the NewsPage class? I’m off to try that now.īack with an update on best way to migrate from DOAP SS3 to SS4. Is there a better way to customise the backend of the CMS in SS4? I have installed Lumberjack but I can’t figure out how to customise the CMS part to be more friendly to use. Don’t forget to manually set the new ParentID for the new NewsHolder page.Copy that all into SiteTree_Live as well.Now carefully INSERT the fields from DOAP that match field names in NewsPage and to the same into SiteTree.Copy across the new NewsPage table from the new setup.Reindex the DOAP table ID field starting from the next ID from SiteTree.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. Copy DOAP and NewsItem (example) and SiteTree tables over to a new temporary database for modding.Get the DB working and the Templates up and running under a new temporary Parent menu Item. Make new Page Classes to mimic your old DOAP setup.Especially if you have a lot of data to deal with. It’s a massive manual database ID matching nightmare to move from DOAP back to SiteTree. 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. The backed of DOAP used a Gridfield which you could customise nicely for end users. Kinda wishing I hadn’t used any modules what so ever now though. I’ve ended up with many SS3 websites that use the old DOAP Module for better or worse.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |