This problem was my fault. I was pulling forward a previous configuration (from Concrete5) that required there to be a 503 redirect to index.php. Wordpress was forcing /ndex.php back to /. Hence the loop. What a pain. Once I'd found that error, I was still having problems so I asked for help on IRC and Skinkie pastbinned a vserver definition for me to splice into my config.
This raises two fairly large usability/support issues: 1. I'm a complete idiot at times. People are. They set things and due to the non-trivial amount of available settings, it's quite easy for idiots like me to completely overlook a setting I made on an old site and just clone it over without realising what it's going to break. 2. It's nigh-on impossible for people to help idiots like me when we're so adamant that we haven't set any thing bad. Cases where "it used to work fine" or "I did nothing; it just stopped working". Of course it's not your fault when a PEBCAK strikes but perhaps it would be easier if there was direct read/write access to the raw vserver rules and even pastebin them straight from the admin (a bit like django can with error traces) for making asking for help (and having people see the problems) much, much easier. I know a lot of the mantra for Cherokee is all about making things really simple but keeping users so far away from the config makes things harder at times. One example would be a cookbook recipe. At the moment, we have to follow a series of click here, do this, select that, etc commands until (we hope) we have something as specified in the tutorial. If I could copy a block of code across and bung that straight into a vserver, it would take a tiny amount of time. I imagine it would make writing recipes a lot simpler too! The one technical issue I can see is the config file uses numbers to know which vserver a rule is for. Perhaps cookbook entries could use "?" instead and the admin could look for vserver!?! and replace the ? with the correct number. Or move to YAML/XML/etc where you don't need so much repetition. On Tue, Apr 28, 2009 at 2:22 PM, Alvaro Lopez Ortega <[email protected]>wrote: > On 28-abr-09, at 13:21, Oli Warner wrote: > > I'm trying to get wordpress running. I have the following rules for my >> virtual host: >> • Extensions (php) => fastcgi (php) >> • File exists => static >> • Default - Redirection - internal "^/(.*)$" => "/index.php/$1" >> This is exactly how I have another PHP site set up (that uses Concrete5, >> not Wordpress) and it works fine. >> >> The setup script went fine (once I enabled errors) but once that had >> finished, I tried to log in and it sent me to / and ended up in an redirect >> loop. >> >> Any ideas? I'm starting to go a little crazy. >> > > > Have you read the cookbook that Taher wrote? > > http://www.cherokee-project.com/doc/cookbook_wordpress.html > > -- > Octality > http://www.octality.com/ > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
