Search

Hi there,

I'm new to Symphony and am having some trouble getting it started.

I am following the install docs, and downloaded the newest .zip file (2.2.1). I placed it in a subfolder on my server (I'm using hostgator and checked to make sure they handled all of the minimum requirements listed in the website footer).

When I try to navigate to the install.php, I get a 500 error. Is it because I have it in a subfolder? My URL looks like http://mydomainname.com/subfolder/install.php

Is there any additional information that I could provide that would help troubleshoot the problem?

Thanks!

Could you provide the contents of your .htaccess file?

Here it is:

#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes.
<FilesMatch ".(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(.php)?|xtmpl)$|^(..*|Entries.*|Repository|Root|Tag|Template)$">
  Order allow,deny
</FilesMatch>

# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Multiviews creates problems with aliased URLs and is not needed for Drupal.
Options -Multiviews

# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php

# Force simple error message for requests for non-existent favicon.ico.
<Files favicon.ico>
  # There is no end quote below, for compatibility with Apache 1.3.
  ErrorDocument 404 "The requested file favicon.ico was not found.
</Files>

# Set the default handler.
DirectoryIndex index.php index.html index.htm

# Override PHP settings that cannot be changed at runtime. See
# sites/default/default.settings.php and drupal_initialize_variables() in
# includes/bootstrap.inc for settings that can be changed at runtime.

# PHP 5, Apache 1 and 2.
<IfModule mod_php5.c>
  php_flag magic_quotes_gpc                 off
  php_flag magic_quotes_sybase              off
  php_flag register_globals                 off
  php_flag session.auto_start               off
  php_value mbstring.http_input             pass
  php_value mbstring.http_output            pass
  php_flag mbstring.encoding_translation    off
</IfModule>

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
  # Enable expirations.
  ExpiresActive On

  # Cache all files for 2 weeks after access (A).
  ExpiresDefault A1209600

  <FilesMatch .php$>
    # Do not allow PHP scripts to be cached unless they explicitly send cache
    # headers themselves. Otherwise all scripts would have to overwrite the
    # headers set by mod_expires if they want another caching behavior. This may
    # fail if an error occurs early in the bootstrap process, and it may cause
    # problems if a non-Drupal PHP file is installed in a subdirectory.
    ExpiresActive Off
  </FilesMatch>
</IfModule>

# Various rewrite rules.
<IfModule mod_rewrite.c>
  RewriteEngine on

  # Block access to "hidden" directories whose names begin with a period. This
  # includes directories used by version control systems such as Subversion or
  # Git to store control files. Files whose names begin with a period, as well
  # as the control files used by CVS, are protected by the FilesMatch directive
  # above.
  #
  # NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is
  # not possible to block access to entire directories from .htaccess, because
  # <DirectoryMatch> is not allowed here.
  #
  # If you do not have mod_rewrite installed, you should remove these
  # directories from your webroot or otherwise protect them from being
  # downloaded.
  RewriteRule "(^|/)." - [F]

  # If your site can be accessed both with and without the 'www.' prefix, you
  # can use one of the following settings to redirect users to your preferred
  # URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
  #
  # To redirect all users to access the site WITH the 'www.' prefix,
  # (http://example.com/... will be redirected to http://www.example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} !^www. [NC]
  # RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  #
  # To redirect all users to access the site WITHOUT the 'www.' prefix,
  # (http://www.example.com/... will be redirected to http://example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} ^www.(.+)$ [NC]
  # RewriteRule ^ http://%1%{REQUEST_URI} [L,R=301]

  # Modify the RewriteBase if you are using Drupal in a subdirectory or in a
  # VirtualDocumentRoot and the rewrite rules are not working properly.
  # For example if your site is at http://example.com/drupal uncomment and
  # modify the following line:
  # RewriteBase /drupal
  #
  # If your site is running in a VirtualDocumentRoot at http://example.com/,
  # uncomment the following line:
  # RewriteBase /

  # Pass all requests not referring directly to files in the filesystem to
  # index.php. Clean URLs are handled in drupal_environment_initialize().
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !=/favicon.ico
  RewriteRule ^ index.php [L]

  # Rules to correctly serve gzip compressed CSS and JS files.
  # Requires both mod_rewrite and mod_headers to be enabled.
  <IfModule mod_headers.c>
    # Serve gzip compressed CSS files if they exist and the client accepts gzip.
    RewriteCond %{HTTP:Accept-encoding} gzip
    RewriteCond %{REQUEST_FILENAME}.gz -s
    RewriteRule ^(.*).css $1.css.gz [QSA]

    # Serve gzip compressed JS files if they exist and the client accepts gzip.
    RewriteCond %{HTTP:Accept-encoding} gzip
    RewriteCond %{REQUEST_FILENAME}.gz -s
    RewriteRule ^(.*).js $1.js.gz [QSA]

    # Serve correct content types, and prevent mod_deflate double gzip.
    RewriteRule .css.gz$ - [T=text/css,E=no-gzip:1]
    RewriteRule .js.gz$ - [T=text/javascript,E=no-gzip:1]

    <FilesMatch "(.js.gz|.css.gz)$">
      # Serve correct encoding type.
      Header append Content-Encoding gzip
      # Force proxies to cache gzipped & non-gzipped css/js files separately.
      Header append Vary Accept-Encoding
    </FilesMatch>
  </IfModule>
</IfModule>

# $Id: .htaccess,v 1.111 2010/11/23 02:59:05 dries Exp $

Symphony creates the '.htaccess' file during installation. You have an old '.htaccess' file from a Drupal installation in your subdirectory. Try deleting it and install Symphony again. And make sure that the directory ist editable via PHP. The subdirectory itself shouldn't be a problem.

Thanks for the reply. I removed the old .htaccess file, reinstalled, and I still get the 500 error. All files and directories have permissions of 777, so I believe the subdirectory should be editable by php. Is there something else to check on? Is there something else I have to do to make it editable via PHP?

You said you reinstalled. Does that mean that you uploaded fresh copies of the Symphony files or that you actually ran the installer, install.php? If you ran install.php, then did you get the form that asks for your username, password, database settings, etc.? If so, then did you get the 500 error immediately after clicking on the button at the bottom of the installer form?

If that's what happened, then the problem would seem to be when Apache/PHP attempts to make a connection with MySQL. Make sure you have used the correct database location, username, password, and port settings in the Symphony installer. If you have already made sure of that, then you would probably be best served by contacting your web host. Ask them to look up the 500 error in the server logs for you, and make sure you give them the URL to your Symphony installer to make it easy for them to find the error in their logs.

I'm still getting a 500 error when I type in mydomain.com/subfolder/install.php. I still can't even see the form.

Thanks for the help, though! I appreciate it -- I think Symphony CMS is what I've been looking for for a little project of mine, and I'm sure it's just something stupid that's holding me up from installing.

Odd. I wonder whether the problem is local to Symphony. Please upload and try to install some other complicated PHP script, such as PHPBB, and let us know how that goes.

Would it be possible that you delete and recreate the entire folder you are trying to install Symphony in? Or do you run any other scripts in that folder?

I used to run Drupal in that folder just fine. I deleted the folder, re-created it, added the files, changed the permissions, and went to ../install.php. Same problem 500 error. Is there somewhere I can find out what is happening behind the scenes?

Thanks again for all your help!

Is there an .htaccess in the parent directory?

Yep. It doesn't have much in it. Just some info from apps (wordpress) running in other subdirectories.

RewriteEngine on

RedirectMatch permanent ^/sfaa/$ http://dcsff.com/sfaa.php
ErrorDocument 404 /404.shtml

RewriteCond %{HTTP_HOST} ^anniegetyourgluegun.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.anniegetyourgluegun.com$
RewriteRule ^/?$ "http://www.gluegunannie.com" [R=3

01,L]

VERSION 2.2.1 - INSTALLATION ERROR - 500 INTERNAL SERVER ERROR

Install directory: http://mydomain.com/subfolder/install.php

EXPERIMENT #1:

1) Removed .htaccess files in install directory and parent directories.

2) Navigated to install directory. 500 error right away.

3) Installation form never appeared.

EXPERIMENT #2:

1) Renamed INDEX FILE file to "xindex.php"

2) No error. Normal directory listing. Installation not possible due to name change

EXPERIMENT #3:

1) Renamed only INSTALL FILE to "xinstall.php"

2) 500 error

CONCLUSION: Something in the index.php and install.php files that causes the 500 error.

@Gerhard there is no install directory in Symphony?

With install directory I meant the directory in which install.php resides:

Issue was resolved by my webhost as follows:

1) They said that a 777 setting is not permitted since they use suPHP on their shared servers. After they reset the permissions to 755 and 644 for directories and files respectively in the directory in which the install.php file resides, everything worked great.

2) However, in the installation instructions for Symphony the user is told to temporarily set the permissions to 777 for the "root" directory of the install.php file, i.e. the directory in which the install.php resides.

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details