CF Not getting attached For Translation | Community
Skip to main content
R
RG_AEM
Level 2
March 8, 2021
Solved

CF Not getting attached For Translation

  • March 8, 2021
  • 4 replies
  • 1623 views

I have a Custom Component with a path browser to the CF's . However when I send this component for Translation the content Fragment that is being referred does not attach to the project for Translation. I have defined the rules in the below in the config file but it does not seem to work. Any pointer on how this can be resolved.

<assetNode assetReferenceAttribute="component node property reference to CF " resourceType="path to custom component"/>
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 aanchal-sikka
  • Go to Tools > General > Translation Configuration
  • Go to references Tab
  • Configure component's resource type and property name referencing CF

 

The CF should now be picked up for translation

4 replies

ammbra
ammbra
March 8, 2021

Hello,

 

This looks similar to https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-4-translation-for-contentfragments-not-working

Please check that one out.

 

Hope it helps!

    R
    RG_AEMAuthor
    Level 2
    March 8, 2021
    Hi @ammbra, Hi , This seems be working when using the OOTB component but I have a custom component which has a path browser to CF's and this fragment does not get attached. The article mentions to you the resourceType of my custom Component but I don't have one defined since this is custom component and does not inherit OOTB CF through sling:resourceType
      A
      AkAgarwal
      March 8, 2021

      Hi @rg_aem ,


      Can you try by adding this translation rule in "/libs/cq/translation/translationrules/contextproperties.html?context=/content" so that it will unblock CFs for translation.

      Resource Type : core/wcm/components/contentfragment/v1/contentfragment
      Reference as : fragmentPath

      As per this article there are some translation rules which can be edited..

      "https://experienceleague.adobe.com/docs/experience-manager-learn/sites/content-fragments/content-fragments-translation-feature-video-use.html?lang=en#content-fragment-translation-use-cases"

      Please check if it helps!

      Regards,
      Ak$hit Agarwal


        R
        RG_AEMAuthor
        Level 2
        March 8, 2021

        Hi , @akagarwal  This seems be working when using the OOTB component but I have a custom component which has a path browser to CF's and this fragment does not get attached.

          aanchal-sikka
          Community Advisor
          aanchal-sikkaCommunity AdvisorAccepted solution
          Community Advisor
          December 5, 2023
          • Go to Tools > General > Translation Configuration
          • Go to references Tab
          • Configure component's resource type and property name referencing CF

           

          The CF should now be picked up for translation

          Aanchal Sikka
            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            December 11, 2023

            @rg_aem Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

            Kautuk Sahni
            Terms & ConditionsAccessibility statement

            Loading footer...