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

PCHR-4346: CiviCRM Upgrade #432

Merged
merged 3 commits into from
Dec 14, 2018

Conversation

davialexandre
Copy link
Member

@davialexandre davialexandre commented Oct 23, 2018

Overview

This PR is part of the updates to make CiviHR compatible with CiviCRM 5.7.0. The other part of the work was done in compucorp/civihr#2899.

Technical Details

In CiviHR, we use hook_civicrm_tabset in multiple extensions to make sure the tabs in the Contact page will be displayed in some specific order. This order mandates that the "Documents" tab should be displayed after the "Communications" (activities, internally). However, due to a recent cleanup in CiviCRM core, the order of these two items was inverted after upgrading to 5.7.0. The reason is that after the cleanup, the "Communications" tab now has a hardcoded weight of 70 and since the weight of "Documents" was set to 60, it started being display before "Communications". To fix this, I changed the weight to 75, making it greater than 70 but also leaving some room for any other possible items in the future.

@davialexandre davialexandre force-pushed the PCHR-4346-civicrm-upgrade branch from 72ddb40 to 11eae1b Compare November 6, 2018 17:16
@davialexandre davialexandre changed the title [WIP] PCHR-4346: CiviCRM Upgrade PCHR-4346: CiviCRM Upgrade Nov 7, 2018
Now that the final version has been released, we don't
need to use the branch version anymore
@davialexandre davialexandre changed the base branch from master to PCHR-4321-php7-upgrade December 14, 2018 09:58
@davialexandre davialexandre merged commit 67b71a2 into PCHR-4321-php7-upgrade Dec 14, 2018
@davialexandre davialexandre deleted the PCHR-4346-civicrm-upgrade branch December 14, 2018 10:37
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.

2 participants