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

Disable JS minification only for Author

Avatar

Level 4

HI,

Is there way to disable minification only or Author but not for Publisher.

We installed SP7 and it has issue with component edit and the solution is to disable minification of JS. But we don't want to disable minification in publisher as it will impact performance.

 

The Apache Granite HTML Library Manager property is present in our config "htmllibmanager.minify". So I can not manually disable minification from OSGi as next build will overwrite it as we have it set as "true" in code. I do not see option to mark it as "false" only for author..How can we do that only for author..?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Mayukh007 , 

 

It is possible by overlaying the Apache Granite HTML Library config so that config will not be overridden by next deployment and also you can make config specific to author alone. 

So please follow the below steps. 

1.Overlay the config, Apache Granite HTML Library. 

2. Disable the minification flag

3. Add the config to config.author folder. For other environments author, add the config accordingly. So that minification disable will be applicable to author alone

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

Hi @Mayukh007 , 

 

It is possible by overlaying the Apache Granite HTML Library config so that config will not be overridden by next deployment and also you can make config specific to author alone. 

So please follow the below steps. 

1.Overlay the config, Apache Granite HTML Library. 

2. Disable the minification flag

3. Add the config to config.author folder. For other environments author, add the config accordingly. So that minification disable will be applicable to author alone

Avatar

Level 4
Hi Vaibhavi, although it worked in my local, but I dont see that updated in our Dev env....Do we need to restart any bundle to take it into effect

Avatar

Level 4
It seems some bundle restart was required which i did not require in my local. Restarting instance fixed the issue in Dev