wimleers · November 30, 2010 21:39
diff --git a/gistfile1.txt b/gistfile1.txt
 I was (finally!) creating the final release for one my modules (the CDN module). I had typed quite a bit in the release notes field. So I wanted to verify that those release notes looked ok, by clicking the Preview button. Unfortunately, that's where things went wrong.

 It seems Drupal.org created a *completely* messed up project release node: no version number in the node title (just 'cdn'), no version number in the file name (just 'cdn-.tar.gz'), linked to the correct CVS tag (which I can also not select again when creating a new project release), with a (seemingly) valid tarball, but no release notes. See it for yourself at http://drupal.org/node/985576.

 Screenshots attached (fortunately, Google Chrome has an excellent backward cache, which included the form in its full glory).

 So:
 1) could you please delete that messed up project release node or edit it to have version number 2.0 and the following release notes:
 <code>
 The goal for 2.0 is simple: make the CDN module kick ass. This will be done in three ways:
 <ol>
 <li>✓ significant expansion of functionality</li>
 <li>✓ awesome UI</li>
 <li>✓ excellent documentation, including high-quality screencasts</li>
 </ol>

 (Screencasts are yet to be made.)

 <strong>Upgrade notes</strong>
 (Can also be found in UPGRADE.txt.)

 Upgrading from CDN integration 1.x to 2.x requires applying a new core patch. Alternatively, there is now a new type of CDN integration that does not require a core patch, instead it relies on the theme layer to alter file URLs. It is slower and won't be able to alter *all* file URLs, but it is easier to use. When the module detects that the patch is not applied, it will automatically fall back to this mechanism.
 Also note that the core patch is already included in Pressflow!

 The recommended steps to update your Drupal site are:
 1) Copy the 1.x core patch (patches/drupal6.patch) to the Drupal root directory.
 2) Revert the 1.x core patch:
 <code>
 patch -p0 -R < drupal6.patch
 </code>
 3) Disable CDN integration at admin/settings/cdn.
 4) Update the CDN integration module code.
 5) Copy the 2.x core patch (patches/drupal6.patch) to the Drupal root directory.
 6) Apply the 2.x core patch:
 <code>
 patch -p0 < drupal6.patch
 </code>
 7) Re-enable CDN integration at admin/settings/cdn.

 The ImageCache module patch has remained unchanged since version 1.x. When you did not apply the core patch and thus want to rely on the theme layer fallback mechanism, you don't have to apply the ImageCache module patch either.
 But when you update to an ImageCache version that's newer than 2.0 beta 10, you will have to apply the alternative patch: patches/imagecache_6--2.patch.

 (Additional note for those who are running a 2.x-dev release, a beta or an RC of version 2.0: the Drupal core patch has last changed in 2.0 beta 6 (<em>not</em> in this final 2.0 version)! So, before updating, revert the patch of 2.0 beta 3 (or from 2.0 beta 2, if you're upgrading from 2.0 beta 2). Then update the code. Then apply the new patch.)</code>

 2) Could you maybe fix that bug, or temporarily disable the "Preview" button? If this was a random fluke, then I'm very sorry for being the single stupid person to trigger it.
	I was (finally!) creating the final release for one my modules (the CDN module). I had typed quite a bit in the release notes field. So I wanted to verify that those release notes looked ok, by clicking the Preview button. Unfortunately, that's where things went wrong.

	It seems Drupal.org created a completely messed up project release node: no version number in the node title (just 'cdn'), no version number in the file name (just 'cdn-.tar.gz'), linked to the correct CVS tag (which I can also not select again when creating a new project release), with a (seemingly) valid tarball, but no release notes. See it for yourself at http://drupal.org/node/985576.

	Screenshots attached (fortunately, Google Chrome has an excellent backward cache, which included the form in its full glory).

	So:
	1) could you please delete that messed up project release node or edit it to have version number 2.0 and the following release notes:
	<code>
	The goal for 2.0 is simple: make the CDN module kick ass. This will be done in three ways:
	<ol>
	<li>✓ significant expansion of functionality</li>
	<li>✓ awesome UI</li>
	<li>✓ excellent documentation, including high-quality screencasts</li>
	</ol>

	(Screencasts are yet to be made.)

	<strong>Upgrade notes</strong>
	(Can also be found in UPGRADE.txt.)

	Upgrading from CDN integration 1.x to 2.x requires applying a new core patch. Alternatively, there is now a new type of CDN integration that does not require a core patch, instead it relies on the theme layer to alter file URLs. It is slower and won't be able to alter all file URLs, but it is easier to use. When the module detects that the patch is not applied, it will automatically fall back to this mechanism.
	Also note that the core patch is already included in Pressflow!

	The recommended steps to update your Drupal site are:
	1) Copy the 1.x core patch (patches/drupal6.patch) to the Drupal root directory.
	2) Revert the 1.x core patch:
	<code>
	patch -p0 -R < drupal6.patch
	</code>
	3) Disable CDN integration at admin/settings/cdn.
	4) Update the CDN integration module code.
	5) Copy the 2.x core patch (patches/drupal6.patch) to the Drupal root directory.
	6) Apply the 2.x core patch:
	<code>
	patch -p0 < drupal6.patch
	</code>
	7) Re-enable CDN integration at admin/settings/cdn.

	The ImageCache module patch has remained unchanged since version 1.x. When you did not apply the core patch and thus want to rely on the theme layer fallback mechanism, you don't have to apply the ImageCache module patch either.
	But when you update to an ImageCache version that's newer than 2.0 beta 10, you will have to apply the alternative patch: patches/imagecache_6--2.patch.

	(Additional note for those who are running a 2.x-dev release, a beta or an RC of version 2.0: the Drupal core patch has last changed in 2.0 beta 6 (<em>not</em> in this final 2.0 version)! So, before updating, revert the patch of 2.0 beta 3 (or from 2.0 beta 2, if you're upgrading from 2.0 beta 2). Then update the code. Then apply the new patch.)</code>

	2) Could you maybe fix that bug, or temporarily disable the "Preview" button? If this was a random fluke, then I'm very sorry for being the single stupid person to trigger it.