Everything is blank

[zainisupplies]

we getting as below error when we log on web , my web site is blank , i cant even acess my admin , plz help

[Thu Aug 03 08:44:22 2006] [error] [client 82.198.15.244] File does
not exist: /home/httpd/vhosts/zainisupplies.com/httpdocs/favicon.ico
[client 82.198.15.244] PHP Warning: main() [<a
href='function.main'>function.main</a>]: open_basedir restriction in
effect.

[DrByte]

"open_basedir restriction in effect."

If this is the first time you're seeing this, then either:
- your webhost has changed configuration settings
- a new module you've installed has gone in incorrectly
- your /includes/configure.php file may be corrupt

[zainisupplies]

Thank you very much for your quick reply ,

in my control panel , all PHP file in my control panel has been marked by "red "

i coplaint it to my provider but according to them " You may want to check your scripts and files " , plz advice what is going wrong

[zainisupplies]

yes this is the first time i have seeing this,
- a new module i've not installed

i have already ask to my web host , according to them " check your scripts and files " but i have seen so all PHP files in my control panel has been marked by "RED " and any of this showing "blank " when we try to use it ,
plz advice whether i have to replace my includes /configure.php ???? or still you thinking that something settting change from my webhost

[DrByte]

1. You need to secure your site to protect against any future hack-attempts. This article explains the main steps for doing that:
http://www.zen-cart.com/wiki/index.p...ecommendations

2. You will need to download all your PHP files to your PC for assessment to determine if any have been compromised. This article talks about how to do that:
http://www.zen-cart.com/wiki/index.p...d_odd_problems

Once you have a list of compromised files, then you can decide on the best way to resolve the problem. If you have been hacked, you need to confirm it to your webhost so they can protect the server from further attacks. Naturally, you would also need to repair your own files on your site.

[zainisupplies]

i have compared all files by win merge with my back up file , i do not see any mistake in my web site script, if u require Dr, Bytes then i can PM you my control panel access , i am really looking to working my web site as soon as possible , or plz suggest me any other way where i can get help on it

[DrByte]

"open_basedir restriction in effect."

As I said earlier, if this is the first time you're seeing this, then either:
- your webhost has changed configuration settings
- a new module you've installed has gone in incorrectly
- your /includes/configure.php file may be corrupt

What has your webhost changed on their server?

What "else" is in your errorlog ?

If you upload the /zc_install/techsupp.php file, can you post a URL to it so we can look at your site specs?

[DrByte]

NOTE: I've moved this discussion out of the Hack Attempts area, as this isn't a hack problem, but rather a server configuration problem.

In looking at your Zen Cart files, I notice several things:
1. In the PHP code headers you've replaced the Zen Cart and OsC copyrights in the store with your own. You've done similarly with the Admin footer and removed the Version link from the header. Isn't credit due? ... after all, you did get the software for free...
2. You've installed a few addons, namely: Image Handler, Quick Orders, Dual Pricing, and a few others
3. You are running v1.3.0.1 code with a v1.3.0 database
4. Your admin/includes/configure.php was last edited 05/02/2006 and contains information different from your includes/configure.php with respect to database password. ... and the admin gives an error on connection.
5. Your problem is occurring as a result of some conflict between how the Image Handler calls its files and your server configuration.

I have resolved #3 and #4 above.
I have disabled Image Handler in #5 above by renaming functions_bmz_image_handler.php to *.bak in both admin and catalog.

You'll need to work with your host to find the right resolution to the problem, largely based on server errorlogs which will show details of the problem when you rename the *.bak files to *.php.