Inactive
- Join Date:
- Oct 2006
- Location:
- Alberta, Canada
- Posts:
- 4,572
- Plugin Contributions:
- 0
V1.3.7.1 causing these Server errors ?
Server errorlogs usually also contain IP addresses.
Although that is true in most cases, when running PHP as an Apache module and somebody tries to do something 'funky' (i.e. they are a somewhat experienced Hacker and not a ScriptKiddie) or there is a Database problem, you will see Error msgs. that do not provide an IP address. In these cases one would need to have PHP run as CGI in order to see the IP and a more intelligent error msg.
One can easily find out using: Admin > Tools > Server information and look for "Server API".
If it says Apache then PHP is run as an Apache module.
If it says CGI then PHP is run as a CGI.
If PHP is run as an Apache module then checking within the Admin section for Orders placed or attempted, could provide some more information as to what happened and when.
As to the OP (teamzr1) in general, it has been stated that Zen Cart is free software. You probably have a Hosting account that provides 'one-click' install of various Free scripts. That does not mean you paid for the scripts. You are paying for a "Service" provided by a Hosting company and some provide more/better service than others. As Zen Cart is a free script and Support is also free, one must remember that even though "they" may have a frustrating problem, answers to questions posted are provided on a volunteer basis. Nobody "has to" provide a reply and it's best to keep emotions in check when back 'n forth discussions are going on.
On the flip side, reading the Feb. thread it was mentioned that "Code has been committed to bug fix branch to try and address the problem." and a temporary code fix was provided. In that thread, nobody having the problem mentioned if they used the code fix or what the results were.
It would be nice to see the Zen Cart Development Team also update their posts and state the results of a bug fix; either within the same thread and/or a link to the update in the Bug Reports section. :wink2:
I must admit, both threads mention the identical problem and it seems to happen, only when mySQL 5.x is being used. It is a known fact that mySQL 5.x does cause problems for "some" scripts and is the main reason why many Hosters do not yet use it, or offer both mySQL 4 & 5 to their Clients. But that has its own problems as well.
Troubleshooting can be very challenging. With so many variations available; Script used, Mods added, Server setup, etc., the more eyes looking at a problem and trying things the more likely a solution can be found.
