Product Updates
Joomla 5.2.3 Compatibility for JA Templates, Bug Fixes, and More

rbelanger Thank you. I love DT Register, but it seems like some additional dev work to simplify the system is needed.

Thank you so much for your kind words and your support. It means so much for the JA team and keeps us motivated in bringing even more enriched product for our members 🙂

You may also let me know if you have any specific suggestions in terms of improving workflow so the same can also be considered whilst the workflow is being updated.

Cheers

The team is working to fix the issue and it has been asked that the workflow should be simplified, if any of the payment requires specific information other than the routine information, it would be displayed and asked for user to provide post selection of the payment gateway. Otherwise selection of payment gateway should take them straight to that payment gateway for payment processing.

    drarvindc
    thanks for your update. As this has been an ongoing issue since version 4.0.4 for us - getting a proper auth.net accept hosted payment gateway - do you have any update on when this might be ironed out?

    Thanks!

      smanders
      Thanks for your understanding, we're working on resolving some remained minor issues first, then will revamp the checkout workflow. Kindly follow our blog post for update news.

      What in the world is going on with the payment options now?

      There is no way to adjust the logo; why are customers shown a "gateway" instead of a "method?" Why can't I adjust what should be sent to the CC gateway - this particular company doesn't ask for all that address garbage. Do you think people know what Authorize.net is or would it be better to name it something like Pay By Credit Card? On and on and on! This is just a terrible plugin.

      It's hard for me to imagine that anyone there actually uses your software because this is just silliness. We don't want people to have to input the same information over and over again or guess at what they're trying to do when paying!

      If this can't be adjusted to make it easier for my clients to set up events then I'm going to have to look for alternatives. And just FYI DT Register, there are plenty out there now.

      Mark

      Hi Mark,

      Thanks for your feedback, these things existed when JoomlArt acquired DTHDevelopment, we will revamp and improve it step by step.

      Appreciated your feedback on this.

      Regards

      I've been using DT Register for five years and have multiple clients using it.

      This payment gateway is just about the worst thing I've seen and is in no way is similar to the original DT Register one. But keep saying it and maybe someone will believe you.

      Mark

      I agree with Mark. Payment is so confusing now. We do group registrations often using PayLater. Now I appear to have to collect Billing field information AND go through a bolt on payments gateway that requests information I dont even want. This information replicates the mandatory fields presented as DT Register billing fields. Ughh....

      Double ugh, brwalker.

      Like I've said before, there are a lot of alternatives out there now - out of respect for this forum and Joomlart I won't list them - but I'm pretty sure the next time this client needs an event component it won't be this one.

      I have so many bugs (like any new fields I create don't show up in the backend, and I have to go to the database table to manually re-arrange the fields I do have) that I also can't see using DT Register for my other clients going forward, period.

      I can't have excuses for why something doesn't work. My clients trust me to make their websites work in a reasonable fashion and when they don't they cannot hear from me that "it's under development." It works or it doesn't.

      Do you all understand that? Hopefully, you do.

      Mark

      • AWA likes this.

      Hi guys,

      We're working on revamping the checkout workflow for DT Register, it would be alike the onepage checkout workflow so that it will be more easy & simple. At this moment, the development is in progress, when there is new update, we’ll announce via our blog accordingly.

      Thank you!

        saguaros how about asking people who actually use this stuff for their input after it's in beta?

        Wouldn't that be a benefit?

        Mark

          marse17 how about asking people who actually use this stuff for their input after it's in beta? Wouldn't that be a benefit?

          Sure, It should immensely benefit JA Dev. Team and expedite the whole process by working on improving DT Register's usability, stability, functionality wherever needed, based on user feedback 🙂

          Moreover, The feedback and inputs from the users would help the team work closely and help align with the same in terms of usability and workflow test as there could be times when several aspects can go amiss which can be made known from the users who have deployed and been using specific product

          You may kindly start new new topic ensuring to incorporate - "Feedback and suggestion" in forum topic title, based upon which concerned team can set the context for the actionable tasks to be done and identify exactly which areas or sections can be improved and thereon, prioritize and facilitate tasks to be done

          Thanks and we look forward to your inputs which would be greatly appreciated 🙂


          Nonetheless, The team has already started working on improving workflow as informed by @saguaros and @drarvindc. Please stay tuned..

          Cheers

          9 days later

          I have similar issues with the Payment Information Process as follows with Step 2:

          The radio button is already filled in which indicates to computer literate users that the selection has already been made. Since users think a selection is already made, it's not obvious that they should repeat the selection that's already displayed in order to fix the problem below with the two "next" buttons. If the UI indicates it's selected, then the website should acknowledge it as accepted. If the website is not acknowledging it as selected, then the radio button should not display shaded in as though it is selected. Any situation where that's not the case, the website is broken and it's not obvious to users what they should do.

          My guess is that this has to do with browser defaults. Sometimes browsers pre-fill form elements (due to defaults, history, etc.) and sometimes this leads to bugs where programmers are only looking to see if the user clicks the button, not if it was already selected by other means (like browser defaults or even selection by keyboard). That can lead to this kind of issue where the user validly thinks their answer is already indicated because it was shaded by default by the browser, but the web application is wrongly assuming that the choice is empty until a click occurs. The easiest solution is explicitly "empty" the selection so that any default selections are wiped out and/or to more carefully check the selected values to detect all means by which the selection could be made.

          Ideally, users shouldn't even have to make a choice like payment gateway with only one valid option (especially as a means to hiding future always-invalid options like the second next button). But at the very least, please implement a solution lives up to the following and test it in the major browsers:

          A) If the website is waiting for a selection, the user should see that selection as not having been made (i.e. the radio button would be unchecked).

          😎 If the "next" button doesn't take the user to the appropriate "next" step, it should not be visible. The user should not have a way to "break" the process and if they must, it should be obvious to them that that's what they're doing.

          UPDATE: : I resolved this issue by changing the payment method from Accepted Hosted to simply SIM payment method. Now there is only one instance for the NEXT button.

            jstratos

            We have to use the accept hosted method because of our PCI policies. Has this been fixed in the latest update?

              smanders
              Hi,

              The onepage checkout is still in development stage, we hope it can be released it soon.

              In the meantime, if you face the issue with accept hosted method, you can create a new discussion or new ticket and share the details there, I will help you out.

              Regards

              11 days later

              I can create a new thread, but there's been no solution provided, so it would be the same information. You've helped in the past, with specific fix files, but we were at the point of them being rolled into the main package so that I could deploy it over all of my sites. When the next packaged files came available, it created this new issue. So I'm not sure where we go from here...

              Write a Reply...
              You need to Login to view replies.