nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Image Referencing from Mediabin to the Component

kumardas

I am facing a problem, when i try to select an image (asset) from Mediabin through component Image Datum Type (By clicking on "Import from Mediabin" link), its downloading the image to local teamsite or livesite server. I dont want to download the image to my teamsite or livesite server. I just want to provide a reference url (reference to the image or asset) in the component. Is there any way to restrict to download the image into teamsite server ? I know there is a way to restrict but it is in the form api ( in DCT, using, immediate dialogue type. But how to apply the same thing for the component Image datum type ?

Thanks in advance for your help...

Find more posts tagged with

Comments

cliff1

I don't believe the ImageDatum has the same "deferred import" capability as is available in FormsPublisher. The immediate download solution was implemented because most usages depend on having the image available in TeamSite so that you can preview the page and deploy the image to runtime. To the best of my knowledge, you are the first to mention this desire for the image datum. I would be interested in knowing more about your use case so we can figure out if this is an isolated scenario or has broader implications. At what point do you plan to download the image rendition? If you don't plan to download, I'm not sure how the image datum applies?

As an aside, it turns out that most of the FormsPublisher customers use immediate instead of deferred because the time delay for download is more obvious to a user at selection time than at "generate/preview" time.

kumardas

Here is the use case...

We are having thousands of images in mediabin and we dont want every image to be downloaded to teamsite and again the same will be deployed to webserver.

If we do not follow the above scenario, the same image will be copied in 3 places like one is in mediabin, second in teamsite and third is in web server. why to maintain 3 copies of same images, instead having a single copy and refer from there itself (including for preview/publish). Even for preview also the image reference should work. can you please suggest us is there any way for this type of image referencing ?

Adam Stoller

Here is the use case...

We are having thousands of images in mediabin and we dont want every image to be downloaded to teamsite and again the same will be deployed to webserver.

If we do not follow the above scenario, the same image will be copied in 3 places like one is in mediabin, second in teamsite and third is in web server. why to maintain 3 copies of same images, instead having a single copy and refer from there itself (including for preview/publish). Even for preview also the image reference should work. can you please suggest us is there any way for this type of image referencing ?

I'm a little confused here:

want?