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

Follow up to PR 12160 to update the DB version of the templates #12417

Merged
merged 1 commit into from
Jul 6, 2018

Conversation

aydun
Copy link
Contributor

@aydun aydun commented Jul 4, 2018

This just updates the DB version of the event registration templates following the changes in PR 12160

@civibot
Copy link

civibot bot commented Jul 4, 2018

(Standard links)

@aydun
Copy link
Contributor Author

aydun commented Jul 4, 2018

@eileenmcnaughton - here's the follow-up to #12160 Is '5.4.alpha2' the right version to use?

@eileenmcnaughton
Copy link
Contributor

@aydun so we already have this merged to 5.4 & I believe your template update is merged already.

  /**
   * Get any templates that have been updated.
   *
   * @return array
   */
  protected function getTemplateUpdates() {
    return [
      [
        'version' => '5.4.alpha1',
        'upgrade_descriptor' => ts('Use email greeting at top where available'),
        'templates' => [
          ['name' => 'membership_online_receipt', 'type' => 'text'],
          ['name' => 'membership_online_receipt', 'type' => 'html'],
          ['name' => 'contribution_online_receipt', 'type' => 'text'],
          ['name' => 'contribution_online_receipt', 'type' => 'html'],
          ['name' => 'event_online_receipt', 'type' => 'text'],
          ['name' => 'event_online_receipt', 'type' => 'html'],
        ]
      ],
    ];
  }

So I think your text & html will get picked up already - a weakness is that the upgrade_descriptor only mentions one descriptor whereas we now have multiple :-(

If subject also changed then I think a PR to the 5.4 branch altering the above to include

['name' => 'event_online_receipt', 'type' => 'subject'],

Will work

@@ -81,6 +81,15 @@ protected function getTemplateUpdates() {
['name' => 'event_online_receipt', 'type' => 'html'],
]
],
[
'version' => '5.4.alpha2',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this should be 5.5.alpha1 i think

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep - if it is against master - see above for why I think 5.4 rc makes sense

@aydun aydun force-pushed the core_124_template_upgrade branch from 4f3d68f to 2db5cab Compare July 4, 2018 22:43
@aydun
Copy link
Contributor Author

aydun commented Jul 4, 2018

Ok... is this what you mean?

@eileenmcnaughton
Copy link
Contributor

@aydun - yes - but rebase onto the 5.4 branch since the rc has been cut & we should include this with the other lines

@aydun
Copy link
Contributor Author

aydun commented Jul 5, 2018

Hmm, that's what I thought I had done ... git diff 5.4 shows only my change

@seamuslee001 seamuslee001 changed the base branch from master to 5.4 July 5, 2018 22:52
@seamuslee001
Copy link
Contributor

@aydun Just needed to change the basis of the PR :-) @eileenmcnaughton you ok with this being merged to RC then?

@eileenmcnaughton
Copy link
Contributor

@seamuslee001 yes - added merge on pass - in theory adding these templates to the array like this is 'always safe'

@seamuslee001
Copy link
Contributor

Merging as per the tag

@seamuslee001 seamuslee001 merged commit 5163811 into civicrm:5.4 Jul 6, 2018
@aydun
Copy link
Contributor Author

aydun commented Jul 6, 2018

@seamuslee001 Thanks for doing that - would you mind sharing the git commands you needed to do for this? I did a 'git rebase 5.4' but clearly there was something else needed.

@eileenmcnaughton
Copy link
Contributor

@aydun this is what I do

1 ) git fetch -f origin
(to make sure I have the latest locally
2) git rebase -i origin/master (or git rebase -i origin/5.4 in this case
3) git push -f myrepo/mybranch

@seamuslee001
Copy link
Contributor

@eileenmcnaughton that is what @aydun had done but then all i did was just edit the PR to change the branch of the civicrm-core repo the PR was targeting @aydun

@eileenmcnaughton
Copy link
Contributor

@seamuslee001 ah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants