Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

Alexander_Prikhodko
Community profile Alexander_Prikhodko Level 2
Job title here
Location here
13 BADGES
Level 2

Level 2

Learn more
Joined the community 12-07-2017 12:31:05 AM
Offline
Top badges earned by Alexander_Prikhodko
Customize the badges you want to showcase on your profile
Re: Old JS and CSS served under new name after deployment
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi @kchaurasiya When the issue was reproduced, we also tried clearing CDN cache. It did help for new visitors, but the ones who visited the site during the issue had the wrong file cached in their browsers already. So I would like to find the root cause of this and prevent it in future.

Views

27

Likes

0

Replies

0
Re: Old JS and CSS served under new name after deployment
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi @fanindras So far we have observed it on Dispatchers and CDN. We haven't yet managed to reproduce it on Publisher on intent, but apparently it does happen there: since Dispatcher has JS with a new name cached, it means it requested it from Publisher after deployment, when Publisher had already generated the new name.

Views

38

Like

1

Replies

0
Re: Old JS and CSS served under new name after deployment
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi @Ritesh_M Yes, each time we deploy to Publisher, we also clear Dispatcher cache. We haven't yet managed to reproduce it on Publisher on intent, but apparently it does happen sometimes: since Dispatcher has JS with a new name cached, it means it requested it from Publisher after deployment, when Publisher had already generated the new name.

Views

39

Like

1

Replies

0
Re: Old JS and CSS served under new name after deployment
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi @asutosh_jena We deploy by installing a package that contains basically all parts of the app: components with their markup, styles and scripts, OSGi bundles, OSGi component configurations. We clear Dispatcher cache each time after this; the issue is (as far as I can see), when a visitor goes to that Dispatcher shortly after deployment, the request to JS with a new name goes through to Publisher, and Publisher responds with JS having old contents, and this wrong state is cached on Dispatcher. ...

Views

40

Like

1

Replies

1
Old JS and CSS served under new name after deployment
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
When a package with JS and CSS code is built and deployed, and then a page requested from the website, it contains links to JS and CSS files processed by AEM (with additional name parts and possibly minified), e.g.: Generally, when a new version of the package is installed, new JS and CSS file names are generated; and, when they are requested, the new code is served. However, from time to time we notice that, right after deployment, pages already contain links to files with new names but those links serve old code, which often breaks important functionality, as old code is invalid for the new markup. These invalid JS and CSS files are then cached in visitors' browsers, and even when Publishers start serving the new code, it does not help, as the scripts' names are the same and client browsers get them from cache. The only way to fix it is to deploy a new build so file names are updated. But this takes hours to arrange and perform, and all this time the site is partially broken. Looks like the issue is reproduced for only a short time after deployment: we have never managed to obtain the broken JS or CSS from a Publisher manually, but still, it was cached on Dispatchers, so some visitor managed to get it. What can be the cause of this behavior? Regards,Alexander

Views

87

Likes

0

Replies

9
Re: Publish later function
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi, Could someone please help with my question above (from 28-07-2021)? Regards,Alexander

Views

13

Likes

0

Replies

0
Re: How to use the AEM Asset Selector in a dialog?
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi @Arun_Patidar Do you know if this issue is tracked and/or planned to be fixed? Regards,Alexander

Views

192

Like

1

Replies

1
Re: How to exclude internal nodes from pathfield search
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi @kishorekumar14 , Thanks a lot, excludepaths solved the issue!

Views

36

Likes

0

Replies

0
How to exclude internal nodes from pathfield search
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi all, In one of our page type's properties, we have a pathfield with pickersrc="/mnt/overlay/granite/ui/content/coral/foundation/form/pathfield/picker.html" and root path set to a folder in DAM. The initial dialog is displayed without issues, but if you search for some keyword, the results contain some internal nodes of the assets, in addition to assets themselves: How to configure pathfield so that it only displays assets in search?

Views

69

Likes

0

Replies

2
Showing content newest to oldest by default
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi all, There are several places in Authoring UI where you see content listed oldest to newest by default, e.g. pages and assets in column view, or pathfiled dialog with /granite/ui/content/coral/foundation/form/pathfield/picker.html as source. Is there some configuration to reverse this behavior, so content is listed newest to oldest by default?I understand there is a workaround, at least for pages and assets navigation: to switch to list view. However, it means additional actions, and it can't...

Views

61

Likes

0

Replies

1
Provide Javascript API to retrieve single translations
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: There is an OOTB function CQ.I18n.getDictionary() to get translations, but it always gets the whole dictionary to the UI, which puts much load on the visitor's browser. This reuest is to provide a function that retrieves only the requested translations. E.g. it could accept key name(s) and language name as parameters. Use-case: Use localized strings in custom JS code on user-facing pages. Current/Experienced Behavior: Improved/Expected Behavior: Env...

Views

65

Like

1

Replies

1
Re: Publish later function
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi, I can see different behavior in AEM 6.5.8. Here is my scenario:edit the page, make change #1 to a text componentgo to Manage Publication, schedule publication for a later momentedit the page, make change #2 to the same componentwait until the scheduled momentAfter this, on Publish instance there is change #1 present but not change #2. So looks like Manage Publication publishes content that was there at the moment of scheduling. Is this the expected behavior?If yes, is there an out-of-the-box...

Views

26

Likes

0

Replies

0
Re: Enable page versioning from page editor UI
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hi @Arun_Patidar Yes, I thought of this too, but custom workflows require additional maintenance as workflow API may change version to version. So we try to minimize such changes if they are not specific to our website's functionality.

Views

140

Likes

0

Replies

0
Enable page versioning from page editor UI
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Request for Feature Enhancement (RFE) Summary: Enable page versioning from page editor UI Use-case: A content author is making changes to a page and would like to create a version with its current state before proceeding with editing Current/Experienced Behavior: One should go to Sites navigation UI, switch the left toolbar to Timeline, create the version and return to the editor Improved/Expected Behavior: It is possible to create the version without leaving the editor. I see two ways how it co...

Views

157

Likes

0

Replies

5
Re: Skip Assets from Asset Translation Job
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hello @Jörg_HohI can confirm the behavior described by ktm2308 about 2-letter folder names in AEM 6.5.8. Do you know if there are plans to change it?As for the initial request, do you know if it has been raised as a feature request and if there are any plans about it?Regards,Alexander Prikhodko

Views

88

Likes

0

Replies

0
Re: Managing translations in AEM by both content authors...
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
@Jörg_Hoh There are two cases when our content managers use Translator:Updating translations of labels in custom components (so we don't need a deployment to adjust a label to marketing needs)Updating translations that are used in the content of custom components (it's a custom-made feature: e.g. in our version of Text there can be references to translation keys). However it's a good point that it should be content translation, I am going to duscuss it with our content managers

Views

160

Like

1

Replies

1
Managing translations in AEM by both content authors and developers
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Manager
Hello all, We manage our company's website in AEM, and there are two teams on which I'd like to focus here: content managers and developers. Developers create new templates and components, and content managers use both developed and out-of-the-box components ti create and update pages. Both teams use localization strings via AEM Translator: content managers manage them in the production instance, developers on dev and test ones. To minimize issues in newly developed code, developers would like a...

Views

206

Likes

0

Replies

4
Re: Approaching: DTM Sunset Milestone 2
Avatar
Give Back 10
Level 2
Alexander_Prikhodko
Level 2

Likes

6 likes

Total Posts

18 posts

Correct reply

0 solutions
Top badges earned
Give Back 10
Boost 5
Boost 3
Give Back 5
Validate 1
View profile
Alexander_Prikhodko
- Adobe Experience Platform Data Collection
Hello We are migrating to Launch and will at some point need to deactivate our DTM rules and activate the ones in Launch. Do I understand it right that we won't be able to deactivate DTM rules after milestone 2? If yes:are any issues expected if Launch rules are active while similar DTM ones are not yet deactivated?are there any specific recommendations on migrating after milestone 2?

Views

3.5K

Likes

0

Replies

0
Likes from