This same problem was reported and fixed in #1559 but it looks like we missed another place in the code where we are printing the bride's name first instead of the groom's name. This affects search results. Run a search for any marriage (say, John SMITH in Staffs between 1800 and 1805). The list of hits all have the bride's name first, but if you click on any one of them to display the details, then the groom's name is first (which is normally how it is in the original records, so that's how we should display it consistently).
The offending code might be that in lib/freereg1_translator.rb which we call from app/models/search_record.rb. At least, that's the only place I can find where the bride's name is handled before the groom's name. It would be worth grepping the code base for groom_surname or maybe just 'groom' to make sure we are aware of all places where the display order might still be wrong.
This same problem was reported and fixed in #1559 but it looks like we missed another place in the code where we are printing the bride's name first instead of the groom's name. This affects search results. Run a search for any marriage (say, John SMITH in Staffs between 1800 and 1805). The list of hits all have the bride's name first, but if you click on any one of them to display the details, then the groom's name is first (which is normally how it is in the original records, so that's how we should display it consistently).
The offending code might be that in
lib/freereg1_translator.rbwhich we call fromapp/models/search_record.rb. At least, that's the only place I can find where the bride's name is handled before the groom's name. It would be worth grepping the code base for groom_surname or maybe just 'groom' to make sure we are aware of all places where the display order might still be wrong.