Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRM-21585 - Fix erasing membership start_date when membership batch data entry #11462

Closed
wants to merge 3 commits into from

Conversation

chandana-bandara
Copy link

@chandana-bandara chandana-bandara commented Dec 27, 2017

Overview

This PR fixes the issue of membership start date erasing issue when making batch membership data entry

Before

The input field for membership's starting date is empty in membership batch data entry

After

The input field for membership's starting date get populated with the member's existing membership starting date in membership batch data entry

Comments

Not sure if the initial functionality was intentional. I.e. not populating the membership's starting date.


@civicrm-builder
Copy link

Can one of the admins verify this patch?

@seamuslee001
Copy link
Contributor

Jenkins test this please

@jitendrapurohit
Copy link
Contributor

@coolbit Jenkin test is failing as this PR has gone stale and need to be rebased.

@chandana-bandara
Copy link
Author

chandana-bandara commented Dec 28, 2017

Shall I go ahead and rebase it to the master branch? or will you do it?

Thanks,

@jitendrapurohit
Copy link
Contributor

jitendrapurohit commented Dec 28, 2017

You need to do this, for eg: from your terminal (on CRM-21585 branch), execute the below command inside civicrm dir -

$ git pull --rebase upstream master

where upstream is the civicrm/civicrm-core remote listed in $ git remote -v.

This will pull the latest changes to your local civicrm directory.

  • If there are conflicts

    • you need to resolve it manually, maybe you'll get the conflict in templates/CRM/Batch/Form/Entry.tpl file.

    • After resolving the conflict enter this into your terminal.

      $ git add <filepath>
      $ git rebase --continue
      
  • Push the latest code to your branch.

    $ git push origin CRM-21585 (use -f option before `origin` if not pushed with this command).
    

where origin is the coolbit/civicrm-core remote listed in $ git remote -v.

Hope that helps! If not, you can create a new branch and re-submit a new pull request and close this one.

@jitendrapurohit
Copy link
Contributor

@coolbit I saw the "before edited" comment of yours which said you needed a documentation. Anyway, the above can work and yes you need to rebase it to the master branch.

@chandana-bandara
Copy link
Author

In the master branch, https://github.com/civicrm/civicrm-core/blob/master/templates/CRM/Batch/Form/Entry.tpl has my patch applied already. Is that it or is there anything else I need to do to make it complete?

@jitendrapurohit
Copy link
Contributor

jitendrapurohit commented Dec 28, 2017

@coolbit ok - I see the change made in this PR is already submitted #11202 and merged into CiviCRM version 4.7.30. So you can now close this pull request.

@monishdeb
Copy link
Member

@coolbit I am closing this PR in favor of #11202 which is already merged against 4.7.30. Thanks!

@monishdeb monishdeb closed this Dec 28, 2017
@chandana-bandara
Copy link
Author

@monishdeb Sure. No worries.

@chandana-bandara chandana-bandara deleted the CRM-21585 branch December 28, 2017 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants