Unfortunately I didn't realise the new features of the Types plugin when I updated it to latest version and of course the backward incompatibilities.
I will appreciate it a lot if you please could point me in the right direction to uninstall this version with the aim to go back to a version that actually works with my original code without database changes - there are a lot of new posts in the database important to preserve. This is workaround until I have enough time to learn more about the latest version, not now, and update the plugin.
At this moment all my original relationships, on the production site, points out to the same object after the plugin update... and this is not what people are expecting.
Types 3.0 includes a lot of backwards compatibility measures and it is likely to be in limited cases where custom code is used that some things may not work without manual intervention.
If you update to Types 3.0 and do not run the wizard, then everything should continue to work exactly as before, including your custom code.
If you are not actively developing the site and making changes then there is no need to run the wizard.
If you are still developing the site and want to take advantage of some of the enhanced functionality and workflow provided by the new relationships, then you can run the wizard.
There is then an additional backwards compatibility layer so that the site should continue to function as before, even though your Forms and Views would be based upon the old relationship formats. We even include special steps so that your custom code will continue to work as before, even where you are using functions such as get_post_meta or creating a new WP_Query that relies on the parent id field ("_wpcf_belongs_parent-slug_id"). One thing we cannot handle is where you use get_posts with a meta query working with this field because by default get_posts does not apply filters (though you can modify your code so that it does, which would be the only change you make).
So, a great deal of thought and effort has gone into making the update fully backwards compatible, and only in edge cases with custom code might some things fail.
But there is no reason to downgrade from Types 3.0 if you feel you may be such an edge case, just don't run the migration wizard, and Types will continue to work as before.
You are right in that I'm not actively developing the site at this moment and I understand that your team have put in a great effort into making the update backwards compatible. However the plugin is not working as expected and I will need to take a closer look into the code to understand what is causing the issue. I will back to you after my research.
