Hello AEM Guru,

 

We have many versioning documents available but still have few queries.

 

I am new to AEM and have to implement  clientlibs versioning as with every deployment client libs are not getting updated in the normal browser even after flushing the dispatcher cache and CDN cache. Tried to implement as suggested by many.

Facing below few issues :

1. I am tried to implemnet this via crxde in local . if we want to do it via code how to do that . /apps/<project folder/config/rewriter/ - should a create an xml file and copy paste this code :

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:sling="<http://sling.apache.org/jcr/sling/1.0>" xmlns:jcr="<http://www.jcp.org/jcr/1.0>"

jcr:primaryType="sling:Folder"

contentTypes="[text/html]"

enabled="{Boolean}true"

generatorType="htmlparser"

order="{Long}1"

serializerType="htmlwriter"

transformerTypes="[linkchecker,versioned-clientlibs]"/>

This is required, as in our higher environment we don't have access to CRXDE console.  

 

#2 - In my local, i did the changes via  crxde and save all.  but still not seeing configuration in sling rewrite. even after restarting the instance.

  
Any help would be highly appreciated





 
 Solved!
 
 [Go to Solution.](/t5/adobe-experience-manager/aem-implementation-of-versioning-for-clientlibs-and-css/m-p/399346#M7116)
Did you had ACS common installed in your AEM.

<https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html>




[View solution in original post](/t5/adobe-experience-manager/aem-implementation-of-versioning-for-clientlibs-and-css/m-p/399346#M7116)
The documentation for [`ConfigurationManager.RefreshSection`](https://docs.microsoft.com/en-us/dotnet/api/system.configuration.configurationmanager.refreshsection?f1url=https%3A%2F%2Fmsdn.microsoft.com%2Fquery%2Fdev15.query%3FappId%3DDev15IDEF1%26l%3DEN-US%26k%3Dk(System.Configuration.ConfigurationManager.RefreshSection);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.6.2);k(DevLang-csharp)%26rd%3Dtrue&view=netframework-4.7.2) method does say (emphasis is mine):



> 
> Refreshes the named section **so the next time that it is retrieved** it will be re-read from disk.
> 
> 
> 


The problem is that EF6 caches the [`ConfigurationManager.ConnectionStrings`](https://docs.microsoft.com/en-us/dotnet/api/system.configuration.configurationmanager.connectionstrings?view=netframework-4.7.2) in an internal class static property, so it never gets refreshed.


Unfortunately there is no "official" way to refresh it. Following is a brute force hack using reflection, so use it on your own risk:



```
static readonly Type EF6AppConfigType = typeof(DbContext).Assembly.GetType("System.Data.Entity.Internal.AppConfig");

static readonly PropertyInfo EF6DefaultAppConfig = EF6AppConfigType.GetProperty("DefaultInstance", BindingFlags.Public | BindingFlags.Static);

static readonly FieldInfo EF6ConnectionStrings = EF6AppConfigType.GetField("_connectionStrings", BindingFlags.NonPublic | BindingFlags.Instance);

static void RefreshEF6ConnectionStrings()
{
    EF6ConnectionStrings.SetValue(
        EF6DefaultAppConfig.GetValue(null),
        ConfigurationManager.ConnectionStrings
    );
}

```

Just call it after saving the changes:



```
config.Save();
RefreshEF6ConnectionStrings();

``` Apparently you have a version of NodeJS that does not understand the new features of ES6+, update.  

Way to put on the server, NodeJS and VueCLI at least strange. hey [@edgar.mtz](/u/edgar.mtz),

currently [interpretation](https://support.zoom.us/hc/en-us/articles/360034919791-language-interpretation-in-meetings-and-webinars) is not available on the web sdk.

here is a list of the supported features:

[image]

[web - native sdks - zoom software development kit (zoom sdk)](https://marketplace.zoom.us/docs/sdk/native-sdks/web#browser-support)

zoom web sdk

the web sdk enables the development of video applications powered by zoom's core framewo… This is indeed something of a problem. It is always difficult to jump into a new and large code-base. You should concentrate on any available overview documentation (e.g., explaining how it works or is structured), tutorials (e.g., showing how to make mods), and reference documentation (e.g., class references).


If you need to really dig into the source code of the library / application, then you need to find a relevant starting point. This could be something that is similar to what you want to do or modify. When you find a decent starting point, just look it up and try to understand what it does and how it works, and work your way out from there, by looking up related code (e.g., that is called within that code you are looking at, etc.). The "find in files" is definitely a central tool when exploring a code-base because it gives you an instant snapshot of where certain things are used and declared. For example, if you want to modify the behavior of class A, then there is a good chance that you will want to look at all the places where class A is used so that you can assess if your modified version will work or if you need to modify other things.


There is no doubt that doing this is hard and takes a lot of patience. I've done this several times with different code bases (some small ( < 50,000 LOCs ), some big ( > 1,000,000 LOCs )), and it's always a tedious process, especially if documentation is lacking (which it very often is). we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: hi mike, thanks for bringing this to our attention, i can confirm that i’m aware of this issue and a fix is in progress. i expect the latest version to be available the debian/rpm repositories in the coming days.

one short term work around would be to download the .deb or .rpm file directly from th… hi [@staffan](/u/staffan) ,

sorry for not responding to this sooner.

i know that chromeos now has some support for linux applications. odrive has a linux version, but this isn’t something we’ve tested on chromeos yet.

[agent/cli (linux, macos, win)](https://docs.odrive.com/docs/odrive-sync-agent)

sync agent and cli overview the odrive sync agent provides advanced users with a flexible, scriptable interface to odrive’s progressive sync engine. use it to bring cloud access and sync to almost any environment. the odrive sync agent can be used... i seem to have fixed this by myself. i disabled probe on my .vcl and this seemed to fix the 503 issues. here is my .vcl for varnish incase anyone needs it(this might work for you)! :slight\_smile:

vcl 4.0;

backend default {

.host = "127.0.0.1";

.port = "81";

.connect\_timeout = 5s;

.… We identified a scenario where locking could occur, and released a fix in version 13.0.1. If anyone is experiencing this issue, please upgrade to 13.0.1. here is the fixed version: [[release] 1.1.2](https://forums.lindale.io/t/release-1-1-2/2011)