This tidies up the speaker and category pages so they're easier to parse and use.
This has a fix for login_failure that we need.
A bunch of things have been released, so this switches to the released versions. Also, we don't use test-utils, so I'm not sure why that was in there.
* make front page sort by added * fix the migration to default added to start_date
pyvideo extends home and tweaks the branding. This makes that a whole lot easier without duplicating the template code.
This adds a feed for categories. As we add new ones, it'll update the feed. Further each item in the feed will contain a complete list of all the videos in the feed. Fixes #150
* rework search view so it doesn't use Haystack's view * tweak searching so it does a stardswith on speaker names; makes it easier to find specific speakers
As near as I can tell, the common use case for looking through the category list is to look for a known category by name or date. The description isn't useful.
* add persona authentication * add settings_local.py-dist file * update documentation to talk about settings_local.py-dist file * tweak some settings Fixes #144
1.4.5 is like 1.4.4 except without the .pyc files that were causing travis-ci to fail the python 2.6 builds.
* make name and url fields unique -- this will cut down on spam a lot. * add messages to the suggestions page after you submit. otherwise it's not obvious the submission went through.
This changes all fields that previously used HTML to now use Markdown. This fixes a bunch of issues: 1. no one likes writing raw HTML---Markdown is a lot easier 2. conferences don't put their content in HTML, so I usually have to go back and fix everything---Markdown is an easier format to work with and convert everything to 3. HTML is harder to make safe from XSS and similar issues 4. HTML is easier to make HTML mistakes in causing bad rendering for pages with problems Given all that, I knew I wanted to switch to either reST or Markdown and it was just a question of when. That when is now.
This fixes some goofy things with "null" and adds a "default" key that denotes whether the field has a default set or not.
This lets me abuse the order in steve so that I can show the fields in an order that makes sense. The order is derived from the order the fields are defined in in the model.