Backport-CRM-11918

[FatherShawn]

http://issues.civicrm.org/jira/browse/CRM-11918?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab

We use an individual subtype for about 10% of our contacts - this bug makes in place editing unusable for subtyped contacts.

What is the process for backporting.  Do I fork and pull request on GitHub? Submit  a patch?

[Eileen]

Yes, That's exactly right - the repo is here

https://github.com/CiviCRM42/civicrm42-core

we don't have much of a ticket logging system (but it's also low volume) so post here when you have done it so we don't miss it (most of the other PRs have intentionally been left open because I will only merge them if someone wants to check them out & test them)

[FatherShawn]

OK - so I started working on this and immediately hit an architectural question.  The bug-fixes are to files in CRM/Contact/Form/Inline.  These classes were re-architected to be extensions of a general CRM_Form_Contact_Inline class in 4.3.  Do we want to bring that into 4.2 or should I take the fix applied to the parent class in 4.3 and implement it in the separate classes as appropriate in our 4.2?

[Eileen]

You might need to check whether this is worth backporting or whether the work / risk means an upgrade would make more sense