Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now

Hot answers tagged

8

Might be easiest to update the database is_default field. Works for me on a 4.6 site: update civicrm_option_value set is_default=0 where option_group_id=26 and name='Scheduled'; update civicrm_option_value set is_default=1 where option_group_id=26 and name='Completed'; You may need to change the 26 but it's a stock option group. To confirm first can do: ...


6

CiviCRM PHP requirements recommends PHP5.5 or greater, and notes PHP5.3.10 is the bare minimum required. As well as this, you want to be sure your PHP version is actively getting security updates, and also consider what PHP versions CiviCRM is tested with. As of Feb 2016, I recommend PHP5.6 - Support ended for PHP5.3 in 2014, and for 5.4 in 2015. PHP 5.5 ...


6

CiviCRM is not warning you about a file named Array.php, the confusing error message is because it's rendering a PHP array to a text string. I've opened an issue in JIRA about this and submitted a suggested quick fix: CRM-17909: File 'Array' presents a security risk and should be deleted. It looks like the fix is as simple as adding [0] as shown in this ...


6

Line 435 in CRM/Export/BAO/Export.php that your error message is referring to says: if (!empty(self::defaultReturnProperty($exportMode))) { This will give an error in all PHP versions below 5.5. From the PHP manual (http://php.net/manual/en/function.empty.php): Prior to PHP 5.5, empty() only supports variables; anything else will result in a parse ...


6

There are multiple calls to CiviCRM.org in the site codebase, so it's not clear which are triggering errors on your site. These are some of the things you could do ... Disable Version Checking According to a comment in CRM-17637, from 4.7 it's possible to disable the daily Version Check scheduled task. See under the menu entry Administer > System Settings >...


6

The slowest part of upgrading on a large installation is usually the civicrm_mailing_event_* tables. That data is also often stale, so consider deleting it if you don't need to keep historical information about past civimailouts.


6

The performance improvements to move from 4.6 to 4.7 when you have a large installation is, in itself, worthwhile (we did it when we had about 500k contacts, we would have done it earlier if we'd known how much faster some things were). If you go for a big upgrade, I recommend you to move to php7 too. As for the features, this blogs list a few, but it's ...


6

This is a preference you can set, but it's not exposed in the web interface. There's a section of civicrm.settings.php that documents it. In case you've upgraded from an older version of CiviCRM that doesn't have it, I'm including it here: // Opt-out of announcements by the CiviCRM core team for releases, paid services, events, etc. Separate each ...


5

This does appear to be a legitimate issue, so I've created a bug in the tracker here: https://issues.civicrm.org/jira/browse/CRM-18079 Generally it's better not to use this folder for maintainability reasons - it is better to use an extension - but since it is an advertised piece of functionality, it should work as intended! Thanks for reporting this.


5

If you have CiviCRM 4.7 then from the top menu: Administer > Administration Console > System Status Your version number will be in the CiviCRM Up-to-Date section. [side note: the demo version of Wordpress CiviCRM does have the version number in the footer -- not sure why you're not seeing it.]


5

You can also check the version from the file: civicrm-version.php in the downloaded folder of civicrm. File path : civicrm/civicrm-version.php


5

This is a bug and will be updated in the next release. In the meantime, you can use this PR to fix. Further info on Jira.


5

Agree, it's probably time to remove it. Over on https://civicrm.org, it's handled like this: .crm-container #printer-friendly { display: none; }


5

We had some more luck with the integrated UI configuration of CKeditor, and after some trial and error we came up with the following solution: In the following documentation I will assume that the fonts, files and configurations will be put in /sites/default/files/civicrm/persist/ and /sites/default/files/civicrm/persist/customfonts. The persist folder can ...


5

There is a helpful explanation. The numbering system changed, this is detailed here 5.0.0 is the next version after 4.7.31 and is not a major update. In The Q&A section there is an answer to this question which explains why the limitations of the update messaging system in 4.7 led to the decision to use the End of Life message in this instance: ...


4

The JIRA Issue for this feature https://issues.civicrm.org/jira/browse/CRM-17795 reads This adds support for joins in api.get operations to fetch information from more than one table. It also adds ACL enforcement to the Contact and related (email, address, phone, etc) apis for get, create & delete actions. The JIRA issue links to a couple of ...


4

@jdax worked on this at the Maryland sprint, and she's done except for a tiny bug to fix that a test just found. I expect it'll be included soon. Alerts will have a link to the status page, and the bottom of each admin page will have the site's status as "System Status: OK", "System Status: Emergency", or something in between, with a link to the page. You'...


4

You posted this question almost exactly at the same time that a PR to merge in this feature was posted - see the last comment on the CRM-13823 issue. I was part of the team that worked on this during the Colorado sprint. The entity and APIs have been in place for months, and the 4.7 code all uses the new entity - but the status page, for the sake of easier ...


4

General tip: When I've had problems like this (a mysterious setting/value/datum), one other technique is to search the full database. There's no direct way to do that in MySQL, but you can dump the database to a file (mysqldump) and then search that. Specific tip: In the Civi database, check table civicrm_setting, e.g. select * from civicrm_setting where ...


4

You can use the buildForm hook on an activity to check if the activity belongs to a case (in which case case_id will not be empty I think) and then set the default status to Completed. There is an example here, although it sets different statuses for different types it basically does the same thing. Copy and change I would say :-): https://github.com/PUMNL/...


4

The case custom fields are formatted as a series of one row tables. You could add some jQuery to move them around. For example: CRM.$(function($) { $('#Outcomes table:nth-of-type(3n+1)').each(function (index) { // Combine 3 rows into 1 for (var i = 0; i <= 1; i++) { $(this).find('td:last').after($(this).next().find('td')); $(...


4

For the specific case of upgrading to 4.7, here's a useful tip from Dave Jenkins : https://issues.civicrm.org/jira/browse/CRM-18526#comment-106825 In short: upgrading to 4.7 involves multiple changes (4 or 5?) to foreign keys on two tables that are often very large. In order to do this, mysql makes copies of those tables for each change, which can take a ...


4

There was an issue due to some refactoring around the handling of date fields to try to standardise them. This lead to a problem most notably in birth date fields in 4.7.16 but i'm guessing can be found elsewhere. This issue was raised CRM-19982 I suspect the same fix will most likely work for you. If you have a test site or would like to give a test a ...


4

You can apply this PR - and reload System status page. This will let you know in advance which indices are already present in DB and would result in DB error on hitting Update Indices button. So what need to be done is - Apply this PR. Reload System status page. Some duplicate indices would be shown above Update Indices button including a message of what ...


4

I think there is confusion on release date. Version 4.7.31-2.3.0 was released on March 2018 not March 2017. I guess the maintainer forgot to update the year to 2018 in info.xml file. HTH Pradeep


3

I think you're asking a very UK-specific question about direct debit. UK has special rules for direct debit that CiviCRM doesn't know anything about. But the iATS Payments payment processor does support the required workflow and the civicrm extension for iATS Payments does have a dedicated payment processor for that purpose, so that might work for you. ...


3

If you have access to your DB you can look in the civicrm_domain table for field= version


3

Another way from the API (4.7 onward) is to use the System.check API: $result = civicrm_api3('System', 'check', array( 'name' => "checkVersion", )); to get something like Array ( [is_error] => 0 [version] => 3 [count] => 1 [id] => 5 [values] => Array ( [5] => Array ( ...


3

Exists an unresolved localization issue that probably explains your translation problems. You can see here: CRM-17737 New Mailer dialog seems impossible to translate


3

In Drupal under Configuration > Development > Logging and Errors ie admin/config/development/logging you can set Errors and warnings to be 'off' and it is normal to do so on the production site, while leaving them showing on the development version. The reason you don't see this on 'edit' but do on 'create' is, as you say, because Edit uses the overlay, but ...


Only top voted, non community-wiki answers of a minimum length are eligible