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
Hi, I'm using the presentation editor and it seems I have a use case that is not yet supported.
My project has both languages and markets. https://<market>.domain.com/<language>/pathname
The languages work fine as they are simple path prefixes. But the markets being subdomains is what causes issues.
When inside the editor and navigating to a specific subdomain, I get many obscure errors that don't provide much relevant context.
I do know it's not a DNS or CORS issue.
Describe the solution you'd like
I think the solution would be to add some more options in the presentationTool() plugin. Perhaps a allowedSubdomains array?
If subdomains are defined, there could be a dropdown in the editor to select them.
Describe alternatives you've considered
I have considered implementing alternate logic to pull market data via URL query params, but that's a bit too hacky to my taste.
Additional context
The text was updated successfully, but these errors were encountered:
Hi, I'm using the presentation editor and it seems I have a use case that is not yet supported.
My project has both languages and markets.
https://<market>.domain.com/<language>/pathname
The languages work fine as they are simple path prefixes. But the markets being subdomains is what causes issues.
When inside the editor and navigating to a specific subdomain, I get many obscure errors that don't provide much relevant context.
I do know it's not a DNS or CORS issue.
Describe the solution you'd like
I think the solution would be to add some more options in the
presentationTool()
plugin. Perhaps aallowedSubdomains
array?If subdomains are defined, there could be a dropdown in the editor to select them.
Describe alternatives you've considered
I have considered implementing alternate logic to pull market data via URL query params, but that's a bit too hacky to my taste.
Additional context
The text was updated successfully, but these errors were encountered: