Remove hard-coded style= for donate-sidebar div

Move the CSS for the donate-sidebar into the conservancy.css file
instead of hard-coding in the HTML.

Larger error message when submitting bad amount.

This addition to the Javascript and text ensures a clear message to the
user of a Javascript-enabled browser that there is an issue with the
amount. Also, it prevents submission of the form until the amount is
correct.

A user with Javascript disabled can circumvent these validation steps;
however, the worst-case scenario is that they make a donation for less
than $120 that is categorized in Conservancy's internal system as a
Supporter donation, and we'll be adding internal checks to find that.

Correct regular expression and comma thing fully.

parseInt() likely wants no commas, so we use a value without it, and the
regular expression now seems to properly match was PayPal will take as
valid.

Modify CSS, image & related so img of heart works.

Putting the heart on the floated right corner should work pretty well
now with this CSS.

Force scaling of width for banner.

The banner should scale with the width of the window.

Apparently, we aren't using this now.

<tony> bkuhn, karen: so, let's not bother using the logo-heart. The pic adds
enough visual interest. Now, what about the the text header. Do you
want it to be a smidgen smaller?

Thank-you page to redirect supporters post-payment

This page is now set as part of the PayPal giving forms to redirect
supporters to after they've paid.

Another adjustment to the forms CSS.

This is working on my test site but not on the main website. I can't
figure out why.

Customized buttons for annual/monthly supporter.

These buttons were drawn by Tony and replace the default PayPal buttons.

Subscriptions for monthly supporters.

There are now two options at the bottom of the page, annual and monthly
supporters.

In addition, there is Javascript code to cause the annual and monthly
items disappear and reappear upon selection either in the donate box or
the selector above the items.

I tested this in links and it seems to degrade reasonably well.

Float Donate button to the center beside questions

The donate button is now centered beside the questions that relate to
the supporter program.

Better formatting for submit button.

The needed CSS is already in forms.css

Rework form with error messages & basic validation

Since PayPal cannot seem to be cajoled into verifying a minimum amount,
we have to do it here with Javascript. This isn't perfect validation:
the form can currently still be submitted with an amount less than $120,
but at least this way Javascript-enabled browsers might prevent some
folks from doing that.

Remove ! from this sentence, per karen:

<karen> I would take the exclamation point off of "Support us via PayPal or
credit card!" [13:55]

Campaign is no longer "campaign", but npoacct.

Changes in preparation of launching supporter program; no longer
highlight this as the "campaign".

Rename file to new directory.

/campaign will now be redirected to npoacct in apache config.

Rename file names to remove the word "draft".

RedirectPermeant's have been added server-side to handle the fact that
the URLs were already live.

Rename file to no letterhead version,

letterhead version is coming shortly.

Remove Loïc Dachary from the eval committee

Loïc is on a leave of absence from the eval committee.

Remove Loïc Dachary as Director

Loïc resigned due to lack of time but hopes to return in the future.

Update Monthly Donation form to fix PayPal problem

On a monthly subscription box, PayPal silently fails to allow the user
to select any option but the first one (despite selecting another value
from the form) if you name the values the same.

It's somewhat obvious when you review the form code that PayPal gives
you that all the value="" fields were the same, and thus the incorrect
behavior is somewhat unsurprising.

I fixed this by modifying the buttons to include the amount in words.

Use same logic for blogs as for news

Put the code for blog.1 within the if block of blog.0, as this is the
logic used for news. As a result, the <hr> divider for blogs is now
in the "shaded" element (as it already is with news).

.* no longer desirable in /admin in urls.py

According to:
http://stackoverflow.com/questions/10145583/django-1-4-and-noreversematch-at-admin-error

the .* was no longer correct. It is herein removed.

No longer "stash" the GET object in self.

I don't think this was actually necessary ultimately. I think the older
code, herein removed, in item_author_email() was wrong-headed in the
first place, or at the very least, was overkill.

Each item has a distinct author, according to the BlogEntry model. So,
I think this is actually what we want. I noticed the author filed isn't
properly going into the RSS at the moment anyway, but I'm somewhat past
caring about that, as long as the URLs now work to get author- and tag-
specific feeds.

GET object is accessible everywhere in BlogFeed.

This solution is likely a hack to ensure the GET object is regularly
accessible.

use get_object() in BlogFeed to get request object

Upon reading
https://docs.djangoproject.com/en/dev/ref/contrib/syndication/#a-complex-example

I think that this is what I need to do to forward-port this Django 1.2
to Django 1.4's Feed objects.

Fix regression introduced in commit early today.

6a2918c288c26ed1503365ded9ceb2f52a7b7d09 introduced a removal of this
line. This line is necessary for the front page to work.

Make sure return values match title.

I received this error from the feeds:

AttributeError at /feeds/news/

'PressRelease' object has no attribute 'title'

Request Method: GET
Request URL: http://sfconservancy.org/feeds/news/
Django Version: 1.4.5
Exception Type: AttributeError

'PressRelease' object has no attribute 'title'
Exception Location: /var/www/conservancy/feeds.py in item_title, line 46

I think this change fixes that.

Additional argument was likely incorrect.

Rereading https://docs.djangoproject.com/en/1.4/ref/contrib/syndication/
shows that the first argument should no longer be that class.

First attempt to follow Django 1.4 feed classes.

I followed the instructions at
https://docs.djangoproject.com/en/1.4/ref/contrib/syndication/
and attempted to get these feeds to match that one.

Try putting these settings in each class.

I am not sure what the loop was for anyway.