Search results
-
I
Radiant CMS (LSAPI) - hardly working
This is already set. Its strange, I set the context for /forum/, yet it still uses the CMS's 404 page at /forum/. Any idea's? I can link you again, if you wish.- iHack
- Post #9
- Forum: Ruby/Rails
-
I
Radiant CMS (LSAPI) - hardly working
Not sure what you mean by the rails route configuration. I've sort of got it to work, apart from /forum/ doesn't autoindex to index.php? Same with any subdirectory (eg. /forum/admin/ doesn't autoindex to /forum/admin/index.php) Is there any way I can solve this?- iHack
- Post #7
- Forum: Ruby/Rails
-
I
Radiant CMS (LSAPI) - hardly working
permissions were messing things up, would it be possible to use the LSAPI in the path /forum/ to say, /opt/lsws/www/forum/ ? Thanks.- iHack
- Post #5
- Forum: Ruby/Rails
-
I
Radiant CMS (LSAPI) - hardly working
Hello, I followed each of the instructions. I couldn't find anything wrong - all files chmod'd correctly and are chowned "nobody" - the user that LSWS runs on. I could PM you a link to it? If thats any use?- iHack
- Post #3
- Forum: Ruby/Rails
-
I
Radiant CMS (LSAPI) - hardly working
Hey, I'm trying to setup Radiant CMS in a VHost in LS v3.3.3. At the moment I can't get anything from the public/ folder to actually be *public* (eg. I'm getting a 404 on them). Some other things work though, like the admin panel for Radiant CMS. At "/" I'm getting this error: Application...- iHack
- Thread
- Replies: 9
- Forum: Ruby/Rails