Wednesday 12 May 2010 8:52:11 am - 2 replies
I have "some" trouble or maybe misunderstanding concerning the objects relation attribute/datatype.
For a new project, the client wants to have all its assets (images, files, videos and audio files) stored in the "Media" section. That's fine.
In my article I have set up an attribute of kind "Image" for image insertion. Then according to the client needs I've decided to switch to objects relation attribute.
If the image is already available in the media section no problem (even if the way the contributor choose the image could be improved using some lightbox,jquery and so on, instead of "browsing" ...)
My problem is when the "asset object" does not exists yet in the "Media Section". In the attribute the user can decide to add "a new object". But the only things he can do is assign a name to this new object, publish or save his draft, and then go in the Media Section, find the new created object, and then send the image, set the caption, description and tags for it.
This process seems a bit awkward to me, so I can not even imagine the final contributor feeling with it. It would be nice if we could proceed the same way as we proceed in an ezXML field, where adding, choosing and inserting "media" is easier (with a "popup".
I just wanted to be sure I did not made something wrong on my configuration and that the process I described above is the "real" one for every new eZ installation (I currently started this new project with the 4.3 version), and wanted to share with you the best practice, template modifications that I can do, extension that could make this "user experience" more friendly concerning "media assets" linking and publishing.
Thanks a lot eZ Community.
You must be logged in to post messages in this topic!