[mezzanine-users] Re: HomePage with contact form

2014-05-20 Thread aleksiy
Hello! I created small contact form on Home page by may be wrong, but quite simple way - without programming at all 1) Create regular mezzanine form in admin with URL contact-form, 2) Open form on site and look for fields names, 3) Hardcode form fields in index.html template using generated

[mezzanine-users] Re: HomePage with contact form

2014-05-20 Thread Mathias Ettinger
Isn’t it even simpler to just {% extends page/form.html %} in index.html ? Le mardi 20 mai 2014 09:24:44 UTC+2, aleksiy a écrit : Hello! I created small contact form on Home page by may be wrong, but quite simple way - without programming at all 1) Create regular mezzanine form in admin

Re: [mezzanine-users] Re: modeltranslations - round 2

2014-05-20 Thread Mathias Ettinger
I’m not sure what you’re implying about toggling the translation fields. If it is about shrinking every translation field into a single one with tabs for each language, go ahead. I know that django-modeltranslation is supposed to allow that but I never had it working. If it is about adding

Re: [mezzanine-users] upgrading from 1.4.6 to 3.1.6 south disappears

2014-05-20 Thread Penny Leach
On Tuesday, May 13, 2014 6:55:44 AM UTC+2, Stephen McDonald wrote: Nice work tracking that down. The error you're getting looks like a missing library (called future, that link you found is misleading) - how have you installed the latest Mezzanine version? It should automatically install

Re: [mezzanine-users] Mezzanine under url prefix

2014-05-20 Thread Scott Diehl
No problem, I appreciate all your help. This is a weird one...because basically I am unable to add/edit pages when I have the prefix enabled. I've followed the directions outlined in urls.py - and everything else seems to be working as expected. Scott On Tuesday, May 20, 2014 6:47:10 AM

[mezzanine-users] Re: HomePage with contact form

2014-05-20 Thread bob hosk
Hi many thanks for all the different approaches here. In the end I did return {'contact_form': form} in my page processor, then {% fields_for contact_form %} in the template and all worked. It seems that the name 'form' must be passed to template by something else that was overriding it. --

[mezzanine-users] Re: HomePage with contact form

2014-05-20 Thread bob hosk
Hi many thanks for all the different approaches here. In the end I did return {'contact_form': form} in my page processor, then {% fields_for contact_form %} in the template and all worked. It seems that the name 'form' must be passed to template by something else that was overriding it. On

[mezzanine-users] Re: Amazon s3 storage backed, upload image to blog from admin HTTP 500 on demo site.

2014-05-20 Thread bob hosk
My settings.py is here http://paste.ubuntu.com/7494954/, and I think everything else is just the default mezzanine project install. local_settings.py is here http://paste.ubuntu.com/7494963/ -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To

[mezzanine-users] Re: HomePage with contact form

2014-05-20 Thread bob hosk
But how would that deal with the actual business processing of the form? -- 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