kevingtan

Thanks for your advice, it's really helpful. I am actually doing mostly as you are advising. It's impossible to copy and paste as I am looking deeper into the two different versions.

285

Re: Upgrading from AEM 6.0 to 6.5 - Adobe Experience Manager

Do we have to follow Adobe's Archtype13 structure, or just keep the old if considering the easy way at the first step? Moving to new structure invites a lot of challenges such as package names, dependencies. But I am afraid keeping the old structure will not be compatible with 6.5.

475

Re: Upgrading from AEM 6.0 to 6.5 - Adobe Experience Manager

Thank you! Yes, we are considering moving to CoralUI. Another challenge is we need to change all jsp, jstl to htl also.

592

Re: Upgrading from AEM 6.0 to 6.5 - Adobe Experience Manager

Thanks for your advice, it's really helpful

480

Upgrading from AEM 6.0 to 6.5 - Adobe Experience Manager

Hi all, Wish everyone to stay well during this difficult time.We are considering to upgrade from 6.0 with sp3 to 6.5. I read through this article and it doesn't look like we need to run the repo conversion jar. The most difficult thing is the code migration. The structure is very different and it seems we need to rewrite a lot. For instance, the old project has two directories, "bundle" and "content". There are 5 now, which means that we have to handpick all the components, models, beans, servle...

756

Re: Creating AEM 6.4 Project Using Archetype 13 - Adobe Experience Manager

I built the bundle successfully anyway. Probably the Eclipse is not configured to import the appropriate packages. This happened to my 6.0 also.

769

Creating AEM 6.4 Project Using Archetype 13 - Adobe Experience Manager

Hi All,We've been building AEM 6.0 bundles using the old archetype and it looks like a lot of changes moving to AEM 6.4. I followed all the instructions as described in this page: Creating an Adobe Experience Manager 6.4 Project using Adobe Maven Archetype 13 Here's what I've done:- I created a settings.xml file under my .m2- Upgraded my maven to 3.6.2, as I encountered a failed message complaining about my maven 3.2.5- Created a project using the Archetype 13, answered all the prompts in the te...

830

Re: New features/method not executed after deployed - Adobe Experience Manager

It's installing the jar file, but not loading the updated one. I tried a few times to upload it from the package manager and installed it on different servers, all other servers are the same. I barely remember if it was working without restarting the server, seems that it changed to the current behavior a few months ago.

3.5K

Re: New features/method not executed after deployed - Adobe Experience Manager

Yes, tried multiple times, but it doesn't help.

3.5K

New features/method not executed after deployed - Adobe Experience Manager

Hi All,I figured that my bundle is not executing new features after the manual maven installation. So I tried a log trace code as:log.trace("start my new features");Then I ran maven as:mvn -Pinstall -Pinstall-publish clean installThe code basically installs the bundle on both author and publisher instances. But when I looked at the log, the line is not logged. I looked at the package installer and figured everything is correct, service is running fine from /system/console. So every time I have t...

3.6K

Re: JCR query datetime issue - Adobe Experience Manager

Hi Shashi123,First of all, the property "datestamps" is not a jcr property, but a customized one, we do not need to have a leading "jcr:" in our case. "datestamps" is a string array holding all dates for the same event. As in our example, there could be an event lasting for a few months. This is a problem to construct a meaningful query because the oldest date is always used when the order is in descending. By the way, "desc" doesn't work in our case. We are running 6.0, Jackrabbit Oak 1.0.22.

2.2K

JCR query datetime issue - Adobe Experience Manager

Hi All, Has anyone dealt with timestamp ordering issue with multiple timestamps?For instance, we have the following query:/jcr:root/content/my-site//element(*,cq:PageContent)[@sling:resourceType='event-page' and (@datestamps >= '2018-05-01')] order by @datestamps descendingSupposed we have a few results returned and some of them have multiple entries for datestampsevent1 [2018-08-01],event2 [2018-02-01, 2018-07-01, 2018-12-01] (repeating event)event3[2018-06-01]...the results will be in the orde...

2.3K

AEM 6.3 Upgrade Path - Adobe Experience Manager

Hi All,We are considering upgrading AEM 6.0 to AEM 6.3. With quite limited knowledge on this, can anyone suggest what would be the best solution for us?The following is what we have now:AEM 6.0 with SP1, SP2 and SP3Java 8 (1.8.0_201-b09)CRX: Apache Jackrabbit Oak 1.0.22Classis UIFrontend: Extjs, JSP60 templates and customized components, all in html and jspWhat we expect:AEM 6.3Content migration with minimal work, such as without modifying templates and components code. Retain classic UIRetain E...

575

Re: Deactivate assets - Adobe Experience Manager

Well, I think we figured we should implement the way as you are suggesting. Thanks a lot for your help. In regards to your question, it means that without the "On Received" checked, the cached version of the asset is always there regardless of what you do on the Author, even if you deactivate the asset and upload/activate a modified version of the asset. But this won't happen to the HTML pages.

2.6K

Re: Deactivate assets - Adobe Experience Manager

Also, we set this up probably we have a firewall rule that only the Publisher can communicate with the Dispatcher.

2.6K

Re: Deactivate assets - Adobe Experience Manager

Thanks for your explanation. The serialization type of the agent is "Dispatcher Flush". These are the settings for "Settings" and "Extended" tabs. So your suggestion is that we should set this up in Author instead of Publisher?Thanks again!

2.6K

Re: Deactivate assets - Adobe Experience Manager

"Web" is the dispatcher. We do not have the setup as you laid out. We have the following setups:Author: Agents on author: Author-to-publisher Agents on publisher: No active agentsPublisher: Agents on author: No active agents Agents on publisher: Publisher-to-dispatcherThe attached image is the "Publisher-to-dispatcher" on the publisher. Yes, we don't have any flush agent on either server.

2.6K

Deactivate assets - Adobe Experience Manager

Hi All,We are running AEM 6.0. We only set up Author-to-Pub and Pub-to-Web agents, but there is no invalidate flush agent. The current setups are not good for assets such as images and PDF's. The problem is that whenever an asset is deactivated or modified, we cannot see the asset having the correspondent action, either deleted or updated. I figured that we are checking the "On Receive" option on the "Triggers" tab, see attached. I like to have that option checked, but concern about the subseque...

2.8K

Re: Activate Page new feature - Adobe Experience Manager

Is the process com.day.cq.wcm.workflow.process.ActivatePageProcess the default process? I disabled the process, but the page activation is still working.

614

Re: Activate Page new feature - Adobe Experience Manager

Yes, looks like there isn't a perfect solution for this. But the workflow one seems to be the closest one. Workflows don't solve everything, just to reduce as many manual processes as possible. Thanks for both your help!Kevin

609

Re: Activate Page new feature - Adobe Experience Manager

That's correct.

575

Re: Activate Page new feature - Adobe Experience Manager

The question is would the message of "Page successfully activated" still come up? If yes, it will cause some confusion to the editors.

588

Re: Activate Page new feature - Adobe Experience Manager

Thank you! I will try that.

589

Activate Page new feature - Adobe Experience Manager

We are trying to implement some new features on the "Activate Page" function. Currently AEM has its own, but we like to add some validation when users click on that button, both the admin listing page(such as right click on a page) and the page detail with the sidekick. Web editors sometimes activate a page without opening up the "Page Property", whereby they should fill out some required fields. But they can bypass it simply click on the "Activate Page" button. We like to enforce them to fill o...

2.0K

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences