You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: