Link to images in content management deliveries in packages | Community
Skip to main content
N
nbisoft
Level 2
June 9, 2021
Solved

Link to images in content management deliveries in packages

  • June 9, 2021
  • 1 reply
  • 1113 views

Hi,

When we set up delivery templates using content management, we add images using links to xtk:fileres objects. But when transfering those delivery templates from an environment to another one, using packages, the links to those images are lost, probably because the ids are not the same in both environments. Because of that we have to redefine the links to images in the deliveries and it is time consuming when we have a lot of those.

 

How can I keep the link between deliveries and images (xtk:fileres objects) ? Has someone encountered this and been able to solve it?

 

Kind regards,

 

Nbe

 

EDIT: I found a solution. Forcing link to internal name instead of ID solve the issue and keep the link from an environment to another.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jonathon_wodnicki

Hi,

 

In the past I've just zipped up all the images from one env and unzipped them in the other.

Not sure if the software's improved since or if there was a better way.

 

Thanks,

-Jon

1 reply

Jonathon_wodnicki
Community Advisor
Jonathon_wodnickiCommunity AdvisorAccepted solution
Community Advisor
June 11, 2021

Hi,

 

In the past I've just zipped up all the images from one env and unzipped them in the other.

Not sure if the software's improved since or if there was a better way.

 

Thanks,

-Jon

N
nbisoftAuthor
Level 2
June 14, 2021

Hi @jonathon_wodnicki ,

Thanks for your answer. Sorry, I did not give enough details of my issue. Actually, my issues is the actual link to xtk:fileres table in the content delivery form,

 

 

there is an error like:

 

 

To solve the issue, we have to manually redefine the link in the form by choosing the right xtk:fileres object.

 

Thanks,

Nana

 

 

 

EDIT: I found a solution. Forcing link to internal name instead of ID solve the issue and keep the link from an environment to another.

 

Terms & ConditionsAccessibility statement

Loading footer...