Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Issue with pages appending "/" at the end

Avatar

Level 2

Hello,

We are seeing issue with our site for some pages. Welcome to Interflex  When you go to New and Events page from navigation, it opens the page appending   "/" at the end. After we clear the dispatcher cache, page loads fine for some time. Again, it starts appending "/". Is it considering it as a directory and appending that "/" ? What can be done to fix this issue. Will appreciate your response on this.

Thanks.

4 Replies

Avatar

Level 10

When you create your Nav component - are you not specifying the URL to open the page?

For example - look here at how we developed the Nav component. There should be no /appended:

Adobe Experience Manager Help | Creating your First Adobe Experience Manager 6.3 website

Avatar

Employee Advisor

sounds like an issue with the dispatcher cache; the most typical error case is that

/opt/cache/docroot/news-and-events

cannot be a directory and a file at the same time. This might cause issues. On the other hand side what kind of URLs are you creating? How do they look like?

Jörg

Avatar

Level 2

Yes, it is dispatcher cache issue but it comes up often.

There is a page new-and-envents.html that is what we are trying to access.

Regarding URL - we have - /content/interflex/en/news-and-events.html page created and we are trying to access this page from our website  - News and Events

This seems to load fine now. But it doesn't stay that way. It goes blank and it is because it appends  "/" at the end when you try to access this page url.

Avatar

Employee Advisor

Hi,

when this situation happens again, can you share these details:

  • What are the details of the dispatcher cache structure (that means, what directories and files do exist, plus the structure of them).
  • Webserver logs, dispatcher logs (preferable at loglevel debug), AEM request.logs for these requests

Jörg