Recent Posts

Pages: [1] 2 3 ... 10
Using CiviCampaign / Re: Disable Campaign button doesn't work
« Last post by ken on Today at 08:42:58 pm »
The Disable buttons on the Survey and Petition dashboards have the same issue.
Using CiviCampaign / Disable Campaign button doesn't work
« Last post by ken on Today at 07:40:36 pm »
This is reproducible on the Drupal demo for 4.5.

Clicking on the Disable button fails, when viewing a list of Campaigns on the Campaign dashboard.

The Javascript console contains messages like ...

TypeError: $row[0] is undefined
   ret.entity = $'entity') || $row[0].id.split('-')[0];

The line reference is jquery.crmeditable.js?nfivnx and line 13.

This Javascript appears to expect that the <TR> in which this button sits has a CLASS of "crm-entity" and an ID like "campaign-123". On the Campaign Dashboard the only CLASS is "even" or "odd" and the ID is "campaign_row_3".
Upgrading CiviCRM / Re: upgrade failure from 4.4.6 to 4.5.4
« Last post by ldgpangeo on Today at 05:29:13 pm »
I recollect disabling all extensions and other modules. 

I just retried it doing the following:
   1.  place drupal in maintenance mode
   2.  backup the dbs.
   3.  disable all civicrm-related extensions
           remainder is standard drupal
   4.  clear drupal and civicrm caches
   5.  install 4.5.4 code
   6.  Try to go to upgrade url.
             Problem reappears...  redirected to drupal home page
   7.  Clear files/civicrm/templates_c/en_US and  ConfigAndLog/Config.IDS.ini
   8.  Re-clear drupal cache
             Same problem... redirected to drupal home page
   9.  revert code back to 4.4.6
             Site behaves normally.

This is both bizarre and frustrating.   Suggestions anyone?
Using CiviCase / Re: Cant Save CiviCase Settings Screen
« Last post by pmoz on Today at 05:23:07 pm »
My error was due to the Case Coordinator role in the case type.
Once I deleted that role, case saved as expected.
Drupal Webform Integration / Re: Webform, views and case activities
« Last post by pmoz on Today at 03:50:10 pm »
That's funny, I was busy blurring while you wrote that!

Image is now attached of accordian with no styling.
Upgrading CiviCRM / Re: Problems upgrading to 4.5.3 (from 4.4.x)
« Last post by joanne on Today at 03:36:06 pm »
CiviCRM 4.5 is fairly new and point releases that fix (mostly edge-case) bugs have been coming out as often as every 2 weeks.  If you want the version of CiviCRM with the most features you should upgrade to 4.5.4.

CiviCRM 4.4 has been around for over 12 months now and is being maintained by the community as the LTS version.  The latest version is 4.4.10.  If you want to stick with the 4.4 series instead of moving to the 4.5 series you should upgrade to 4.4.10.

See for more information.
Drupal Webform Integration / Re: Webform, views and case activities
« Last post by petednz on Today at 02:16:54 pm »
might help others to add a screenshot or two of your accordians?
Drupal Webform Integration / Re: Webform, views and case activities
« Last post by pmoz on Today at 02:12:42 pm »
Thanks Pete.  The url tricks are pretty cool.

And even more clarity...

This view will list all clients assigned certain case(s) in an accordion view with Last Name as title.
Info in accordion can include:
•   Date case opened
•   Case status
•   Date case closed
•   And more…
Create new View of type CiviCRM Cases

Create a relationship to:  CiviCRM Case Contact: Case Contact's Contact ID

Add fields:
CiviCRM Contacts: Display Name (Display Name) (use relationship)
CiviCRM Contacts: Contact ID (use relationship)
CiviCRM Contacts: First Name (use relationship)
CiviCRM Contacts: Last Name (use relationship)
CiviCRM Cases: Case Status (Case Status)
CiviCRM Cases: Start Date (Case Opened)
CiviCRM Cases: End Date (Case Closed)
Global: Custom text

The last field, Custom text is where you rewrite the url to the url of your webform followed by ?cid2=[id_1].
In our case:
(node/9 is the webform we want to populate with the client's name, cid2 is the second contact on the webform, and [id_1] is the token for the clients unique id)

Filter however you want.
We filter by Case Type  and Display Name (we exposed both filters so users could change which cases they see).

I used bootstrap accordion but it can be any view.  It looks pretty cool in isotope, but more practical for our use in an accordion.
"It would be great if CiviCRM would enable custom fields for images that would either use Drupal's Image Styles"

I concur. Question will be who has time/resources to implement this. We 'can' do it, but don't have a client who would resource it, and it wouldn't be high up on our list of things we can improve in drupal/civi in our own time to be honest.
Pages: [1] 2 3 ... 10