1) Only consider user's with 'status': 'active'. We don't want to
display unconfirmed/blocked users, right?
2) Actually query user's media in the view and display on their home
page.
3) Throw an error 404 if we don't find a valid user, rather than saying,
"User not found" (from within the template).
4) Pass in medias as media_entries to remain compatible with the 'root'
page.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
Natty has a too old system dateutil, but buildout will put the system
modules in the search path first. By adding the dateutil spec to the
'egg' requirement, we put the dateutil inclusion of the local egg first
and natty compiles (buildouts) fine.
Part of http://bugs.foocorp.net/issues/308
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
This patch creates a "homepage" for each media. The URL is
/u/<username>/m/<objID>.
On it we display the media and some details. It is ugly and lacking some
stuff but it works. The only thing left to do is to throw an 404 error
if the <username> and the media uploader don't correspond.
- Also create a user "home page" while at it. It is merely a place
holder for now though.
- Link from the entries on the homepage, to the media pages, so we
actually find them.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
When we submitted an image the description would remain empty. THis was
because of some weird typo in form handling. Get an attribute with
.get('description') and not with .get(['description']). With this patch,
descriptions actually go into the database.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
In the verification email we would output the URL using HTML encoded
text, so that e.g. & -> &. We don't want that and we know the URL
won't contain user contributed content, so it is safe to turn off HTML
encoding here.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
When we configured an explicite db_port in mediagoblin.ini, paster would
crash claiming that the port number must be an int. Given that we don't
have a "get_conf_int()" function or something similar (yet?), simply
convert the port number to int before passing it to the mongo Connection
instance.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
