Content properties not visible on publish | Community
Skip to main content
M
mguerriero
March 4, 2025
Solved

Content properties not visible on publish

  • March 4, 2025
  • 3 replies
  • 616 views

Hi all,

I'm adding a new block to my EDS project, I edited the component-definition.json file for new component definition, the component-models.json for model and the component-filters.json file to enable the component to be added under sections. I'm currently working on a branch detached from main branch and I'm using the "ref" query param to refer to this branch in the Universal Editor. I committed the code on my branch and I can see it in the available blocks that I can add under sections. I can add the component and configure the two text properties (1 richtext and 1 text) of the defined model and I can see them with their values in the editor preview without problems, but when I publish the content in Preview and in Publish and I access the link https://<branch>--<repo>--<owner>.aem.page I see the page and the component wrapper but I cannot see the properties values, I see only an empty <div></div> inside the component wrapper. What could be the cause of this issue?

 

I attached two screenshot, the first is the component in the editor and the second is the component on the publish.

 

Thank's in advice.

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 c-piosecny

Hi,

being able to use model definitions for a new block created in a feature branch might still be guarded by a feature flag (early access).
The approach that works 100% is also still reflected in the documentation

Adobe recommends that you develop blocks in a three-phased approach:

  1. Create the definition and model for the block, review it, and bring it to production. (this is the main branch)
  2. Create content with the new block.
  3. Implement the decoration and styles for the new block.


You can you check the /bin/franklin.delivery/<your-gh-org>/<your-gh-repo>/main/<shortened path>.html endpoint on your author to see the html which would be ingested into the content bus.

3 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
April 8, 2025

@shaileshbassi @gkalyan @ganthira1 Would appreciate it if you could check out this question and share any insights you might have!

Kautuk Sahni
c-piosecny
c-piosecnyAccepted solution
Level 2
April 8, 2025

Hi,

being able to use model definitions for a new block created in a feature branch might still be guarded by a feature flag (early access).
The approach that works 100% is also still reflected in the documentation

Adobe recommends that you develop blocks in a three-phased approach:

  1. Create the definition and model for the block, review it, and bring it to production. (this is the main branch)
  2. Create content with the new block.
  3. Implement the decoration and styles for the new block.


You can you check the /bin/franklin.delivery/<your-gh-org>/<your-gh-repo>/main/<shortened path>.html endpoint on your author to see the html which would be ingested into the content bus.

    ShaileshBassi
    Community Advisor
    ShaileshBassiCommunity Advisor
    Community Advisor
    May 9, 2025

    Hi @mguerriero 

     

    I tried it out by adding the ?ref=<branch-name> and I am getting the option to author the changes done for the authoring, otherwise you can do it via the alternate approach

     

    There are HELIX5 configurations by which you can bind your environments with the respective branches and the content bus.

    For that you can use the lower environments in which you can push the changes as suggested by @c-piosecny  and then once everything is verified you can take it to the higher environments and make the necessary authoring over there. PFA for the place from which HELIX5 configurations could be created.

    Once the build is deployed, the sequence of the authoring matters so you should always add the additional fields at the last, otherwise the previous commits UI could be distored for the component you are making additional changes.

     

    Hope this helps!

    Thanks

      Terms & ConditionsAccessibility statement

      Loading footer...