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

VOL-140: Flexible needs -- ensure their creation and display in search results #337

Merged
merged 7 commits into from
Feb 10, 2016

Conversation

universalhandle
Copy link
Contributor

No description provided.

This is handled in the form layer:
- for compatiblity with Volunteer 1.4, which also creates needs in the form layer
- for API compatibility (1.4's project create API does not create flexible needs)

Maintaining the status quo theoretically gives third-party developers more flexibility
to do whatever they want using the API. This commit is intended to be a stopgap
measure -- the "flexible need" concept is overloaded and needs rethinking.
…exible need.

This is probably only necessary for installations which tested an alpha or beta version.
… Implemented it where previously a string was hardcoded.
…ting code.

civicrm_api3_volunteer_need_get() already handles setting display time and role label for flexible needs.
ginkgomzd added a commit that referenced this pull request Feb 10, 2016
VOL-140: Flexible needs -- ensure their creation and display in search results
@ginkgomzd ginkgomzd merged commit 6353caf into civicrm:master Feb 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants