Archive for January, 2008

Disabling the ImageMagick check

It has been reported by some users, notably those on Windows servers running IIS, are getting the following error message after logging in as an administrator. 

The specified CGI application misbehaved by not returning a complete set of HTTP headers

The cause for this is ProofBuddy checking whether ImageMagick is at the correct path.  Since a majority of web servers are Linux, the default setting in ProofBuddy is a Linux path (/usr/bin) which causes the above error on some IIS setups.

To fix this, download the zip file below and follow the directions in the readme.txt file.  It will change the settings in ProofBuddy to use the GD Library instead of ImageMagick and tell ProofBuddy to not check for ImageMagick. 

If you are using ProofBuddy 1.0.1 or earlier you will also need to download a patch file from our support forum that will fix a problem on the Admin -> About page.

Categories:Development Blog

ProofBuddy and Winklet

A question that comes up every 2 or 3 weeks is whether ProofBuddy and Winklet will work together.  Fortunately Winklet offers demonstration downloads of their templates so I was able to download one and see if I could get it to work.

The answer is sort of

The first thing I tried to do was to create a form on one of the Winklet pages that would let me enter a passcode and login directly.  It didn't work.  Whether Winklet specifically strips out HTML forms or it's a Flash thing I don't know.  

Next I tried to use JavaScript to output the form.  Also did not work.  In fact it looks like JavaScript tags are stripped out, but the code is kept because the code showed up on the Winklet page but didn't do anything.

What you can do is to create a link to your ProofBuddy site using standard anchor tags using code similar to what's below.

 

<a href="http://www.example.com/proofbuddy/">Click to view your proofs</a>

While this doesn't allow them to login directly, it does at least create a link so that your clients can find their proofs.

If you still want the form you can add an HTML form in the index.html file.  It worked, but I couldn't get it to look right. 

Another suggestion is that you change the settings in ProofBuddy so that it goes back to your Winklet site after your client logs out.  You can do this on the Options -> General tab by filling in your complete URL (including http://) in the field labeled "After Logout".

 

Edit:

After a little more messing with the code I found a possible solution that allows you to have the form on the page and it still looks fairly decent. 

If you look at the top right you'll notice a login form.  To add this you'll need to open up the index.html file and add a few things.  I'm going off the example #23 I downloaded, so yours might be a little different.  If you have any questions be sure to post them in the comments section and I'll do my best to help answering them.

This first bit of code needs to go somewhere between the <head> and </head> tags. 

<style type="text/css">
div#form    {
    width: 775px;
    text-align: right;
    color: white;
    }
</style>

The 775px width is the same as the Winklet Flash object.  If your Winklet is different than that (look for WIDTH="775" in the index.html file) then change it to fit.

And to actually add the form add the following code just below <td align="center" valign="middle">.

<div id="form">
<form action="http://www.example.com/proofbuddy/user/user-script-login.php" method="post">
Client Login <input type="text" name="passcode">&nbsp;<input type="submit" value="Login">
</form>
</div>

You're going to have to replace the form action with your domain name and the path to your ProofBuddy folder, but leave the /user/user

Categories:Development Blog

Emails not sending on Yahoo hosting

There have been a few reports of emails not being sent from ProofBuddy on Yahoo hosting.  What I've found is that the company email address set under the Options -> Company tab has to be at the same domain as the Yahoo account.  So if you're company is using example.com as the domain name, you can't use bob123@yahoo.com for the company email address.  You'll have to setup bob@example.com and use that instead. 

If you're using Yahoo for hosting and this doesn't help you can also look at the mail error log file.  To do this login to your account with a FTP program and open the /tmp/ folder.  You'll see a file called mailError.log.  Open this file and it will list any errors that occurred while trying to send mail.

One important thing to keep in mind is that Yahoo limits the number of emails that can be sent through a script like this to 250 recipients per day.  This shouldn't be an issue for most people, but if you're running a mailing list program or you have a lot of activity on your ProofBuddy site you could come up against this limit.  It looks like any emails that are attempted after the 250 limit will be ignored.

Categories:News & Updates