Re: [mezzanine-users] Re: Blog post pagination broken

2016-01-28 Thread Stephen McDonald
Thanks for the info, that's fixed here: https://github.com/stephenmcd/mezzanine/commit/7dfbf1c5f7a2299a861ca694ce370b815ae0ec13 On Fri, Jan 29, 2016 at 12:27 AM, michela wrote: > Hi Danny > > I hit the same issue, with 2.7.3, so thanks for above. > > >My workaround for now will be to change MAX

Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread George M
Oops, sorry. Its my first mezzanine app and django migration. I'll keep at it. Thanks. On Thursday, January 28, 2016 at 7:15:50 PM UTC+3, Eduardo Rivas wrote: > > I don't think that's a valid Django migration. You can't simply edit > South migrations to make them Django compatible. Please follow

Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread Eduardo Rivas
I don't think that's a valid Django migration. You can't simply edit South migrations to make them Django compatible. Please follow the steps outlined in the link I provided in my previous message. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" g

Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread George M
Thanks Eduardo, I've customised the migration that had south as below:- # -*- coding: utf-8 -*- #from south.utils import datetime_utils as datetime #from south.db import db #from south.v2 import SchemaMigration from django.db import models from django.db import migrations class Migration(migratio

Re: [mezzanine-users] South Migration Issue

2016-01-28 Thread Eduardo Rivas
Django implemented built-in migrations with the release of 1.7, and South became obsolete. You will need to create standard migrations for the application to be compatible with Django 1.7+. The Django docs explain this with detail. https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading

Re: [mezzanine-users] Problem deploying Mezzanine on DigitalOcean

2016-01-28 Thread Eduardo Rivas
Glad you could move forward. Have you created the migrations for the onepage app? I don't think you'll be able to do much without that. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails f

[mezzanine-users] Re: Blog post pagination broken

2016-01-28 Thread michela
Hi Danny I hit the same issue, with 2.7.3, so thanks for above. >My workaround for now will be to change MAX_PAGING_LINKS in my site settings to something larger. This worked for me. MIchela On Sunday, 24 January 2016 10:06:34 UTC+11, Danny S wrote: > > Hi all, > > I updated my site to Me

[mezzanine-users] South Migration Issue

2016-01-28 Thread George M
Hi all, I am using Python 2.7.6, Django 1.8.7, Mezzanine 4.1.0 I've used an app called onepage to help me with the site. As of the last update, the app uses south on this part:- from south.utils import datetime_utils as datetime from south.db import db from south.v2 import SchemaMigration from d

Re: [mezzanine-users] Different Forms for Signup and Profile Update

2016-01-28 Thread christian . kuper1
That was indeed the way to go, thanks Steve for pointing me into the right direction. I discovered that the AccountForm class already has got an attribute _signup which does what you suggest. I subclassed the AccountForm. If I am not mistaken I had to hide the profile form fields during signup

Re: [mezzanine-users] Different Forms for Signup and Profile Update

2016-01-28 Thread christian . kuper1
That was indeed the way to go, thanks Steve for pointing me into the right direction. I discovered that the AccountForm class already has got an attribute _signup which does what you suggest. I subclassed the AccountForm. If I am not mistaken I had to hide the profile form fields during signup

Re: [mezzanine-users] Problem deploying Mezzanine on DigitalOcean

2016-01-28 Thread George M
I've upgraded Mezzanine. New errors. Trying to fix them first. Thanks. On Thursday, January 28, 2016 at 12:01:36 PM UTC+3, George M wrote: > > Hi Eduardo, > Methinks you're right. > The problem seems to be that pages_page has an unapplied migration which > also isnt working. I've been using mys

Re: [mezzanine-users] Problem deploying Mezzanine on DigitalOcean

2016-01-28 Thread George M
Hi Eduardo, Methinks you're right. The problem seems to be that pages_page has an unapplied migration which also isnt working. I've been using mysql locally. I've switched to postgresql and this is my new error. Creating tables... Creating table pages_page Creating table pages_richtextpa

[mezzanine-users] Re: drum template tag error

2016-01-28 Thread Minwoo Park
I met same error and solved by adding below line "mezzanine.pages", on INSTALLED_APPS (settings.py) 2015년 8월 30일 일요일 오전 3시 3분 45초 UTC+9, Micah Yoder 님의 말: > > Hi, > > So Drum works when I first started it (well, after > https://github.com/stephenmcd/drum/pull/22 was merged, thanks). But, > after

[mezzanine-users] Re: 404 page with USE_I18N = True

2016-01-28 Thread dborisov86
I've replaced urlpatterns = i18n_patterns("", # Change the admin prefix here to use an alternate URL for the # admin interface, which would be marginally more secure. ("^admin/", include(admin.site.urls)), ) with urlpatterns = patterns("", # Change the admin prefix here to use an a