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
{{ message }}
This repository has been archived by the owner on Apr 16, 2024. It is now read-only.
I've been using this gem for a few months in development with spree 3.0 and have been noticing this very subtle problem where sometimes the URLs in the app end up with the IP address of the server and not the tenant's subdomain. I have not had much luck in trying to debug the issue here. I've got some suspicion that the during the caching process the tenant isn't getting evaluated. If I clear the cache through spree's admin interface the correct URLs get rendered. So I wonder if this is related to issue #1?
So far my solution is to patch the spree views with _path instead of _url routes. But I'm worried that this will burn me on some other places that I haven't caught/patched yet.
If there's anything anyone can suggest as far as ways to debug this I'd greatly appreciate it. I've yet to find any way to reproduce this, so if there's any strategy on that, it would be tremendously useful, too.
The text was updated successfully, but these errors were encountered:
Hello,
I've been using this gem for a few months in development with spree 3.0 and have been noticing this very subtle problem where sometimes the URLs in the app end up with the IP address of the server and not the tenant's subdomain. I have not had much luck in trying to debug the issue here. I've got some suspicion that the during the caching process the tenant isn't getting evaluated. If I clear the cache through spree's admin interface the correct URLs get rendered. So I wonder if this is related to issue #1?
So far my solution is to patch the spree views with _path instead of _url routes. But I'm worried that this will burn me on some other places that I haven't caught/patched yet.
If there's anything anyone can suggest as far as ways to debug this I'd greatly appreciate it. I've yet to find any way to reproduce this, so if there's any strategy on that, it would be tremendously useful, too.
The text was updated successfully, but these errors were encountered: