TOPIC: Update requires fields tab to be reconfigured for each event

Every time I upgrade to the latest version, each published event acquires any published fields not previously being used for that event.

For example:
Event 1 requires only name, email to register.
Event 9 requires multiple fields of information in addition to name, email.
Upon upgrade, all the fields being used in Event 9 appear in Event 1. This has happened for the last several upgrades.

I will soon have over 30 open events, so it is very time consuming to have to go in and edit each event. Is there a fix for this?

I am using 2.7.13a and yes, every time I upgrade, I go into config and reset all the parameters.

Thanks for your help.

This doesn't make any sense. We've never seen that on ANY site or had anyone else report it. There is not even code in the installation to modify any field assignments. We will do some further checking though, but that seems pretty odd.

I haven't understood it yet - but I can 100% confirm I have on several occasions found my published events have suddenly inherited fields which I hadn't assigned to them.... So confirming this is an issue - I just hadn't shouted yet as I tried to understand the behaviour first.... I'm regularly checking my events now to remove the unwanted additional fields that appear..... Can't help identify the cause of the problem at this stage - can only confirm it's there!

Having said that, I haven't experienced it yet with the latest DT Reg version... but I certainly had it in the immediately prior version... Always an intermittent issue though...

I just updated to 2.7.14 and this is what I found:
I updated as instructed and reset all the config parameters.
I then opened each published current event.
Only the events that were copied from a previous event had the issue within the fields tab.
The events that were created from scratch did not have any issues with incorrect fields appearing after the update.

edit: When I copy an event, the fields (almost) always stay the same. In fact, I usually only copy an event when it is the same event, repeated at a later date, or at a different location. The registrant parameters stay the same.

I too can confirm that this exact thing has happened to me on many updates.