metaweblogapi newMediaobject

Posted by: Samiuela LV Taufa on August 28, 2006 5:53:54 PM

Oooops, the function already exists, and has been for a long time.

bTonga fails, refuses to use it, because (at least up till 0.7.0.2) bTonga expects that mt.supportedMethods actually exists (and will return newmediaobject as one of the supported method apis)

Now that I look at it, this is a pretty stupid assumption since supportedMethods is a MoveableType API whereas newMediaObject is a MetaweblogAPI.

Why use newmediaobject ? Security ?

One advantage of the Xaraya implementation of the newmediaobject method is that the file is stored "off the grid." The image is not directly available through a standard file URL. The file, as is in my nomoa.com configuration, stored outside the webserver document path and accessed through a module call.

This feature has some security benefits for multi-user sites. Unfortunately, everything gets dumped into a single directory and can get real messy if you have a lot of images being published through this methd.

Seems as good a time as any to 'fix' that problem with bTonga and in clearing it up fixed a few other niggly/little problems that were hiding away for the right moment to bite you.

I've progressed somewhat with Photo inclusions with the blog, previously setting up FTP, and now using Gallery Remote, but I guess it doesn't hurt to go all the way and use newmediaobject. The advantage of Gallery Remote (although it was a two step process) is that it allows the files to be centrally located (i.e. administered through the Gallery2 module.)

Now, to reinstall Visual C# Express before the next round of Vista Alpha/Betas wipes the machine again,

Nomoa.com

Modules

metaweblogapi newMediaobject

Why use newmediaobject ? Security ?