Skip to content
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

Modules: 403 Error #150

Closed
jlkane opened this issue Feb 16, 2018 · 7 comments

Comments

Projects
None yet
2 participants
@jlkane
Copy link

commented Feb 16, 2018

I completed a new installation of Form Tools 2 (Core=2.2.5), and all seemed fine ...until I tried to access Modules from the main menu. That click yielded a 403 error.

The modules directory was present, all of its files were there, and the permissions seemed appropriate. I deleted the modules directory and re-uploaded it. Still no love.

Any suggestions?

Thanks in advance for your help,
Jim

@benkeen benkeen added the Question label Feb 16, 2018

@benkeen

This comment has been minimized.

Copy link
Member

commented Feb 16, 2018

I heard the same problem reported a few months back but was never able to reproduce it. Which modules (any?) are in your installation?

@jlkane

This comment has been minimized.

Copy link
Author

commented Feb 16, 2018

@jlkane

This comment has been minimized.

Copy link
Author

commented Feb 16, 2018

PS
If I should simply clean house and reinstall FT, just say the word.

@benkeen

This comment has been minimized.

Copy link
Member

commented Feb 16, 2018

To be honest I'm not sure what to suggest, a 403 permissions denied error is rather peculiar if the files are there and they have the right permissions. There was never a problem with that page on FT2.x back in the day (3 / 4 years ago) so it's possible there's some sort of incompatibility with more modern PHP versions...

No chance I could get temporary access to your env so I could debug this directly?

@jlkane

This comment has been minimized.

Copy link
Author

commented Feb 16, 2018

@benkeen

This comment has been minimized.

Copy link
Member

commented Feb 17, 2018

Thanks Jim! For anyone else that runs into this, we found out that in this case there was a setting on the server's .htaccess file that was redirecting all .php files within any folder called "modules" to display a 403 error.

@benkeen benkeen closed this Feb 17, 2018

@jlkane

This comment has been minimized.

Copy link
Author

commented Feb 17, 2018

Thank you SO much for discovering the source of the problem, Ben. That line is part of the .htaccess file distributed with the CMS system I'm using: CMS Made Simple. It looks as if it's intended to keep unauthorized visitors out of TinyMCE and the responsive filemanager modules, and it's simply guilty of overreach here.

VERY much obliged to you for your willingness to investigate and resolve this problem,
Jim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.