Recent Posts

Pages: [1] 2 3 ... 10
Using CiviCRM / Re: Blank CiviCRM - "unable to read resource" errors
« Last post by jsimonis on Today at 05:18:47 pm »
Ok, I've had our web host looking at it for a while now. At this point it appears memcache might be the culprit. As soon as turned that off, both sites loaded up. Now to keep watching them to make sure everything is ok.
Feature Requests and Suggestions / Re: Sort Name for Org Records
« Last post by Dave Greenberg on Today at 02:38:40 pm »
There's good documentation for getting started with CiviCRM hooks / extensions on the wiki. Start from here:
Feature Requests and Suggestions / Re: Relationship issues
« Last post by Eileen on Today at 02:07:05 pm »
do you mean one relationship type at a time?

Sometimes reports work well as searches
The code is publicly available (my github)- as in the CiviCRM integration part of it - but you need an Ominpay Android app to make this work - so people are better off contacting Lawrence as I don't think the app is openly available yet

hey ltgreen1:

thats cool to hear :) would be great if you can post detalls here and also share your code under an open source license as an extension. I suspect many in the community would benefit


Developer Discussion / Re: Queue Runner documentation?
« Last post by lolas on Today at 12:31:47 pm »

Thanks for links! I hadn't figured out all that stuff out yet because I probably won't get to try to use the Queue until next week. Perhaps I can write up a couple of notes on the wiki after I do.
Developer Discussion / Re: Queue Runner documentation?
« Last post by totten on Today at 12:26:14 pm »
There's an extension called "org.civicrm.demoqueue" which may be easier to read than the others:

You've probably figured this out already, but the main concepts are:
 * Task: A particular unit of work. (Note: The queue can store anything serializable, but if you want to use the QueueRunner, then the queue should store Task objects.)
 * Queue: The stored list of tasks. This usually stored in a SQL table (CRM_Queue_Queue_Sql).
 * QueueRunner: The worker which consumes the tasks iteratively, executing each. For CLI usage (like drush), one would call runAll() or runNext(). For the web UI, one would call $runner->runAllViaWeb(). runAllViaWeb is a terminal call - executing it will immediately trigger a redirect to the queue UI.

There's a little more documentation about the options accepted by QueueRunner in the docblocks:
we are in alpha on this now.  the model we are working with is a flat rate pricing for all card types in the united states.  please feel free to contact with questions
Using Profiles / Re: Can you create a smart group this way?
« Last post by petednz on Today at 11:54:02 am »
in the field, near the bottom, is an option to 'is this field searchable'

have you checked that?

you will see on the demo that the Participant Custom Fields show under EVENTS (not under Custom Fields) in Adv Search

Using CiviEvent / Re: Batch exporting participant's files
« Last post by kebap on Today at 11:47:09 am »
Hm, interesting, didn't think of the views way on drupal. And yes, using drupal. Will post again on the result
Pages: [1] 2 3 ... 10