New post relationship (in beta) breaks my content template

This thread is resolved. Here is a description of the problem and solution.

Problem:
New post relationship breaks the content

Solution:
Well - if you migrate your content to old to new post relationship, you need to run the wizard given at:
=> Toolset => Relationship

You can find proposed solution, in this case, with the following reply:
=> https://toolset.com/forums/topic/new-post-relationship-in-beta-breaks-my-content-template/#post-623656

Relevant Documentation:

This support ticket is created 6 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	10:00 – 13:00	10:00 – 13:00	10:00 – 13:00	10:00 – 13:00	10:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Kolkata (GMT+05:30)

Tagged: Setting up post relationship, Types plugin

This topic contains 4 replies, has 2 voices.

Last updated by craigB-3 6 years, 10 months ago.

Assisted by: Minesh.

Author

Posts

March 6, 2018 at 5:25 pm #622670

craigB-3

Hello,
I heard about the new parent/child relationship changes in Types, so I downloaded the beta and installed on a test/staging site.

I have a parent content type called 'Applications' which contains fields such as date, location, summary. I also have a child content type called 'Application Documents' which is what holds PDF files associated with the application.

When I click into an Application ... I'm getting errors related to the relationship. (see screenshot).

I have done nothing other than updated Types & Views to the latest betas.

I tried following this document for guidance (https://toolset.com/2018/03/how-to-prepare-your-sites-for-the-new-post-relationships-coming-in-types-2-3/), but I was never prompted to to run an 'automated migration' that this document implies - https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/.

When I originally built the site, I didn't write any custom PHP queries...everything I did was inside the Toolset editor windows.

Please advise.

Thank you,
Craig

March 7, 2018 at 11:35 am #622934

Minesh

Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Well - I need to check why that error is throwing on your install.

Could you please send me copy of your site?
https://toolset.com/faq/provide-supporters-copy-site/

I have set the next reply to private which means only you and I have access to it.

March 8, 2018 at 10:06 am #623238

Minesh

Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Well - I need to send the site copy to our Devs for further debug and every issue is important to us.

Do you have any other way to send me site copy - using different plugin:
=> https://wordpress.org/plugins/all-in-one-wp-migration/

March 9, 2018 at 11:59 am #623656

Minesh

Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I would like to know here - have you try to migrate to new post relationship:
=> hidden link

Please note that - you should do this on staging site do not apply this to your production site.

March 9, 2018 at 3:03 pm #623723

craigB-3

Hi Minesh...

Running the migration wizard tool fixed my problem. Your staff should highlight this important step – and point out where to find it – in the documentation otherwise you're going to get a ton of support requests.

Thank you,
Craig