rcotta

Geolocation personalization on CQ 5.6.1 - Adobe Experience Cloud 15-10-2015

Hi, all.I noticed some problems after putting the Geolocation store on a production website, and I am wondering if it's related to API usage limits, as the problem does not occur in QA environment.Do you have any experience using it in production sites? Am I supposed to use it in production at all? I couldn't find where to configure API keys or something like that on the Geolocation store.Any direction on this subject will be much appreciated.

214

Re: Geolocation personalization on CQ 5.6.1 - Adobe Experience Manager 15-10-2015

rcotta wrote... Hi, Sham. The region name (state) and city name is enough for our use case. So, just to confirm, this out of the box implementation is suitable for production websites, right? Regards, Most of customer I worked had additional requirements & ended implementing T&T/audiance aem integration or custom one. If the one comes oob sufficient you can use for production but make sure to take care of below things. * Test out especially at uk region if there is any restriction. * It exposes ...

486

Re: Vanity URLs x Dispatcher - Adobe Experience Manager 15-10-2015

Better late than never: 1. correct, if you need to support vanity urls that can be anything, you need to allow all and then deny specific paths, like so: /filter { # to start, deny all requests (we will not handle PUT DELETE TRACE OPTIONS CONNECT PATCH with dispatcher) /0001 { /type "deny" /glob "*" } # in general allow all GET HEAD POST requests (including vanity URLs) /0002 { /type "allow" /glob "GET *" } /0003 { /type "allow" /glob "HEAD *" } # enable features /0004 { /type "allow" /glob "POS...

682

Dispatcher x Vanity URL - Adobe Experience Manager 15-10-2015

[sorry if this post is duplicated, but I cannot find the one I posted earlier today]Hi all,On my scenario I have a few hundred pages, and each page have a vanity URL assigned without extension (eg.: native AEM path is /content/site/language-code/product-type/country/state/city/product-instance.html and vanity path URL is /city/product-instance or even /marketing-appealing-url).We have new pages being created and activated on a daily basis, and this information is relevant because I won't be able...

234

Re: Please suggest on how to cache extension less urls in cq5 dispatcher? - Adobe Experience Manager 15-10-2015

Hi, AnnamalaiI know this post it a little bit old, but I like to come back and add the solution whenever I find one I got it working with a configuration very similar to yours: DispatcherUseProcessedURL set to "1", and RewriteRule with he [PT] flag set.But two things still needs attention:My RewriteRule discards trailling slashes, because when the user access http://domain/path she is redirected to http://domain/path/ (I didn't identify who is doing this redirect, and I still didn't test it unde...

812

Re: How do I add a global javascript and css to a whole page that uses a predefined template in Adobe CQ5? - Adobe Experience Manager 15-10-2015

Hi,If the page component includes client libraries by category, you can create a new client library with the *same* category as an existing client library. You must have the source of the components. Aren't they just in JSP scripts in /apps/ ?Justin

423

Re: How to use information from JSONPStore on segments resolution - Adobe Experience Manager 15-10-2015

Yes -- the CQ_Analytics. is used in this use case. This code is shown in the doc:<%@page contentType="text/javascript;charset=utf-8" %><%%><%@include file="/libs/foundation/global.jsp"%><%log.info("***** initializing geolocstore ****");String store = "locstore";String jsonpurl = "http://api.wipmania.com/jsonp?callback=${callback}"; %>var locstore = CQ_Analytics.StoreRegistry.getStore("<%= store %>");if(!locstore){ locstore = CQ_Analytics.JSONPStore.registerNewInstance("<%= store %>", "<%= jsonpu...

262

Re: Vanity URLs with extension problem - Adobe Experience Manager 15-10-2015

Hi, Orotas and Jörg,I've been playing with the /etc/map before, with no luck.I'll try the hack proposed by Orotas, and report back in here if it works (or not) as soon as I finish it.Regards.

435

Re: Global component properties - Adobe Experience Manager 15-10-2015

Just a side note on Scott's reply, as I was having the very same question in here: the complete path is something like:instead of(note the slash on the beginning of path attribute).

327

Re: Referencing a content node from within a component - Adobe Experience Manager 15-10-2015

Just to document the steps needed to achieve the effect:1 - Create your custom component2 - Add a pathfield widget on the dialog, and name it "contentPath"3 - On the JSP a code like the one below: [Click "Edit" to select component] Thanks once again, Orotas.

538

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe