Skip to content
Sign up
Sign in
This repository
Explore
Features
Enterprise
Pricing
Watch
You must be signed in to watch a repository
105
Star
You must be signed in to star a repository
705
Fork
You must be signed in to fork a repository
362
modxcms / revolution
Code
Code
Issues
Issues
Pull requests
Pull requests
Pulse
Pulse
Graphs
Graphs
HTTPS clone URL
Subversion checkout URL
You can clone with
or
.
Get help on which URL is right for you.
Clone in Desktop
Download ZIP
Loading…
New issue
Container resources are available by urls both with and without container suffix
#12465
Open
sitex-pro opened this Issue on Jun 12
· 0 comments
Labels
None yet
Milestone
No milestone
Assignee
No one assigned
1 participant
sitex-pro
sitex-pro
commented
on Jun 12
Summary
If we turn furls on and create a container, it will be available by both urls: site.com/container and site.com/container/ – regardless of the value of [friendly_urls_strict] setting.
Step to reproduce
Install modx 2.3.3-pl
rename ht.access to .htaccess
set [friendly_urls_strict] on
create container
Observed behavior
One can access container’s page both slash and without a slash at the end of url
Expected behavior
301 redirect to the url with trailing slash should occur when accessing container’s page without trailing slash
Environment
modx 2.3.3-pl
How to fix
file /core/model/modx/modrequest.class.php, comment out the unwanted line 332:
$identifier = “{$identifier}{$containerSuffix}”;
followed by line:
$found = $this->modx->findResource(“{$identifier}{$containerSuffix}”);
Sign up for free
to join this conversation on GitHub .
Already have an account?
Sign in to comment
Status
API
Training
Shop
Blog
About
Pricing
© 2015 GitHub , Inc.
Terms
Privacy
Security
Contact
Help
Something went wrong with that request. Please try again.
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.
Leave a Reply