You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code automatically generated on containers is not working for dotAssets in dotCMS.
If you are creating a new container and use the Add Variable stuff we are generating a piece of code to display some of the field properties, but this work just for fileAssets, if you reference to a dotAsset this will not work as expected
Screen.Recording.2023-10-06.at.1.30.30.PM.mov
Steps to Reproduce
Login as admin
Create a new content type that includes an image field
Create a container
Add the Image image variable for that field
Add a new template that use the container
Create a new page that use the template
Publish a new content on that page
View the page on the front-end.
Acceptance Criteria
Tested on master // Docker // FF
dotCMS Version
The code automatically generated on containers for dotAssets should work correctly.
The dotAssets content should be displayed as expected on the front-end when viewing the page.
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
The text was updated successfully, but these errors were encountered:
bryanboza
changed the title
Auto-generated code on containers does not working for dotAssets
Containers: Auto-generated code on containers does not working for dotAssets
Oct 6, 2023
Parent Issue
Related to #26348
Problem Statement
The code automatically generated on containers is not working for dotAssets in dotCMS.
If you are creating a new container and use the
Add Variable
stuff we are generating a piece of code to display some of the field properties, but this work just forfileAssets
, if you reference to adotAsset
this will not work as expectedScreen.Recording.2023-10-06.at.1.30.30.PM.mov
Steps to Reproduce
Image image
variable for that fieldAcceptance Criteria
Tested on master // Docker // FF
dotCMS Version
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
The text was updated successfully, but these errors were encountered: