Hot answers tagged

13

LTS stands for Long Term Stable version. It is intended for use on more conservative sites that are more concerned with having a stable CiviCRM environment than with having access to the latest features in CiviCRM. You should decide which type of site yours is. The LTS version contains all fixes for security vulnerabilities that affect the software, and ...


7

4.6 will be the next LTS version. The switch from 4.4 to 4.6 will probably occur at the end of 2015, since the 4.6 branch will be quite stable by then.


7

We advise our customers to stay on the LTS versions of CiviCRM unless they have a functional need for the latest and greatest. This is in line with the detailed explanation that Joe Murray entered (thanks Joe).


6

For CiviCRM 4.6+ go to Administer menu > Customize Data and Screens > Date Preferences. From there, change the Start Offset of SearchDate. I found this answer in Member since date before 1995 and although it talks about Membership dates, it apparently applies to Relationship dates too.


6

The LTS as you know it is the last one! Eileen explained the details here: https://civicrm.org/blog/eileen/the-lts-going-forwards Essentially the idea is that through better release/QA/testing we can make the current 4.7 the Long Term Stable release. In combination with the fact that innovative ideas / new features are going to be housed in extensions.


6

Is it possible? - Probably, with a lot of time and skill. In most releases, there are changes to the database structure or table content determined by the files under CRM/Upgrade. To revert back to a previous version you could in principle work through all the updates between your current version and the one you want to go back to and reverse each change in ...


5

The current trend (although this may change in the future) is for even-numbered versions to get long term support (LTS) while odd numbered versions don't. If you are installing CiviCRM for the first time, I recommend always going with the latest version and not LTS. This is because there is a cost to upgrading, and starting off on a higher version # means ...


5

The process to get a bug fix included is to submit a Pull Request ("PR") to that branch on Github. This is documented in the civicrm wiki: How to Submit a Patch to a Version Branch Get yourself a GitHub account. Create an issue in JIRA (already done, CRM-13287). Create a fork of the appropriate branch of civicrm-core to your own account. At this point I'd ...


4

I would double check the civicrm.settings.php file to make sure the paths and URL are updated in there. For example: define( 'CIVICRM_UF_BASEURL' , 'http://foo.example.com/' ); While you are in there make sure the server paths look right: $civicrm_root = '/home/path_to_html/sites/all/modules/civicrm'; define( 'CIVICRM_TEMPLATE_COMPILEDIR', '/home/...


4

Any field (including custom fields) that accepts an option value will take either its machine name or it's id. The machine names for countries are their ISO codes, e.g. the code for 'United States' is 'US'. So you could do: civicrm_api3('Contact', 'create', array( 'custom_77' => 'US', )); which is equivalent to civicrm_api3('Contact', 'create', array(...


4

After looking Civi log it seems that problem is with civicrm_uf_group.frontend_title field. I would suggest you to do incremental upgrade i.e Upgrade CiviCRM to 4.6.x to 4.7.30 Upgrade CiviCRM to 4.7.31. On a separate note make sure you disable all the CiviCRM extension or wp plugin and also disable wp post or pages that have CiviCRM profile ...


4

I have discovered that the delete-this files are temporary files created by CiviCRM for the sole purpose of generating this error! This error is good, it means that these directories are not browseable, and they shouldn't be browseable. CiviCRM's CRM_Utils_Check_Security class does these checks in order to report what would-be security errors. It creates a ...


2

If you really - really - want to get to 4.6.x create a new instance and migrate your data from the 4.7.x to the 4.6.x as you would when coming from any other database/CRM;


2

https://github.com/civicrm/civicrm-core/compare/4.4.20...4.4.21 Nothing that looks security-sensitive to me. Are the three 2016 flaws also present in 4.4.20/4.4.21?


1

This seems to be related to an incorrect website join in the query. Is there any website field in your custom profile? If yes, you can try disabling/deleting it and check if you still find an issue. You can also raise a bug in JIRA with some info of replicating the same.


1

No it's not an issue with the iATS Payments Extension. I got this question - and have reproduced it using 4.7.7 and iATS Payments Extension [note the transaction IDs are identical]: But I also get this on the http://dmaster.demo.civicrm.org/civicrm/contribute?reset=1 [today May23 at 9:40MT] - again: note the transaction IDs are identical: I will file a ...


1

This was asked on IRC last week, see https://irc.civicrm.org/logs/%23civicrm.log.2016-02-04.txt : [09:16] <bails> Hi all, slight confusion here: Is 4.6.12 / 4.4.21 a security release? [09:18] <bails> I ask as https://civicrm.org/advisory says 4.6.11 but thast was released 2016-01-06 rather than yesterday and we didn't get any emails saying a ...


1

Chain API call would be an answer for this. Let's for example : $result = civicrm_api3('Country', 'get', array( 'sequential' => 1, 'name' => "India", 'api.Contact.create' => array( 'contact_id' => 202, 'custom_7' => "\$value.id"), )); So here we first fetching country on basis of its 'name' => "India" and providing your ...


1

At Cividesk we recommend going with the LTS. That may be because we help maintain the LTS ;). All security fixes are backported to the LTS and it tends to be more stable than the newest release. As @Coleman points out the newest release does get more stable over time so this is something to consider as well.


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