saguaros
Retested it with 4.2.1 ... because it was in the releasenotes marked as fixed... it is not! field ordering is total scrumbled @rjeffl thanks for also reporting this issue.

saguaros
.... come on guys. I am in production still on 4.0.9 because that was the last version i could use for more or less without errors... since then i see trying to include new features, increasing style but that all does not help, when the component is not working any more.....

    Bobblue .please share the ordering issue in details . Checked the mentioned record 3563 for ordering. Ordering is fine just backend shows extra fields . Thanks

      gslitt91
      for example:
      Sicherheitscode (Ueberschrift_Sicherheitscode) should be last field in form. but is shown as first.

      Zusatztage (Ueberschrift_Extratage ) should be on -3 but is +2
      Zusatztage (Zusatztage) should be on -2 but is +3

      when i switch between conditional fields the first select is not done correctly... i have to select some other option and then select back the first option to get the conditional fields and they are then someware...
      (See http://playground.inseln-der-macht.de/anmeldesystem.html?task=register.register&eventId=200)
      try Alter to Erwachsen 18-x.... nothing happens. than try it to Kleinkind something loads than again to Erwachsen now it loads something someware..

        Bobblue . Please see "Sicherheitscode " is top field in ordering . "Alter" field has issue , Fixing it .

        gslitt91
        That is only one of many examples....
        please compare:
        https://www.inseln-der-macht.de/anmeldesystem.html?eventId=200&controller=event&task=individualRegister <= production
        with
        http://playground.inseln-der-macht.de/anmeldesystem.html?task=register.register&eventId=200 <= playground where you have all logins...
        as you can see, the fields are in a total different ordering.

        1. Point. I checked now your changes: conditional field "SC Kontingent" is loaded with value "Kontingent 1" but this is not availible any more... this i see also when i try to select something different. But when i just click continue then the booking will be done with a value which is not availible any more (over the limits)

          Bobblue . As per page loading improments Field ordering is not compatible to old data . You can Order fields on field listing in field management . For quick ordering modifications to match exactly to old data . Added the drag/drop ordering of fields in event management on your Site .

          1. Disabled dropdown option also fixed .

          Compared full form . it is fine now .
          Please have look at it . and Leave feedback .
          Thanks and Reagrds

          4 days later

          gslitt91

          ok ordering seams now to be ok. how can i copy it to production (wich table/columns does i have to save?)

          next issue: birthday field is not beeing saved. not from front or backend.
          next issue: when i create a booking and like to pay it later. and then change the due value in admin backend... it is not represented in pay now option.
          For example booking: IDM-19-T0-SC-D-5726383 should now cost only 1 euro because of admin change.... this is also shown in frontend under my bookings ...?controller=user&task=index so here it is correct.

          When I click now to "pay now" i get shown a wrong due (245€)

          This wrong value is also send to payment gateway.

            Bobblue > Just fixed date field . Files modified are
            /com_dtregister/admin/helpers/dtregister.php
            /com_dtregister/admin/lib/defines.php
            /com_dtregister/admin/lib/dt/form/fields/date.php

            birthday-field-fix.zip
            15kB

            Files for field ordering issue files are .
            models/devent.php
            models/field.php

            admin/views/event/add_tab.field.php

            field-ordering-fix.zip
            44kB

            For due price display .

            paynow-price-fix.zip
            7kB

            . 3 files .
            /com_dtregister/controllers/due.php
            /com_dtregister/templates/default/views/due/default.php
            /com_dtregister/templates/default/views/due/default_detail.php

              13 days later

              gslitt91

              So Date filed is fixed,
              ordering issue seams to be fixed.
              Pay now is only partialy fixed.

              So Record: IDM-19-T0-SC-D-2149857 costs original 45 € i modified it in backend so that it costs only 1 € than I used the Pay Now option from frontend like discribed above. Now your fix show me 1 € and this is also given to Paypal... (thats the working halve) when it comes back from paypal as payed ... it seams that he recalculate the price of the record and throw away what ever I modified in backend. So now the record costs again 45 € but 1 € is already paid. Emails are generated also like this with 44 € are open. so consitent wrong 😉 Also the paypal transaction number is not stored back to the record... and as there is something still open the record is not marked as paid.

                Bobblue . "Item Price" can't be changed as it is related to event basic price . When ever someone pays . All fee items calculated base on that basic price . "Amount Paid" can be changed .

                  5 days later

                  Bobblue
                  Tried to go to production with 4.2.3 .. had to roll back because ordering is still not working. I just installed the backup also on the playground (data above) please make an option to migrate old ordering to new ordering with one click. other ways i cant go live. its just not working.

                    Bobblue . Those are fixed , for ordering . You can order field by drag/drop in event management too

                      Bobblue .Please share details so i can fix on your development . I know you have quite complex fields setup .

                        You need to Login to view replies.