|
|
FAQ (Frequently Asked Questions) |
Have a question? Please read all documentation first to see if it's already
been answered. I cannot help with issues specific to your database, installing
Perl, or why your Windoze machine freezes up all the time.
I'm more than happy to answer relevant questions to the best of my ability—send
them to
nick@pantsblazing.com
When emailing, be sure to include the version of ReciPants and the name and version
numbers of your Web server, database, and operating system.
Troubleshooting
Why aren't login cookies working?
Why can't I sign in? I sign in and go to change my password and
it says "Crapcakes! You have to be logged in to do that.".
|
|
ReciPants isn't getting your login cookie.
First, make sure cookies are enabled in your browser.
If that doesn't do it, there is a mismatch between the
cookie server name and path specified in
recipants.cfg.pl vs. the address it's being
accessed by in your browser. The names must match even if two
different values resolve to the same host, i.e. if
$cookie_domain is set to
"127.0.0.1" but it's being
accessed as "localhost" in your
browser, the cookie won't get sent back to ReciPants.
Also check the $cookie_path variable. Try
setting it to "/" to get you
started.
If your browser has a tool that lets you examine
cookies, check to see 1) if the cookie is there (it's
called "rp_user") and 2) what
the domain and path values are. Compare against the URL
you're accessing ReciPants from.
If it doesn't have a cookie inspector, there's a Java
application called
Burp Proxy
that will intercept and let you examine and change all of
your Web traffic, including server headers (and therefore
cookies). If you have it set to intercept, you have to
click the "Forward" button to get anything to
happen.
You can download Burp Proxy from
portswigger.net/proxy
|
Why do I get a "Forbidden - You don't have permission to
access /recipants/xxx.cgi on this server." error
from my Web server when I try to access a ReciPants script?
|
|
There are two possibilities:
1) Your scripts don't have execute permission (though they
should unless you've explicitly changed them). See the
man page for chmod.
2) Your Web server isn't properly set up to execute CGI
programs.
If you're using Apache, see the How-To document "Apache Tutorial:
Dynamic Content with CGI" for
Apache v2.0.x
or
Apache v1.3.x.
If you're using another Web server, see its documentation.
|
|
Why do I get a "Permission denied" error when exporting recipes?
|
ReciPants doesn't have write permission on the export directories
(default: static/exported-recipes/*).
On unix-like systems, see the man page for
chmod.
|
Bugs
|
Why do I get a SQL syntax error when clicking on Categories in v1.0.x
while using MySQL?
|
Apparently, AUTO_INCREMENT values start with 1 instead of
0 in MySQL v4.x. As the ID number of the master default category must
be 0, the whole thing barfs.
SOLUTION:
Upgrade to ReciPants v1.1 or higher (go to
Downloads).
-- or --
Issue the following SQL statement to your database:
UPDATE categories SET category_id = 0 WHERE parent = -1;
|
Why do ingredient quantities show up as 0 or only whole
numbers in v1.0.x and v1.1 while using MySQL?
|
The column that holds ingredient quantities was declared as the wrong
type—the NUMERIC type stores decimals in Postgres,
but in MySQL it only stores whole numbers, causing fractional values
to get rounded off to the nearest whole number.
SOLUTION:
Upgrade to ReciPants v1.1.1 or higher (go to
Downloads).
-- or --
Issue the following SQL statement to MySQL:
ALTER TABLE 'ingredients' CHANGE 'qty' 'qty' DECIMAL(10, 5) NOT NULL;
...and update your existing ingredient quantities.
Postgres databases are not effected.
|
|
Why do I get a "Looks like a bad ingredient format. Please check
the Ingredients box." error when entering fractional ingredient
quantities in v1.0.x?
|
|
The code that validates the ingredient format was broken. It was fixed
in v1.1.
SOLUTION:
Upgrade to ReciPants v1.1 or higher (go to
Downloads).
|
|
Why do I get an orphaned recipe or incomplete ingredients when saving
a recipe with valid info except bad ingredient formats in v1.0.x?
|
|
ReciPants validated the format or each ingredient immediately before
saving it, so it was possible to not catch the error until it was too
late. It was fixed in v1.1.
SOLUTION:
Upgrade to ReciPants v1.1 or higher (go to
Downloads).
|
|
I installed v1.1.1 but it says it's v1.1. What gives?
|
|
I'm a dork—I forgot to change the application version number.
SOLUTION:
If you feel like it (it doesn't really make a difference other than helping
you keep track of what version you have installed), open the file
recipants.cfg.pl, scroll to the bottom, and change
$app_version = "1.1";
to
$app_version = "1.1.1";
|
|
Why doesn't ReciPants accept email addresses with hyphens in
the mailbox name in versions before 1.2?
|
|
The code that verifies the format of email addresses was broken.
It was fixed in v1.2.
SOLUTION:
Upgrade to ReciPants v1.2 or higher (go to
Downloads).
|
|
Why do I get a SQL error when searching for recipes using a single quote
or apostrophe in the search string in versions before 1.2?
|
|
The search code didn't escape single quotes, which is the quote character
in SQL, so the database got confused. It was fixed in v1.2.
SOLUTION:
Upgrade to ReciPants v1.2 or higher (go to
Downloads).
|
General
|
Why is there no prep time field for recipes?
|
|
It's my feeling that as different people prep at very different speeds,
each individual will be able to get a better feel for how long a given
recipe will take by looking at it themselves.
|
|
Why do ingredient quantities entered as decimals show up as fractions?
|
ReciPants can't scale recipes or convert between measurement
systems if it doesn't have an actual numeric value for the
quantity, so we use the Math::Fraction
Perl module to convert all incoming measurements to decimal
and all outgoing measurements to mixed fractions (or whole
numbers as appropriate, the module figures it all out nicely).
|
|
Why doesn't ReciPants use fancy graphics for navigation?
|
|
ReciPants supports localization, which means that the interface
can be translated into other languages. If the navigation were
pictures instead of text, nobody in their right mind would translate
it because of the heinous amount of work that would be involved in
making pictures rather than text.
|
|