Sitellite CMS - Internal Server Error (PHPsuexec?)

[CSS]

Hello,
I install sitellite CMS http://www.sitellite.org/ but I get "Internal Server Error" whenever I try to access the site.

I believe this is because of the PHPsuexec that Dathorn runs.

Sittelite includes the following .htaccess file:

# These directives are necessary in order to tell Apache to treat
# the file 'index' as a PHP script.  Avoiding the .php extension
# has some benefits, as some search engines don't parse .php files.
# Otherwise, you can simply rename this file with a .php extension
# and it should work fine with little or no modification.

# Make sure PATH_INFO is available
<IfDefine APACHE2>
   AcceptPathInfo On
</IfDefine>

# Let Apache know that 'index' is really a PHP script in disguise.
<Files index>
   ForceType application/x-httpd-php
</Files>

# Let Apache know that 'sitellite' is also a PHP script in disguise.
<Files sitellite>
   ForceType application/x-httpd-php
</Files>

# Make SCS the directory index handler (instead of index.html or index.php).
DirectoryIndex index index.html index.php

# Instruct Apache to treat XT templates as HTML files upon direct access.
# Useful for previewing.
AddType text/html .tpl

# Short tags are bad.
php_flag short_open_tag off

*I renamed the index and sitellite files to index.php and sitellite.php and removed the .htaccess file, but I was getting a 404 error in this case!

Also in the install directions the following is included, and I am not sure how I should handle it with the case of suexec:

4. Now you must make sure Sitellite can read and write to any files within
   your web site.  On Unix Sitellite runs as the same user Apache and PHP do,
   which is commonly the user 'nobody'.  To allow the user nobody (assuming
   nobody is part of 'other'), to write to your web site, issue the following
   command:

$ chmod -R o+w *

   If you are on a system with numerous users, you may want to protect your
   site contents and set your Unix permissions up differently.  Please make
   sure you understand the Unix file system and how users and groups interact
   with it before setting Sitellite up in a production environment.  Security
   at this level is your responsibility.  Another common permission scheme
   would be to "chown" the entire installation to the user "nobody" and change
   the permissions to 700 (modifiable only by owner).

   If you do not wish to make your entire web site writeable by the web server,
   you can limit this command to the following three directories:

$ chmod -R 777 cache
$ chmod -R 777 inc/data
$ chmod -R 777 inc/app/cms/data

Here is a post at their forums to somebody with similar problem, but the answer is to edit the httpd.conf file. I don't know if I can do that:

http://www.sitellite.org/index/sitef...ction/post.483

Thanks!

[openbox]

You can't edit the httpd.conf file.

With phpsuexec, you also won't be able to run 777 permissions. Assuming the CMS is owned by your username, try changing the directories you listed to 755 permissions.

[CSS]

I tried, but it didn't work.

With the .htaccess I get "Internal server error"

If I just remove the .htaccess I can read the contents of the index file

If I remove .htaccess and rename index to index.php I get a 404 error.

Any other ideas?

[Buddha]

.htaccess can not have any php configuration values in it. Put those values in a php.ini file.

[CSS]

So in effect to rename .htaccess to php.ini?
I tryied that but it didn't work

[Buddha]

So in effect to rename .htaccess to php.ini?
I tryied that but it didn't work

No don't rename .htaccess to php.ini.

This line here is causing the "Internal Server Error" (probably anyway):

# Short tags are bad.
php_flag short_open_tag off

Dathorn servers run phpsuexec so you can't modify PHP's configuration through the .htaccess file. I think you could just delete that line now that I looked at it more closely.

If there are any other php_ type entries in .htaccess you need to move them to a text file called php.ini.

In the php.ini file the above entry would look something like this:

short_open_tag = 0

Notice that off was converted to a zero (i.e. off, false) and also the spaces proceeding and following the equal sign, Dathorn servers seem picky about such things.

Sorry for my rather curt answer previously.

[vizability]

CSS - So what do you think of Sitellite?
I'm looking at it as a contender for an upcoming project, and would like your opinion on it, especially in regards to getting it running here...

Stuart

[kingzasz]

Did you figure out how to fix this? I am having the same problem. None of the posted solutions worked.

[stdio]

create a php.ini file and place any php_ options in there.

1) Create php.ini file

2) Place any php_ options in there. Here's an example:

short_open_tag off

3) Then upload it to the server and you should be done.

Works for me.

Regards.