TOPIC: ** DT Register 2.7 Status **

Hello! As you should know by now, we released DT Register 2.7 on Nov. 19. See the official announcement on our front page. For new installs and some upgrades, all is well. However, a couple critical issues have been discovered that are affecting many people... unfortunately just didn't show up in testing. We are aware and are addressing them right now. We have already updated the package to 2.7.0a and made that available just shortly prior to posting this note. Please download and upgrade to this update. Some of the known issues that were resolved already are:
- error shown when trying to edit the payment options
- discount code field showing for all registrations even when disabled
- calendar items on the same day now show in time order

New installs right now should be totally fine. Those migrating from a previous install are the ones having the main issue. Of course, this was supposed to be more seamless than it has become, but there's nothing we can do about that now... just to resolve and provide a quick solution. This migrate issue causes the backend records to not display correctly and in some cases causes the events not to show up on the frontend for registration. We will have this issue sorted out today for sure. Please watch this thread instead of posting a bunch of threads about the same issue. We know it exists and are one it.

Sad story... this issue was actually resolved earlier today, then lost. I was at a meeting then during a break, I put my MacBook Pro in my vehicle. Someone must have seen me because between that time and about 3 hours later, my vehicle was broken into... glass broken out and the MacBook is gone... along with tons of my work. That, of course, destroyed the rest of my day. Now I'm scrambling to help everyone here and get this back on track. Not trying to make excuses, but that is the simple reality of this weekend.

Keep an eye here, we'll get this all corrected right away. We are very sorry to those of you that have experienced the failed migration attempt. Thanks for your patience.

- Nathan

Sad to hear that Nathan!

Will it affect to the following work? Did you backup your data?

How can we help you?

I'll be fine... just lost the fixes that were done earlier today... so just delayed this overall migration fix a day or so. All will be sorted today (Sunday).

Oh, also, for those who upgrade and just can't see their events on the frontend... check to make sure your categories are published. If they are unpublished, you will see none of those events on the frontend

Nathan,

Sorry to hear that. I've gone to trunk only, but I think if they see it go in there that's not even safe. Messenger Bag hangin' on me only I guess

--Randy Starkey

Hi Nathan:

Sorry to hear about your loss. I had a similar experience with my MacBook about a year ago but fortunately, I had a clone backup so no data was lost.

I'd like to know if I'm okay upgrading to 2.7.0 from 2.6.6 or whether I need to complete some interim step. Please advise. Despite being old, my DT register 2.6.6 is very stable now and I do not want to disrupt it since I have active events going on.

At the same time, I'm very eager to upgrade to 2.7 when it is safe to do so.

Sincerely,
Howard