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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

daitienshi
Community profile daitienshi Level 2
Job title here
Location here
10 BADGES
Level 2

Level 2

Learn more
Joined the community 01-11-2016 8:48:43 AM
Offline
Top badges earned by daitienshi
Customize the badges you want to showcase on your profile
Changes in local publisher CRX not reflecting on the site
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi,I've noticed that changes to a jsp or css in my local publisher's CRX are not showing up on the site after saving. I'm viewing the pages directly against the publisher instance without a dispatcher.The only time the changes seem to be reflected is when I make changes in my IDE and I re-build and deploy the package to AEM. This makes it very cumbersome for minor tweaks to the page to have to re-build everything.I recently upgraded to 6.2 with the SP2 and CFP. It was all working prior to the SP...

Views

427

Likes

0

Replies

0
Re: Dispatcher mod_rewrite not working?
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Yep. Turns out because the site is using SSL, I had to put the rewrite rules in our ssl.conf file that contained the virtualhost entry for the secured site. Once that's in there, it worked.

Views

827

Likes

0

Replies

0
Re: Dispatcher mod_rewrite not working?
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Thanks. Yes, between switching the values, I've restarted apache. I'll open up a ticket with AEM support and provide all of the configurations there.

Views

778

Likes

0

Replies

0
Re: Dispatcher mod_rewrite not working?
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
I've actually set it to TRACE just but here's the log snippet for when the DispatcherDeclineRoot is set to 0:Here is the log snippet when I set the DispatcherDeclineRoot to 1:Thanks!

Views

782

Likes

0

Replies

0
Re: Dispatcher mod_rewrite not working?
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
I've set it to 0 so the publisher can return the right page back, but I'm still seeing an index.html being returned to the dispatcher and the publisher's request log doesn't seem to show the request for the page.When setting it to 1 and having those rewrite rules on, it doesn't seem to be working either as it comes back with index.html instead of the login.html

Views

780

Likes

0

Replies

0
Re: Dispatcher mod_rewrite not working?
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi,I did set that value to 1 and the dispatcher.log still says it's returning a 302 to /index.html. Is this supposed to let the root request pass through to the publisher? This way the publisher can return the redirected page as configured in the sling:redirect in the /content node?Thanks!

Views

786

Likes

0

Replies

0
Dispatcher mod_rewrite not working?
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Related to another post (AEM Dispatcher not resolving vanity urls),​ I've created some rewrite rules in my httpd.conf in my dispatcher so that when I hit my site's root (e.g. www.mysite.com/), it should rewrite/redirect to a page of my choosing (e.g. www.mysite.com/content/mysite/login.html).However, when I hit the root, I'm getting a response with a redirect (302) to /index.html instead, even though I've created a rewrite rule for this.In my httpd.conf, I have:Ideally, what I'd like is a combin...

Views

3.2K

Like

1

Replies

12
Re: AEM Dispatcher not resolving vanity urls
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
I believe this is now fixed. It turns out the documentation on the dispatch configuration (Configuring Dispatcher - docs.adobe.com ) has a typo in the first example configuration, where it lists the entry as "/vanity-urls". However, later on in the vanity urls section (https://docs.adobe.com/content/docs/en/dispatcher/disp-config.html#Enabling Access to Vanity URLs - /vanity_urls), it's listed as "/vanity_urls". The proper configuration is indeed with the underscore and not the hyphen (i.e. /van...

Views

1.1K

Likes

0

Replies

0
Re: AEM Dispatcher not resolving vanity urls
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Looking at the dispatcher log, I'm seeing that the vanity-urls entry in the dispatcher.any file is not being recognized.That would explain why it's not making the call to the publisher. Any reason you can think of as to why this warning is showing?

Views

1.1K

Likes

0

Replies

0
Re: AEM Dispatcher not resolving vanity urls
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
- I'm able to access the vanity urls if I bypass the dispatcher and go straight to the Publisher. I know it has something to do with the webserver config but just trying to see what it could be.- how would I switch off the mod_rewrite to do the quick test? Based on the dispatcher log, it seems like it's trying to go to my vanity url (/home) even after the filter, so it seems like it's checking the vanity urls file. However, like I said, the access.log on the publisher never shows the dispatcher ...

Views

1.1K

Likes

0

Replies

0
AEM Dispatcher not resolving vanity urls
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi there,I'm trying to set up our dispatcher to resolve the vanity urls we have set up in our publisher. However, after following the configuration guide, when I try to hit a vanity url, I'm getting a 404 error rather than the page itself.Here's a snippet from our dispatcher.any configuration:Here's what I see in the dispatcher.log when I try to hit my vanity url:It looks like it's trying to get to the /home vanity url after the filter rejects it, but nothing ever shows up. When I look at the ac...

Views

4.1K

Likes

0

Replies

5
Re: Configuration of JSESSIONID cookie set by CQSE
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi there,I'm in a similar situation as you with regards to configuring the cookie for all subdomains.Did you happen to find a solution to this?Thanks!

Views

710

Likes

0

Replies

0
How to configure AEM JSession cookie?
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi,I've noticed that there is a cookie that AEM puts on the browser for the JSessionID.Currently, the cookie includes the fully qualified name of the AEM host, but is there a way to configure it to only look at the main domain and not the subdomain?e.g. current: aem.serverhost.com. desired: *.serverhost.comThanks in advance!

Views

454

Likes

0

Replies

0
Re: Custom repsonse header set in JSP not set via Dispatcher
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Does this apply to both request and response headers?Feike Visser wrote... By default headers won't be cached by the dispatcher. You can configure this via the /headers section inside the cache configuration.

Views

909

Likes

0

Replies

0
Re: Custom repsonse header set in JSP not set via Dispatcher
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Thanks!However, we only need this custom response header on a particular page and it seems like overkill to have to enter all possible default headers and then this one custom one under /clientheaders. Also, my understanding is that the /clientheaders is for allowing which request headers to allow through, whereas I'm looking to get a custom response header through the dispatcher.Thoughts?Thanks again!

Views

916

Likes

0

Replies

0
Custom repsonse header set in JSP not set via Dispatcher
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
I am trying to set a custom response header in my jsp via:<% response.setHeader("my-custom-header", "custom-value"); %>When I access the page directly through the Publisher, I can see the header being set. However, when I hit the same page through the Dispatcher, the header is not there.I checked the dispatcher.any file and the /clientheaders property is set to "*" to let all headers through.Would any one know why the header is not present when accessing through the Dispatcher?Thanks!

Views

2.4K

Likes

0

Replies

8
Re: Granite jQuery csrf error
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
It seems to be appearing on all pages where the granite-utils libraries are included.

Views

904

Likes

0

Replies

0
Re: Granite jQuery csrf error
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Also, it seems because this is breaking, we are not able to use the Granite library to retrieve i18n values in javascript.

Views

904

Likes

0

Replies

0
Granite jQuery csrf error
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi,Our site in AEM (6.2) uses the bundled jQuery inside Granite.From what I see, the generated granite.js file consists of the csrf.js.Currently, when a page loads, it is throwing an error in the browser console of:Uncaught TypeError: Cannot read property 'externalize' of undefined(...) getToken @ csrf.js:103The line that it's referring to in the csrf.js is:xhr.open('GET', Granite.HTTP.externalize(TOKEN_SERVLET), true);I'm not sure what is causing this (and what it's supposed to be doing even) a...

Views

1.1K

Likes

0

Replies

3
Re: AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
It seems that the generated /etc/clientlibs/granite/jquery/granite.js includes code from granite.http.externalize.js, which contains this line of code that is erroring out.I'm not sure where that granity.http.externalize.js comes from as it doesn't seem to included in the default bundle when installing AEM from scratch.Is there a way to remove that file and force the granite.js to be generated without it?Thanks!

Views

3.6K

Likes

0

Replies

2
Re: AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi Ankur,I've noticed that there is an error in the browser console related to the granite.js:Uncaught TypeError: Cannot read property 'externalize' of undefined(...) getToken @ granite.js:176The granite.js it's referring to is the /etc/clientlibs/granite/jquery/granite.js. However, that doesn't seem to stop me from successfully calling the Granite.I18n.getDictionary() and getting an object back.Otherwise, my calls are very simple:Granite.I18n.setLocale("FR"); Granite.I18n.get("TEST-001");Maybe ...

Views

3.6K

Likes

0

Replies

4
Re: AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi Ankur,I've added the keys in the translator.html.In my JS, I use Granite.I18n.get("TEST-001"); using just I18n gives me an error of I18n not being defined?I've restarted both the org.apache.sling.i18n and com.day.cq.cq-i18n bundles.Refreshing the page with that code on their still only returns back the "TEST-001" value rather than the translated version.Of note, my translations keys are in a separate dictionary for my app (/apps/myApp/i18n) rather than the default /libs/wcm/core/i18n. Do I ne...

Views

3.6K

Likes

0

Replies

6
Re: AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi Ankur,The dictionaries do have the keys TEST-001, TEST-002, TEST-003 during runtime, as I can retrieve those values via JSP. I can even modify the values and see those changes come in via JSP after a page refresh

Views

5.9K

Likes

0

Replies

8
Re: AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi Joseph, How would I request the dictionary via AJAX? I can call Granite.I18n.getDictionary() and get an object back but I have no clue what this object is (have tried a bunch of the functions it has defined) but still can't get anything out of it.

Views

5.9K

Likes

0

Replies

0
Re: AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi Anton, Yes, I'm able to successfully use i18n using JSP, but we're looking to dynamically retrieve the string via javascript rather than preloading the string on page render.

Views

5.9K

Likes

0

Replies

11
Re: AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Hi Leandro,The relationship between String and EN is based on the translator library found in /libs/cq/i18n/translator.html.The String value is normally used as the lookup key in JSP or Sling and the EN is the actual translated value being returned if the locale is EN.Regardless, if I pass the "This is a Test1" string into the Granite.I18n.get() function, with the locale set to FR, I still get back "This is a Test1"

Views

5.9K

Likes

0

Replies

0
AEM i18n from Javascript (try 2)
Avatar
Ignite 5
Level 2
daitienshi
Level 2

Likes

2 likes

Total Posts

27 posts

Correct reply

1 solution
Top badges earned
Ignite 5
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
daitienshi
- Adobe Experience Manager
Apologies for the duplicate post. Seems like something in the original is breaking the page, so I'll try this again:I'm trying to dynamically retrieve a translated message using Javascript from my created dictionary in AEM's translator (/libs/cq/i18n/translator.html).We've got dictionary values set up like:String EN FR========================================================TEST-001 This is a Test1 FR:This is a Test1TEST-002 This is a Test2 FR:This is a Test2TEST-003 This is a Test3 FR:This is a ...

Views

8.6K

Like

1

Replies

18
Likes from