[5.6] fix for route url generator when request()->basePath exists #24074
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for a bug that was introduced with #24051 and tagged in version
5.6.19
yesterday.Basically, if you had another script (non Laravel) in a sub-folder in the public root that loaded Laravel (by requiring the bootstrap.php file), every route url would include that sub-folder path.
This is a common thing to do in legacy code you are slowly converting to the framework, or when trying to utilize laravel resources in non laravel code (like with wordpress for instance).
In the past, the url generator stripped the whole url root but that changed in #24051 and introduced this side effect.
This fix simply removes the base path string if it exists on the request.
/cc @staudenmeir