


preethamk694748
preethamk694748
16-10-2018
Hi Julio, even we are getting same error 403 forbidden if I click on parsys.( After migrating to 6.4)
Can you please let me know if you have found any fix for it.
It will be helpful
Julio_Baixauli
Julio_Baixauli
16-10-2018
Hi preethamk69474858.
My issues were related with some overlays of original CQ 5.6.1 components, in /libs/foundation/components/*. With foundation/components/page, exactly. These overlays didn't work with newest versions of AEM 6.4.
Once deleted these overlays, we started to be able to edit the components as usual.
Hope this helps.
Kind regards,
Julio.
ankitrana
ankitrana
07-03-2019
Hi,
Did you found any working solution ? i am also facing same issue.
ionut_p
ionut_p
13-03-2019
Hello,
Any news about 403 (Forbidden) when we click in the parsys 'Drag components here' container ?
I checked on a clean AEM 6.4 instance on bellow projects and the problem still persists.
http://localhost:4502/editor.html/content/we-retail/us/en.html
http://localhost:4502/editor.html/content/wknd/en/sports/la-skateparks.html
Kindly ask if someone can provide a solution / workaround for this issue.
Thank you,
Ionut
Arun_Patidar
MVP
Arun_Patidar
MVP
13-03-2019
Can you try to add 'Edit' option from cq:editConfig
Jörg_Hoh
Employee
Jörg_Hoh
Employee
13-03-2019
I downloaded the mentioned zip file and installed it also on my local AEM 6.4 instance, and I am able to add new components to the page and also open the component dialogs. I am using Touch UI.
Jörg
ionut_p
ionut_p
15-03-2019
Thank you for reply @Arun Patidar, but seems that it's not working, maybe I'm missing something. There is an working example where we will not get 403 when we click on 'Drag component here' for one of those 2 projects ?
thank you
sukumard5750513
sukumard5750513
08-04-2019
Hi,
I am facing same issue, did you get any chance to get some solution around this issue ?
Jörg_Hoh
Employee
Jörg_Hoh
Employee
08-04-2019
The biggest change to the resourcetype foundation/components/page from 5.6.1 (and probably up to 6.2) compared to 6.4 is the fact, that foundation/components/page does have a ResourceSuperType configured in 6.4. You might check if this somehow affects your components.
bilala23933647
bilala23933647
25-09-2019
Did we get any solution for the issue? Please share if you have found any, cause I'm also facing such issue upon clicking on the parsys:
I'm using AEM6.4.4 and we upgraded from 6.1.
Many thanks in advance.