Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Admin showing a blank page or HTTP 500 error


Ahmed_Megerisi

Recommended Posts

Hi,

 

I'm on OSC 2.2 and running a windows server, MYSQL database is alright as seems to be the PHP installation as catalog works fine. However when i go to my admin, http://www.2-kl.co.uk/catalog/admin/index.php, depending on my browser i get a blank white screen(mozilla firefox) or an HTTP 500 error(internet explorer). I have checked the configure.php file and it seems to be in order and the i enabled php errors on php.ini file hoping that would give me a hint but neither seem to be working. Any ideas or help would be great as im completley stumped as to why this is happening, as after the initial install it was working fine. However this error just seemed to come up a few days ago.

 

Thanks for any and all help,

Link to comment
Share on other sites

Hi,

 

I'm on OSC 2.2 and running a windows server, MYSQL database is alright as seems to be the PHP installation as catalog works fine. However when i go to my admin, http://www.2-kl.co.uk/catalog/admin/index.php, depending on my browser i get a blank white screen(mozilla firefox) or an HTTP 500 error(internet explorer). I have checked the configure.php file and it seems to be in order and the i enabled php errors on php.ini file hoping that would give me a hint but neither seem to be working. Any ideas or help would be great as im completley stumped as to why this is happening, as after the initial install it was working fine. However this error just seemed to come up a few days ago.

 

Thanks for any and all help,

 

 

I am also having the same problem, except it is with both my catalog and admin. I am running on a Linux host with DWHS.net. I have followed all of the post-installation guidelines,

 

My .htaccess file looks like this:

 

# $Id: .htaccess,v 1.1 2003/06/20 00:18:30 hpdl Exp $

#

# This is used with Apache WebServers

#

# For this to work, you must include the parameter 'Options' to

# the AllowOverride configuration

#

# Example:

#

# <Directory "/usr/local/apache/htdocs">

# AllowOverride Options

# </Directory>

#

# 'All' with also work. (This configuration is in the

# apache/conf/httpd.conf file)

# The following makes adjustments to the SSL protocol for Internet

# Explorer browsers

<IfModule mod_setenvif.c>

<IfDefine SSL>

SetEnvIf User-Agent ".*MSIE.*" \

nokeepalive ssl-unclean-shutdown \

downgrade-1.0 force-response-1.0

</IfDefine>

</IfModule>

# If Search Engine Friendly URLs do not work, try enabling the

# following Apache configuration parameter

#

# AcceptPathInfo On

# Fix certain PHP values

# (commented out by default to prevent errors occuring on certain

# servers)

#

#<IfModule mod_php4.c>

# php_value session.use_trans_sid 0

# php_value register_globals 1

#</IfModule>

Php_flag register_globals on

AuthType Basic

AuthName "OS Commerce Administration"

AuthUserFile "/home/anniepro/.htpasswds/public_html/toystore/admin/passwd"

require valid-user

 

 

and my php.ini file looks like this:

 

 

 

;;;;;;;;;;;

; WARNING ;

;;;;;;;;;;;

; This is the default settings file for new PHP installations.

; By default, PHP installs itself with a configuration suitable for

; development purposes, and *NOT* for production purposes.

; For several security-oriented considerations that should be taken

; before going online with your site, please consult php.ini-recommended

; and http://php.net/manual/en/security.php.

 

 

;;;;;;;;;;;;;;;;;;;

; About this file ;

;;;;;;;;;;;;;;;;;;;

; This file controls many aspects of PHP's behavior. In order for PHP to

; read it, it must be named 'php.ini'. PHP looks for it in the current

; working directory, in the path designated by the environment variable

; PHPRC, and in the path that was defined in compile time (in that order).

; Under Windows, the compile-time path is the Windows directory. The

; path in which the php.ini file is looked for can be overridden using

; the -c argument in command line mode.

;

; The syntax of the file is extremely simple. Whitespace and Lines

; beginning with a semicolon are silently ignored (as you probably guessed).

; Section headers (e.g. [Foo]) are also silently ignored, even though

; they might mean something in the future.

;

; Directives are specified using the following syntax:

; directive = value

; Directive names are *case sensitive* - foo=bar is different from FOO=bar.

;

; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one

; of the INI constants (On, Off, True, False, Yes, No and None) or an expression

; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").

;

; Expressions in the INI file are limited to bitwise operators and parentheses:

; | bitwise OR

; & bitwise AND

; ~ bitwise NOT

; ! boolean NOT

;

; Boolean flags can be turned on using the values 1, On, True or Yes.

; They can be turned off using the values 0, Off, False or No.

;

; An empty string can be denoted by simply not writing anything after the equal

; sign, or by using the None keyword:

;

; foo = ; sets foo to an empty string

; foo = none ; sets foo to an empty string

; foo = "none" ; sets foo to the string 'none'

;

; If you use constants in your value, and these constants belong to a

; dynamically loaded extension (either a PHP extension or a Zend extension),

; you may only use these constants *after* the line that loads the extension.

;

; All the values in the php.ini-dist file correspond to the builtin

; defaults (that is, if no php.ini is used, or if you delete these lines,

; the builtin defaults will be identical).

 

 

;;;;;;;;;;;;;;;;;;;;

; Language Options ;

;;;;;;;;;;;;;;;;;;;;

 

; Enable the PHP scripting language engine under Apache.

engine = On

 

;

; You should do your best to write your scripts so that they do not require

; register_globals to be on; Using form variables as globals can easily lead

; to possible security problems, if the code is not very well thought of.

register_globals = On

 

 

I have removed all of the other options of the php.ini file, in hopes that this would clear up the server error, but no. These two files are in both my catalog folder and the admin folder

Link to comment
Share on other sites

  • 2 months later...

We get a blank page in /admin, but the shopping cart works fine. Admin does not work and although it has worked over the course of 2 years and nothing has changed, we uploaded a new index file copy etc. Nothing seems to work in admin directory. What could we change on server? What can be changed in /admin directory? If you come up with a solution, please advise. urgent.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...