david at kineticode
Jul 31, 2009, 3:29 PM
Post #2 of 2
(1157 views)
Permalink
|
On Jul 30, 2009, at 4:54 PM, Adam Wilson wrote:
> 1. Create a media.
>
> 2. Click save and stay.
>
> 3. Check in and publish.
>
> 4. Go to the story; add container; click save and stay.
>
> 5. Add the media as a related media to that container; save and
> stay; preview.
At this point, did you save all the way out to your workspace? Or just
go directly to the media workflow?
> 6. Check out the same media.
>
> 7. Upload a different image under that same filename.
>
> 8. Click Save.
>
> 9. Go back to the story; add a second container; click save and stay.
>
> 10. Add the media as a related media to that container; save and
> stay; preview.
>
>
>
> 11. view source, you'll see something like the following:
>
>
>
> <!-- image /test.jpg (id 1677)
>
> version 1 (id 2323) -->
>
>
>
> <!-- image /test.jpg (id 1677)
>
> version 1 (id 2325) -->
>
>
>
>
> <!-- image <% $image->get_uri() %> (id <% $image->get_id() %>)
>
> version <% $image->get_version() %> (id <% $image-
> >get_version_id() %>) -->
>
> Is it intentional that related media are version specific?
No.
> If it is, is there a way to modify this behavior?
> If it is, is there a built-in function that can be
> called when an asset is published that will find all the stories
> related to older versions?
> Is there a way to update the related media to the most recent version?
If you log out and log back in, or if you save out of the story before
editing the media document and going back to the story, your session
will be expired. The next time you edit the story or preview it, it
will be removed from your session and you should then get 2325 for both.
Best,
David
|
