As we move along checking and publishing the migrated data in Camden's production box, we have been finding items that were not migrated: These are items in the 5.2 server http://camden.aplaws.org.uk/content/environment/planning-and-built- environment/advice-and-publications/planning-advice---residential- properties.jsp?g11n.enc=UTF-8 http://camden.aplaws.org.uk/content/environment/planning-and-built- environment/advice-and-publications/the-planning-process.jsp? g11n.enc=UTF-8 http://camden.aplaws.org.uk/content/environment/planning-and-built- environment/sustainable-planning/camdens-green-building-guide.jsp? g11n.enc=UTF-8 http://camden.aplaws.org.uk/content/environment/planning-and-built- environment/conservation-and-design/listed-buildings/a-guide-to- listed-buildings-in-camden.jsp?g11n.enc=UTF-8 http://camden.aplaws.org.uk/content/business/business-advice/business- rates/pay-your-business-rates-online.jsp?g11n.enc=UTF-8 http://camden.aplaws.org.uk/content/business/business-advice/running- a-business/sources-of-funds-for-growing-businesses.jsp?g11n.enc=UTF-8 http://camden.aplaws.org.uk/content/business/business-advice/running- a-business/how-to-win-new-customers.jsp?g11n.enc=UTF-8 If you look for them on the Production server you will see they are not there.
Having examined the database, these items are indeed present, but have not got the 'type_id' field in cms_items set correctly. So this is yet another instance of bug 116119
This is resolved on Staging - please verify and update this ticket if its working as expected.