Concrete5 on Nginx, /tools giving a 404
Permalink
Hi there!
I've recently installed concrete5 on an nginx server, and have gone past a few hurdles [1] along the way. However, this latest problem is one that leaves me clueless yet again.
The general installation seems to work fine (Dashboard looks a-ok), but the pages that are called via AJAX from the /tools directory return a mysterious 404.
For example, it concerns the page /index.php/tools/required/edit_area_popup.php?cID=1&arHandle=Header&atask=add&addOnly=0 when I attempt to add a new block to the area with cID=1.
I'm hoping this sounds familiar to someone here, as it's getting a bit too specific to search for..
Thanks!
[1] http://www.concrete5.org/community/forums/installation/concrete5-on...
I've recently installed concrete5 on an nginx server, and have gone past a few hurdles [1] along the way. However, this latest problem is one that leaves me clueless yet again.
The general installation seems to work fine (Dashboard looks a-ok), but the pages that are called via AJAX from the /tools directory return a mysterious 404.
For example, it concerns the page /index.php/tools/required/edit_area_popup.php?cID=1&arHandle=Header&atask=add&addOnly=0 when I attempt to add a new block to the area with cID=1.
I'm hoping this sounds familiar to someone here, as it's getting a bit too specific to search for..
Thanks!
[1] http://www.concrete5.org/community/forums/installation/concrete5-on...
Same problem here. I installed Concrete5 with Nginx - fpm
Did you fix this problem?
Did you fix this problem?
I have the same problem
Any of you have found a solution on this ?
Thabks
Any of you have found a solution on this ?
Thabks
Did anyone resolve this as running into it myself.
For anyone who comes across this, I was able to fix this by enabling CORS in the Nginx config.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_COR...
https://github.com/concrete5/concrete5/issues/1561...
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_COR...
https://github.com/concrete5/concrete5/issues/1561...
did you fix this problem?