thank you @tomvocb3 .  I also encoutered the similar issue where the multifield having json array data was getting stored as simple non-json array on browser back and forth button.Your solution has fixed my issue as well. Original Saved Date was - "items": ["{\"label\":\"test1\"}","{\"label\":\"test...

I had also faced the similar issue. The way, I handled is by adding the validation="false" attribute to parentConfig node for the the next button and with that I was able to disable the validation done by the foundation.js<parentConfig jcr:primaryType="nt:unstructured" validation="false...

Thank you @vivekanand-mishra for the input. We have decided to keep the config in the codebase as we might be moving to cloud soon.As of now we are going to update only one property org.apache.felix.http.jetty.responseBufferSize for which we dont need encryption.

We have this configuration - Apache Felix Jetty Based Http Service and we need to make few updates to it. We think keeping this xml configuration in the codebase will be risky in terms of security point of view and  System Admin or DevOps should manually control the entries in this configuration.   ...

Thank you @Ganthimathi_R for the suggestion. We also thought about doing the rollout first but we were not sure if it will be the recommended way or we should handle it in different way.Your comment had added more weight on this approach. Thank you. This forum has always been very helpful in providi...

Looking for best adobe practices and recommendations.   1. We have pages in en-us with the live copies maintained in locales eg es-es.   2. We add a component in en-us and do the rollout which makes the component available in the live copy locale es-es with cq:LiveRelationship property.3. We submit ...

Thank you @edubey  It resolved my issue. I was not using the format and was forming the path as ${'item'$itemList.counter}

We also found the issues in the code where multiple loops where doing rollout several times.

Hi rush_pawan - We are not overriding any blueprints. All those blueprints are independent and separate and created for block of content/pages.We dont have custom implementation for creating the blueprint, but it seems we have so many blueprints as that is our need, rollout performance is getting af...

Moving the blueprints from /etc/blueprints to /apps/msm had no impact in the performance. I had deleted the /etc/blueprints folder after moving the blueprints.