Support for Drupal 5.5

If you patch 5.3 by hand and reroll the patches and upload them to this issue it will speed the process of getting a stable advcache release for 5.3. Otherwise you are somewhat tied to my schedule (in lieu of another volunteer) and I won't be able to get to it before next week. Thanks for helping!

If there would be a Drupal 5.2 -> 5.3 patch, then module updates like this one would become trivial:
1) apply advcache patch on D5.2
2) apply 5.2 -> 5.3 patch
3) generate new patch for advcache

Maybe something worth considering?

Thanks, keep them coming.

Here's all the patches for 5.3. All but block applied with a little fuzz. These apply cleanly to 5.3 and Drupal still works after applying them, other than that, not a lot of testing.

Yeah, looking back at the revision for the changes in block.module between 5.2 and 5.3 it appears that they were important.

The block patch in my previous post reverted the changes to that query to the version in 5.2, if anyone applied that patch they should reverse it out from the root directory of your Drupal install with patch -p0 -R < /path/to/block_cache.patch

Here are updated patches that use the updated query from 5.3 (only block_cache.patch and all_patches.patch) changed, but posting all for completeness. Again, they apply cleanly, and Drupal seems to work afterwards, but use at your own risk.

Tom, all of your patches worked for me. This is my first time using this module, but I'll report back if anything seems to not be working.

Ok, I encoutered a problem today. I don't know if it is a problem with Tom's 5.3 patch or a bug in general. Regarding the comment caching, I noticed that for nodes that don't have any comments, cache_set is called *every* time the node page is loaded, even though no comments exist and a cache record already exists anyways.

I'm not sure it makes sense to cache an empty value, or if so, we probably shouldn't be caching some value that's the same as what we retrieved from the cache, even if that value is empty.

this is a minor bug, unrelated to the 5.3 patches. it also existed in 5.2. imo it's pretty harmless.

@ilmaestro: if you haven't already, could you please file a separate issue for the comment cache patch? Good catch!
@tomchuck: Thanks *very* much for the patches. Sorry I haven't had time to review them. Your help is appreciated.

@firebus feel free to commit these when you deem them ready.

The 5.3 patches apply with some offsets to 5.4 and 5.5. Attached are patches that apply cleanly against 5.5. I haven't had a chance to test these at all, but will in the next day or two.

i just committed this to the dev branch, so a new tarball should be available once the cron runs.

it tests out fine for me, but i'd like to get confirmation from at least one other person before i create a new release for this.

thanks for your work on this, tomchuk!

Right now I'm only using the path patch but I can report that it's working for me an a D5.5 installation with 1000+ nodes. Thanks for all of your work, guys.

setting to fixed. i'll roll a new release once i've tested sufficiently.

opened http://drupal.org/node/208941 for this (new :) issue.

don't worry about reposting the patches there.

i'll have time to review and hopefully commit this weekend.

thank you!!!