Andrea
Andrea
Does anyone have a solution for this? I have been struggling with this issue for 3 days with no results (#912, #913). I tried @Nks solution but it doesn't work...
@bkintanar I don't have a public one but I suppose I could make one for this purpose
@bkintanar I'm quite stuck and until this is fixed my app won't work so I think I'll spend some time setting up the test environment for you
@bkintanar I created a test repository with a test queue and the settings library https://github.com/Bibendus83/laravel-app-multi-tenant-demo/tree/dev Tell me if you need something to set it up
@bkintanar To reproduce the bug you can do one simple thing. Go in the `User` model and disable the trait `UsesTenantConnection`. Then uncomment `App\User::class` in `force-tenant-connection-of-models` and visit the homepage,...
@bkintanar I'm already using this workaround or else I would get the Settings library error even while accessing the tenant website. The problem is that this workaround doesn't work with...
@bkintanar So, do you think that disabling auto discovery and changing the order of providers in `config/app.php` could fix the problem?
but we are talking about the `url()` helper so it should contain a full URL not only the FQDN
It's not a question of supporting it or not, using this setting causes an error on the default laravel helper. Shouldn't it be fixed?
Of course in production port 80/443 will be used. My main issue is that I wasted a couple of days to understand what was the cause of the problem on...