I have been migrating my existing blog to Mezzanine.  It has been a great 
experience so far.  Mezzanine has been able to accommodate all of the 
features on my "wish list" so far with the exception of the few "hiccups" 
below.  Fortunately, I am positive that these outstanding problems can be 
overcome, it's just a matter of me learning more about Mezzanine and 
Django.  I'd appreciate your help!

1)
I want to have a "create new post" button that links to a "form" for 
creating a blog post.  The form will ask the user for a blog post title, 
content, and an optional featured image.  The featured image will prompt an 
upload that must work on smartphones.
So far I am able to get all of this to work except for the image upload 
part.  I've tried a few different ways of setting it up - in some cases the 
upload image button doesn't do anything, in other cases it launches a new 
window with the admin content management gui, and with some tweaking i can 
get the upload button to work but the site bombs when the "request.FILES" 
object is passed.  The admin content management gui isn't really ideal for 
my blog, i'd prefer for it to go directly to an upload prompt.

2)
I added two new columns to my blog_blogPost table in the database, but - 
unsurprisingly - these columns are not accessible when I refer to them in 
the blog detail or blog list pages.  I suspect they need to be added to the 
model, not sure how to do that.


I am thinking I need to ditch the standard "blog" app and instead make my 
own blog app that somehow extends the default blog app.  I am not 100% sure 
about how to do this, but its on my short list of possible options for 
resolving the issues above.

I am fairly strong with python and web design, but I'm still learning 
django.  If you steer me in the right direction, I think I can figure it 
out.

Thanks for the help!
Ryan

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to