[mezzanine-users] Re: new release?
Django 1.7.7, Python 3.4.3 python manage.py runserver Performing system checks... System check identified some issues: WARNINGS: ?: (1_6.W001) Some project unittests may not execute as expected. HINT: Django 1.6 introduced a new default test runner. It looks like this project was generated using Django 1.5 or earlier. You should ensure your tests are all running behaving as expected. See https://docs.djangoproject.com/en/dev/releases/1.6/#new-test-runner for more information. System check identified 1 issue (0 silenced). You have unapplied migrations; your app may not work properly until they are applied. Run 'python manage.py migrate' to apply them. -- 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: new release?
Same results on Python 2.7.9 I notice that all of the 4 tests except the first one had this text 'You have unapplied migrations; your app may not work properly until they are applied. Run 'python manage.py migrate' to apply them.' -- 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] Taxes per product in Cartridge ?
Hello, I'm really starting like Mezzanine/Cartridge, mostly due to relative code cleanness and straightforwardness. Good job from devs. Hope I didn't miss something important, but even in latest Cartridge tip there is only flat per order tax implementation. It seems if shop sells products with different tax categories and rates, like in our country, I'm on my own here ? Did anybody already attempted to write per product tax handler and don't mind to share with others ? If there is not yet such implementation, what approach would you recommend ? I don't see a hook for tax processing override and the current solution seems to be hardcoded without extensibility in mind. 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.
Re: [mezzanine-users] Page Teaser
Hi Roland, first use a page process, template tag or some other method to pull the page you want to show content from onto the home page. Then use either https://docs.djangoproject.com/en/1.8/ref/templates/builtins/#truncatechars-html or truncatewords_html to cut the text down to the size you want. Good luck! On Tue, Apr 7, 2015 at 2:00 PM, roland balint rabal...@gmail.com wrote: not sure if this has already been asked or done... how can we do a page teaser? was thinking about the first 100 character from a rich text page to be displayed on the index page thank you, roland -- 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 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] Testing an existing app in the new (Django 1.7 / 1.8 / Mezzanine environment) - seeking guidance
Hi there I am already developing a Mezzanine app using the *existing* version of Mezzanine. I would like to be able to test it using the new (Django 1.7 / 1.8 / Mezzanine environment). I have set up a new vanilla Django 1.7 / 1.8 / Mezzanine environment but I can't work out how to move the existing application to the new vanilla environment. Any guidance / pointers would be appreciated. TIA g -- 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] Testing an existing app in the new (Django 1.7 / 1.8 / Mezzanine environment) - seeking guidance
To be clear, Graham has actually posted lots of feedback in the thread mentioned, he's just done the right thing by posting a new thread here asking for help in getting set up. To answer the original question, you should just need the relevant virtualenv activated, then run your existing project as usual. On Wed, Apr 8, 2015 at 10:18 AM, Mario Gudelj ma...@twoblokeswithapostie.com wrote: I believe that Mezzanine still doesn't support 1.7 and 1.8. There's a recent thread in this group about it. On Wed, Apr 8, 2015 at 8:52 AM, Graham greenbay.gra...@gmail.com wrote: Hi there I am already developing a Mezzanine app using the *existing* version of Mezzanine. I would like to be able to test it using the new (Django 1.7 / 1.8 / Mezzanine environment). I have set up a new vanilla Django 1.7 / 1.8 / Mezzanine environment but I can't work out how to move the existing application to the new vanilla environment. Any guidance / pointers would be appreciated. TIA g -- 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 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. -- Stephen McDonald http://jupo.org -- 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] lack of /static/ in urls
I'm following this tutorial: bitofpixels.com/blog/mezzatheming-creating-mezzanine-themes-part-1-basehtml/ I've added the theme app, and made all the templates specific changes. Done! I run the app in browser, and all references to static files and media files are all lacking the ../static/... part. So for instance, Instead of: http://localhost:8000*/static/*img/home_blog/4.jpg/ I get http://localhost:8000/img/home_blog/4.jpg (without the static part) When I explicitly add the static part to any url, the item loads, meanwhile, for whatever reasons, Mezzanine doesn't add the /static/ part. Here's my settings file: http://pastebin.com/6ZWgggSC I don't know where to look anymore, as the settings file looks perfect, and the urls are okay, because if not, I wouldn't be able to have the urls with /static/ in them pointing to the resources. 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.
Re: [mezzanine-users] Testing an existing app in the new (Django 1.7 / 1.8 / Mezzanine environment) - seeking guidance
Hi Mario Yes you are right. I am just trying to test the new release so that support can be provided. Cheers g On 08/04/15 12:18, Mario Gudelj wrote: I believe that Mezzanine still doesn't support 1.7 and 1.8. There's a recent thread in this group about it. On Wed, Apr 8, 2015 at 8:52 AM, Graham greenbay.gra...@gmail.com mailto:greenbay.gra...@gmail.com wrote: Hi there I am already developing a Mezzanine app using the *existing* version of Mezzanine. I would like to be able to test it using the new (Django 1.7 / 1.8 / Mezzanine environment). I have set up a new vanilla Django 1.7 / 1.8 / Mezzanine environment but I can't work out how to move the existing application to the new vanilla environment. Any guidance / pointers would be appreciated. TIA g -- 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 mailto:mezzanine-users%2bunsubscr...@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 mailto: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] Re: Testing an existing app in the new (Django 1.7 / 1.8 / Mezzanine environment) - seeking guidance
I think you meant to post to this thread instead of the other, as your latest question has to do with your custom app. Are you using migrations in soulapp2? As the link that appears in the Traceback says: Be aware, however, that unmigrated apps cannot depend on migrated apps. https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies. This basically means that anybody looking to leverage Mezzanine's Page, Displayable or the like is forced to use migrations. -- 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: Testing an existing app in the new (Django 1.7 / 1.8 / Mezzanine environment) - seeking guidance
Q : Are you using migrations in soulapp2? A : I don't think so. I wasn't using South because I knew that it was going to be rolled into Django... When I did a schema change I just deleted the table and did a syncdb g On 08/04/15 13:54, Eduardo Rivas wrote: I think you meant to post to this thread instead of the other, as your latest question has to do with your custom app. Are you using migrations in soulapp2? As the link that appears in the Traceback says: Be aware, however, that unmigrated apps cannot depend on migrated apps. https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies. This basically means that anybody looking to leverage Mezzanine's Page, Displayable or the like is forced to use migrations. -- 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 mailto: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.