I am having an issue with updating a specific component's policy. I have updated it in code, but when I deploy the code, the changes are not there. I have a file /conf/project/settings/wcm/policies/.content.xml that includes all policies related to templates and components. Within it I have a custom...

This was caused by an issue with shared and global component properties.  Through debugging I figured out that the problem was some properties injected like this:@SharedValueMapValue(injectionStrategy = InjectionStrategy.OPTIONAL)private String str;They were always null on Portal B on the publish in...

I did not find the answers to be useful in solving my issue yet. I provided a couple follow ups to the replies but have not received a response. This is still open but i will be updating when I figure it out.

Hey Esteban, I have some more information that I just figured out. I am getting this error in the logs:12.06.2024 15:50:24.465 *INFO* [qtp2098876788-2488723] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credential...

Thank you for your reply. I have looked into these steps and the only issue that I have found was by putting more logs into the component and then deploying locally, because the issue is replicated on my local instance as well. I have an init function in the component code that has this line:String[...

Hello, I am having an issue with a custom component that is not rendering on the publish server but renders fine on the author server. Here are the different combinations that I have tried to get it to work.It always renders on the Author instance no matter what. We have different portals set up in ...

I just implemented LanguageManager for the same use case as @pradeepdubey82. getLanguageRoots() does not get the language copies, rather it gets the language roots in your site structure based on the provided page.  For the original example getLanguageRoots() on /content/test/en/pagea would return:/...

Yes this was the issue. I updated Guides on our publish instance and everything worked perfectly after that.

Yes all existing pages built before node flattening was turned on display correctly on publish. I found this in the logs though:10.11.2023 08:24:50.601 *ERROR* [10.2.38.14 [1699622690449] GET /content/ariel-portals/docs//en/documentation/engineering-references/all-members/er-57.html HTTP/1.1] org.ap...

I have turned on the node flattening feature in code with this config file: com.adobe.dxml.flattening.FlatteningConfigurationService.configprocess.label="DXML Flattening Configuration (A)"flattening.enabled=B"true" And my documents output and display correctly on my Author server, but when I publish...