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.

Sign up for GitHub

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

Jump to bottom

VOL-318: Addresses Backbone using CiviCRM's namespace. #471

Merged
merged 1 commit into from Mar 23, 2018
Merged

VOL-318: Addresses Backbone using CiviCRM's namespace. #471

merged 1 commit into from Mar 23, 2018

Conversation

universalhandle
Copy link
Contributor

@universalhandle universalhandle commented Mar 19, 2018 •
edited by civicrm-builder

@universalhandle
Copy link
Contributor Author

Appears to address all issues manifesting as a result of the changes in CiviCRM 4.7.31. Needs further testing -- in particular I haven't tried to load CiviVolunteer in CiviEvent yet.

@universalhandle
Copy link
Contributor Author

User QA passes, both in the "standalone" and CiviEvent contexts.

I'm pretty sure this breaks instances pre-4.7.31, but I'm not inclined to try to provide a patch that supports both releases.

@ginkgomzd ginkgomzd merged commit 4af0a82 into civicrm:master Mar 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
master
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@universalhandle @ginkgomzd @civicrm-builder