Hi donald,

Thanks for getting back so soon.

Ill think over the issues over the weekend and on Monday or Tuesday have
a word with our technical developer Darron about his thoughts about
approaches to the various issues.

Your comments will be useful in helping us figuring out where things are
at with civiCRM.

Once Ive chatted with Darron Ill get back in full.

So far we have modified the Drupal Ecommerce module to accept multiple
currencies and tie up with PayPal for payments OR deal with payments on
an account basis. also weve looked at having ACL on groups of products
in Ecommerce so we have public products and then products for specific
campaigns users.

PayPal pricing for consumers and merchant from a UK based org.

PayPal costs
http://3d.openmute.org/modules/mantis/file_download.php?file_id=635&type=bug

Ltr

Simon

Donald A. Lobo wrote:
> hey simon:
>
> thanx for sharing the review.
>
> a few comments and updates. We'd love to work with
> u'll and fill in the missing pieces.
>
> 1. Note that you can integrate any drupal module using
> the civicrm api. we have used this successfully with
> the mass mailer / volunteer / profile module in drupal
>
> 2. Customization: Custom Fields. We disallow deleting
> / changing some properties to ensure that we dont
> violate any FK constraints. Also we'll get into
> trouble if we change a string into a checkbox etc and
> not be able to convert data properly. This all is
> possible technically, and we'll address it in a more
> complete manner at some point. We do need to give
> users the ability to "delete" a record (and hence all
> associated values attached with it) in multiple place
> (custom fields, profile fields, groups etc). Not being
> allowed to change default fields is a bug. Can u
> please file an issue in our issue tracker :)
>
> 3. Export Data: 1.2 will have a more comprehensive
> export facility and give the user more flexibility in
> creating and storing both export and import maps.
> Users will be able to export both contact and custom
> data
>
> 4. You'll raise a few interesting points with regard
> to permissions. Some of them are bugs, and some are
> missing features/capabilities. We will address some of
> those issues in 1.2. More specifically:
>
> a. The "Edit Groups" permission is used to control if
> the user can edit/view groups. So u can control which
> users can delete / create groups
>
> b. the add new contact / view issue will be fixed in
> 1.2 by allowing users to add a contact to a group when
> creating a contact
>
> c. 'Past Members' view is a bug and should be fixed.
> Can u file another issue for this one too :)
>
> 5. Outputting contact information in a "mail merge"
> format has been a requested feature. Would be great if
> you'll could develop this module and ensure it works
> with both MSFT and OpenOffice
>
> 6. History: Tracking of users add/edit actions on DB
> tables is on our roadmap :)
>
> 7. Jasper Reports. This would be excellent, if you'll
> could spearhead the process of getting good reports
> from jasper and start the knowledge base with regard
> to this for the community. While CiviCRM will provide
> simple reports, we want to move all complex reporting
> to a more suitable open source solution, and Jasper
> has gotten pretty good reviews. Other packages to
> potentially consider are rlib and agata
>
> 8. Using contact info on site. You can accomplish this
> using CiviCRM Profile (similar to Drupal Profile
> Listings). You can check this at:
>
> http://demo.openngo.org/civicrm/drupal-php5/civicrm/profile?q=civicrm/profile&force=1&crmRowCount=100
>
> Documentation at:
>
> http://objectledge.org/confluence/display/CRM/Configure+CiviCRM+Profile
>
> 1.2 will also expose a listings search form and a way
> to create a contact without creating a user
>
> 9. Not being able to accept UK postcodes is a BUG. i
> assume these are alpha-numeric and we have a rule
> validation for it. Please file an issue and it will be
> fixed for 1.2 :)
>
> 10. For your e-commerce integration requirements, i
> suspect you will find the API very useful and make
> life much easier. The API is in decent shape in 1.1,
> we'll add and improve the api features in 1.2 (which
> also introduces a new SOAP interface to interact with
> the API)
>
> We would love to help you'll integrate, extend and
> make CiviCRM more powerful. It is incredibly feature
> rich right now, and we are looking for folks who'd
> like to improve the usability of the product. Another
> major missing feature is good end user documentation.
> We are at a point where this is becoming pretty core
> to the future success of the product. Anyone wanting
> to help out in this regard, please get in touch with
> me :)
>
> lobo
>
>
>
>
>
>
>