CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Pre-installation Questions (Moderator: Dave Greenberg) »
  • Considering using CiviCRM, but want to be sure it will meet our needs.
Pages: [1]

Author Topic: Considering using CiviCRM, but want to be sure it will meet our needs.  (Read 948 times)

JimV

  • I’m new here
  • *
  • Posts: 1
  • Karma: 0
  • CiviCRM version: NA
  • CMS version: NA
  • MySQL version: NA
  • PHP version: NA
Considering using CiviCRM, but want to be sure it will meet our needs.
December 06, 2013, 06:39:11 am
We have a Wordpress site, but want to add in membership capabilities.
We have not found a WP membership plugin that does what we need, most are directed towards making money from subscribers, which is not what we need.

Since CiviCRM now has Wordpress integration, we think it might be an option for us.

Can CiviCRM do the following:

We are looking for a plugin or app that works with Wordpress that does the following:
- input institutions (universities and colleges in the Wisconsin/midwest area)
- add contact details for that institution, especially email address, but also name/address/phone/etc
- have a signup form where a person
- - can enter their logon details, and then select one of the institutions from the list above
- - allow the login details to be entered manually, and let the user select a username and password
- - allow the user to log in via social media (FB/Twitter/Linkin/etc)
- - not allow the person to log in till their application has been approved by the contact at the institution
- - automatically generate an email to the institution contact that someone had requested an account on WACRAO for their institution
- - allow the institution contact to approve/dis-approve the persons application. Ideally, this would be by replying to the email, but logging into the site and approving there would also be ok. As long as the workflow was simple and easy to understand.
- - have a limit on the number of people an institution can accept.

Any help appreciated!
Jim

Upperholme

  • Administrator
  • Ask me questions
  • *****
  • Posts: 568
  • Karma: 8
    • MC3
  • CiviCRM version: 4.x
  • CMS version: Drupal 6.x/7.x, Wordpress, Joomla
Re: Considering using CiviCRM, but want to be sure it will meet our needs.
January 28, 2014, 01:27:37 pm
CiviCRM can't deliver all of this functionality out of the box. Looking at your list of requirements I would say that it is unlikely that you will be able to find a solution off the shelf
If you were talking about using Drupal as your CMS then maybe your wishlist would be achievable by leveraging a number of contributed Drupal modules. And it's just possible that the same is true of Wordpress, which also has a wide range of plug-ins available. Good luck with it.
Graham Mitchell
http://mc3.coop

Erik Hommel

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1773
  • Karma: 59
    • EE-atWork
  • CiviCRM version: all sorts
  • CMS version: Drupal
  • MySQL version: Ubuntu's latest LTS version
  • PHP version: Ubuntu's latest LTS version
Re: Considering using CiviCRM, but want to be sure it will meet our needs.
January 28, 2014, 10:33:23 pm
Most of what you mention can be done with CiviCRM, but I agree with Upperholme that not all of your functionality can be delivered out of the box. And I agree that you will probably not find a solution off the shelf. My advice would be to contact a local CiviCRM expert and discuss what customization will be necessary. Alternative is to dive into the configuration yourself using the community resources and check if you can adapt your processes to what CiviCRM provides off the shelf. Good luck with your decision making!
Consultant/project manager at EEatWork and CiviCooP (http://www.civicoop.org/)

petednz

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4899
  • Karma: 193
    • Fuzion
  • CiviCRM version: 3.x - 4.x
  • CMS version: Drupal 6 and 7
Re: Considering using CiviCRM, but want to be sure it will meet our needs.
January 29, 2014, 11:21:26 am
I agree with Graham that I would be more confident of delivering the below with Drupal because of what the Webform-civicrm module allows. But more specifically

We are looking for a plugin or app that works with Wordpress that does the following:
- input institutions (universities and colleges in the Wisconsin/midwest area)
Do as Orgs in civi either directly or via Import

- add contact details for that institution, especially email address, but also name/address/phone/etc
Do via Relationships

- have a signup form where a person
- - can enter their logon details, and then select one of the institutions from the list above
via Membership form using 'on behalf of' and with a profile that requires 'user account creation' (if the latter is in WP)

- - allow the login details to be entered manually, and let the user select a username and password
see above, in drupal they enter username, get an email with one-time login where they can change password

- - allow the user to log in via social media (FB/Twitter/Linkin/etc)
not out of the box

- - not allow the person to log in till their application has been approved by the contact at the institution
in Drupal this can be done either by setting 'admin approval required' on the user login, or let them login, but not give the Authenticated Role any special permissions, instead have a Approved Member 'role' and set that to work off Civi Group (or Member) Synch module

- - automatically generate an email to the institution contact that someone had requested an account on WACRAO for their institution
In Webform yes, in Civi directly need a bit of magic to push the Orgs email in to the 'to' field of the 'receipt'

- - allow the institution contact to approve/dis-approve the persons application. Ideally, this would be by replying to the email, but logging into the site and approving there would also be ok. As long as the workflow was simple and easy to understand.
Getting trickier. In Drupal the main contact for the org would need to have some extra permissions either on Drupal or Civi side, eg for the latter would involve some ACL work based on Relationships

- - have a limit on the number of people an institution can accept.
Civi can do this for inherited memberships so that would be fine via webform - not sure how tricky this might be via another route.

HTH
Sign up to StackExchange and get free expert advice: https://civicrm.org/blogs/colemanw/get-exclusive-access-free-expert-help

pete davis : www.fuzion.co.nz : connect + campaign + communicate

Tadpole Collective

  • I’m new here
  • *
  • Posts: 27
  • Karma: 2
    • Tadpole Collective
  • CiviCRM version: Latest
  • CMS version: latest
Re: Considering using CiviCRM, but want to be sure it will meet our needs.
January 29, 2014, 01:25:31 pm
Hi Jim,

Like was noted before, much of what you mention can be done in CiviCRM. Not matter the CMS, you will be able to allow folks to create a username & password as long as user registration is enabled and the profile used during registration is set for account creation. So you will be able to let users get a username & password in WordPress too.

Social Media I'd manage that from the CMS to allow other login options.

The access piece, when using WordPress, at this point would likely revolved around WP user Roles & CiviCRM ACLs. We can use the member sync to work with this too. We would have to develop a plugin or templates to accomplish this. Something that would have to dig into get more detail.

Hope this helps.

Dana

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Pre-installation Questions (Moderator: Dave Greenberg) »
  • Considering using CiviCRM, but want to be sure it will meet our needs.

This forum was archived on 2017-11-26.