TOPIC: DT Register updated to 2.7.0f

We have addressed another set of bug fixes in 2.7.0. All users should now update to 2.7.0f which is now available. Some of these are very important fixes... they include:

- Detailed group registration has restored the headings for Member 1, Member 2, etc.
- More foreach() warnings were corrected
- Special language characters were not displayed right for field labels when editing the field.
- Hidden fields are fixed so they now display as expected in the backend records
- NEXT STEP bug resolved which was affecting frontend registration, mainly for IE users.
- If only one payment method is offered, the payment selection screen is now skipped. If only Pay Later is offered, it will only show the payment method screen if more than one pay later option is enabled.
- All payment methods were updated as new records were not properly being marked as Paid or storing transaction IDs. Fixed.
- Return from PayPal error fixed.
- Duplicate Registration Prevention fixed
- Auto Joomla User Creation fixed and is verified to properly populate form data into the new user profile.
- Email field can now be disabled for view in the attendee's list and group members list.
- Validation error for minimum and maximum group members fixed when creating/editing events.
- debug left in the initial 2.7.0e has been removed.
- Event base price issue from the initial 2.7.0e is fixed.
- other miscellaneous adjustments to layout and such.

We do realize that there are more items to fix and are working hard to address all of them this week. We do appreciate your patience as we do so. We are very behind on support tickets but are working to catch up. It has been more effective to do large updates like this one which help many users at one time.

Wanted to also mention as some are reporting that payment gateways are not being populated with the event name or confirmation number like they used to. This is on purpose. If you are registering for 3 events at one time, which name would be sent to PayPal or another gateway?? We are working on an enhancement where if only one event is registered, the gateways will be populated like they were in 2.6. When multiple events are registered, we'll likely have a hard-coded description pulling from the language file.

Thank you everyone! Many people are already using 2.7 on their live sites without issue. Hopefully the rest of you will be joining them shortly. This new build will help a great number of you. Now onto the next batch...

Guys,

Thanks for the openness of the responses and the speed at which you are correcting the bugs.

Is there a list of still outstanding issues somewhere? I've been holding off on upgrading since I figured there would be some teething involved with this major release.

Just trying to save myself some frustration.

Cheers,

Rich

Here are the bugs I have found so far in 2.7.0f :

#1) BUG with new users who have registered for an event with the "joomla user auto creation" (and with duplication prevention enabled) > when they go to their user panel, if they try to edit their profile, they can't validate the form as the system says "you have already registered for this event" next to the e-mail field.
Same problem if they cancel their registration and then register again with the same e-mail address (system shows "you have already registered for this event" next to the e-mail field).

#2) When a user cancels his registration, he is still being used for the calculation of selection limits.

#3) Password created during registration can't be sent to the user in the e-mail (the [PASSWORD] tag always returns "password" in the e-mail)

#4) BUG with conditionnal fields and selection limits is still there (see my post in http://www.dthdevelopment.com/index.php?option=com_jfusion&Itemid=91&jfile=viewtopic.php&f=16&t=6133#p10022 )

#5) In FireFox, when fields reach their selection limits, they become "unselectable" (they appear in light gray). In Internet Explorer 7, if a field has reached it's selection limit, the field is still selectable. It's only when the user validates his form that the "x" icon appears next to the concerned field without any further explanation (so the user has no way of understanding why this particular field won't validate).