Install

Works with Drupal: 7.x

Using Composer to manage Drupal site dependencies

Downloads

Download tar.gz 39.41 KB
MD5: 697fd86e6ee81447fbfa096310edbcee
SHA-1: 0b4520ca4830a03232b1040e97a894e83b5b579e
SHA-256: 0ce7b8ea8116d20743a447b745a5efed052ba7451fbcbbf9493dfb6fa4c1f054
Download zip 56.63 KB
MD5: 1f3f758dc06bab9876bbc6b9836ae176
SHA-1: 1e482ee48581155a484881b469650c33780e5a80
SHA-256: 0ecab95c35b16bb9423da15bbb6a8192d654d56820beda681580b7f2093bb3c1

Release notes

There are two objectives with this early release:
1) Make a release to check and confirm that an incident like the one that happened to the release of 7.x-1.5, see issue #1562070, does not happen again.
2) Make an official, albeit unstable, release for testing and confirming the upgrade transition process from 7.x-1.x to 7.x-2.x.

For those who want to test the transition process, you must do the following:
- Be prepared to have to upgrade modules that depend on cf to their development versions in case they had to have some sort of compatibility adjustment. It is not known if this is required or not, thus the "unstable" status.
- Make sure to be using the 1.x series version of at least cf-7.x-1.6.
- Enable the following transition modules:
- CF 1.x Compatibility
- CF Database Options
- CF Settings
- After enabling said modules, replace the cf-7.x-1.6 with this unstable release (cf-7.x-2.0-unstable1).
- Run the drupal update.php script.
- FYI: during my tests, I ran into 1 issue where some of the updates failed to apply. It turns out that some sort of order of operations bug happens and some of the modules may update in the wrong order. I simply ran update.php a second time and the remaining updates managed to apply fine.

Created by: thekevinday
Created on: 10 May 2012 at 13:22 UTC
Last updated: 6 Nov 2013 at 22:20 UTC
New features
Unsupported

Other releases