TOPIC: Bug: calculating wrong amout with checkbox!

Hi,

I've found a bug. I tested it on a newly installed website locally. (Unfortunately the demo version here still runs on J! 1.5.)

The scenario:
J! 2.5.9
DT Register 2.7.18b
Group registration: Detailed
Create 2 checkbox fee fields (with different fee amounts)
Register a group, select for person 1 two items of checkbox 1 and for person 2 two items of checkbox 2.
So far everything ok.
Open one registant of the group and click save.
Open another registrant of the group and save.
The amount will be false!
Open the first registrant again and click save.
The amount will change! (Although you didn't change anything.)

This is a big bug in my eyes because you can't relay on anything anymore and have to test anything in any way but you can't.

I'd appreciate a quick response.

Thanks

I've found out, that's enough to create one checkbox field and check more than one option for at least one registrant.

Hi, I'm looking into this for you. Thank you for opening a support ticket. Issues like these require more detailed information for us to troubleshoot.

A couple notes and questions for the benefit of other readers, however:
1. Just because you can duplicate the problem in a fresh install does not necessarily mean it is a bug. You could be creating the same configuration, same server settings, etc. It does help us eliminate the question of conflicts, so that is good.
2. Calculating fees is based a number of settings, all of which need to be carefully gone over. We need to establish whether you are implementing change fees, taxes and or other fees/discounts that are ordered in such a way as to tabulate based on those fee fields, or date-specific fee changes.

3. Question: is this happening before or after the order is complete?

Thanks,
We definitely want to get to the bottom of this for you, so any help you can provide is great.

Jen

Hi Jen,

Thank you for your repley even on the weekend!

It happens when the order is complete and someone (frontend and backend) saves changes of a group member.

Here how I became aware of it:
(all installatinos below J! 2.5.9 & DT Register 2.7.18b)

I installed and configured a website locally with MAMP, used some database entries from an old installation and moved it with Akeeba Backup to LAMP. Everything fine. There I tested the frontend DT register user panel and noticed that when I edit and save a group member sometimes the total fee changes. Now the search began. I found a mistake in my field entries but that didn't cause it. I went through the taxes and all this stuff but finally I thougt it just can't be that another fee than the primary is calculated with whatever settings for the change fee option is disabled (and the newly calculated fee was below the primary).

So I installed a new site on MAMP to be sure that nothing went wrong with my database manipulation nor that other extensions cause the issue. I made only entries that I really had to make for DT Register to work (e.g. no location, no change fee, no taxes, no payment options (I think), most standard fields disalbed, no Falang nor other extensions but: detailed group registration set to yes). But there I found the same thing happenig in the backend.

Then I thougt: Maybe it's a MAMP issue and I tested it on an old site which I installed on another (1&1) LAMP. But the same problem remains.

Finally I tested it on the DT Dev. Demo Site which is J!1.5 where the issue doesn't appear.

To be clear on the issue: You create a fee checkbox field with more than one option. You register a group (front- or backend) with more than one person and check for at least one person more than one option of the ceckbox field. Then the total fee should be rightly calculated. Then you edit one person (front- or backend, I think it doesn't matter which person you edit) and only the checkbox fee(s) of the just edited person will be calculated. The other fee(s) are not added.

So I think that you can recreate the issue on your own system very easily, can't you? Maybe someone can give me a reply to this because I don't want to call anything a bug that isn't! (Of course I can send you my local installation, too.)

Thanks,

Dan

Not at all, if it's a bug we want to find it and fix it. Well, we want to fix it regardless. We just need to track down whether it's specific to a certain environment or universal. It helps in diagnosing. I am testing today to see if I can replicate from your very detailed (thank you!) explanation. I will reply both here and in the ticket.

Jen

ok thank you. Mayby my attached screen shots help to understand the issue. (The arrows mean click.)

Dan