TOPIC: {GROUP_MEMBER} Tags - No Data Showing up in actual email

I was having the same problem. What fixed it form me was including in each member. It seems that the email field is what ties the group member to the registration. ALso, I do agree that there should be a uniform way to treat single registrants and groups without including the same fields if they're blank. Maybe a group email and an individual registrant email, although that seems clunky. How about an [b]option [/b]so that if there is not data to now show the field? Additionally, they just released a fix to 2.7.3c that should fix the order issue, I haven't tried it quite yet.[email] in each member. It seems that the email field is what ties the group member to the registration.

ALso, I do agree that there should be a uniform way to treat single registrants and groups without including the same fields if they're blank. Maybe a group email and an individual registrant email, although that seems clunky. How about an option so that if there is not data to now show the field?

Additionally, they just released a fix to 2.7.3c that should fix the order issue, I haven't tried it quite yet.

The last package fixes the ordering of data in the [ALL_FIELDS] tag... but group members are still displayed in reverse order of how they were entered. We're aware of that, but it's not exactly a priority issue compared to other things we're working on

We've been thinking through this and will probably try to add a new similar tag where you can set certain data to show only for individual registrations so you don't have the blank fields issue. For many people, it works just fine as-is... but everyone sets up their fields differently.

Thanks. I tried including in each group member. It did not fix it. The reverse order issue I can live with, but you did not address the other functionality issues above. Can you please revisit those and tell me if there is a fix or work around to make that work effectively. These things never break when you don't need them. They only break when you have a crushing deadline if you catch my drift. Thanks! Jonathan[email] in each group member. It did not fix it.

The reverse order issue I can live with, but you did not address the other functionality issues above. Can you please revisit those and tell me if there is a fix or work around to make that work effectively.

These things never break when you don't need them. They only break when you have a crushing deadline if you catch my drift.

Thanks!
Jonathan

By the way, the ordering of data is not fixed in the [ALL_FIELDS] tag. It still shows up in reverse order for me in both the admin email and the thank you email. I am using the latest version of your software.

Additionally, I found another error that showed up which I will post under another heading, as it is independent from this error.

Are the errors that I have cited in this thread something that is going to be fixed soon or is this something that is gonna have to be lived or worked around for an extended period of time? I don't ask in anger, just as a reality check. I will work around it if I must, but I have an event coming up that needs these features working and if they will not work, I will have to find an alternative for this event. So please reply.

Thanks for your time and understanding.
Jonathan

PS - I am available to help test if you need it. I am not much for writing code from scratch, but I can edit any code you ask me to. This is a great product overall - just buggy right now.

PSS - In case I need to, is it possible to revert back to the previous version (2.6 was it?) without catastrophic effects?

DTAdmin,

I was wondering if you had any input on my last question?

I have an event that I need to get started with registrations that I would love to have a few of these things worked out.

Thanks!
Jonathan