Incorrect fields deleted and some fields do not delete

edjec2

J-3.9.3, DTR-4.1.0

Here’s something new I unfortunately discovered; when trying to delete several unused fields, the first three fields (first name, last name & address) were also deleted, but were not marked for deletion. This happened on both of my servers; local and production, so I’m certain that this is not operator error.

Also interesting is that fields further down the list will not delete at all, no matter how many times I tried. Deleting these fields required manual deletion via the database.

edjec2

[Update]

My client is applying pressure to take this event registration live, so I was forced to roll back to DTR 4.0.8. Deleting fields is working properly in this version. I have no choice but to abandon v 4.1.0 and wait for the next release.

saguaros

edjec2

Hi,

I can't replicate this issue at my end, do you have a test / staging site with 4.0.1 version installed so I can check for you?

edjec2

The new 4.1.0 field updates corrected some of the issues, but also created several new problems:
- Conditional fields stopped working on the registration forms and displayed even though they were disabled.
- Sponsor, Speaker and grid details images did not display.
- There was something else, but I'm so frustrated I don't remember what it was.

I've given up on 4.1.0 and reverted back to 4.0.8. The images returned, but all fields in each event and registrations were missing. In checking the dtregister_fields database table, I found that the parent_id column had all been set to random numbers. I reset all of these back to 0 and all fields came back in admin and the front-end. This is the sql I used to reset:

UPDATE your_prefix_dtregister_fields SET parent_id=0

Replace "your_prefix" with your own.

I've probably spent over 40 hours trying to fix these problems created by the 4.1 update. I'm losing so much money on this client's event that I can't continue with this and will wait until the 4.2 or 4.3 updates have proven themselves to be stable before updating again.

On a positive note; I see that JA has been releasing new templates while we've all been struggling with this...

saguaros

edjec2
Hi,

The fields issue in 4.1.0 version are fixed, if you have any issue, kindly share with me in details so I can help like: which conditional fields, sponsor / speaker images in which event?

If you have a test / staging site with this latest version, share the login info with me, I will check it for you.

In case, you need a live chat, you can reach me via Skype: hiennm88

Regards

edjec2

Well, change is a constant…

Today, my client decided to change/acquire more information on the event registration form and additional fields are required, so I decided to try the update to 4.1.0 again with the controller and model field.php fixes.

The new fields are saving and displaying as they should, but conditionals are now broken (as stated above) on previously existing fields. The first level conditional fields function properly, but sub-conditional fields display even when the first conditional is negative. Below is the expected logic chart and when ‘Age=Adult’ is selected, the sub-conditionals function properly. However, if ‘Age=Youth’ is selected, the Show Car field is not displayed (correct), but the three other sub-conditional fields do display. I’ve found no combination that will produce the correct output.

Note: this has been working fine (since 2011) until the 4.1.0 update.
Note 2: I discovered that the DTR SSL plugin was causing the issue with the images. Uninstalling this plugin has corrected the problem.

Third level conditional fields are ignoring the second level conditional field settings. I haven't tested below the third level.

Thanks for your assistance.

saguaros

edjec2
Hi,

Let me check with our developer on this and will get back to you.

Pls stay tuned.

edjec2

saguaros

Let me check with our developer on this and will get back to you.

Pls stay tuned.

Has anyone checked lower level conditionals yet? This is still an issue.

Thank you.

saguaros

edjec2
Hi,

There maybe the same issue as above with the parent_id of conditional fields (3rd level), the same process can be applied but may need to re-assign child fields again.

Our developer will check on this and get back to you.

Regards

edjec2

saguaros

may need to re-assign child fields again.

I've done this many time with no change in results. I've also recreated all of these fields and the 3rd level conditionals exhibit the same errors on the new fields.

versionvirtual

This extension is a great idea, but is extremely buggy, I think it's not safe to use it. I'm using Version: 4.1.0, it's my first time with it and:
1. Currency can't change, when you press "save" it continue appearing US DOLLAR.

I added a custom field, it appears in the register form but it doesn't appear in the list of fields, so now I can't delete, unpublish, edit... I'm thinking about using PHPMyAdmin and look for that record myself, but I think it's not the idea of using this extension.
I was looking for help in this forum and I have found this post, looks like a nightmare having this issues with a live event.

edjec2

versionvirtual

Yes, I've been trying to take our event live for over a month now and still having trouble.

For the fields issue; did you try replacing these two files? https://www.joomlart.com/forums/d/20776-custom-fields-afther-4-1-0/5

It seems to work for some, but not for me. New fields added still do not display. I have to edit the raw database and change the 'dtregister_fields' 'parent_id' column from 0 to get the new fields to display. The new Rebuild button does not change anything on either of the two servers I'm running this on.

Good luck.

versionvirtual

Hi edjec2!! Many thanks, I'll try but it seems not the way it should work by default... specially if the site is for a customer.

saguaros

versionvirtual

The issues you're mentioning was already fixed, if possible, pls create a ticket and share me the credentials of site you're working on, I will fix it for you.

edjec2

4/8/2019: today my client was asking why we couldn't get this working when millions of other sites use ecommerce without issues. How do I answer that?

I had no choice but to roll back to to a functioning version. First to 4.0.8, tested the conditional fields to the 3rd level and the payment processing. Both areas functioned as they should. I then updated to v4.0.9 and again tested with positive results.

4.1.0 does not work properly in either field conditionals or single payment processing. Something you folks changed or added going from 4.0.9 to 4.1.0 is causing problems here. That narrows it down quite a bit, I would think.

With v4.1.0, everytime I added a new field for an event, I would find a null field in dtregister_fields and any of the newly created fields would not be visible. I had described this in a previous post and two files were updated but did not correct this problem. The new Rebuild button does not bring the non-visible fields back either.

Here's how to manually fix for anyone having similar issues with non-visible fields:
Open dtregister_fields table (phpmyadmin or similar) and locale a row with nothing in it but NULL. Delete this row. If you don't find this empty row, then good for you.

All main level fields must be set to parent_id=0. If your level 1 fields are not set to 0 use this to correct:
UPDATExxxx_dtregister_fieldsSETparent_id='0' WHEREparent_id='?'

Replace 'xxxx' with your prefix and '?' with the parent_id number that is not correct. In my case I had 23 level 1 fields that were set to 132. Level 1 fields are those that are not conditional on another field to display. Name, address, etc., are usually level 1 fields.

After you run the sql command and reset the parent_id columns back to 0 (zero) it should allow them to display in both admin fields and event/fields.

I hope this helps someone who may be having similar issues.

I now have over 110 hours invested fiddlefarting around my with clients event trying to get this program to function and my patience is exhausted. We're going live with v4.0.9 and we'll see if this is fixed by next spring as to whether or not we continue using DTR.

saguaros

edjec2

Could you update the login info again? our developer will take a closer look at the 3rd level conditional fields and check for you.

miroslav-tunjic-gmail-com

Hi
what DTR v works for you?

edjec2

miroslav-tunjic-gmail-com

@edjec2 is saying: you guys shoot something badly
This is not about fixing ONE (!) website issue, it should be about solving a problem you caused for all of us.
Again: we talking basics here, it´s fields, in a form, as always...

This is so frustrating, i am thinking moving away from DTREG, Afther 10 YEARS!!

saguaros

edjec2

saguaros

We have rolled back to v4.0.9 and the conditionals are working as they should. Our event registration period will last until the end of August and we're going to hold pat on v4.0.9 until the event is over. It's working now and we'll just keep it at that.

edjec2

miroslav-tunjic-gmail-com

I am successfully using v4.09. The event is live and we are receiving registrations. This version is not without issues as well, but the fields and conditionals work fine. We're using the grid theme and I've had to do a few styling corrections for alignment and to make input box sizes consistent. I'm now working on the Profile tab display under Manage My Registration because the field display is a mess and the fields are in a random order - confusing for registrants.

We too have been using DTR for over 9 years and this has really thrown a wrench in the works for this year's events.

saguaros

edjec2
Hi,

These reported issues have been fixed, we're waiting for the onepage checkout feature of DT Reg before releasing a new version. The checkout process will be revamped to be easy and clearer. It's in final stage of testing, we do hope to release it next week.

We're sorry for any inconvenience it may cause.

Regards