[MTOS-dev] attaching vs. embedding assets to entries patch

[Timothy Appnel]

On Fri, Mar 21, 2008 at 3:44 AM, Byrne Reese <byrne at sixapart.com> wrote:
>  Does it add a field to the UI?

No.

> Does it simply make
>  the necessary database schema changes to allow for these types of
>  associations?

Yes. More importantly it stops the entry/page object from deleting any
asset associations it doesn't find embedded in the text or text_more
fields.

>  What specifically does it do and how is the user's experience inside of the
>  app affected?

See above.

This patch was meant to be small (MTOS doesn't seem to ready to handle
big patches) and to only make it possible to effect the user
experience whether it be through plugin or changes to the core. I was
prepared to create some attachment functionality; however, the save
function in MT::Entry (that calls sync_assets the real culprit here)
made that impossible without hacking the core. With this change
hacking the core isn't necessary.

I'm trying to take baby steps with this one.

Make more sense now?

<tim/>

-- 
Timothy Appnel
Appnel Solutions
http://appnel.com/