|
|
|
|
|
|
Frequently Asked Questions
|
| |
|
|
|
Willow Products
|
|
What's the difference between the Free and Pro versions of Job Tracker?
|
Many things. The pro version has cron (automated job) support, a job calendar, the ability to add multiple types of custom fields and control who can see them (even in the followups), and complete db transaction safety. It looks nicer too -- we don't deliberately cripple the free version, but we don't have the resources to keep it pretty either.
You can upgrade to the pro version from the free version.
|
|
|
| |
|
Configuration
|
|
How do I configure Willow?
|
|
All Willow products provide a "configuration" link to Administrators. The configuration page allows you to edit the configuration directly. Of course you should be careful when editing the configuration, since a typo could deny you access to the system.
|
|
|
|
I added a custom field to Willow Job Tracker, but it doesn't show up! What's wrong?
|
You need to make sure the use_custom_fields configuration is turned on. Go to the Administration page, then click Edit Configuration.
|
|
|
|
I can't get Willow to send mail! What's wrong?
|
This could be for a few different reasons. One is that there is no SMTP server running on the machine where you installed Willow. You can check this yourself by typing the following on a command line (unix shell or DOS):
telnet yourserver.com 25
If you see something like "connection refused" or "connection failed", then there is no SMTP server running.
The problem could also be the default From: address in the willow.ini file. Make sure it's a valid address, as some SMTP servers won't accept mail from garbled addresses. Also, some servers require that the From: address be the same domain as the server. By default, the installation sets the following line in willow.ini:
app_email = "willow@yourdomain"
Change "yourdomain" to your domain.
|
|
|
| |
|
Installation
|
|
How do I install Willow?
|
All Willow products install the same way:
- Extract (unpack, unzip, whatever) the distribution (which is usually a
tar.gz file) to your webroot.
- Make sure your webserver can read and write to the directory created by the extraction.
- In your web browser, browse to the newly-created directory
- Follow the prompts
In most cases, you will be up and running within minutes.
|
|
|
|
How do I upgrade a Willow product?
|
|
Download the latest version and run the installer. Make sure you click the "upgrade" button on the install page. The installer will figure out which version you are running, and then make the appropriate changes. If the installer can't figure out what version you are running, then you should not proceed with the upgrade.
|
|
|
|
How do I install a Willow product on Windows?
|
The Windows installation is the same as the Linux/Unix installation. The main difference we have noticed is that it's a bit more difficult to get the directory permissions right. However, this may be because we are not Windows gurus.
But rest assured, the installer will not only report any problems, but will also suggest a course of action. If you just follow the directions, you'll be fine.
|
|
|
|
Whenever I try to install Willow on my Windows server, a DOS box pops up. What's wrong?
|
When you are either installing or running Willow on Windows, if a DOS box pops up at any point, then you are running PHP in command line mode.
To verify that this is your problem, look at the Address bar at the top of your browser. If it begins with anything other than http:// (or https://), then your request is being processed by the operating system, not the web server. You probably double-clicked the installer index.html or index.php file, instead of browsing to it in IE.
If you have installed PHP and MySQL correctly, then you should be able to browse to the installer by entering something like the following in the Address bar of your browser:
http://localhost/willow-installer-path/
|
|
|
| |
|
Operation
|
|
Help, I can't login! What could be wrong?
|
There are many possible reasons you can't login. First, check the simple possibilities. Did you type your usename and password correctly? Is your caps-lock key on?
If it's not one of the above, check to see if the user is active. On the Browse Users screen, you should see an A in the Status column. Only active users can login.
Now for the tricky stuff. First, check your ini file to see how you have configured sessions. This is set with the login_session_type configuration parameter. You have three choices:
phpsession - Use the native PHP session.
cookie - Use a cookie.
request - Embed the session information in forms and urls.
If you have chosen either of the first two, then it is likely that your browser is not accepting cookies. Or, it is possible that you are logging in to one domain (e.g. yourdomain.com) but then browsing to the homepage in a different domain (e.g. yourotherdomain.com). Cookies are domain-based, so even if the two domains point to the same physical machine, your login won't work in this case.
There is one other possibility -- we have recently discovered a bug that prevents users from logging in if there is an underscore character ("_") in the username. We are terribly sorry about that -- we would have found that sooner, but we hate underscores. :-) A fix is forthcoming.
If you find another possible cause, please let us know and we'll add your information to this faq.
|
|
|
|
I hate the auto-logout feature. Can I turn it off?
|
Sure! Go to the configuration editor (or edit the .ini file directly) and change these two parameters:
login_timeout =
logout_warning_interval =
Make sure there are NO characters after the equals signs. After you save the file (or click "apply changes" in the configuration editor), you should be able to remain logged in indefinitely.
If you do this, you might want to disable simultaneous logins as well. To do this, turn off login_allow_simultaneous in the same manner as you did with the two parameters above.
|
|
|
| |
|
| |
|
|
|
|
| |
© 2008, Dawnstar. All rights reserved.
|
| |
