-
Notifications
You must be signed in to change notification settings - Fork 577
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
Front displaying Twill's error pages #2692
Comments
Something isn't clear for me in your report @antonioribeiro. The yellow error pages are from Twill and that's what we want when there is an error inside Twill, not the frontend. Did you get it on the frontend? That was my concern when reviewing that PR but I thought it was covered. |
Sorry @ifox , what I wrote was really unclear :(, as I just re-read it. I just edited the description, tell me if it's better now. |
I did review this and actually made a fix for it here 042c87e. Could you check what I may have overlooked? |
@ifox , the problem happens here: $matchesDomain = config('twill.support_subdomain_admin_routing') ?
Str::startsWith($requestHost, config('twill.admin_app_subdomain', 'admin') . '.') && Str::endsWith($requestHost, '.' . $adminAppUrl)
: !config('twill.admin_app_strict') || $requestHost === $adminAppUrl; As my So, it works fine if I set ADMIN_APP_STRICT=true Maybe this config should be true by default? |
Here's the only URLs config I'm using for this site: APP_DOMAIN=area17.test
APP_URL=https://${APP_DOMAIN}
ADMIN_APP_URL=https://admin.${APP_DOMAIN}
#ADMIN_APP_STRICT=true |
Description
It seems that the 404 pages on the routes that are not inside Twill went from this on 3.3.1:
to this, on Twill 3.4.1
The first one is the correct behaviour since the page is not under Twill, it's on frontend.
Steps to reproduce
composer require area17/twill:"3.3.1"
, to move to Twill 3.3.1The text was updated successfully, but these errors were encountered: