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; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Adding an association

mizage

I have added a new aspect to ws:indexPage, which is an assocation. Everything works fine as long as it's a new index page, meaning that it was created after I altered the content model.
If I try to alter an older index page, I get the following warning (shouldn't it be an error?):

10:26:58,464 WARN [org.alfresco.repo.forms.processor.node.NodeFormProcessor] Ignoring field 'assoc_cis_groupedLinkList_removed' as an association definition can not be found
10:26:58,467 WARN [org.alfresco.repo.forms.processor.node.NodeFormProcessor] Ignoring field 'assoc_cis_groupedLinkList_added' as an association definition can not be found

<!—new aspects for ws:indexPage—>
<type name="ws:indexPage">
  <!–the rest hidden—>
   <mandatory-aspects>
       <aspect>cis:associatedGroupedLinks</aspect>
    </mandatory-aspects>
</type>
‍‍‍‍‍‍‍‍‍

<!–custom aspect—>
       <aspect name="cis:associatedGroupedLinks">
         <title>Associated Grouped Links</title>
         <associations>
            <association name="cis:groupedLinkList">
               <title>Associated Grouped Links</title>
               <source>
                  <mandatory>false</mandatory>
                  <many>true</many>
               </source>
               <target>
                  <class>cis:groupedLinks</class>
                  <mandatory>false</mandatory>
                  <many>true</many>
               </target>
            </association>
         </associations>
      </aspect>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Is there an issue in my aspect definition?

Find more posts tagged with

Comments

bremmington

No, this is just the form processor that's handling the edit form submission warning you that the node being edited doesn't appear to have this particular association defined.

mizage

My issue is that when I add an article to an existing node (via the newly created aspect) it doesn't save the association to the article. But with a new node (created after the model was altered)
it does save the association to the article. Sorry if I'm not being clear.

bremmington

How are you trying to add the association on the "old" node? If the aspect isn't applied to that node then you won't be able to add an association of that type. Does it work if you add the aspect to the old node before trying to add the association?

mizage

Sometimes it's easier to show!

Open a ws:indexPage (one created before the model was altered):

[img]http://www.acthiv.org/2010slides/indexOldMeta.png[/img]
[img]http://www.acthiv.org/2010slides/indexOldMeta2.png[/img]
[img]http://www.acthiv.org/2010slides/indexOldMeta3.png[/img]

Then after saving, re-open and the assocation has not been saved:

[img]http://www.acthiv.org/2010slides/indexOldMeta4.png[/img]

Now if I do the same with a ws:indexPage created after I altered the model, the association is saved. No problems.

bremmington

This is due to your revised form definition showing the "generic links" even though the node being edited doesn't have that association available (since it doesn't have your custom aspect on it). I suggest that you write a little webscript that finds all nodes of type ws:indexPage that don't have your custom aspect applied and adds your custom aspect to each one that doesn't already have it. You can then execute that webscript to fix up your content, and that will resolve this problem.