Hey @
teriyaki I am unfortunately kind of useless here. I don't intend to upgrade v19 or support that version AND I've never used profiles so I don't know much about how they work or if anything has changed about them in v19. Since you were able to modify some of the code to get it working in v19, here's what I can tell you:
You can find the parsing for profiles in CDatabase.py. Top of the file sets some variables regarding the paths of the profiles, and then the getASpath function looks to see if profiles exist, or else it uses the masterprofile. Based on what you describe, my first theory is that something has changed in v19 about the location (?) of the profiles, and therefore getASpath isn't finding the individual profiles and is using the masterprofile instead. That theory could be wrong! But it sounds like it might fit.
It seems like the Wiki is still (correctly) showing information for v18 - for example the
Database page still shows the schema for the v116 database instead of v118. So similarly i assume that the
Profiles page is still showing the v18 info. And therefore maybe you can check and see if you can locate the profiles where the documentation says there will be. If not, that would validate my theory, and then we could look into changing the variables at the top of CDatabase.py. If they ARE still at the expected location, we'll have to come up with a new theory!
Sorry to offload the investigation to you but i'm not in a good position to set up a test environment at the moment.
It would also be good if we could find the schema for v118 but i don't think a change there is the issue. Also, probably the first thing to do is turn on the debugger and trigger the tagoverview program and see if anything gets written to the log, if you haven't already.