Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Html Client library Manager impl

Avatar

Level 4

We are facing one more issue in our publish environment.

We created runmodes for publish instance,  in one of my publish run modes my HTMLLibraryManagerImpl.config is coming as nt:file.

How we can give permanent solution for this.

 

Temporary fix : we copied from another publish instance.

1 Accepted Solution

Avatar

Correct answer by
Level 10

You might have saved from felix console directly & creates a config file. You can configuration has config or a node.  What is the issue with having as file?

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

You might have saved from felix console directly & creates a config file. You can configuration has config or a node.  What is the issue with having as file?

Avatar

Level 4

We created run modes for our environment.

When ever we are installing packages in all the environments run modes are working fine and nothing is coming as nt:file

Only in publish environment run modes, we can see HTMLLibraryManagerImpl.config  is coming as nt:file.

It's not coming as sling:OsgiConfig.