I discussed this with the developer in question who said to escalate, where he will look into it further, it looks like a problem with the session timing out during the migration, and he will need to produce a fix for that.
So I'm escalating this and will get back to you when I have some feedback to share.
Types 3.4.2 has been published today and it includes a fix for this, specifically it should prevent the migration timing out when it takes a very long time.
Thank you for not forgetting about me.
I received a message about a new version of the Toolset. I upgraded to 3.4.2 and started the database upgrade process.
The process will take some time. When it's finished, I'll come back here.
The process is not yet complete.
The upgrade takes approximately 21 hours. I haven’t come that far yet, it usually ended at 8 hours.
Therefore, this time I am more optimistic.
Fingers crossed, waiting for the finish😉 Current status: 14 hour(s) remaining (72%)
Status .. completed😉.
But... all singles of CPTs (just on them I use a views with relationships) give error 500 and a white screen, because the execution time is too long.
So despite all this effort and time, I rolled back to an interrupted state using the rollback Toolset function, and now everything works fine. My thinking about this is that something went wrong while upgrading the database (although I got a successful migration message and small errors - "Database layer mode has been updated successfully. The upgrade has finished with some warnings. This may be caused by small inconsistencies in the database and it most probably has no impact on your site..."). I will try the whole process again and report the results. If possible, do not close the ticket, this process will take a couple of days.
Anyway, thanks for keeping in touch.
I'm waiting on more details from another client who said that the migration completed successfully, but then some of her Views that included fields of related posts were much slower than before the migration, which sounds somewhat similar to what you describe.
When you have completed the migration if you run into the same problem make a note of what in particular doesn't work.
Evidently your site is very large and it may not be possible for us to get a copy to test, but if you can describe the specific set up of what fails then we can try to reproduce it. (Or we may discover something with the site of the other client, which I think is rather smaller.)
Let me know when you are in a position to re-test and if you discover anything.
Thanks for the details. Yesterday I started the upgrade process again, it has not finished yet. If the problem reoccurs, I'll investigate in more detail. I will also try to provide you with a copy of the database for testing.
I have finally completed the migration process. But unfortunately the result is the same.
I found it causing an awful slowdown and a 500 error. This is a view that uses a one-to-many relationship.
If I remove it from the content template, the page loads as quickly as it did before the upgrade.
Of course, removing this view is not an option for me😉
What can I provide so that you can investigate this in more detail?
I hope you already have a backup before you run migration. In addition to that I will also require problem URL where I can see the view which you claim that it took too much time to load and any other additional details that you would like to share.
I have set the next reply to private which means only you and I have access to it.
*** Please make a FULL BACKUP of your DATABASE**
Can you please navigate to section "Rollback after the migration of the relationship data structures" on the following link: Scrrenshot: hidden link
=> hidden link
And perform the rollback and once you done please let me know.
*** Please make a FULL BACKUP of your DATABASE**
