TOPIC: Documenting my upgrade 2.6 - 2.7

Upgrading anything can be a pain.
I have faith in the guys from DTH as they have proven to produce an excellent component and continually improved upon it.

I've been using DT REGISTER for sometime now, both on commercial sites I produce but also my own "registration" site for another business I run.

I thought I would document my process for others.

Here's the steps I follow.

1. Backup my site using Akeeba Backup.
2. Restore my site to a testing environment.
3. Follow the upgrade process as documented.

I will now document my findings.

First upgrade discovered that no events were being shown.
Discovered that this issue is being caused by the Categories NOT being published after the upgrade.
Published them and now I can see the events

Upgrade is complete.
Everything appeared to be correct, until I looked closely at the registration records that were already in the system.

Seems that they have all been shuffled around. Records are no longer assigned to the correct event.

I was using JEvents prior and I've also tried using the "UNSYNC JEVENTS" method but no difference.
Obviously this is a major error and clearly I can't go ahead with the upgrade.

I will try going into each event and clicking save and see what happens

No luck.
In fact I've looked at the database and I can confirm that the group_event table has "0" in every record for the column "eventid".

Clearly this is a major error. One that I hope can be easily solved.

I'm stopping the upgrade process now, until I can get a few answers from the DTH team.
Cheers

Further to this. Discovered that some "old" tables with a different prefix may have been causing the issue.

However I've also since tried again to upgrade without these other tables and the problem of mixed up event id's still exists.

I'm about to try the 2.7g version and will report back

Thank you for this. We are producing our first implementation of a registration system for a major client for GoLive delivery on 12/13. Seeing all the chatter on the forums, and with an open ticket for 2.7 version which fails to submit a payment, we have chosen to build in 2.6.9 to be safe.

You upgrade log will be crucial to us when we decide to trust 2.7.