[mezzanine-users] React Mezzanine project starter kit

[Niels Jakob Buch]

Hi there, I am working on a front-end that has become annoying because of 
too many page loads and has decided to move into using ReactJS.

Anyone has experiences to share with Mezzanine (not only Django) on this 
topic?

-- 
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 more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Cannot resolve bases ??

[Niels Jakob Buch]

Nevermind, I found a solution:

Run "python manage.py makemigrations myapp" first to create migrations 
focused on your app...

Before the usual createdb stuff...

I still dont understand why this is an issue with a clean database.

On Saturday, 12 September 2015 18:15:19 UTC+2, Niels Jakob Buch wrote:
>
> Im stuck in this annoying error. Trying to run the "python manage.py 
> createdb" in the project root
>
> [lots of error lines removed]
>   File "C:\Code\MEZ4\lib\site-packages\django\db\migrations\state.py", 
> line 270, in render_multiple
> "for more" % (new_unrendered_models, get_docs_version())
> django.db.migrations.state.InvalidBasesError: Cannot resolve bases for [<
> ModelState: 'myapp.myPage'>]
> This can happen if you are inheriting models from an app with migrations (
> e.g. contrib.auth)
>  in an app with no migrations; see https://
> docs.djangoproject.com/en/1.8/topics/migrations/#dependencies for more
>
>
>
> I am having a page that is used for an app:
> class TrapsPage(Page, RichText):
> add_toc = models.BooleanField(_("Add TOC"), default=False,
>
>   help_text=_("Include a list of child 
> links"))
>
>
> class Meta:
> verbose_name = _("My Page")
> verbose_name_plural = _("My Pages")
>
>
> Can anyone point in a meaningful direction for further investigation...?
>
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Cannot resolve bases ??

[Niels Jakob Buch]

That explains the need for the first app-specific migrations.

What about mezzanine, does it come with built-in migrations.

On Sun, Sep 13, 2015 at 3:48 PM, Eduardo Rivas 
wrote:

> I think Django wouldn't know how to create your application's tables
> without the migration files. Migrations are required with every concrete
> model in Django 1.7 and up.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/x6oxLhpK7Io/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Cannot resolve bases ??

[Niels Jakob Buch]

Now it all makes sense, thanks a lot!

On Sun, Sep 13, 2015 at 4:47 PM, Ken Bolton <kenbol...@gmail.com> wrote:

> Hi Niels,
>
> Mezzanine does come with built-in migrations; pages
> <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/pages/migrations>,
> blog
> <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/blog/migrations>,
> core
> <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/core/migrations>,
> forms
> <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/forms/migrations>,
> and gallery
> <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/gallery/migrations>
> should interest you.
>
> -ken
>
> On Sun, Sep 13, 2015 at 10:27 AM, Niels Jakob Buch <njb...@gmail.com>
> wrote:
>
>> That explains the need for the first app-specific migrations.
>>
>> What about mezzanine, does it come with built-in migrations.
>>
>> On Sun, Sep 13, 2015 at 3:48 PM, Eduardo Rivas <jerivasmel...@gmail.com>
>> wrote:
>>
>>> I think Django wouldn't know how to create your application's tables
>>> without the migration files. Migrations are required with every concrete
>>> model in Django 1.7 and up.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Mezzanine Users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/mezzanine-users/x6oxLhpK7Io/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> mezzanine-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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 more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/x6oxLhpK7Io/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Buildin an app in Mezzanine - best tutorial??

[Niels Jakob Buch]

Hi all

Took a look at 4.0.1 today and it looks really great, thank you for the 
amazing work!

I have some old apps built long time ago, and I want to port and improve 
them.

When building apps inside the Mezzanine frame I have always looked at the 
blog app, as the best example of an app built in the best way.

When looking at it, my brain is rather rusty, and I would love a kind of 
tutorial to assist me.

Is the blog app still the defacto cool example to study?

Are there any great tutorials on building an app inside mezzanine?

Thanks again

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Mezzanine with Django Rest generates 302

[Niels Jakob Buch]

Hi there, thanks for getting back...

Indeed, it seems that something has changed in a new release of either 
Django, Mezzanine, djangorestframework, or something else, that protects 
the APIs - but I have no clue where to start digging.

If I copy a working session with Fiddler, coming from a browser, and 
deletes the cookies and the token, it does not work now, but worked in the 
my older (not updated version).

The APIs are protected with basic authentication.

I have looked through some of the release-notes for Django and 
djangorestframework - but cannot find indicators for changes that should 
impact my setup.

Any hints as to where I should start digging...?

On Tuesday, 30 December 2014 14:47:08 UTC+1, Kenneth Bolton wrote:

 Hi Niels,

 Hard to guess from your description the cause of the problem, much less 
 the solution. The symptoms you describe indicate that your API urls are 
 protected and require login, hence the 302 redirect response which includes 
 that link to the login page. What happens when you hit the API from a 
 browser with an authenticated session?

 - ken

 On Tue, Dec 30, 2014 at 4:26 AM, Niels Jakob Buch njb...@gmail.com 
 javascript: wrote:

 Hi, 

 I have enjoyed the Django Rest framework for a year now as part of my 
 mezzanine setup, but after a recent update my API calls are not 
 authenticated correctly or something else is wrong.

 My calls is returned with an empty body, the view is never reached and 
 the 302 code (FOUND). In the returned header there is a link to the login 
 page.

 Can someone assist here and tell what setting I have messed with, or if a 
 package update has changed this...

 Thanks

 -- 
 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-use...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Mezzanine + Angular.js

[Niels Jakob Buch]

Sincere apologies for being rude and not professional. And thanks to 
Stephen for being always professional. No bad intentions - just exitcement. 

Keep up the awsome direction this thread is moving...

Sorry again.

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Mezzanine + Angular.js

[Niels Jakob Buch]

Guys, I can only confirm that the time is mature for a mezzanine rest framework 
and some goodies for more advanced UI. 

I am crossing my fingers that some of you cool dudes will grab your balls and 
start creating something nice. 

Full support from here!

-- 
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 more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Re: Something wrong with default theme?

[Niels Jakob Buch]

Putting in the top-padding to 100px in the mezzanine.css did the job. 
Thanks for helping me out :-)


-- 
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 more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Something wrong with default theme?

[Niels Jakob Buch]

https://lh3.googleusercontent.com/-cyvRhiGpg8s/U1irjwpPwgI/D6Y/QKY7B62MBCY/s1600/mezztheme.PNG
Here is a screenshot, where you can only see a few pixels of the header on 
the page 

On Wednesday, 23 April 2014 22:04:37 UTC+2, Niels Jakob Buch wrote:

 I am now getting really happy with my mezzanine sites.

 But there is one thing that really puzzles me, the default theme is not 
 working really well.

 I was expecting the theme to be responsive, but it only works on certain 
 screen sizes, on my screen size the header of the page and warning message 
 disappears under the menu in the top.

 Am I using the wrong theme, or is the theme just a draft, that needs some 
 polish before being usable?

 To try it, just take a clean mezzanine project, grab your mouse and resize 
 your window, and you will see that on certain screen sizes, the header is 
 hidden.

 Thanks for your great work..


-- 
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 more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Something wrong with default theme?

[Niels Jakob Buch]

I am now getting really happy with my mezzanine sites.

But there is one thing that really puzzles me, the default theme is not 
working really well.

I was expecting the theme to be responsive, but it only works on certain 
screen sizes, on my screen size the header of the page and warning message 
disappears under the menu in the top.

Am I using the wrong theme, or is the theme just a draft, that needs some 
polish before being usable?

To try it, just take a clean mezzanine project, grab your mouse and resize 
your window, and you will see that on certain screen sizes, the header is 
hidden.

Thanks for your great work..

-- 
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 more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: Best way to show user-specific info?

[Niels Jakob Buch]

Thanks Ed, your first approach was the one I started on, but not sure how 
to approach it in detail. 

Your second approach sounds more normal and I think the ownable idea from 
Lucian makes sense here. I think I will go with this. Still looking for 
examples though...any pointers?

-- 
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 more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Best way to show user-specific info?

[Niels Jakob Buch]

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)
owner = models.ForeignKey(Customer)

class Event(models.Model):
product = models.ForeignKey(Product)
eventtime  = models.DateTimeField(Date/time of event)

class CustomerPage(Page, RichText):
customer = models.OneToOneField(Customer.user)
eventtime  = models.DateTimeField(Date of birth)
eventtype = models.CharField(max_length=50)

I want to show a specific page for the user, where all related info is 
shown, making up both details and lists.

On the customer-page, when a user is logged in, I was hoping to get an 
authenticated user-id, and the ability to iterate over the products for the 
customer (=user) and iterate one level deeper on the events for the product.

I have read through the authentication stuff for Django and Mezzanine, but 
its not clear to me.

How to approach this?

Thanks

-- 
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 more options, visit https://groups.google.com/d/optout.