Project:Coral Defender
Version:5.x-1.0
Component:Miscellaneous
Category:task
Priority:normal
Assigned:Andrew M Riley
Status:closed (fixed)

Issue Summary

any plan to make the Drupal 6 Port for this nice n simple module?

Comments

#1

can't wait it.. :(

#2

After the 1.1 release (which is now code complete) I'll be creating the 6.x dev branch and begin porting it over.

#3

Assigned to:Anonymous» Andrew M Riley

#4

Has there been any progress on a Drupal 6 branch? I'd love to use it on my site.

#5

Version:5.x-1.x-dev» 5.x-1.0

I converted about 80% of it today. I hope to have a 6.x-dev version checked in tonight (This will be based off the 5.x-1.0 branch not the 5.x-dev branch - I didn't like where the dev branch was going).

#6

Can't wait. Coral Defender is just what I'm looking for in a cdn module.

#7

Status:active» fixed

The dev version has been committed. The dev package will be be created sometime in the next 12 hours (d.o. does this it's self, I can't control it). The current code isn't the prettiest but it's working right now and over the next week I'll clean it up/test it for a full release.

#8

I see the dev version has made it's way thought the cvs. If you like I can start testing it and report back any issues I find.

#9

Hey Duncan,

I always welcome testers :) One thing I'm concerned about is the hook_init and how that's working in d5 vs d6 for cached pages (anon users). It looks like in D6 I'm going to have to use something like hook_boot to get around the problem.

#10

Try out today's release once it's built, I fixed an issue on cached pages that should help you out.

#11

Sure thing, as soon as it's built I'll get it right away and start trying it out. Yeah using hook_boot would be beneficial apposed to hook_init because I'd imagine that most people using this module would also be using either the core cache or boost in conjunction with it.

#12

Status:fixed» closed (fixed)
nobody click here