Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Minor bugs found in 2.7.1C

Minor bugs found in 2.7.1C 14 years 2 weeks ago #10682

  • jstephens
  • jstephens's Avatar Topic Author
  • Offline
  • Junior Boarder
  • Junior Boarder
  • Posts: 31
  • Thank you received: 0
I've found some very MINOR bugs in my 2.7.1C installation

1. I'm seeing the full event message when I try and register a group for any event. All of my events are set to be unlimited.

2. When NOT using the event cart, if a person clicks on individual and then hits back to register as a group a second (blank) record is created and they get a message stating that the email function can't be instantiated. A blank email is sent to the admin. This may be tied to being logged in as I am using it on a test event that I don't want users to see. The registration that they complete goes through fine though, but I think it'll cause user confusion.

3. Even though I have set it to not send email to all members of a group, it still does. Member emails aren't very descriptive, and most of my registrants are putting one email address in for all of their members so they get a bunch of extra email.

Please Log in or Create an account to join the conversation.

Minor bugs found in 2.7.1C 14 years 2 weeks ago #10695

  • Howard Sambol
  • Howard Sambol's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 61
  • Thank you received: 0
Hi Everyone:

I have found some additional minor issues or bugs with 2.7.1c.

1. The Date Event Tag is not displaying with correct format. When set for 1-8-2011 it is displaying as 2011-01-08. This issue is pervasive and is showing up on thank you messages and emails sent to new registrations.

2. The DT Register Event Link Plugin is not responding to the setting of Event Listing. It is always going to Calendar View even when set to Event Listing.

3. When clicking on today in calendar view, the calendar is not properly displaying the correct dates. For example, when clicking on today, Dec 26th, it did not bring up the correct dates to include this date.

4. As I mentioned in an earlier posting, the calendar is seriously lacking a large month text identifier on top. We need to see December or January on top.

5. When selecting a past event in the records page and clicking on attended for a particular person, the page jumps back to select an event instead of remaining on the event selected. This requires you to have to keep selecting the same event over and over again.

Aside from the above, most everything seems to be working well and I'm very appreciative of the efforts made by the DTH team to squash the remaining bugs. 2.7 is awesome and I know it will get better.

Sincerely,
Howard

Please Log in or Create an account to join the conversation.

Minor bugs found in 2.7.1C 14 years 1 week ago #10757

  • lkpackard
  • lkpackard's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 0
1. I'm seeing the full event message when I try and register a group for any event. All of my events are set to be unlimited.


Did anyone resolve this issue? I have two sites that it is doing this with!

Please Log in or Create an account to join the conversation.

Minor bugs found in 2.7.1C 14 years 1 week ago #10759

  • twill
  • twill's Avatar
  • Offline
  • Junior Boarder
  • Junior Boarder
  • Posts: 24
  • Thank you received: 0
To lkpackard > I too encounter this bug for group registrations, for now just set the capacity of the concerned events to 999999 and it will work fine.

As for the remaining bugs in 2.7.1c, they don't seem minor to me :

1) BUG with conditionnal fields and selection limits is still there

2) Say you have a dropdown field with 3 possible values : "option 1", "option 2" and "option 3". If "option 1" has reached it's selection limit and that a user, who had chosen that particular option, tries to edit his registration (say he wants to change his e-mail), the system acts like he had never answered the dropdown field > so instead of just changing his e-mail, he also has to choose another option ...

3) Same problem occurs in backend, looking at the records, if a field has reached it's selection limits, it appears empty (like the person hadn't answered it)

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

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).

6) On an Iphone or Blackberry, people can submit the registration form even if they didn't answer any required field.

Please Log in or Create an account to join the conversation.

Minor bugs found in 2.7.1C 14 years 1 week ago #10799

  • lkpackard
  • lkpackard's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 0
twill THANK YOU!!! I have done the upgrade to d but still no fix on my end. Yours is doing the job for now!!

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.220 seconds