Migration project error

Avatar

Avatar

yellar5366253

Avatar

yellar5366253

yellar5366253

16-10-2018

@@@Hi All ,

I'm going to migrate my project  from aem 6.2 to aem 6.4 issue is  i'm not able to edit the component in edit mode , i'm getting below error in browser console

Forbidden

Cannot serve request to /mnt/overlay/wcm/core/content/editor/_jcr_content/content/items/content/content/items/styleselector.form.html/content/lgs/us/legal/index/test01/_jcr_content/par/*/ in org.apache.sling.servlets.get.DefaultGetServlet

0 TIMER_START{Request Processing}

  0 COMMENT timer_end format is {<elapsed microseconds>,<timer name>} <optional message>

  3 LOG Method=GET, PathInfo=null

  3 TIMER_START{handleSecurity}

  942 TIMER_END{938,handleSecurity} authenticator org.apache.sling.auth.core.impl.SlingAuthenticator@43fed61c returns true

  1183 TIMER_START{ResourceResolution}

  1259 TIMER_END{70,ResourceResolution} URI=/mnt/overlay/wcm/core/content/editor/_jcr_content/content/items/content/content/items/styleselector.form.html/content/lgs/us/legal/index/test01/_jcr_content/par/*/ resolves to Resource=StarResource, type=sling:syntheticStarResource, path=/mnt/overlay/wcm/core/content/editor/jcr:content/content/items/content/content/items/styleselector.form.html/content/lgs/us/legal/index/test01/jcr:content/par/*

  1267 LOG Resource Path Info: SlingRequestPathInfo: path='/mnt/overlay/wcm/core/content/editor/jcr:content/content/items/content/content/items/styleselector.form.html/content/lgs/us/legal/index/test01/jcr:content/par/*', selectorString='null', extension='null', suffix='/'

  1267 TIMER_START{ServletResolution}

  1269 TIMER_START{resolveServlet(/mnt/overlay/wcm/core/content/editor/jcr:content/content/items/content/content/items/styleselector.form.html/content/lgs/us/legal/index/test01/jcr:content/par/*)}

  1443 TIMER_END{166,resolveServlet(/mnt/overlay/wcm/core/content/editor/jcr:content/content/items/content/content/items/styleselector.form.html/content/lgs/us/legal/index/test01/jcr:content/par/*)} Using servlet org.apache.sling.servlets.get.DefaultGetServlet

  1445 TIMER_END{176,ServletResolution} URI=/mnt/overlay/wcm/core/content/editor/_jcr_content/content/items/content/content/items/styleselector.form.html/content/lgs/us/legal/index/test01/_jcr_content/par/*/ handled by Servlet=org.apache.sling.servlets.get.DefaultGetServlet

  1452 LOG Applying Requestfilters

PuzanovsP

Could you please help me.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

910

Correct Answer

1.0K
Jörg_Hoh
Employee

17-10-2018

Please redo this test and then lookup the request in the "Recent Requests" overview (/system/console/requests); it gives you this information and much more.

From the above messages it's not clear to what is not found. The resource itself is accessible (otherwise you should see early that the path is resolved to a NonExistingResource); so I assume that this message is rather caused by some rendering scripts not being present, which can also result in a 404. But the above mentioned view should be able to give you that information. Please also have a look in the logfiles.

Jörg

Answers (6)

Answers (6)

Avatar

Avatar

yellar5366253

Avatar

yellar5366253

yellar5366253

17-10-2018

i logged as an admin. admin having the full permissions right.

Avatar

Avatar

dgordon86

Employee

Avatar

dgordon86

Employee

dgordon86
Employee

16-10-2018

Are you moving from the Classic UI to Touch UI in addition to moving from AEM 6.2 - 6.4? Do you see the Editor Drop zones?

I'm curious if you see additional information in the error log or anything else in the browser console. The error you posted, unfortunately, is quite common and can be seen when selecting an empty drop zone even in We.Retail...

Upgrading to AEM 6.4 and  Upgrading Code and Customizations provide some good high level information on upgrading to AEM 6.4.

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

1.0K

Correct Answer

831
Arun_Patidar
MVP

16-10-2018

Hi,

did you login as admin? Just wanted to check here if this is due to insufficient permissions.

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

16-10-2018

Best practice to build an AEM 6.4 site is to follow the same approach as is discussed in the WNDK tutorial here - Getting Started with AEM Sites - WKND Tutorial

Build your project from the ground up instead of trying to rip parts from an AEM 6.2 project and replace. Upgrade your dependencies to UBER 6.4 JAR, use the latest granite/coral, etc.

Avatar

Avatar

yellar5366253

Avatar

yellar5366253

yellar5366253

16-10-2018

Yea we  did same thing . We removed the awm 6.2 related deprecated apis in  project code replaced with aem 6.4 related apis and also  i removed apps/cq/authoring/core/xlientlibs/editor/js/ editor.js file because side rail and my components are not  visible in touch ui pages  thats the reason I removed editor.js file . Aftrr i removed editor.je file my components and side rail visible .But issue is if I add or edit the components but I'm unable to do. If I opened the already existing pages I'm unable to get errors in my log or browser console ...

Please suggest me how to do ..

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

16-10-2018

Please provide more details. Did you just package up your AEM 6.2 code and try and deploy the package on 6.4 and expect that to work? When components are not editable - means there are errors.