Issue with Site Navigation

[sonalik83665772]

Hello,

I have a simple navigation with some menu items and submenus.

On click of any of the navigation items ,it should redirect to the corresponding page.

However,our requirement is not to render the entire page each time,but only the main content area should change.The header,footer and navigation should not be rendered eachtime.

I tried redirecting it to the paragraph node on click example  /content/appname/pagename/jcr:content/par but this gives an error at the webserver - 

Forbidden

Cannot serve request to /content/appname/pagename/jcr:content/par on this server

Is there any setting that I am missing or is there any other way to achieve this.

[Opkar_Gill]

sonalik83665772 wrote...

Hello,

I have a simple navigation with some menu items and submenus.

On click of any of the navigation items ,it should redirect to the corresponding page.

However,our requirement is not to render the entire page each time,but only the main content area should change.The header,footer and navigation should not be rendered eachtime.

Hi,

What is the reason for this requirement? Is the main content areas dynamic and will it change with every call? If not and it is static, then the whole page can be cached in Dispatcher.

Regards

[Pawan-Gupta · Accepted solution]

Hello,

Request to JCR:Node directly with rendering type would not be allowed from HTTP, you should make request via defining the rendering type you are looking for, for example .html, json or xml so if you call /content/appname/pagename/jcr:content/par.html or /content/appname/pagename/jcr:content/par.xml will work for you.

Now to answer your first question. What you are looking for is basically intra portlet communication (search in google to know more in details) which is possible in portal environment OOTB whereas in content management system like CQ it will be lot of work (just to refresh particular part for content on page via firing some event on page). So in content management system it is still a good idea to request same page again and based on request refresh the content you are looking for and ofcourse it would not create any performance issue, if it is ok to do it as per your requirement. Else use bind event at client side scripting (it very much possible if you using 6.0 because it has sigtly to support that)

Let me know if you have more question.

Thanks,

Pawan

[sonalik83665772]

Thanks for the response on this folks! It was of a great help today.

Basically the way the front-end html code is developed is that they are using URL routing in angular and have created partial htmls for the main content area (which maybe static/dynamic) and on click of something in navigation,it would only change the main content area.

In AEM,I was hoping to get a simple solution like provide a URL in href in navigation which would redirect to only that main content area of the page hence giving the parsys path(which is for my main content area content)  did work, but does give an issue in loading within the required div classes but opens without any styles on a separate page.

As of now I gave the entire html page path within href and it does work for to the end user it does not look like its loading the entire page again but this is just a work-around :) and hopefully won't give any much of performance issues.Any other suggestions are welcome.