COMMON ERRORS

Started 10/19/03

Common closedShop Errors

Problem
You don't know your server path to your image folder.

Solution
Put the file findpath.php in your image folder. (assuming
your server can use php). then use your web browser to
go to your website/image folder/findpath.php
this file will tell you your path.

Problem
After you press install it says,
"cannot connect to mySQL database with user @localhost"
where it does not seem like the data you typed was included
in the connect

Solution
This is caused by the biggest problem closedShop has. If the 
folder where closedShop is saved in is not owned by the 
web server user, then it cannot create teh closedShop.vars file
Either chmod this folder 777, making it writeable, or upload 
a blank file called closedShop.vars and chmod that to be 777.


Problem
Error says, mySQL cannot connect through /tmp/mysql.sock

Solution
This is usually a webhosting problem where they don't have 
the write things set up. You can call them or you can try
to fix it yourself. Since you have access to the /tmp folder,
first find the real mySQL sock
try: locate mysql.sock
it will usually be at /var/lib/mysql/mysql.sock
then create a link to the place the program is asking for it
ln -s /var/lib/mysql/mysql.sock /tmp/mysql.sock


Problem
What are header, footer and template files?

Solution
The header and footer files let you create HTML pages that
"border" the closedShop program. This way, you can
customize the way things look "around" the closedShop program
The template files (new to 1.6) allow you total control over
look and feel for the Individual item and category listing
pages. They let you have access to perl programming inside
a normal HTML template. More instructions are in the 
sample templates (template.cat, template.item). They are
not required by any means. If you use templates, then
the header and footer are ignored. 

Problem
Internal Server Error

Solution
There are many causes for this dreaded problem. In fact, I think
this is the biggest problem with Perl run programs. It's quite
impossible to figure out what went wrong. Usually, the files
have not had the correct permissions set. Make sure all the files
have been "chmod" 755 so that they can be executed. If that fails,
try to move the files to the cgi-bin folder instead of putting the 
files in a different folder. Sometimes your webhoster doesn't
allow you to run scripts in a folder that you have created.


Other Problems?
Feel free to email - chris@fleizach.com, happy to help