Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching CONTENT_API_DRAFT in Enonic XP across layers ? #180

Open
pfrang opened this issue May 2, 2023 · 0 comments
Open

Caching CONTENT_API_DRAFT in Enonic XP across layers ? #180

pfrang opened this issue May 2, 2023 · 0 comments

Comments

@pfrang
Copy link

pfrang commented May 2, 2023

When spinning up 2 instances of our nextJS Application, where the second instance is running on a different port and have some different env variables like CONTENT_API_DRAFT, basePath and defaultLocale in order to correctly distinguish the servers across languages, everything seems to be working fine, apart from the getUrl() links in CS. It seems to be cached to whichever first layer I access first in CS.

I.e, if I go to the norwegian layer first, the CONTENT_API url is always norwegian, even if I swap to the english layer, which is pointing to a different port and has no norwegian CONTENT API setting in it at all, the getUrl function seems to still generate the paths to the norwegian layer content type, and the opposite if I visit an english content type first after spinning up XP server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant