Abyss Web Server *revisited*
Permalink
I was playing with Abyss webserver again today and trying to figure out why Concrete5 won't work with it. Previous forum posts pointed to a PATH_INFO issue. I wanted to post some specific information in case any other ideas came to light.
1) PATH_INFO does work in Abyss webserver. This is evident with phpinfo().
2) 90% of Concrete5 works with Abyss. Logging in, editing pages, etc. The issues are in a few sections of the Dashboard.
3) The sections of the dashboard the DO NOT work are: files, reports, users and groups, pages and themes. To explain "DO NOT work", I mean you click the link on the main navbar in the dashboard and get the error "No input file specified". There is a way around this (see #4 below).
4) You can get around the non-working pages in the dashboard by accessing sub-pages. For example, clicking on reports does not work, but going to the sub page reports/forms DOES work. All sub pages are accessible manually.
All of this information is relevent to 5.3.3.1. If I remember correctly, older versions had more problems, so much more is working than previously.
Sorry, I hate to revive this topic as I am actually using Apache now. I am not a big Apache fan, so I would like to switch back to Abyss again at some point if possible. I know there are quite a few others in the same boat as me.
Hopefully someone might notice what is different about these dashboard page links vs the others. C5 is just a little too deep for me to hash out :-)
1) PATH_INFO does work in Abyss webserver. This is evident with phpinfo().
2) 90% of Concrete5 works with Abyss. Logging in, editing pages, etc. The issues are in a few sections of the Dashboard.
3) The sections of the dashboard the DO NOT work are: files, reports, users and groups, pages and themes. To explain "DO NOT work", I mean you click the link on the main navbar in the dashboard and get the error "No input file specified". There is a way around this (see #4 below).
4) You can get around the non-working pages in the dashboard by accessing sub-pages. For example, clicking on reports does not work, but going to the sub page reports/forms DOES work. All sub pages are accessible manually.
All of this information is relevent to 5.3.3.1. If I remember correctly, older versions had more problems, so much more is working than previously.
Sorry, I hate to revive this topic as I am actually using Apache now. I am not a big Apache fan, so I would like to switch back to Abyss again at some point if possible. I know there are quite a few others in the same boat as me.
Hopefully someone might notice what is different about these dashboard page links vs the others. C5 is just a little too deep for me to hash out :-)
Remo, yes that's correct. Odd huh?
Give me a bit to get a server for you...
Give me a bit to get a server for you...
yes..
the only thing /reports/ does is call $this->redirect which is located in libraries/controller.php
But it's not much more than this code
But just to be sure, could you try to create a php file with the content above and try to call it? (Remove the two blanks, I had to put them there because the syntax highlighter wanted to insert a link)
I expect it to work but better be sure..
the only thing /reports/ does is call $this->redirect which is located in libraries/controller.php
But it's not much more than this code
But just to be sure, could you try to create a php file with the content above and try to call it? (Remove the two blanks, I had to put them there because the syntax highlighter wanted to insert a link)
I expect it to work but better be sure..
If you meant /forms and not forUms, then yes it worked.
/reports/forms/ = worked
/reports/forums/ = didn't work
/reports/forms/ = worked
/reports/forums/ = didn't work
More info I missed - many of the dashboard pages actually don't work (IE: clicking on any save button in sitewide settings).
Hmmm... stupid PATH_INFO! It looks like it's interpreting some stuff, just not all. Could it be anything in \libraries\request.php? There's quite a bit of expression-work going on there.
No dice on getting server public :(
Hmmm... stupid PATH_INFO! It looks like it's interpreting some stuff, just not all. Could it be anything in \libraries\request.php? There's quite a bit of expression-work going on there.
No dice on getting server public :(
yes of course, I meant forms.
request.php does handle some PATH_INFO stuff but without being able to see how abyss sets PATH_INFO I can't give you any hints..
request.php does handle some PATH_INFO stuff but without being able to see how abyss sets PATH_INFO I can't give you any hints..
http://www.bla.ch/index.php/dashboard/reports/...
you get an error but when you open
http://www.bla.ch/index.php/dashboard/reports/forms/...
it works?
Do you have a public server where you could give us ftp access?