Do developer updates to airports trigger a need to re-add them to the disabled list? Given this is the list of airports that GSX is not replacing the jetways for, I would think an airport update would not matter.
Sure it doesn't matter: you are not acting on other developers files, you are selecting what files from GSX you are moving in or out two folders ( active and inactive )
When I purchase / install a brand new 3rd party airport, I immediately go into GSX Pro/Config, find the airport, add it to the disabled list, and click apply.
This is what you are always supposed to do, and it's the correct procedure, since the automatic disabling is done when you first install GSX, or when you update it, but not when you install a new 3rd party airport.
Usually it sticks but a few weeks later I'll notice it is missing from list and need to re-add it.
This is what is not supposed to happen, and nobody ever reported it before.
Is there anything else that would cause an airport to be removed from the list by GSX?
It depends if the airport is removed from the Disabled list, or it's added back to the Enabled list, as if you would have it on both sides. Reinstalling GSX will surely cause the airport being added to the Enabled list, which is normal, but since the installer would immediately launch an update, it will see that airport was in your Disabled list ( the "backup" folder ), so it should remove it again during the update step so, the only possible reason I can think of, is having reinstalled GSX but the update step that was performed upon reinstalling didn't complete.
