-
-
Notifications
You must be signed in to change notification settings - Fork 824
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
Migrate CiviGrant component to an extension #22064
Conversation
(Standard links)
|
001cd4b
to
0fd1ed2
Compare
mysql: [Warning] Using a password on the command line interface can be insecure. |
35b7192
to
8727067
Compare
@monishdeb could you do a review of this. Please include how this impacts extensions like Grant Application Pages, Grant Programs. I think there may be a profile edit one, and at least one financial regarding Sage Intacct. What is of interest and unlikely to be found is breakage of related extensions when CiviGrant is changed from Component to Extension. I'd focus on calls and installs. If related extensions need to check for enabled status of CiviGrant as an extension now that is fine. |
@colemanw when I tried to install the civigrant extension on a clean setup I got this error:
Have you encountered this strange error earlier? |
@monishdeb I just tried it myself and was able to run it without error. I ran setup to generate a fresh database based on this branch to avoid conflicts: git checkout civigrant
./bin/setup.sh
cv en civigrant I also just made some additional fixes and force-pushed this branch. 3 things are still not working as they should:
|
17b9c8e
to
d02b9b7
Compare
'update' => 'unmodified', | ||
'params' => [ | ||
'version' => 4, | ||
'values' => [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@colemanw shouldn't the parameters declared directly under params
not under values
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@monishdeb - no because APIv4 structures it this way. civicrm_api4('OptionValue', 'create', ['values' => [...]])
@colemanw I have rebased the PR. However I have one concern on the mgd file. Can you please take a look ? |
@monishdeb we'll have to rebase this again and move the upgrade code to 5.46. That'll be easier after merging #22224 |
I have reviewed and marked #22224 with MoP. Reviewed the current PR in my local setup, everything works fine. Tested by submitting new Grant from and didn't encounter any issue |
@monishdeb did you test all of these?
|
@monishdeb I've got this rebased again to use the 5.46 upgrader. But I think search/reports still need testing per my above comment. |
@colemanw yep my bad ... I missed the advanced search, reports . Will update the PR shortly with search fixes. |
Sounds good @monishdeb - FYI you'll have to reset your local branch because of the rebasing I just did. |
04d8dd3
to
1b276ef
Compare
'import' => TRUE, | ||
'where' => 'civicrm_grant.application_received_date', | ||
'export' => TRUE, | ||
'table_name' => 'civicrm_grant', | ||
'entity' => 'Grant', | ||
'bao' => 'CRM_Grant_BAO_Grant', | ||
'bao' => 'CRM_Grant_DAO_Grant', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@colemanw any reason why this is being changed from the BAO to DAO?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤷 GenCode wanted to...
Insert and then delete CiviGrant to avoid messing up legacy code with expectations of component IDs.
…table in core Removes CiviGrant from hardcoded lists when possible, or at least puts up guards to check that it's available before attempting to use it.
This fixes up the `CRM_Contact_BAO_Query_Interface` class which had incorrectly omitted `static` from some static functions. Adds defaultReurnProperties to search hook interface.
Disable & delete component, install extension as either "enabled" or "disabled" depending on the status of the component. Migrate option values to managed entities Migrate navigation menu to extension managed entities
9159fc0
to
29d2ce6
Compare
retest this please |
I chatted with @colemanw and as
I'm merging after a light 'click around' and we should continue to QA during the release cycle. @colemanw told me there is still a report issue - although I didn't spot it when I ran the report just now (as demo user). However I did spot a couple of things
|
The changes to |
@MegaphoneJon I would be OK reverting - but I worry that extensions may have already adapted so that could break them.... Note it is implementing |
Overview
This a straight port of CiviGrant to be packaged as an Extension instead of a Component. All the functionality is the same aside from how it's enabled or disabled in the UI.
Before
Enable or disable CiviGrant through Administer -> System Settings -> Components. As a component it cannot be uninstalled.
After
Enable, disable or uninstall CiviGrant through Administer -> System Settings -> Extensions. As an extension it can be uninstalled, which completely removes grant data from the database.
For existing sites, the extension will be automatically installed as either "enabled" or "disabled" depending on the status of the component.
For new sites, the extension is not installed by default.