I'm also experiencing the same issue with setting up any new custom fields for a fresh install. I have testing scheduled this weekend with the registration committee and really need to have this resolved soon, or I'll need to roll back the 4.1.0 install.

Hi guys,

Try to take a backup of this file: [root]/administrator/components/com_dtregister/models/field.php and update with the attached file:

fieldphp.zip
15kB

santorijose

I can't access your site now

I updated file - Now after saving changes to fields in filed management it comes back to a blank page and events are still missing fields@saguaros#70815

It did not resolve the issue for me either.

I'm experiencing the same types of issues. Can't create or copy custom fields. Can't change order of custom fields. Existing custom fields show on some forms and not on others. We need this corrected as soon as possible. It frustrating to have this happening when we just updated to a new version.

I think there are still a bug in this file. After i add a new field, and create a conditional option, ALL of the other fields are gone in the front end. After i check again each of the field, it seems that all the fields have some conditional options, and need to be edited one by one.

    Hi If you guy did some changes now i can't even see the register event user which is a big problem. i need to see who paid for the events...

    When enter record for register user detail i get back a HTTP ERROR 500

    Going to downgrade to working version - i don't want to loose my client
    saguaros

      Downgrade to version 4.07

      • had to save each field in field management so they could appear in events

      Website DT Register module was reset back to version 4.0.7 from version 4.1.0– after last 3 version had bug issues to its functionality.
      • Version 4.0.8 some registration emails were not arriving to administrator
      • Version 4.0.9 Emails where arriving but where being duplicated to event administrator.
      • Version 4.1.0 Fields were missing form events in administration side, was not able to make changes or create new fields in field management. Email notificaitons were arriving with out field information.

      I'd like a solution to this as well. We're running a live event and need to add fields ! We can't edit an old field to serve as a new field either. It looks okay when attempting to edit but it won't save.

      We have also noticed that the placeholder [ALL_FIELDS] is showing up blank in the Custom emails going to registrant and to Administrator.

      Please don't make us switch to eventbrite (shudder). We've depended on DTRegister for nearly a decade.

      santorijose

      Could you tell me the record that missing the paid user? I will check for you.

      P/s: I can't access backend of your site now, kindly check and update again.

      I am having the same problem as ladyweave. My event registration emails are not showing any of the fields. [ALL_FIELDS] not working since upgrading to 4.1.0.

      I loaded 4.1.0 as a clean install (not an upgrade to a previous version) of DT Register. I also cannot add new fields or copy fields as described above. Changing fields.php didnt help

        brwalker

        I updated the latest version of this 'field.php' here: [root]/administrator/components/com_dtregister/models/field.php

        fieldphp.zip
        15kB

        If there is still no go, you can create a new discussion / ticket and share me the credentials of your site, I will try to check for you.

        Regards

          Is the problem resolved? Yesterday I rolled back two sites that use DT Register because the fields were not showing up in the registration emails. If the problem is resolved, do I need to open a new ticket to get the updates? Thanks!

            ammattingly

            If you're using 4.1.0 version, try to update above file also.

            In case it still doesn't work on your site, you can create a new ticket and share the info, I will check for you.

            Regards

              saguaros

              I rolled back to 4.0.9. I think my best option is to wait until the version that corrects the problem is released.

              Thank you.

              You need to Login to view replies.