The Blog that Noone Reads

Coralize for WordPress

This plugin is designed to automatically update parts of the site to use the Coral Content Distribution Network (coralcdn.org). This is not a feature complete release. Features that are not implemented are noted as such in the configuration panel. This is still a work in progress, so use at your own risk. Please check back soon for an updated version.

Download: Coralize for WordPress v0.8 beta

Installation

To install, simply unzip it and drop the coralize folder in your extensions directory. Then you can go into the Plugins admin panel and enable it. Once it’s enabled, you’ll have a Coralize sub-panel under Options. Simply enable the features you want.

Current Features

Coralize currenly features support for several methods of cache control:

Caching of links and images using the class=”coralize” propety in the link or image tag.
Caching all images on the site linked from the site’s domain.
Caching all images on the site linked from specified domains. (whitelisting)
Caching all images on the site linked from all but specified domains. (blacklisting)
Caching of feeds
Caching of enclosures in feeds (podcasts)
Caching of pages linked to from feeds
Slashdotting protection by caching the entire site when linked to from specified domains.
Panic Mode, which caches the whole site for all users.

Change Log

Checkout my Coralize blog category for a list of changes.

Planned Features

This is a list of features I’m working on implementing:

Caching of images, css files, and javascript files used in templates

Compatibility

As of v0.6, using gzip is not supported with the feed features. In future versions, this will probably not be an issue.
I just need to find a workaround for some problems.

As of v0.7, using the gzip feature is not supported, but will not break anything. The Coralize options page will let you know which features are not compatible with gzip and will automatically disable them.

As of v0.8, enabling panic mode will not break the site admin tool.

Discuss

Please discuss this plugin here.

Feedback

Send feedback to: grijalva@gmail.com

This entry was posted on Sunday, February 12th, 2006 at 4:55 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “Coralize for WordPress”

David Leon Says:
August 23rd, 2008 at 1:04 am
Thank you so much. Check out my blog, it is already there… You might not understand much, since it is in Uk

Coralize

I’m working on a plugin for WordPress to automatically use Coral Content Distribution for files and images on a wordpress site. This feature will be especially helpful to podcasters, which is why I’m working on it. Anyway, please use the comments form on this page to discuss this plugin. Feature suggestions are welcome.

View the full details here.

This entry was posted on Sunday, February 12th, 2006 at 4:32 pm and is filed under Coralize, Geek. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

10 Responses to “Coralize”

Azmeen Says:
February 13th, 2006 at 12:39 am
Just brainstorming here…

But isn’t the basic concept (not including the referral domain tracking widgets and gizmos) here as easy as appending .nyud.net:8090 to the Wordpress and/or Blog URI setting in the General Options admin area?

Personally, I’m too paranoid to try this myself
Dave Grijalva Says:
February 13th, 2006 at 12:43 am
Yeah, it sure is. And that’s basically what the plugin does. It’s basically an interface to allow you to quickly make site wide changes about what is cached.

For example, it can be set to automatically use the cache for users coming from killer sites like slashdot and digg. Also, there is a panic mode just incase you are in the middle of a slashdotting that will force the whole site to use the cache.

Also, I’m going to support podcast caching in the very near future that should help out many a podcaster with bandwidth cost issues.
Guest Says:
March 9th, 2006 at 11:26 am
You should use port 8080 now, not 8090
Dave Grijalva Says:
March 10th, 2006 at 6:51 pm
Next rev will probably use 8080 instead.
Jeremy Douglass Says:
June 22nd, 2006 at 9:56 am
Could you explain briefly how this compares with the Digg Defender plugin? In particular, does it modify .htaccess, and do you know whether / if it plays nicely with WP-Cache?
Dave Grijalva Says:
June 24th, 2006 at 11:18 pm
This is not an htaccess modification. This plugin works in a totally different way from Digg Defender. Specifically, it allows you to automatically coralize certain parts of the content without pushing the user to a static mirror.

It allows much more specific control of what and when to use caching. The actual Digg Defender feature, which my plugin calls “Slashdot proofing” is done at the PHP level, not the Apache level, so it should still work if you don’t have access to the .htaccess file.

There is a full breakdown of all the features at http://theblogthatnoonereads.tunasoft.com/coralize/. I haven’t tested it with WP-Cache, but much of the functionality should work just fine.
Stephen Says:
July 31st, 2006 at 5:23 am
I can’t seem to get this to coralize anything. I have it set to coralize images, external links, and a set of whitelisted images too — it does not seem to do anything to any of the sources or links. If I set the panic button then the site itself seems to be coralized but again the links etc. are not. Also, you can’t login to your site if you panic it, as there is no longer a real admin section. You have to go into PHPMyAdmin and fix things.
Stephen Says:
July 31st, 2006 at 5:32 am
I have just tried using the coralize class on an image;

[code][/code]

Still no dice.
HN Says:
August 29th, 2006 at 1:02 am
Works VERY well! I like this one a lot After I started to publish my own wallpaper images, my bandwidth bill skyrocketed, but thanks to this plugin it is once again manageable

I’m waiting for the next release with great interest

HNy
David Ryder Says:
April 10th, 2008 at 7:09 pm
Hello,

1st of all thanks for the cool plugin, and I’m happy to see you have regained control of your website from the haxors

I am trying to implement the coralize plugin on my website (although in all honesty the chances of me being slashdotted or dugg are remote), but I was hoping you could clarify one question:

In the slashdot proofing option should the entire url be used (http://www.slashdot.org) or should I just enter slashdot.org?

Thanks in advance for any help,
Dave Ryder