CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Long term release support (Moderators: mathieu, Eileen, youngjin) »
  • Backport-CRM-11918
Pages: [1]

Author Topic: Backport-CRM-11918  (Read 1174 times)

FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Backport-CRM-11918
September 18, 2013, 09:35:30 am
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?
Lead Developer, C3 Design.
Twitter: @FatherShawn

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: Backport-CRM-11918
September 18, 2013, 01:11:38 pm
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)
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Re: Backport-CRM-11918
October 11, 2013, 12:47:47 pm
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?
Lead Developer, C3 Design.
Twitter: @FatherShawn

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: Backport-CRM-11918
October 13, 2013, 01:26:32 pm
You might need to check whether this is worth backporting or whether the work / risk means an upgrade would make more sense
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Long term release support (Moderators: mathieu, Eileen, youngjin) »
  • Backport-CRM-11918

This forum was archived on 2017-11-26.