Page 1 of 1
403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 8:03 am
by webform
When a user hits a MAMS protected page the internal CMSMS created 403 Error page is no longer displayed. Instead, it is the web host's own 403 Error page that is displayed.
I have filed a bug report:
https://dev.cmsmadesimple.org/bug/view/12803
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 1:46 pm
by DIGI3
I was not able to recreate this, so it could be something specific to your server environment. Make sure there's nothing related to error pages in your htaccess or similar, then try on a clean install. If it still happens, add more detail to the bug report (MAMS version, operating system, PHP version, etc.)
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 6:18 pm
by webform
I have now tried a completely clean installation of CMS Made Simple 2.2.22 with the same result.
If I set up a CMS Made Simple 403 error page, it is not displayed when I access a MAMS protected page. Instead, the host's 403 error page is displayed.
Test URL:
https://lab.webform.dk/cmsms/index.php? ... ed-content
Code: Select all
Cms Version: 2.2.22
MAMS: 1.1.0
CMSMSExt: 1.5.1
SmartyExt: 1.3.0
phpversion: 8.3.25
Server Software: Apache
Server Api: litespeed
Server Os: Linux 4.18.0-553.70.1.lve.el8.x86_64 On x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 8.0.43
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 6:27 pm
by DIGI3
I can't recreate it with similar settings, so it's likely an htaccess rule (check in higher directories as they cascade) or something specific to this host or hosting environment. Does the same happen for 404 pages? I tested on your url and it looks like it's using the apache default.
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 6:32 pm
by webform
Yes the 404 error page does work:
https://lab.webform.dk/cmsms/index.php?page=no-result
And I use the htaccess file that comes with CMS Made Simple without modifications or additions.
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 7:58 pm
by Jo Morg
@webform anything in the php error log? that may help us a bit.
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 8:19 pm
by DIGI3
Also:
-make sure you can see your 403 page (typically has the alias error403)
-check higher directories for htaccess and similar, they are cascading. This could include above the root directory, or even a level only your host can access on shared hosting.
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Mon Sep 15, 2025 8:39 pm
by webform
Unfortunately, the log I have access to via the control panel only shows the error number and the URL of the page that is failing.
And yes, I can preview the error page:
https://lab.webform.dk/cmsms/index.php?page=error403
I have tested 8 separate sites that all worked before the update, where my 403 error page contained the login to the site in question. There have been no changes to the htaccess files on the sites in question.
There is no higher directories with a htaccess file!
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Tue Sep 16, 2025 8:28 am
by chrisbt
When I click on
https://lab.webform.dk/cmsms/index.php? ... ed-content I can see the CMSMS 403 page
Maybe the host 403 response was cached on your browser?
Re: 403 Error page not working after updating to CMSMS 2.2.22
Posted: Tue Sep 16, 2025 10:56 am
by webform
Hmm! Strange! Because I had several users who suddenly did not get the login screen on the site's own 403 error page, but instead Apache's 403 error page.
When I tested I discovered that it was the case for all my sites that had the same structure of protected pages (same host).
Maybe it's just a cache problem that came after the update of CMS Made Simple?
Maybe also combined with the fact that the default page for the sites in question are all MAMS protected pages. However, it has not yet been possible for me to recreate the problem from that starting point on my clean installed test site.
I will have to try testing all sites again and hear from other users whether they are still experiencing problems or not.
Thank you all for your time and suggestions.