I guess this is a noob question, but I hope this is the place to learn.
My mezzanine model looks like this (details removed):
class Customer(models.Model):
user = models.OneToOneField(auth.User)
class Product(models.Model):
unique_id = models.CharField(max_length=50, primary_key=True)
2014-03-06 18:36 GMT+01:00 Federico Bruni fedel...@gmail.com:
2014-03-06 18:20 GMT+01:00 Federico Bruni fedel...@gmail.com:
2014-03-03 13:01 GMT+01:00 Federico Bruni fedel...@gmail.com:
First of all, the DATABASES options are divided in 3 files:
- local_settings.py: the setting for local
Hi Niels. Quick question: have you given User Profiles a shot? You need to
do two things: tell Mezzanine which model you want use as user profile with
settings.AUTH_PROFILE_MODULE = path.to.your.model and secondly, enable
user profiles with settings.ACCOUNTS_PROFILE_VIEWS_ENABLED = True. This
Hi All,
Just so you know about this, I got mez running on godaddy shared
hosting with fcgi.
You get only one ssh account with the primary ftp user if you enable ssh.
Basically I created a chroot env on a normal host and then copied it
into the server
Hi Ken
I thought that building the docs was indipendent from starting a mezzanine
project. That's why I'm not using a virtualenv in this case.
My goal is being able to test a doc patch about deployment, in case I
manage to write something reasonable.
Il 07/mar/2014 18:13 Ken Bolton
I'm definitely new to the Django/Mezz world... but I've built some fairly
complex and interesting things with Flask so I'm not completely clueless.
Actually, my Flask background may be hurting me as it seems to have an
almost inverse model to Django (Flask is more event driven where it feels
Checkout the third party modlules at the bottom of this
page http://mezzanine.jupo.org/docs/overview.html?highlight=third%20party
Something like mezzyblocks https://github.com/jardaroh/mezzyblocks may
be what you are after...
On Friday, March 7, 2014 11:35:57 AM UTC-6, Derek Gaston wrote:
Ok - it appears that what I need is a Page Processor... but the
documentation is not quite clear (to me) about where to put such a beast.
It says inside one of your INSTALLED_APPS... does that mean I need to
create another Django App to do this custom python? Or is there a place I
can stick
Hey Derek, a page processor could work, although they get registered to a
particular page type or slug so it wouldn't run on *all* pages. I'm not
sure what you meant about a huge warning about not working with newer
versions of Mezz, they definitely do work in the latest Mezzanine.
Another
Thanks Josh!
A template tag looks perfect - and I'm already using that blog tag for
creating a side block with blog posts in it so I can easily see how to do
that.
Now: Where do I put the template tag? All I have is a Mezzanine project -
what file/directory do I need to create to put this
How much customization is required to restrict publish rights to certain
individuals? That doesn't seem to be OOTB but maybe I missed it?
Thanks! - John
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and
Django gets loaded so that we can retrieve all of Mezzanine's settings
(mezzanine.conf), which each contain names and descriptions - these are
then used to generate the settings docs here:
http://mezzanine.jupo.org/docs/configuration.html
You can't load Django without SECRET_KEY defined.
On
Hey Derek, take a look at the Code Layout here,
https://docs.djangoproject.com/en/dev/howto/custom-template-tags/#code-layout
Basically you need to create a new Django app (python manage.py startapp
app_name), add it to your INSTALLED_APPS, create a templatetags directory
inside of the new app
Awesome Josh! Thanks so much! I got it working!
In case someone else stumbles across this I also had to make sure that the
directory containing my new app was in the Python sys.path() (I added it
in the wsgi file). Since that directory is my Mezz directory I figured
that everything would work
14 matches
Mail list logo
