TOPIC: New Fields populate Existing Records

When I create a new field in DTR it is automatically enabled in all active events!

This is crazy because if I need to create a special form for one type of event, and create 10 fields for it, I can't have those fields show up in all my other events. These are files with the ALL EVENTS setting set to NO.

How do I disable this default=on across all events 'feature'
If I have 50 events, and I create a new field for just one event, I have to manually go into 49 other events and turn it off!

Thx

I'm using 2.7.3c and that feature works fine for me. If I select the Default Settings for All Events to No, then the field does not show up in an event unless I turn it on.

Actually I have found this to be a problem as well but wasn't completely straightforward. I am using 2.7.4. It only occurs after you add a new field and then go into an event to edit it. After editing (or just opening the event and re-saving), the field will show up on the front end registration form.

Steps to reproduce:
1) Have two events set up
2) Add a new field - set the Defaults to All Events = No, Show = Individual. After you add the new field, if you view one of the events in the front end, the field does not show... which is what is expected.
4) In Backend, select one of the events to edit. Don't change anything but just re-save the event. Go to front end and the field will be showing as active in the event (even though it still shows default in the backend being all events=no).

The only way that I can see to avoid this is to make sure you put Show to None when setting up the field and then change it when you make the field active in the event that you want.

This seems to happen to me regardless of whether I edit event or not.
I have not hammered at it, but this is what I see:
5 events are 'live' on site
I look at their DTR front end forms and they have 10 fields (example)
In backend I add new field: field_foo for an event #6
Now events #1-6 have 11 fields active, with field_foo showing

field_foo is not set to all records
field_foo could not have been in records 1-5 because it never existed when they were set up.

Something weird going on