Hi guys,
I recently moved a modx 2.2.2 installation from an apache server to an nginx server and I noticed that I could not upgrade to 2.2.6 (or create a completely new modx installation for that matter). On the same nginx server, with the same settings, I have installed Wordpress and it works with and without FURLS.
I tried the nginx config as detailed here:
http://rtfm.modx.com/display/revolution20/Nginx+Server+Config
and here:
https://forums.modx.com/thread/70163/furls-not-working-after-upgrade-2-1-3-pl?page=2#dis-post-394442
and I have tried not adding anything and leaving the default ISPConfig settings.
The result was always the same: when I went to /setup I would get the first screen, where I'm prompted to choose a language, but when I hit the Select button I would get a 404 which wasn't surprising as the path was changing to:
/setup/index.php/setup/index.php?action=welcome
But if I removed the extra /setup/index.php the installation carried on as expected - and I had to do this for every button press.
I'm assuming that this has to do with the (mis)configuration of nginx? Can anyone shed some light as I'm assuming it may affect other things as well. Having said that, once upgraded to 2.2.6 the website works just fine with FURLs and everything.
The other issue (which I had on Apache as well) is that a few months ago when I moved the site to a new VPS I lost the resource tree in the manager and couldn't change any settings, etc, which I resolved by turning off compress_js and concat_js from the db. Never really got to the bottom of this, but it's happening on 2.2.6 as well. If I turn them on and clear the cache I get the same issue. Any ideas?
The only extras I have are: codemirror, FormIt, getResources, QuickEmail and Wayfinder. (and I noticed that I need to update the first three)
Any help on that?
Thanks,
Theo
[ed. note: ntoqiakt last edited this post 13 years, 7 months ago.]
