Eduardo,
You are right, CSS is the way.
Thanks,
Márcio
--
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 mezzanine-users+unsubscr...@googlegroups.com.
For mo
Thanks for the info - I've fixed it here:
https://github.com/stephenmcd/mezzanine/commit/cf7f7eadd138d9635751d2c2825492ef4749b238
On Thu, Jan 28, 2016 at 3:35 AM, Wim Feijen wrote:
> Hi, I clarified the subject.
>
> I propose to pass the selected month in the blog archives as an integer to
> th
I recommend writing new CSS rules or tweaking the selectors instead of
trying to change the markup of the form. If I remember correctly, form
fields are wrapped in a div with a particular class, which should let
you write something like:
.wrapper-class > input {width: 100%}
--
You received this
I just updated to Mezzanine 4.1 from 4.0.1 and made the jump to Django
1.9.1 on python 3. I'm also using django_auth_ldap to authenticate users
and create them automatically. This has always worked fine, but after the
updates it doesn't seem to behave anymore. What happens now is that user
acc
Hello,
I would like to know how to style the default Contact page.
More precisely I just need to change this:
into this (inserting *class="form-control"):*
My goal is simply to have the input fields to fill 100% of the width, but I
just could not figure out how to do this.
Thanks,
Marc
Hi, I clarified the subject.
I propose to pass the selected month in the blog archives as an integer to
the template to solve the mentioned problem and will commit a pull request
for this.
WIm
On Wednesday, 23 December 2015 15:43:15 UTC+1, Wim Feijen wrote:
>
> Hello,
>
> For my blog archive p
Never mind, I think the problem is that you're not using migrations with
your onepage app. I believe that any app that depends on another app
that uses migrations (like mezzanine.pages) must also use migrations itself.
--
You received this message because you are subscribed to the Google Groups
I've been trying all day to deploy my first mezzanine site on DO.
All seemed to be going well until the deployment gets to the database.
Somehow this error will not go away.
[49.109.99.39] out: Operations to perform:
[49.109.99.39] out: Synchronize unmigrated apps: staticfiles, boot,
filebrowse
Looks like a migration in your onepage app is referencing the pages.Page
table before it's created in the DB. IMO it has something to do with
your models and migrations. Can you check if the error happens when
running createdb locally in a blank Postgres DB? Might be easier to
debug in your dev mac
Hi Fosi,
In the link Stephen provided, he highlighted lines 22-23 of page.html, in
which the reader will notice the block you call `all_content` should be
called `main`.
hth.
-ken
On Wed, Jan 27, 2016 at 7:16 AM, fosi wrote:
> Hello stephen, looking at the page.html and the code pasted, it se
Hi !
I am creating a multilingual site and I would like to know how to translate
slug ?
Thank you
--
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 mezzanine
Hi,
I am creating a multilingual site and I would like to know how to translate
slug ?
Thank you !
--
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 mezz
Hello stephen, looking at the page.html and the code pasted, it seems to me
that the defined block is been used. If i'm
missing something kindly point it out to me. Thank you
On Tuesday, January 26, 2016 at 11:56:17 PM UTC+1, Stephen McDonald wrote:
>
> If you're extending a template, don't you n
13 matches
Mail list logo
