Skip Navigation

[Resolved] Activating new relationship type fails at step 3

This support ticket is created 6 years, 11 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
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 10 replies, has 2 voices.

Last updated by Nigel 6 years, 9 months ago.

Assisted by: Nigel.

Author
Posts
#604361

I installed the new Types Beta to try out Many-to-many relationship between post types as it fits my scenario well.

I followed the instructions in your blog post https://toolset.com/2017/12/types-and-views-betas-with-many-to-many-relationships/
but the process of migrating existing relationships to new tables fails at
-step 3: "Migrating of associations between individual posts (this may take a while, depending on site size)"

This is the log output:
> Migration to many-to-many post relationships started.
> Dropped table "wpmn_toolset_associations".
Dropped table "wpmn_toolset_relationships".
> The toolset_associations table created.
> Relationship definitions migrated.

Please advise

#604375

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Matija

Is there a particular message displayed when it fails at step 3?

I will probably need a copy of your site so that I can pass it to the developers so they can test the migration tool for your specific set-up.

(Naturally I will need a copy from before the migration.)

Could you please make a duplicate available and I will forward it to the developers: https://toolset.com/faq/provide-supporters-copy-site/

Let me know if you need assistance with that. Your next reply is private.

#605780

Hi,

I'm trying to get my page to export with Duplicator for a couple of days now, even my hosting provider has helped check why it doesn't finish.
Can I send you different package to duplicate the site on your end?
We're using All-in-one WP migration without any issues, can I send you that?

#605789

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Yes, sure, I use that as an alternative when duplicator fails to I'm familiar with it.

I'll mark your next reply as private again so you can provide a link to the archive.

#607439

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Matija

Thanks for that.

I was able to reproduce the problem on my local copy of your site, where I note a PHP fatal error was reported in the debug log. That should give our developers enough to trace the problem.

I've escalated this thread and I'll update you here when I hear back from them.

Note that you are adding the betas to a site which uses other Toolset plugins. You will certainly find that anything connected to post relationships with the other plugins (e.g. CRED forms) will no longer work, and you may run into issues with the betas that will not be fixed until the final versions are released.

#610091

Hi Nigel,

do you have some feedback for this issue? I'm really behind with this project, mostly because the loading speed of my site si way to slow, when Toolset Views is enabled. I figured because it has to go trough to many posts to query, so I was hoping I could reduce the number of posts by using the new many-to-many relationship option. This would drastically reduce the number of posts and I hope also the load time.

Just for the record: are all of the post types created in Toolset saved in the same table, and is there a way to save each post type in it's own table - that would increase load times as the query wouldn't always have to run trough all posts, right?

#611389

Hello?

It's been almost two weeks since your last reply, can I at least get some feedback?
In the mean time, the Views plugin started producing Error 500 that could only be fixed by disabling and reenabling the plugin. What the hell is going on?

#613378

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Matija

I'm sorry, I missed the notifications for your replies.

I passed the copy of your site on to my colleagues for testing. While they were able to reproduce the error messages they are somewhat handicapped in identifying the issue because the site copy is in the after-state, not the before-state.

Nevertheless the developers have it and will ensure that the update wizard works on that site before we come to publish the final release of the updated Types.

All posts are stored in wp_posts. In the current version, post relationship data is stored in wp_postmeta using a single custom field to connect child posts to their parent.

In the new version custom tables are added to manage the relationships. The posts are still stored in wp_posts, but the relationships get dedicated, indexed tables which should lead to a significant performance improvement on large sites.

Bear in mind that these are betas, so it is to be expected that there will be some issues.

If you have been seeing 500 errors arising from Views, are these from the stable or beta version? Please let us know the details of the errors and what you were doing at the time they occurred.

#613668

Hello Nigel,

thank you for your reply.
I am aware these are betas and was only trying to test this functionality to speed up load times on my site. I will try to solve this issue with Beda trough the other ticket.
As for the migration to the new version: I would be happy send you a before-state version of the site, so your team can try to figure out the migration.
If that doesn't work, I could start a new installation with types beta, but I'm not entirely sure on how to migrate the whole site to that version then.

As for the the 500 errors. Unfortunately I have been spending hours on end trying to figure out where these come from, and my best guess so far is they are related to timeouts/limited resourses. I've changed all that (php limit etc) with my hosting provider, but 500 errors still accour somehow randomly.

Please let me know about next steps.

Kind regards,
Matija

#620410

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Matija

Do you still have a copy of the before-state available for us to be able to re-test the wizard?

I have marked your next reply as private so I can get details from you if possible.

#621431

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Matija

The issue should be fixed in the current version of the beta.

It may not be possible to fix the version of the site where you already tried and failed to complete the wizard, but if you use your backup from before you tried that then you should now find that it completes successfully.

If not, please let me know the details of how and where it fails.