emfield

Oh emfield, why do you need information I already have?

In my previous post I spoke about caching issues. Still a valid discussion, but it got me to thinking. For an emfield image provider why would there need to be any calls to the provider api other then when initially creating a node or perhaps when updating the emfield field in a node?

Just a couple of updates here...

Turns out new emfield providers are being created as separate modules so you can check out mine here.

On another note I've had additional thoughts about caching and emfield providers. Something seems amiss to me so planning to dig in a bit more.

Oh yes, and I'll be adding a video provider for smugmug. Smugmug has pretty nice video support!

So I finally did it - made a real contribution to Drupal. It isn't live yet, but I think it is RTBC (Ready To Be Committed). In this case it was a new provider for emfield image allowing users to embed smugmug images into their pages similarly to the existing providers such as Flickr, Photobucket, etc.

Some easy, Some hard...

So was it hard? Well, like all coding some was easy, but there are always gotchas.