Re: [mezzanine-users] Breaking change in django 1.6.1: south adds 'keywords_string' to migrations?
You're hitting these issues because you're using Mezzanine 1.4.16, which is
3 months old, predates the release of Django 1.6, and explicitly defines
its highest supported Django version as 1.5.x.
The current development branch of Mezzanine aims to be fully compatible
with Django 1.6 and doesn't exhibit the issue you've described, so this
will be fixed for you when the next release is made, which will happen as
soon as time permits.
On Mon, Dec 23, 2013 at 4:05 AM, David Zwarg david.zw...@gmail.com wrote:
Hello list,
I am trying to create a new content type for my own type of page, and I am
running into problems with newest django. I don't know if the problem I'm
facing is in mezzanine itself, south, or django, so please redirect me to
the right group if this is completely off-topic.
I re-created the problem by starting a brand new mezzanine application,
and adding a new app myapp. My 'pip freeze' contains Django==1.5.5 and
south==0.8.4. Before I do anything, I create an initial migration for
myapp:
./manage.py schemamigration myapp --initial
I then modify my models file to create a new content type based on the
Page base model:
from mezzanine.pages.models import Page
# Create your models here.
class MyPage(Page):
pass
Running an auto migration generates a migration that creates this table:
./manage.py schemamigration myapp --auto
Predictably, the only thing in the table is a pointer to the ancestor
content type. All good (this is the 'forwards' portion of the migration:
def forwards(self, orm):
# Adding model 'MyPage'
db.create_table(u'myapp_mypage', (
(u'page_ptr',
self.gf('django.db.models.fields.related.OneToOneField')(to=orm['pages.Page'],
unique=True, primary_key=True)),
))
db.send_create_signal(u'myapp', ['MyPage'])
However, if I use django 1.6.1:
pip install -U django
I move the second migration out of the way, and re-run the schema
migration:
./manage.py schemamigration myapp --auto
I now get an additional field ('keywords_string') in my derived model
table, which begins to cause problems:
def forwards(self, orm):
# Adding model 'MyPage'
db.create_table(u'myapp_mypage', (
(u'page_ptr',
self.gf('django.db.models.fields.related.OneToOneField')(to=orm['pages.Page'],
unique=True, primary_key=True)),
('keywords_string',
self.gf('django.db.models.fields.CharField')(max_length=500,
blank=True)),
))
db.send_create_signal(u'myapp', ['MyPage'])
When I try to run this migration, I get the following error from
./manage.py migrate myapp:
django.core.exceptions.FieldError: Local field 'keywords_string' in class
'MyPage' clashes with field of similar name from base class 'Page'
And if I try to do something sneaky, like remove the field from the
migration manually, it causes more problems. I am able to successfully run
the migration with 'keywords_string manually removed from the migration
script, but when I try to run the app and access the admin (
http://localhost:8000/admin/pages/page/;), I get the error:
OperationalError at /admin/pages/page/
no such column: pages_richtextpage.keywords_string
Any advice is greatly appreciated. I'm unfortunately not able to use
django-1.5.5, so I need to be able to perform this in 1.6.1. Any tips?
Thanks,
David
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: [mezzanine-users] Re: page not found django_redirect
Thanks Ken - with this confirmation I looked into it and added details to the DDT GitHub issue Moltra also opened: https://github.com/django-debug-toolbar/django-debug-toolbar/issues/509#issuecomment-31152850 TLDR: DDT 1.0 requires its middleware be ordered last in the middleware order, as it now prevents any middleware ordered after it from executing, which in this case cancels out Mezzanine's page middleware, causing 404s to trigger. So right now you can either: 1) Fix this in your Mezzanine project right now by explicitly including DDT's middleware last in your MIDDLEWARE_CLASSES setting 2) Wait for the next release of Mezzanine where the setup for DDT will fix this 3) Do as Ken suggested and use DDT 0.9.1 On Tue, Dec 24, 2013 at 11:13 AM, Ken Bolton kenbol...@gmail.com wrote: The culprit is DjDT 1.0. I haven't had time to look into it, but `pip install django-debug-toolbar==0.9.1` will fix your problem. On Mon, Dec 23, 2013 at 6:19 PM, Moltra smsm...@roadrunner.com wrote: Yes, I just tried with a fresh install of mezzanine and had the same problem. ``` Django==1.5.5 Mezzanine==1.4.16 Pillow==2.2.2 bleach==1.2.2 django-debug-toolbar==1.0 filebrowser-safe==0.2.31 grappelli-safe==0.2.23 html5lib==0.95 oauthlib==0.6.0 pytz==2013.8 requests==1.2.3 requests-oauthlib==0.3.3 sqlparse==0.1.10 ``` -- 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/groups/opt_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/groups/opt_out. -- 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/groups/opt_out.
[mezzanine-users] Mezzanine 3.0 and Cartridge 0.9 released
Hi all, I've just released Mezzanine 3.0 and Cartridge 0.9 to PyPi. Like the 1.0 release of Mezzanine, this release represents a major round of housekeeping in the software environment Mezzanine works with. Specifically Mezzanine now supports: - Python 3.3 (as well as 2.6 and 2.7) - Django 1.6 (as well as 1.4 and 1.5) - Bootstrap 3 You might be wondering about the jump from Mezzanine 1.4.16 directly to 3.0 - we've gone with 3.0 as it represents the latest support for Bootstrap 3 and more significantly, Python 3, an entirely new version of the Python language. We also wanted to break away from lurking around similar version numbers with Django, as this would confuse conversations where the various versions of Mezzanine and Django were often discussed together. As well as the above major overhauls and also many bug-fixes, here's a list of other enhancements also included in the Mezzanine release: - Better page handling when APPEND_SLASH is False - Better support for password-less authentication backends - Support for multiple SSL sites in default nginx conf - More flexible instance removal in default fabfile - Thumbnail template tags now accept args for controlling crop centering - Pagination (blog posts, Cartridge products) can now be disabled entirely - TinyMCE handling now includes a pre-populated list of titles/URLs (like a sitemap) to link to - Admin now includes a language selector when multiple languages are defined The 0.9 release of Cartridge (along with new 0.3 versions of the grappelli and filebrowser forks) simply bring everything up to date with all the above. I want to offer a huge thanks to everyone who worked to make these releases possible. My own involvement has somewhat been reduced to code reviewing, merging, and packaging the releases, so all the above has been entirely a community effort. Particular thanks goes to Ed Schofield for the Python 3 work and Eduardo Rivas for the upgrade to Bootstrap 3 - both extremely involved tasks. And also Sebastian Clemens who only joined recently, but has made a large contribution in the Bootstrap 3 and multi-lingual work. Thanks again also goes to the tireless effort of Josh Cartmell, Ken Bolton, and everyone else who has helped out newcomers on the mailing list and IRC - you people are the foundation of this project. Cheers, Steve -- 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/groups/opt_out.
[mezzanine-users] Drum now an installable app
Hi all, A while back I wrote about a new project I'd created called Drum: https://github.com/stephenmcd/drum It's basically a Hacker News / Reddit clone built with Mezzanine, intending to show off Mezzanine's non-CMS capabilities such as threaded comments, ratings, and public user accounts. I wrote about it in detail here: http://blog.jupo.org/2013/04/30/building-social-apps-with-mezzanine-drum/ At the time I'd made the source for Drum public, but it was simply a dump of the Django/Mezzanine project, and not automatically installable in any way. Now I've upgraded it all into an installable app pn PyPI, compatible with Mezzanine 3, along with a project template that gets everything going, in exactly the same fashion as Cartridge, eg: $ pip install -U drum $ mezzanine-project -a drum project_name $ cd project_name $ python manage.py createdb --noinput $ python manage.py runserver Merry xmas! -- 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/groups/opt_out.
Re: [mezzanine-users] newby: Twitter feed issue
Right where you changed the feed query, you'll also need to enter app/consumer keys and secrets for the Twitter API. Mezzanine now has some credentials built in for demoing how the feed looks when first installed, but once you change the feed you need to provide your own credentials. On Sun, Dec 29, 2013 at 12:06 PM, Charles Mire charles.m...@gmail.comwrote: Not a total n00b, as I have played around with Django a little bit before. I've successfully installed Mezzanine 3.0.4, and everything seems to work fine on localhost. I tested some minor changes to the default settings, such as changing the Twitter feed from the default from:stephen_mcd mezzanine to from:charlesmire so I could see my own Twitter feed on the site. Once the change was saved, though, the section of the home page for the Twitter feed was blank. If I changed it back to the default from:stephen_mcd mezzanine then that feed showed up. My Twitter feed is publicly readable (i.e., no private tweets), so I'm confused why the default account shows up, but my feed doesn't. Thanks for any tips! -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Import Error on local_settings
Sounds like a python path issue. You'll see at the top of settings.py in latest Mezzanine, for consistency with Python 3.3: from __future__ import absolute_import ... which answers the questions as to what's changed. You probably need to add to sys.path somewhere or other in order to satisfy uwsgi - good luck. On Fri, Jan 3, 2014 at 10:36 AM, Tim Walzer trwal...@gmail.com wrote: I ran into a strange problem today when setting up a new project. I'm setting up a new project with Mezzanine 3.0.4, Cartridge 0.9.1 and Django 1.6.1. I am setting up the website on a Nginx - Uwsgi stack on AWS. The project was created using '*mezzanine-project -a cartridge project_name'* Now the problem is that when I try to load the site the local_settings are not imported from settings.py, so the site crashes when trying make sure that SECRET_KEY is set. When I move SECRET_KEY in to settings.py it then crashes on the DATABASES info. Now the stranger part is that when I run management commands like '*python manage.py createdb'* then local_settings is imported properly and the data in local_settings is used. This is the 3rd Mezzanine/Cartridge site that I've setup on this server/stack and the other 2 had no problem. So what could be causing this behavior? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Announcing mezzanine-admin-backup
That's brilliant Josh, nice work. I bet a lot of people will find this useful. I'll add it to the apps list. On Fri, Jan 10, 2014 at 8:58 AM, Josh Cartmell joshcar...@gmail.com wrote: I've had a couple of clients recently asking me about back up strategies. There are lots of viable and good backup strategies out there and the fabfile included with Mezzanine does some backing up as well. That in mind there is still something about an admin being able to backup a site at any time that can give some people peace of mind. To that end I created https://bitbucket.org/joshcartme/mezzanine-admin-backup. It adds /admin/backup/ which will create and respond with a zip file containing the site's current media library and a dump/copy of the database. It's probably still rough around the edges and has some caveats: - I'm fairly certain it will only work with media libraries on the local filesystem (I'm not super up on the Django storages so I'm not sure how hard this would be to generalize) - Likewise it currently only works with databses on the local filesystem (this may be pretty easy to change) - I don't have a postgres powered site around to test it on so although I think it will properly dump a postgres database, I'm not 100% certain about that If anyone thinks it's useful and wants to play with it and fork/improve/test/whatever that would be great. If there is any interest in merging this into Mezzanine that would be great or it works just fine standalone as well. In case you missed it the repo is, https://bitbucket.org/joshcartme/mezzanine-admin-backup Thanks, Josh -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Forcing Page Link to open in new window
Nothing like that at the moment. On Mon, Jan 13, 2014 at 10:48 AM, John Barham jbar...@gmail.com wrote: I have a Page Link that I'd like to open in a new window when the user clicks the URL (i.e., the equivalent of a target=_blank...) Is there a way to require this from the Mezzanine admin interface? I could achieve the same result by injecting the target attribute via jQuery after the page has loaded, but am just wondering if Mezzanine supports this. Cheers, John -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] mezzanine-project fails on html5lib version conflict
No offence taken :-)
On Mon, Jan 13, 2014 at 8:00 PM, Sebastian Heyden
sebastian.hey...@gmail.com wrote:
thank you steve!
my comment regarding the complexity was not meant to be offending, but i
am sure it actually offended you. i don't really know why its difficult to
me. but actually i can only learn from thinks i don't understand properly.
Am Sonntag, 12. Januar 2014 21:13:08 UTC+1 schrieb Stephen McDonald:
Thanks for the report.
You've uncovered a conflict in the versions of dependencies, something
that has unfortunately occurred outside of Mezzanine's codebase itself.
Mezzanine specifies it requires a particular version of html5lib, in this
case 0.95, and another of its dependencies, bleach, has recently been
updated to specify it requires a conflicting version of html5lib, in this
case = 0.999.
I'll be pushing a new version of Mezzanine shortly which should resolve
the issue.
On Mon, Jan 13, 2014 at 4:29 AM, Sebastian Heyden
sebastia...@gmail.comwrote:
hey there,
i just tried to start a mezzanine project by typing
pip install mezzanine
mezzanine-project myproject
... on ubuntu and fedora with python2.7 and python2.6 but always get
this output from the last command:
Traceback (most recent call last):
File /usr/local/bin/mezzanine-project, line 5, in module
from pkg_resources import load_entry_point
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2809,
in module
parse_requirements(__requires__), Environment()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 598,
in resolve
raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (html5lib 0.95
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('html5lib=0.999'))
I forced pip to install html5lib 0.999 and then i get the following
error message instead.
Traceback (most recent call last):
File /usr/local/bin/mezzanine-project, line 5, in module
from pkg_resources import load_entry_point
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2809,
in module
parse_requirements(__requires__), Environment()
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 594,
in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: html5lib==0.95
Makes sense so far. But what am I supposed to do now?
I have some experience with django projects and decided to take the
learning curve for mezzanine.
i had a successful installation of mezzanine from a template once on my
development machine. when i wasn't able to deploy my project on the server
due to my messy project structure, i decided to start from scratch and copy
my code in piece for piece. i couldn't find the template anymore, and
therefore i try to go down the route with mezzanine-project. is it just me
or is setting up mezzanine slightly more complicated than average?
That all depends on what your subjective experience of average is I
guess, but in my opinion Mezzanine actually goes to greater lengths than
usual in making the install process and out of the box experience easier
than usual.
cheers,
sebastian
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: [mezzanine-users] Buy Product fails if Product contains non ASCII chars
issue? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Delete Images From Gallery (Media Library)
Demo works fine for me. On Tue, Jan 14, 2014 at 9:02 AM, NOAA CREST noaacrest2...@gmail.com wrote: For some reason , i can not delete images from a media library page , I tried using the online demo and from the admin interface but it won't let me delete images. http://mezzanine.jupo.org/gallery/ http://mezzanine.jupo.org/en/admin/galleries/gallery/8/ Any suggestion , P.S you can recreate this error by just going to the link above and trying to remove an image -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] VariableDoesNotExist exception for JQUERY_UI_FILENAME
Settings available in templates are listed here:
http://mezzanine.jupo.org/docs/configuration.html#template-accessible-settings
You'll find instructions for changing it on that same page.
On Wed, Jan 15, 2014 at 8:26 AM, mapma...@gmail.com wrote:
Hi!
In mezzanine base.html template I add:
script src={% static mezzanine/js/|add:settings.JQUERY_UI_FILENAME
%}/script
This should properly retrieve the JQUERY_UI_FILENAME variable value from
mezzanine.core.defaults.py. It however does not. Here's the traceback:
http://dpaste.com/hold/1551607/
I do not overwrite the variable in my settings.py file.
Any ideas? Thanks in advance!
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: [mezzanine-users] No module named Hashcompat
The traceback shows the error comes from the django-compressor package. On Wed, Jan 15, 2014 at 11:37 AM, Darin Gillies darin.gill...@gmail.comwrote: I think everything was installed fresh, but I might have missed something. Trace attached if it helps. On Wednesday, 15 January 2014 10:18:48 UTC+13, Stephen McDonald wrote: 1.6.1 is certainly supported - it sounds like you're using some other library that isn't compatible, but only a guess is possible without looking at the full error traceback. On Wed, Jan 15, 2014 at 7:06 AM, Darin Gillies darin@gmail.comwrote: Hi all, this is my first message to the group, so apologies if I am not using it correctly. Its also entirely possible that my problem resides between the keyboard and the seat. I have tried to install mezzanine 3.0.5 on ubuntu with django 1.6.1 (Perhaps 1.6.1 is not supported yet) When I run up a server and attempt to browse the site I receive the following error message. No module named Hashcompat From a quick read, I think Hashcompat is deprecated in 1.6 Any ideas? Thanks Darin -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Announcing django-commweb
Nice work Sam, thanks for sharing! On Thu, Jan 16, 2014 at 12:42 PM, Sam Kingston s...@sjkwi.com.au wrote: Hi fellow Australian programmers, I've just released django-commweb onto PyPi ( https://pypi.python.org/pypi/django-commweb/0.1). It is a new library that intergrates Django into CommWeb, Commonwealth Bank of Australia's merchant payment service. It has Cartridge intergration out of the box, simply add the following to settings.py: SHOP_HANDLER_PAYMENT = 'commweb.cartridge_hook.cartridge_payment_handler' It's very basic at the moment, however it can make purchases using a one-step transaction. Hope it's useful to someone. Sam -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Restricting shop to active users only
I think you could just add the existing product view (and any others) to your urlpatterns, but wrapped in Django's login_required decorator - with that you'd get all the fancy redirecting to login and back to the original page. I don't think there's a strong case for including it as a setting. On Wed, Jan 22, 2014 at 2:18 PM, Eduardo Rivas jerivasmel...@gmail.comwrote: Hello Mezzaniners and Cartridgers (??). I have some very specific requirements for a project I'm working in. I would like to have shop categories available to all visitors of the site (they can browse all categories and see which products are included in each, just a thumbnail and short description). However, unauthenticated or inactive users should not be able to access the product detail page (they can't make orders either, of course). Ideally this would only require toggling a setting such as SHOP_CHECKOUT_ACCOUNT_REQUIRED, but I don't think something like that exists. My questions are: 1. Can this be done without modifying Cartridge views to check for user auth? (Monkey patch solution) 2. Would you (Steve) be open to adding a setting to control this behavior in shop.views.product, just as shop.views.checkout_steps does now? (Proper, long-term solution IMO) What do you guys think? Do you see any other solution? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] mezzanine-cartridge pic upload problem :cannot upload product image using admin account
Sounds like you're hitting a PIL/Pillow issue there - google for more info
on getting it set up correctly on whatever system you're running, it's not
really a Mezzanine specific issue.
On Wed, Jan 22, 2014 at 7:11 PM, lu zou zoulucl...@gmail.com wrote:
also when I use safari browser upload the PNG django pony picture to
create a product image it come across a decoder related problem as below :
error info:
IOError at /admin/shop/product/
decoder jpeg not available
*Error during template rendering*
In template
/Users/luzou/Documents/oztrend/cart/lib/python2.7/site-packages/grappelli_safe/templates/admin/change_list.html,
error at line *105*
*{% result_list cl %}*
traceback info:
-
-
/Users/luzou/Documents/oztrend/cart/lib/python2.7/site-packages/PIL/ImageFile.pyin
load
1. d = Image._getdecoder(self.mode, d, a,
self.decoderconfig) ...
-
▶ Local vars
-
/Users/luzou/Documents/oztrend/cart/lib/python2.7/site-packages/PIL/Image.pyin
_getdecoder
1. raise IOError(decoder %s not available % decoder_name)
...
-
▶ Local vars
On Wednesday, 22 January 2014 17:14:10 UTC+10, Stephen McDonald wrote:
That error typically occurs when there has been a problem with the
JavaScript that handles the drag/drop re-ordering.
Check your browser's JavaScript console for errors or perhaps missing
files.
On Wed, Jan 22, 2014 at 6:11 PM, lu zou zoulu...@gmail.com wrote:
when I am create a product in admin account ,if I upload the product
image ,there will be a bug ,donot why, using the default django pic ,same
problem ,all kinds of the image type I have tried to upload ,all come
across the same problem
error info:
invalid literal for int() with base 10: ''
traceback info :
-
/Users/luzou/Documents/djanproj/cartridge/src/cartridge/cartridge/shop/admin.py
in save_formset
1.
self._images_formset, change)
2. ...
▶ Local vars http://127.0.0.1:8000/admin/shop/product/2/#
-
-
/Users/luzou/Documents/djanproj/cartridge/lib/python2.7/site-packages/Mezzanine-3.0.4-py2.7.egg/mezzanine/core/models.py
in save
1.
super(Orderable, self).save(*args, **kwargs)
...
▶ Local vars http://127.0.0.1:8000/admin/shop/product/2/#
also when upload pic from the media library(which have been uploaded into
already ) into gallery
same error:
invalid literal for int() with base 10: ''
-
/Users/luzou/Documents/djanproj/cartridge/lib/
python2.7/site-packages/Mezzanine-3.0.4-py2.7.egg/
mezzanine/pages/admin.py in change_view
1.
return super(PageAdmin, self).change_view(request, object_id,
**kwargs)
...
▶ Local vars http://127.0.0.1:8000/admin/galleries/gallery/8/#
- /Users/luzou/Documents/djanproj/cartridge/lib/
python2.7/site-packages/Mezzanine-3.0.4-py2.7.egg/
mezzanine/galleries/models.py in save
1.
super(GalleryImage, self).save(*args, **kwargs)
...
▶ Local vars http://127.0.0.1:8000/admin/galleries/gallery/8/#
- /Users/luzou/Documents/djanproj/cartridge/lib/
python2.7/site-packages/Mezzanine-3.0.4-py2.7.egg/
mezzanine/core/models.py in save
1.
super(Orderable, self).save(*args, **kwargs)
...
▶ Local vars http://127.0.0.1:8000/admin/galleries/gallery/8/#
-
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: [mezzanine-users] Move mezzanine site to another server
On Wed, Jan 22, 2014 at 7:44 PM, inglor artafi...@gmail.com wrote: Hello, I want to move a mezzanine server from to another box. I'd like to do that with the minimum downtime if possible. The current server setup wasn't from me but seems like it's a standard mezzanine setup described in docs. What's the best approach? There's nothing specific to Mezzanine as far as this goes - it's the same process as it would be for any database driven website. I just searched Google for transfer website without downtime and found tons of answers. Also since I'm new to mezzanine, what do you recommend on standard production setup for mezzanine? The docs mention something about deployment but it's fairly vague. This question is even more vague than the docs you're referring to :-) 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] error occur when applying discount code when checking out or simply applying it before check out
I also tried to quickly reproduce it, without any luck - it looks like it may be when the discount code is put into the session, but without the full traceback no one knows. I also can't stress the importance of providing a detailed description of the steps you've taken to cause the error. Please go into as much detail as possible when writing up the issue, thanks. On Wed, Jan 22, 2014 at 10:54 PM, Stephen McDonald st...@jupo.org wrote: How about providing the whole traceback instead of half of it? It looks like a valid bug - Django 1.6.1 sessions are now backed by JSON instead of pickle objects, and there were some similar looking issues around that. Please go ahead and open a new issue with the full traceback: https://github.com/stephenmcd/cartridge/issues On Wed, Jan 22, 2014 at 10:21 PM, lu zou zoulucl...@gmail.com wrote: error occur when click the APPLY button to apply the discount code when purchasing the product , having set the discount code correctly in admin account error info: django.utils.functional.__proxy__ object at 0x1033c4590 is not JSON serializable traceback info: - /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py in dumps 1. **kw).encode(obj) ... ▶ Local vars http://127.0.0.1:8000/shop/checkout/# - /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/encoder.py in encode 1. chunks = self.iterencode(o, _one_shot=True) ... ▶ Local vars http://127.0.0.1:8000/shop/checkout/# - /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/encoder.py in iterencode 1. return _iterencode(o, 0) ... ▶ Local vars http://127.0.0.1:8000/shop/checkout/# - /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/encoder.py in default 1. raise TypeError(repr(o) + is not JSON serializable) ... ▶ Local vars http://127.0.0.1:8000/shop/checkout/# -- 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/groups/opt_out. -- Stephen McDonald http://jupo.org -- 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/groups/opt_out.
Re: [mezzanine-users] Re: Invalid input syntax for type inet on comment save
Thanks Josh - fixed here:
https://github.com/stephenmcd/mezzanine/commit/9f8a125bdb74f24664d9939ca63fa2876cebbd9c
On Thu, Jan 23, 2014 at 6:37 AM, Josh Cartmell joshcar...@gmail.com wrote:
Ok, I dug into this more and the IP that is trying to be saved is coming
from mezzanine.utils.views.ip_for_request. I just monkey patched it like
this:
def new_ip_for_request(request):
Returns ip address for request - first checks ``HTTP_X_FORWARDED_FOR``
header, since app will generally be behind a public web server.
meta = request.META
ip = meta.get(HTTP_X_FORWARDED_FOR,
meta[REMOTE_ADDR]).split(',')[0]
return ip
views.ip_for_request = new_ip_for_request
A comment in the code of the What's middleware section of
http://www.djangobook.com/en/2.0/chapter17.html says that
HTTP_X_FORWARDED_FOR can be a comma separated list of ips, in my case it
was, which was causing the error.
Does anyone else have thoughts on this? I'm thinking we should update the
ip_for_request in Mezzanine.
On Wed, Jan 22, 2014 at 10:29 AM, Josh Cartmell joshcar...@gmail.comwrote:
I have a Mezzanine site I put up recently and occasionally when someone
tries to save a comment the following error is produced:
Traceback (most recent call last):
File .../site-packages/django/core/handlers/base.py, line 114, in
get_response
response = wrapped_callback(request, *callback_args,
**callback_kwargs)
File .../site-packages/mezzanine/generic/views.py, line 98, in comment
comment = form.save(request)
File .../site-packages/mezzanine/generic/forms.py, line 133, in save
comment.save()
File .../site-packages/mezzanine/generic/models.py, line 56, in save
super(ThreadedComment, self).save(*args, **kwargs)
File .../site-packages/django/contrib/comments/models.py, line 88, in
save
super(Comment, self).save(*args, **kwargs)
File .../site-packages/django/db/models/base.py, line 545, in save
force_update=force_update, update_fields=update_fields)
File .../site-packages/django/db/models/base.py, line 572, in
save_base
self._save_parents(cls, using, update_fields)
File .../site-packages/django/db/models/base.py, line 597, in
_save_parents
self._save_table(cls=parent, using=using, update_fields=update_fields)
File .../site-packages/django/db/models/base.py, line 654, in
_save_table
result = self._do_insert(cls._base_manager, using, fields, update_pk,
raw)
File .../site-packages/django/db/models/base.py, line 687, in
_do_insert
using=using, raw=raw)
File .../site-packages/django/db/models/manager.py, line 232, in
_insert
return insert_query(self.model, objs, fields, **kwargs)
File .../site-packages/django/db/models/query.py, line 1511, in
insert_query
return query.get_compiler(using=using).execute_sql(return_id)
File .../site-packages/django/db/models/sql/compiler.py, line 898, in
execute_sql
cursor.execute(sql, params)
File .../site-packages/django/db/backends/util.py, line 53, in execute
return self.cursor.execute(sql, params)
File .../site-packages/django/db/utils.py, line 99, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File .../site-packages/django/db/backends/util.py, line 53, in execute
return self.cursor.execute(sql, params)
DataError: invalid input syntax for type inet: xxx.xxx.xx.xxx,
xxx.xxx.xxx.xxx
LINE 5: ...your name.', E'2014-01-22 18:23:28.661696+00:00', E'xxx.xxx
I've redacted the actual IP address. I'm geussing that it has something
to do with the presence of two address (that's just speculation). Has
anyone else ever seen this? Or does anyone else have any ideas about what
is going on or how I could prevent it?
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: [mezzanine-users] HOST_THEMES working example?
I'd suggest checking the debugging instructions I provided on the github issue and following through with those. On Thu, Jan 23, 2014 at 7:31 AM, Radomir Wojcik radzh...@gmail.com wrote: to be importable the name has to be valid i.e. no periods and the __init__.py file is required. Is there anything else I should check? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] FIle upload permissions
The value is octal which requires the o in Python 3: $ python Python 2.7.1 (r271:86832, Jul 31 2011, 19:30:53) [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin Type help, copyright, credits or license for more information. 0644 420 0o644 420 $ python3 Python 3.3.2 (default, Nov 4 2013, 18:05:17) [GCC 4.2.1 Compatible Apple Clang 3.0 (tags/Apple/clang-211.12)] on darwin Type help, copyright, credits or license for more information. 0644 File stdin, line 1 0644 ^ SyntaxError: invalid token 0o644 420 On Thu, Jan 23, 2014 at 12:13 PM, nathan maier.nat...@gmail.com wrote: Hi, been a while since I upgraded mezzanine. While changing settings.py, I noticed the FILE_UPLOAD_PERMISSIONS = 0o644 instead of 0644. Am I mistaken or is this a typo. Just a quick check. Trying to be helpful. -Nate -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] make the main page(index.html) changed into the shopping page (category.html)
I would look at making the homepage a page object in the page tree - this
page could be a shop category, which is a type of page itself.
http://mezzanine.jupo.org/docs/frequently-asked-questions.html#why-isn-t-the-homepage-a-page-object-i-can-edit-via-the-admin
On Fri, Jan 31, 2014 at 10:15 AM, lu zou zoulucl...@gmail.com wrote:
using mezzanine and cartridge: want to make the main page (index,html)
into the shopping main page(category.html ) ,using shopping main page as
the main page
this code below doesnot work ,have any suggestion ,seems a easy
question ,but I have tried for long , using a lot of alternative, they
donot word:(
url(^$, page, {slug: /, template:
../../mezzanine_themes/oztrend/templates/pages/category.html },
name=home),
PS :
../../mezzanine_themes/oztrend/templates/pages/category.html
---is where category.html located
--
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/groups/opt_out.
--
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/groups/opt_out.
Re: [mezzanine-users] serve media files on my local development server
nothing. On my productiv Debian 6 Server, everything works perfect. But locally I just get an A server error occurred. Please contact the administrator. What else can I try to solve this? -- 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. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out. -- 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/SnSEsx0g3lo/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/groups/opt_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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Why is PIL/Pillow not a dependency?
Pillow should get installed automatically if neither are available: https://github.com/stephenmcd/mezzanine/blob/master/setup.py#L37-L45 On Thu, Feb 13, 2014 at 7:12 AM, Eduardo Rivas jerivasmel...@gmail.comwrote: Hi everyone. Every time I try to create a new project with some initial data I run: python manage.py createdb --noinput Which fails with the following error: django.core.exceptions.ImproperlyConfigured: Neither Pillow nor PIL could be imported: No module named Image That is very explicit and simply requires running pip install pillow to get if fixed. However, my questions are: Why is pillow needed during the createdb process? How necessary is it to Mezzanine? Shouldn't it be a dependency? I don't know if I've found a bug, or maybe there's some obvious reason I'm overlooking. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Why is PIL/Pillow not a dependency?
I can't reproduce it and pillow installs each time for me - although I don't use virtualenvwrapper: $ virtualenv --distribute foo On Thu, Feb 13, 2014 at 7:44 AM, Eduardo Rivas jerivasmel...@gmail.comwrote: I tried it in a blank venv: mkvirtualenv foobar pip install mezzanine cartridge ... Successfully installed mezzanine bleach requests-oauthlib django tzlocal future grappelli-safe filebrowser-safe requests six html5lib oauthlib pytz cartridge pisa mezzanine-project -a cartridge foobar cd foobar/ python manage.py createdb --noinput And I get the same error as before. If I start the project with Mezzanine's default template (no -a cartridge option), I get another error from mezzanine_tags.py, but also related to Image. Can you reproduce the steps? Is it something only in my end? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Why is PIL/Pillow not a dependency?
Looks like my stuff is really out of date which might explain the difference: (lol2) $ pip --version pip 1.0.2 from /Users/steve/dev/lol2/lib/python2.7/site-packages/pip-1.0.2-py2.7.egg (python 2.7) (lol2) $ deactivate $ pip --version pip 1.1 from /Library/Python/2.7/site-packages (python 2.7) $ virtualenv --version 1.7 On Thu, Feb 13, 2014 at 10:25 AM, Eduardo Rivas jerivasmel...@gmail.comwrote: I tried it without venvwrapper and still the same, no pillow when installing from pip. virtualenv foobar source foobar/bin/activate pip install mezzanine Could it be the version of virtualenv or the env's pip? virtualenv --version 1.11.2 pip --version pip 1.5.2 from foobar/local/lib/python2.7/site-packages (python 2.7) BTW, the --distribute option has been deprecated. See the third list item here: http://www.virtualenv.org/en/latest/news.html?highlight= distribute#id5 -- 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/groups/opt_out. -- 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/groups/opt_out.
[mezzanine-users] Admin navigation
Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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/groups/opt_out.
Re: [mezzanine-users] Admin navigation
On Tue, Feb 18, 2014 at 5:10 AM, Josh Cartmell joshcar...@gmail.com wrote: Hey Steve, that looks pretty cool! I agree with Luc that it would be nice to make it collapse able. It also might be nice if the menu scrolled independently from the rest of the page. Last question, what happens on smaller screens? Not sure, just experimenting at this stage. Kinda hitting the limits of my front-end capabilities, so I might get a basic version working and if others are able to improve on it it'd be great. On Mon, Feb 17, 2014 at 12:23 AM, Luc Milland l...@hekenet.com wrote: Hello, I think it's great, since most of the people have wide screens nowadays. Maybe it would be cool if submenus were toggleable, since the list can become very long when using custom and third party apps. Luc Le lundi 17 février 2014 à 12:01 +1100, Stephen McDonald a écrit : Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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/groups/opt_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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] jquery resize error
Any hints on how to reproduce? On Tue, Feb 18, 2014 at 11:59 AM, Ross Laird r...@rosslaird.com wrote: I'm getting a javascript error (Uncaught TypeError: cannot set property of 'w' undefined) with jquery.ba-resize.js, which is included in the default Mezzanine setup. There is an open issuehttps://github.com/cowboy/jquery-resize/issues/1 about this at the jquery-resize repo, but it seems that the repo has not been updated in four years. Anybody else have this issue, or any thoughts about updating this add-on for Mezzanine? -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Admin navigation
I've just pushed up an initial version of this and am desperately seeking assistance in finishing it: https://github.com/stephenmcd/mezzanine/commit/6fcba4b31e4a9f21275cd22774d8ac24d3342668 The main problem at the moment is that messages invalid login, you've saved foo, etc are completely borked. This is the showstopper. Lastly and of less importance, there's no interactivity - hover states, active nav, nothing - the entire thing is static. Would be nice to have some basic aspects around that working. Further to this, we could have some more ux around it where only the currently viewed section (eg Content, Blog, Site, etc) is open, and the other sections open when clicked on - only one should be open at any time perhaps? We could also use some toggle buttons, for showing/hiding the menu (default should be open, perhaps only if the screen is wide), and separately, toggling the sections being collapsed or expanded. There's a lot of work to be done here and I don't really have the front-end skill nor the time available right now to see it through. Who can help out? On Tue, Feb 18, 2014 at 10:14 AM, Stephen McDonald st...@jupo.org wrote: On Tue, Feb 18, 2014 at 5:10 AM, Josh Cartmell joshcar...@gmail.comwrote: Hey Steve, that looks pretty cool! I agree with Luc that it would be nice to make it collapse able. It also might be nice if the menu scrolled independently from the rest of the page. Last question, what happens on smaller screens? Not sure, just experimenting at this stage. Kinda hitting the limits of my front-end capabilities, so I might get a basic version working and if others are able to improve on it it'd be great. On Mon, Feb 17, 2014 at 12:23 AM, Luc Milland l...@hekenet.com wrote: Hello, I think it's great, since most of the people have wide screens nowadays. Maybe it would be cool if submenus were toggleable, since the list can become very long when using custom and third party apps. Luc Le lundi 17 février 2014 à 12:01 +1100, Stephen McDonald a écrit : Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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/groups/opt_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/groups/opt_out. -- Stephen McDonald http://jupo.org -- 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/groups/opt_out.
Re: [mezzanine-users] Admin navigation
Don't really have one - is there any reason not to modify it? If not, go for it. On Sun, Feb 23, 2014 at 1:42 PM, Josh B josh.batche...@wearetopsecret.comwrote: Stephen, what is your stance on modifying the admin/base.html? On Saturday, February 22, 2014 7:30:30 PM UTC-7, Josh B wrote: I don't have a ton of time, but I will take a look and fix a couple of things. On Saturday, February 22, 2014 12:35:26 AM UTC-7, Stephen McDonald wrote: I've just pushed up an initial version of this and am desperately seeking assistance in finishing it: https://github.com/stephenmcd/mezzanine/commit/ 6fcba4b31e4a9f21275cd22774d8ac24d3342668 The main problem at the moment is that messages invalid login, you've saved foo, etc are completely borked. This is the showstopper. Lastly and of less importance, there's no interactivity - hover states, active nav, nothing - the entire thing is static. Would be nice to have some basic aspects around that working. Further to this, we could have some more ux around it where only the currently viewed section (eg Content, Blog, Site, etc) is open, and the other sections open when clicked on - only one should be open at any time perhaps? We could also use some toggle buttons, for showing/hiding the menu (default should be open, perhaps only if the screen is wide), and separately, toggling the sections being collapsed or expanded. There's a lot of work to be done here and I don't really have the front-end skill nor the time available right now to see it through. Who can help out? On Tue, Feb 18, 2014 at 10:14 AM, Stephen McDonald st...@jupo.orgwrote: On Tue, Feb 18, 2014 at 5:10 AM, Josh Cartmell joshc...@gmail.comwrote: Hey Steve, that looks pretty cool! I agree with Luc that it would be nice to make it collapse able. It also might be nice if the menu scrolled independently from the rest of the page. Last question, what happens on smaller screens? Not sure, just experimenting at this stage. Kinda hitting the limits of my front-end capabilities, so I might get a basic version working and if others are able to improve on it it'd be great. On Mon, Feb 17, 2014 at 12:23 AM, Luc Milland l...@hekenet.comwrote: Hello, I think it's great, since most of the people have wide screens nowadays. Maybe it would be cool if submenus were toggleable, since the list can become very long when using custom and third party apps. Luc Le lundi 17 février 2014 à 12:01 +1100, Stephen McDonald a écrit : Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Stephen McDonald http://jupo.org -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Admin navigation
Sounds like a great idea, wanna kick it off? On Mon, Feb 24, 2014 at 9:08 AM, Josh Cartmell joshcar...@gmail.com wrote: I'd like to try to help as well, would there be any way to put a static version up on jsfiddle or codepen so that we could easily play with the js and iterate? On Sat, Feb 22, 2014 at 6:44 PM, Stephen McDonald st...@jupo.org wrote: Don't really have one - is there any reason not to modify it? If not, go for it. On Sun, Feb 23, 2014 at 1:42 PM, Josh B josh.batche...@wearetopsecret.com wrote: Stephen, what is your stance on modifying the admin/base.html? On Saturday, February 22, 2014 7:30:30 PM UTC-7, Josh B wrote: I don't have a ton of time, but I will take a look and fix a couple of things. On Saturday, February 22, 2014 12:35:26 AM UTC-7, Stephen McDonald wrote: I've just pushed up an initial version of this and am desperately seeking assistance in finishing it: https://github.com/stephenmcd/mezzanine/commit/ 6fcba4b31e4a9f21275cd22774d8ac24d3342668 The main problem at the moment is that messages invalid login, you've saved foo, etc are completely borked. This is the showstopper. Lastly and of less importance, there's no interactivity - hover states, active nav, nothing - the entire thing is static. Would be nice to have some basic aspects around that working. Further to this, we could have some more ux around it where only the currently viewed section (eg Content, Blog, Site, etc) is open, and the other sections open when clicked on - only one should be open at any time perhaps? We could also use some toggle buttons, for showing/hiding the menu (default should be open, perhaps only if the screen is wide), and separately, toggling the sections being collapsed or expanded. There's a lot of work to be done here and I don't really have the front-end skill nor the time available right now to see it through. Who can help out? On Tue, Feb 18, 2014 at 10:14 AM, Stephen McDonald st...@jupo.orgwrote: On Tue, Feb 18, 2014 at 5:10 AM, Josh Cartmell joshc...@gmail.comwrote: Hey Steve, that looks pretty cool! I agree with Luc that it would be nice to make it collapse able. It also might be nice if the menu scrolled independently from the rest of the page. Last question, what happens on smaller screens? Not sure, just experimenting at this stage. Kinda hitting the limits of my front-end capabilities, so I might get a basic version working and if others are able to improve on it it'd be great. On Mon, Feb 17, 2014 at 12:23 AM, Luc Milland l...@hekenet.comwrote: Hello, I think it's great, since most of the people have wide screens nowadays. Maybe it would be cool if submenus were toggleable, since the list can become very long when using custom and third party apps. Luc Le lundi 17 février 2014 à 12:01 +1100, Stephen McDonald a écrit : Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Stephen McDonald http://jupo.org -- 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/groups/opt_out. -- 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/groups/opt_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/groups/opt_out. -- Stephen McDonald http://jupo.org -- You received
Re: [mezzanine-users] Admin navigation
Thanks a lot Josh! Not sure if it's intended bit it still looks a bit off on my end: http://cl.ly/image/1q2H0E1Y1w0w My browser is Chrome 34.0.1847.3 On Mon, Feb 24, 2014 at 4:10 PM, Josh B josh.batche...@wearetopsecret.comwrote: I just opened a Pull Request for the messages issue. Haven't had a chance to look into the collapsing navigation. Let me know if you have time to take care of that Josh. If not I might have some time tomorrow. On Sunday, February 23, 2014 4:05:51 PM UTC-7, Stephen McDonald wrote: Sounds like a great idea, wanna kick it off? On Mon, Feb 24, 2014 at 9:08 AM, Josh Cartmell joshc...@gmail.comwrote: I'd like to try to help as well, would there be any way to put a static version up on jsfiddle or codepen so that we could easily play with the js and iterate? On Sat, Feb 22, 2014 at 6:44 PM, Stephen McDonald st...@jupo.orgwrote: Don't really have one - is there any reason not to modify it? If not, go for it. On Sun, Feb 23, 2014 at 1:42 PM, Josh B josh.ba...@wearetopsecret.comwrote: Stephen, what is your stance on modifying the admin/base.html? On Saturday, February 22, 2014 7:30:30 PM UTC-7, Josh B wrote: I don't have a ton of time, but I will take a look and fix a couple of things. On Saturday, February 22, 2014 12:35:26 AM UTC-7, Stephen McDonald wrote: I've just pushed up an initial version of this and am desperately seeking assistance in finishing it: https://github.com/stephenmcd/mezzanine/commit/6fcba4b31e4a9 f21275cd22774d8ac24d3342668 The main problem at the moment is that messages invalid login, you've saved foo, etc are completely borked. This is the showstopper. Lastly and of less importance, there's no interactivity - hover states, active nav, nothing - the entire thing is static. Would be nice to have some basic aspects around that working. Further to this, we could have some more ux around it where only the currently viewed section (eg Content, Blog, Site, etc) is open, and the other sections open when clicked on - only one should be open at any time perhaps? We could also use some toggle buttons, for showing/hiding the menu (default should be open, perhaps only if the screen is wide), and separately, toggling the sections being collapsed or expanded. There's a lot of work to be done here and I don't really have the front-end skill nor the time available right now to see it through. Who can help out? On Tue, Feb 18, 2014 at 10:14 AM, Stephen McDonald st...@jupo.orgwrote: On Tue, Feb 18, 2014 at 5:10 AM, Josh Cartmell joshc...@gmail.comwrote: Hey Steve, that looks pretty cool! I agree with Luc that it would be nice to make it collapse able. It also might be nice if the menu scrolled independently from the rest of the page. Last question, what happens on smaller screens? Not sure, just experimenting at this stage. Kinda hitting the limits of my front-end capabilities, so I might get a basic version working and if others are able to improve on it it'd be great. On Mon, Feb 17, 2014 at 12:23 AM, Luc Milland l...@hekenet.comwrote: Hello, I think it's great, since most of the people have wide screens nowadays. Maybe it would be cool if submenus were toggleable, since the list can become very long when using custom and third party apps. Luc Le lundi 17 février 2014 à 12:01 +1100, Stephen McDonald a écrit : Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Stephen McDonald http://jupo.org -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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
Re: [mezzanine-users] Admin navigation
Ahhh I'm sorry, I just cleared my cache and it mostly looks right: http://cl.ly/image/1s2j3B121Q3U On Mon, Feb 24, 2014 at 4:17 PM, Josh B josh.batche...@wearetopsecret.comwrote: My bad, forgot to fix the error message once logged in. Give me a minute. On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen McDonald wrote: Thanks a lot Josh! Not sure if it's intended bit it still looks a bit off on my end: http://cl.ly/image/1q2H0E1Y1w0w My browser is Chrome 34.0.1847.3 On Mon, Feb 24, 2014 at 4:10 PM, Josh B josh.ba...@wearetopsecret.comwrote: I just opened a Pull Request for the messages issue. Haven't had a chance to look into the collapsing navigation. Let me know if you have time to take care of that Josh. If not I might have some time tomorrow. On Sunday, February 23, 2014 4:05:51 PM UTC-7, Stephen McDonald wrote: Sounds like a great idea, wanna kick it off? On Mon, Feb 24, 2014 at 9:08 AM, Josh Cartmell joshc...@gmail.comwrote: I'd like to try to help as well, would there be any way to put a static version up on jsfiddle or codepen so that we could easily play with the js and iterate? On Sat, Feb 22, 2014 at 6:44 PM, Stephen McDonald st...@jupo.orgwrote: Don't really have one - is there any reason not to modify it? If not, go for it. On Sun, Feb 23, 2014 at 1:42 PM, Josh B josh.ba...@ wearetopsecret.com wrote: Stephen, what is your stance on modifying the admin/base.html? On Saturday, February 22, 2014 7:30:30 PM UTC-7, Josh B wrote: I don't have a ton of time, but I will take a look and fix a couple of things. On Saturday, February 22, 2014 12:35:26 AM UTC-7, Stephen McDonald wrote: I've just pushed up an initial version of this and am desperately seeking assistance in finishing it: https://github.com/stephenmcd/mezzanine/commit/6fcba4b31e4a9 f21275cd22774d8ac24d3342668 The main problem at the moment is that messages invalid login, you've saved foo, etc are completely borked. This is the showstopper. Lastly and of less importance, there's no interactivity - hover states, active nav, nothing - the entire thing is static. Would be nice to have some basic aspects around that working. Further to this, we could have some more ux around it where only the currently viewed section (eg Content, Blog, Site, etc) is open, and the other sections open when clicked on - only one should be open at any time perhaps? We could also use some toggle buttons, for showing/hiding the menu (default should be open, perhaps only if the screen is wide), and separately, toggling the sections being collapsed or expanded. There's a lot of work to be done here and I don't really have the front-end skill nor the time available right now to see it through. Who can help out? On Tue, Feb 18, 2014 at 10:14 AM, Stephen McDonald st...@jupo.org wrote: On Tue, Feb 18, 2014 at 5:10 AM, Josh Cartmell joshc...@gmail.com wrote: Hey Steve, that looks pretty cool! I agree with Luc that it would be nice to make it collapse able. It also might be nice if the menu scrolled independently from the rest of the page. Last question, what happens on smaller screens? Not sure, just experimenting at this stage. Kinda hitting the limits of my front-end capabilities, so I might get a basic version working and if others are able to improve on it it'd be great. On Mon, Feb 17, 2014 at 12:23 AM, Luc Milland l...@hekenet.comwrote: Hello, I think it's great, since most of the people have wide screens nowadays. Maybe it would be cool if submenus were toggleable, since the list can become very long when using custom and third party apps. Luc Le lundi 17 février 2014 à 12:01 +1100, Stephen McDonald a écrit : Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/grou ps/opt_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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out . -- Stephen McDonald http://jupo.org -- 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
Re: [mezzanine-users] Admin navigation
Yep but I've just fixed that locally and will push in a sec so don't sweat it. Thanks again, really exciting to give the admin a dress up! On Mon, Feb 24, 2014 at 4:21 PM, Josh B josh.batche...@wearetopsecret.comwrote: Did you want it to butt up to the top or? On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald wrote: Ahhh I'm sorry, I just cleared my cache and it mostly looks right: http://cl.ly/image/1s2j3B121Q3U On Mon, Feb 24, 2014 at 4:17 PM, Josh B josh.ba...@wearetopsecret.comwrote: My bad, forgot to fix the error message once logged in. Give me a minute. On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen McDonald wrote: Thanks a lot Josh! Not sure if it's intended bit it still looks a bit off on my end: http://cl.ly/image/1q2H0E1Y1w0w My browser is Chrome 34.0.1847.3 On Mon, Feb 24, 2014 at 4:10 PM, Josh B josh.ba...@wearetopsecret.comwrote: I just opened a Pull Request for the messages issue. Haven't had a chance to look into the collapsing navigation. Let me know if you have time to take care of that Josh. If not I might have some time tomorrow. On Sunday, February 23, 2014 4:05:51 PM UTC-7, Stephen McDonald wrote: Sounds like a great idea, wanna kick it off? On Mon, Feb 24, 2014 at 9:08 AM, Josh Cartmell joshc...@gmail.comwrote: I'd like to try to help as well, would there be any way to put a static version up on jsfiddle or codepen so that we could easily play with the js and iterate? On Sat, Feb 22, 2014 at 6:44 PM, Stephen McDonald st...@jupo.orgwrote: Don't really have one - is there any reason not to modify it? If not, go for it. On Sun, Feb 23, 2014 at 1:42 PM, Josh B josh.ba...@ wearetopsecret.com wrote: Stephen, what is your stance on modifying the admin/base.html? On Saturday, February 22, 2014 7:30:30 PM UTC-7, Josh B wrote: I don't have a ton of time, but I will take a look and fix a couple of things. On Saturday, February 22, 2014 12:35:26 AM UTC-7, Stephen McDonald wrote: I've just pushed up an initial version of this and am desperately seeking assistance in finishing it: https://github.com/stephenmcd/mezzanine/commit/6fcba4b31e4a9 f21275cd22774d8ac24d3342668 The main problem at the moment is that messages invalid login, you've saved foo, etc are completely borked. This is the showstopper. Lastly and of less importance, there's no interactivity - hover states, active nav, nothing - the entire thing is static. Would be nice to have some basic aspects around that working. Further to this, we could have some more ux around it where only the currently viewed section (eg Content, Blog, Site, etc) is open, and the other sections open when clicked on - only one should be open at any time perhaps? We could also use some toggle buttons, for showing/hiding the menu (default should be open, perhaps only if the screen is wide), and separately, toggling the sections being collapsed or expanded. There's a lot of work to be done here and I don't really have the front-end skill nor the time available right now to see it through. Who can help out? On Tue, Feb 18, 2014 at 10:14 AM, Stephen McDonald st...@jupo.org wrote: On Tue, Feb 18, 2014 at 5:10 AM, Josh Cartmell joshc...@gmail.com wrote: Hey Steve, that looks pretty cool! I agree with Luc that it would be nice to make it collapse able. It also might be nice if the menu scrolled independently from the rest of the page. Last question, what happens on smaller screens? Not sure, just experimenting at this stage. Kinda hitting the limits of my front-end capabilities, so I might get a basic version working and if others are able to improve on it it'd be great. On Mon, Feb 17, 2014 at 12:23 AM, Luc Milland l...@hekenet.com wrote: Hello, I think it's great, since most of the people have wide screens nowadays. Maybe it would be cool if submenus were toggleable, since the list can become very long when using custom and third party apps. Luc Le lundi 17 février 2014 à 12:01 +1100, Stephen McDonald a écrit : Playing around with restyling the nav menu in the admin: http://cl.ly/image/3519242k1m0K The nav menu contains the admin classes grouped by app - previously it was implemented as light grey drop-down menus across the top of the screen. You'll see I've moved everything to the left-hand side, with all items permanently visible. What do you think? -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/grou ps/opt_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
Re: [mezzanine-users] Admin navigation
That's awesome - I think next we'd need to figure out how to have the
current section you're on open by default.
On Wed, Feb 26, 2014 at 8:42 AM, Josh Cartmell joshcar...@gmail.com wrote:
Ok, just added some js, take a look at
http://codepen.io/joshcartme/full/wtkrF (that's a different url than the
first one because I was running into some sort of caching issue with
codepen).
JS hides all the dropdowns to start, then clicking a heading either takes
you to it's link or opens it's dropdown (if it has any). If you click a
heading of an open dropdown it goes to the link of that heading. Clicking
a different heading closes any currently open dropdowns.
How does this look?
On Tue, Feb 25, 2014 at 1:21 PM, Josh B josh.batche...@wearetopsecret.com
wrote:
I haven't been able to jump back on it. So feel free.
On Tuesday, February 25, 2014 2:07:11 PM UTC-7, Josh Cartmell wrote:
Yeah, although it ended up being a small CSS change it took me quite a
bit of messing around to get it looking like that.
I think putting the selectors in the top bar is a great idea and using
the js to do it sounds like a simple enough solution.
Is anyone working on collapsible nav at this point? I'll take a stab at
it if not.
On Tue, Feb 25, 2014 at 11:25 AM, Stephen McDonald st...@jupo.orgwrote:
Nice, I had a ton of trouble with the full height and scrollbars so
glad that's better.
I think the lang and site selectors should probably go up into the
existing top nav on the right-hand side but to the left of the existing
buttons.
Easiest way to do that might be at the top of navigation.js where we
are already moving a bunch of elements around using jQuery rather than
trying to repurpose the layers of templates between
django/grappelli/mezzanine.
On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell joshc...@gmail.comwrote:
Ok, I took a look and I did create a codepen so that anyone can look
at/edit it really easily. Here is the pen (you can edit it by clicking
the
link in the bottom left):
http://codepen.io/joshcartme/full/wIcxp
(I hotlinked the css/js files from the dev site, hopefully that's not
a big deal Steve).
So far my only css change is:
.dropdown-menu{
overflow: auto;
height: 100%;
}
To make it so there is only a scrollbar if needed and so that the
sidebar spans the full page width. I also moved the language selector
dropdown to the top and made it an element in the ul.
Thoughts?
On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald st...@jupo.orgwrote:
Guess not. You can probably just fork and start committing.
BTW I've pushed up the latest commits to the demo site (
http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can
login to its admin and see the current state of the new menu plus other
visual tweaks - so if anyone who has a moment to try out their particular
browser (eg I've no idea how this renders in IE) and provide any feedback
that'd be great!
On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell joshc...@gmail.comwrote:
Well, it looks like you guys worked this out in the meantime (I
haven't tried it yet myself) so I'm guessing jsfiddle/codepen would be
unnecessary at this point?
Thanks Josh!
On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald st...@jupo.orgwrote:
Nothing comes to mind but if you have any ideas where we can
easily (eg with a light touch) improve the usability and look of it
then
definitely bring them up!
I had my eye on this style of left-hand nav that the wordpress
admin uses for quite a while, and recently I saw a comment on reddit or
some site describing Mezzanine's admin + grappelli as looking tired
and old
compared to newer CMSes and I couldn't help but agree. So the
left-hand nav
is an attempt to improve things there. You might notice I also tried to
increase font sizes everywhere, but I tried to do this in a way where I
didn't touch anything in grappelli which was only partially
successful. I
think one of the main usability issues currently is the tiny fonts
everywhere.
On Mon, Feb 24, 2014 at 4:24 PM, Josh B josh.ba...@
wearetopsecret.com wrote:
Sounds good, besides the collapsible menu is there other things
you want to do to the admin?
On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald
wrote:
Yep but I've just fixed that locally and will push in a sec so
don't sweat it.
Thanks again, really exciting to give the admin a dress up!
On Mon, Feb 24, 2014 at 4:21 PM, Josh B josh.ba...@
wearetopsecret.com wrote:
Did you want it to butt up to the top or?
On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald
wrote:
Ahhh I'm sorry, I just cleared my cache and it mostly looks
right:
http://cl.ly/image/1s2j3B121Q3U
On Mon, Feb 24, 2014 at 4:17 PM, Josh B josh.ba...@
wearetopsecret.com wrote:
My bad, forgot to fix the error message once logged in. Give
me a minute.
On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen
Re: [mezzanine-users] Re: Current approaches to multiple Product types in Cartridge
There's an old outdated pull request that implemented something like what you're talking about here: https://github.com/stephenmcd/cartridge/pull/57 If I recall it applies a similar approach to Mezzanine's pages where concrete inheritance stems from a base product, allowing custom product subclasses. I'm not sure if that code's too out of date to use, or can be revived - I suspect the latter, but if you're keen to get involved with this, that would be your best starting point. Josh's link to our recent discussion on option types is also very relevant - I think custom product types would shape addressing some of the problems there too. On Thu, Feb 27, 2014 at 5:03 AM, Paul Walsh paulywa...@gmail.com wrote: The thing I'm wondering is - has anyone gone down this path before with Cartridge (subclassing for distinct product types), and, if yes, do other parts of the application need patching to support it. On Wednesday, 26 February 2014 19:22:44 UTC+2, Josh B wrote: Based on what you described I think subclassing is your best bet. Variations currently have some limitations and I don't think would accomplish what you are trying to do. (https://groups.google.com/ forum/#!topic/mezzanine-users/kYzgBKcwSsg) On Wednesday, February 26, 2014 4:40:19 AM UTC-7, Paul Walsh wrote: And, BTW, I don't mind coding something in this direction (for example, subclasses of Product) if it is a common pain-point for other users in Cartridge, but first, I want to see that I understand the current implementation, and how people are using it. On Wednesday, 26 February 2014 13:37:00 UTC+2, Paul Walsh wrote: Hi, I posted something similar a while back: https://groups.google.com/forum/#!topic/mezzanine-users/-ltMQLoS8Jo But now it is getting to the stage where I'm actually going to rebuild a store and move off Satchmo, starting next week. I've reassessed the options in Python land, and I'm mostly happy with Cartridge, except for the issue of different product types. I want to check I'm not missing anything here, and hopefully hear from others who have similar stores on Cartridge. I have at least 4 product types, let's say they all share 7-8 attributes common to all products, and each have another 5-10 attributes that are unique to each Product type. The implementation of product variations/options is a way to go about it, I suppose, but it really seems most suited for variations of one product type, and not for a range of different product types. Ultimately, what I'd like to get to is a set of distinct models: Book, Accessory, Poster, TShirt - etc - for the content editor, and also for the visitor - I'm not sure how to achieve that with what I see in Cartridge. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] HOST_THEMES working sample
It's really went written Jeff, thanks a lot. Will definitely merge in soon. On Fri, Feb 28, 2014 at 8:19 AM, Jeff Pittman geoj...@me.com wrote: This docs PR doesn't have a working example for localhost, but is at least an attempt at documenting the process for HOST_THEMES: https://github.com/stephenmcd/mezzanine/pull/961. Comments welcome on that PR. Jeff On Feb 27, 2014, at 2:18 PM, Radomir Wojcik rado...@cldssinc.com wrote: So after working with the django sites framework, I see how easy it is to have multiple sites running Mezzanine in one instance. It works great if you have a multiple language site and don't want to use the internationalization built into Django and instead create a separate site where the skin/theme remains the same. I would love to see a working example of HOST_THEMES though as I couldn't get this to work. If someone can post an easy, clonable github example using localhost and 127.0.0.1 to make it simple it would I think benefit the whole Mezzanine community! -- 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/groups/opt_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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Re: deployment issue --- gunicorn
Thanks Federico, I never stopped to realise that fix matched up with that
issue - good to know!
On Fri, Feb 28, 2014 at 10:42 AM, Federico Bruni fedel...@gmail.com wrote:
I confirm that this solved the same problem. More info here:
http://gunicorn-docs.readthedocs.org/en/latest/configure.html#configuration-file
It's been fixed two months ago:
https://github.com/stephenmcd/mezzanine/issues/870
Il giorno giovedì 16 gennaio 2014 12:35:58 UTC+1, Klamann, Norbert ha
scritto:
I repeated the whole exercise and now it works .
gunicorn.conf.py is changed an looks like that.
mezzanine@wsa02:~/mezz_test/project$ cat gunicorn.conf.py
from __future__ import unicode_literals
import multiprocessing
bind = 127.0.0.1:8000
workers = multiprocessing.cpu_count() * 2 + 1
loglevel = error
proc_name = mezz_test
Now I get a Error 500 when I visit the new instance but that is another
problem i presume.
Thanks for your help
Norbert
2014/1/16 Stephen McDonald st...@jupo.org
Thanks Harry
FWIW my successful test used 8000 for the gunicorn port.
On Thu, Jan 16, 2014 at 11:32 AM, har...@iinet.net.au wrote:
At least for the most basic deployment of mezzanine (ie. no custom
theme app yet) I seem to have resolved the issue.
Although I did a few different things, I think that the major factor
was changing the gunicorn port from 8000 to anything else (8001, ).
I'll keep you posted as to whether this moment of success persists.
Harry
On Friday, 10 January 2014 13:41:31 UTC+8, har...@iinet.net.au wrote:
Hi,
I'm very new to Mezzanine and have been loving it --- especially the
fabric deploment. However, I seem to be having some troubles with
gunicorn.
I started from a fresh linode running debian and allowed 'fab all' to
build the full system.
I would very much appreciate some assistance with this.
My basic process is:
server:
new linode profile
ssh as root
adduser user
apt-get install sudo vim
add harry to sudoers file
on local machine:
ssh-copy-id -i ~/.ssh/id_rsa.pub
sudo pip install virtualenvwrapper
add to bashrc:
export WORKON_HOME=$HOME/.virtualenvs
source /usr/local/bin/virtualenvwrapper.sh
export PIP_VIRTUALENV_BASE=$WORKON_HOME
local:
mkvirtualenv black_earth_{project}
pip install -r requirements.txt
createdb {project}
mezzanine-project {project}
set database parameters in local_settings.py
copy keys and deploy setting (FABRIC) to local_settings.py
set allowed_hosts in settings.py
ALLOWED_HOSTS = [
'localhosts',
'.mysite.org.au',
]
python manage.py createdb
check local server
set up git repository
git init
git add .
git git remote add origin {gitserver}
git push -u origin master
pip freeze requirements.txt
fab all
pip error:
sudo pip install setuptools --no-use-wheel --upgrade
At the final point in the deployment --- restart --- I get the error:
$ supervisorctl start black_earth_semina:gunicorn_black_earth_semina
-
[blackearthcollective.org.au] out: sudo password:
[blackearthcollective.org.au] out:
black_earth_semina:gunicorn_black_earth_semina:
ERROR (abnormal termination)
[blackearthcollective.org.au] out:
This is with a completely standard mezzanine setup. I thought that
the problem was with my theme project.
from the supervisor gunicorn log:
!!!
!!! WARNING: This command is deprecated.
!!!
!!! You should now run your application with the WSGI interface
!!! installed with your project. Ex.:
!!!
!!! gunicorn myproject.wsgi:application
!!!
!!! See https://docs.djangoproject.com/en/1.4/howto/deployment/
wsgi/gunicorn/
!!! for more info.
!!!
2014-01-10 01:16:35 [12088] [CRITICAL] WORKER TIMEOUT (pid:12097)
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
Stephen McDonald
http://jupo.org
--
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/Ltmdrd3D2aw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
mezzanine-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
--
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
Re: [mezzanine-users] jquery resize error
I don't recall the intention around this library's introduction - I'd be
more than happy to remove it if someone can work out why it's there and
that it's safe to remove.
On Tue, Mar 4, 2014 at 11:16 AM, Ross Laird r...@rosslaird.com wrote:
I have finally got round to testing this out, and the fix does not
actually work for me. The popups still do their thing, but the error
persists.
On Wed, Feb 19, 2014 at 9:36 AM, Josh Cartmell joshcar...@gmail.comwrote:
No problem Ross, did you give it a try and if so did it work for you as
well?
On Tue, Feb 18, 2014 at 7:32 PM, Ross Laird r...@rosslaird.com wrote:
Thanks for your work on this, Josh. Much appreciated.
On Tuesday, 18 February 2014 09:37:57 UTC-8, Josh Cartmell wrote:
I never worried about it too much since it only affected admins. In
the past I've played around with popping up the editable form in a
bootstrap modal, but that requires the site to use Bootstrap, which
probably isn't a good assumption.
I was just thinking (and tried it out which seemed to work) that we
could change ba-resize to define a baresize event, instead of overriding
jquery's default resize event. Getting this working required two changes.
First change the beginning of https://github.com/stephenmcd/
mezzanine/blob/faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
static/mezzanine/js/jquery.ba-resize.min.js from
e=$.resize=$.extend($.resize,{})
to
e=$.baresize=$.extend($.baresize,{})
Then change https://github.com/stephenmcd/mezzanine/blob/
faa736a0b42a6d6a92db13b46b9d322e2d5ffedc/mezzanine/core/
static/mezzanine/js/editable.js#L68 to:
$('.editable-original').on('baresize', function(e) {
I did this and although I didn't test things super thoroughly the
inline editing popups still pop up.
There may be a better approach, but what do you guys think?
On Mon, Feb 17, 2014 at 9:15 PM, Stephen McDonald st...@jupo.orgwrote:
I can tell you one thing at least, it only occurring when logged in as
an admin user is no mystery - the file only gets used for the live
editing:
https://github.com/stephenmcd/mezzanine/blob/master/
mezzanine/core/templates/includes/editable_loader.html
I can't speak for the rest of it, its introduction was 2 years ago:
https://github.com/stephenmcd/mezzanine/commit/
faa736a0b42a6d6a92db13b46b9d322e2d5ffedc
Seems to be related to managing the position of the live editing
overlay - would welcome throwing out the lib in question if there's a
better approach.
On Tue, Feb 18, 2014 at 4:11 PM, Ross Laird ro...@rosslaird.comwrote:
That's interesting -- yes, I see this error only when I am logged in
as admin.
I have installed some extra javascript (such as headroom.js and the
prettify jQuery plugin), so one of those could be interacting with
ba-resize. But it's tough for me to know how to debug this further. It's
not a huge issue, as no regular user to the site will experience this
error.
On Monday, 17 February 2014 17:54:30 UTC-8, Josh Cartmell wrote:
Hey Ross, I've seen this before.
Tell me if I'm wrong but do you only see it when you log in as an
admin? In my experience, it had something to do with a jquery script
trying to use the normal jquery resize functionality (
https://api.jquery.com/resize/) and not working because ba-resize
changes the way .resize works.
Steve, I can't find/think of a concrete example off the top of my
head, but if I do I'll definitely post it up.
On Mon, Feb 17, 2014 at 5:36 PM, Stephen McDonald st...@jupo.orgwrote:
Any hints on how to reproduce?
On Tue, Feb 18, 2014 at 11:59 AM, Ross Laird
ro...@rosslaird.comwrote:
I'm getting a javascript error (Uncaught TypeError: cannot set
property of 'w' undefined) with jquery.ba-resize.js, which is
included in
the default Mezzanine setup. There is an open
issuehttps://github.com/cowboy/jquery-resize/issues/1 about
this at the jquery-resize repo, but it seems that the repo has not
been
updated in four years. Anybody else have this issue, or any thoughts
about
updating this add-on for Mezzanine?
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com.
For more options, visit https
Re: [mezzanine-users] Re: Installing Mezzanine on Vagrant
-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii python 2.7.3-0ubuntu2 interactive high-level object-oriented langu (blog)vagrant@precise32:~/.virtualenvs/blog/bin$ By any case, is there any other site that instructs how to Setup the whole Thing using Windows? I think it would be faster for me. Thanks in advance -- 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. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] fab all runs, but cannot access mezzanine admin page
You shouldn't need to do any of that. Here's my vagrantfile: Vagrant.configure(2) do |config| config.vm.box = precise64 config.vm.network :private_network, ip: 10.10.10.10 end Forget the ports. Your vagrant vm is synonymous with a production server - you're deploying to it, and the various layers of nginx and gunicorn should deal with it. SSH onto this server. Look at the config files deployed there. Read each of the corresponding project's own documentation on these config files, and what they mean. On Tue, Mar 4, 2014 at 5:30 PM, Jesse Carrigan jesse.m.carri...@gmail.comwrote: I tried forwarding a port from my host machine and got the same result. With localhost:8080 forwarded to 80 on the guest machine, I get the message from ngnix. Forwarding localhost:8080 to 8000, I get no response. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] Re: Admin navigation
Ed, yes to everything - let's use that theme, and please help out with those regressions you've found. Thanks a lot! On Wed, Mar 5, 2014 at 1:40 AM, Eduardo Rivas jerivasmel...@gmail.comwrote: Wow guys, excellent work you've done here! It's amazing how different the admin looks with this tweaks. Now, I have a few questions: 1. Would you be interested in using an alternate theme for TinyMCE? I've been using this for several projects: http://thebigreason.com/blog/2008/09/29/thebigreason-tinymce-skin. It only involves dropping a folder into the TinyMCE files and changing a string in tinymce_setup.js. 2. Should we open a ticket to iron out the issues? The discussion is alive and well here, but Github might be better for tracking progress and referencing commits, etc. 3. I'm running the latest master branch from github in Firefox on my Linux box and a couple of issues are evident: 1. The font being used throughout the admin is now the system's default sans-serif font. It looks weird and huge, Arial looked better IMO. Perhaps what we are looking for is a better font stack, like Helvetica Arial sans-serif. That way we can get users in Mac, Linux and Windows to get the same look. 2. The scrollbar is always visible in the navigation pane. I attach some screenshots to demonstrate the issues. I can contribute on all the issues above if you like :) https://lh4.googleusercontent.com/-4fyG5sHM2zg/UxXlyNVSvOI/BsQ/tijNgh_uqsU/s1600/new_admin.pnghttps://lh5.googleusercontent.com/-1orCAfPyEGM/UxXlsRNmpVI/BsI/t3t0Fuwapf4/s1600/old_admin.png -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] CSRF fails on login during automated testing. Issue with caching on non-anonymous?
There are a few moving parts here, my guess is something failing in the last of these: By default in Mezzanine, forms use the fields_for template tag, which is just a helper for rendering forms: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/templates/includes/form_fields.html You'll see at the top of its template, it uses the nevercache tag which is fairly self explanatory - it's wrapped around the csrf token so that it's never cached. Then finally you'll see in both phases of the caching middleware, special handling of the csrf token is required: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/middleware.py#L169-L181 https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/middleware.py#L210-L213 It's likely that last part is somehow incompatible with LiveServerTestCase - I personally haven't used that before, but with regular Django test cases I've experienced a lot of differences in how sessions, request objects and everything related, actually work, compared to an actual running site. My advice would be to first verify these forms actually work for you in production, so that you can isolate this issue down to testing only, and then unless you're feeling particularly adventurous, disable caching for those particular tests that are failing - I understand there's a decorator in Django for modifying settings per test, but the name escapes me. Good luck! On Wed, Mar 5, 2014 at 9:48 AM, jenniferlia...@gmail.com wrote: Hi, I'm using LiveServerTestCase, as described herehttp://chimera.labs.oreilly.com/books/123400754/ch17.html#_getting_the_ft_to_run_the_management_on_the_server, to automate remote staging testing my site which uses mezzanine 3.0.9. The automated tests involve logging and out different users, sometimes quite rapidly. When caching is turned on as per the settings in live_settings.py, I get CSRF errors on login. If I turn off caching to memcache, I don't get the errors. I see that the UpdateCache middleware will go to cache if the user is anonymous. At the time the user fills out the login form, they are anonymous so therefore the login page must be cached, which is causing my CSRF failures (?). Unless I'm missing something, this is also true for the signup page. It seems like this could be a problem if people submit, say, a login or signup form with errors, that then happens to get cached and shown to the next user. Shouldn't there be a strategy to not cache these forms? Jennifer -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] CSRF fails on login during automated testing. Issue with caching on non-anonymous?
Ah so potentially you just need to add the nevercache tag around the csrf token? That would be a relief to know it all works, please let us know. On Thu, Mar 6, 2014 at 4:25 AM, jenniferlia...@gmail.com wrote: Thanks for the answer. You are entirely right. I had forgotten that I overrode mezzanine's account forms as per the instructions here: http://mezzanine.jupo.org/docs/frequently-asked-questions.html#where-are-all-the-templates-i-can-modify ...and the issue only showed up when caching was turned on in a 'real' environment. Jennifer On Tuesday, March 4, 2014 3:24:56 PM UTC-8, Stephen McDonald wrote: There are a few moving parts here, my guess is something failing in the last of these: By default in Mezzanine, forms use the fields_for template tag, which is just a helper for rendering forms: https://github.com/ stephenmcd/mezzanine/blob/master/mezzanine/core/templates/includes/form_ fields.html You'll see at the top of its template, it uses the nevercache tag which is fairly self explanatory - it's wrapped around the csrf token so that it's never cached. Then finally you'll see in both phases of the caching middleware, special handling of the csrf token is required: https://github.com/stephenmcd/mezzanine/blob/master/ mezzanine/core/middleware.py#L169-L181 https://github.com/stephenmcd/mezzanine/blob/master/ mezzanine/core/middleware.py#L210-L213 It's likely that last part is somehow incompatible with LiveServerTestCase - I personally haven't used that before, but with regular Django test cases I've experienced a lot of differences in how sessions, request objects and everything related, actually work, compared to an actual running site. My advice would be to first verify these forms actually work for you in production, so that you can isolate this issue down to testing only, and then unless you're feeling particularly adventurous, disable caching for those particular tests that are failing - I understand there's a decorator in Django for modifying settings per test, but the name escapes me. Good luck! On Wed, Mar 5, 2014 at 9:48 AM, jennife...@gmail.com wrote: Hi, I'm using LiveServerTestCase, as described herehttp://chimera.labs.oreilly.com/books/123400754/ch17.html#_getting_the_ft_to_run_the_management_on_the_server, to automate remote staging testing my site which uses mezzanine 3.0.9. The automated tests involve logging and out different users, sometimes quite rapidly. When caching is turned on as per the settings in live_settings.py, I get CSRF errors on login. If I turn off caching to memcache, I don't get the errors. I see that the UpdateCache middleware will go to cache if the user is anonymous. At the time the user fills out the login form, they are anonymous so therefore the login page must be cached, which is causing my CSRF failures (?). Unless I'm missing something, this is also true for the signup page. It seems like this could be a problem if people submit, say, a login or signup form with errors, that then happens to get cached and shown to the next user. Shouldn't there be a strategy to not cache these forms? Jennifer -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [mezzanine-users] building the docs
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 Sat, Mar 8, 2014 at 4:38 AM, Federico Bruni fedel...@gmail.com wrote: 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 kenbol...@gmail.com ha scritto: Hi Federico, ALLOWED_HOSTS, TIME_ZONE, and SECRET_KEY do not have values. Make sure you have those set in your settings.py or local_settings.py. Backing up a moment, we see that Mezzanine is installed in /usr/local/lib/python2.7/dist-packages/. I urge you to follow the recommendations of http://effectivedjango.com/tutorial/getting-started.html and install Django, Mezzanine, and other applications in a virtualenv ( http://www.virtualenv.org/en/latest/). hth, ken On Fri, Mar 7, 2014 at 12:03 PM, Federico Bruni fedel...@gmail.comwrote: I've tried building the docs but I'm getting this error: $ sphinx-build -b html docs docs/build Running Sphinx v1.2 /usr/local/lib/python2.7/dist-packages/mezzanine/utils/conf.py:51: UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 1.5 requires. Will fall back to the domains configured as sites. warn(You haven't defined the ALLOWED_HOSTS settings, which /usr/local/lib/python2.7/dist-packages/mezzanine/utils/conf.py:59: UserWarning: TIME_ZONE setting is not set, using closest match: Europe/Rome warn(TIME_ZONE setting is not set, using closest match: %s % tz) Exception occurred: File /usr/lib/python2.7/dist-packages/django/conf/__init__.py, line 151, in __init__ raise ImproperlyConfigured(The SECRET_KEY setting must not be empty.) ImproperlyConfigured: The SECRET_KEY setting must not be empty. The full traceback has been saved in /tmp/sphinx-err-sEgI9d.log, if you want to report the issue to the developers Find attached the full log. -- 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/Q7rneOzrv8o/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. -- 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.
Re: [mezzanine-users] Deploying: fab all fails with error password authentication failed
You may need to specify the database host in your Django settings. On Mon, Mar 10, 2014 at 10:43 AM, Thomas Johnson t...@merakicoin.com wrote: I had a completely vanilla debian 6 vps when I started out this afternoon. It is failing at the createdb command with the following error: .. [127.0.0.1] out: return Database.connect(**conn_params) [127.0.0.1] out: File /home/tomfoolery/protraderwiki/lib/python2.6/site-packages/psycopg2/__init__.py, line 164, in connect [127.0.0.1] out: conn = _connect(dsn, connection_factory=connection_factory, async=async) [127.0.0.1] out: django.db.utils.OperationalError: FATAL: password authentication failed for user protraderwiki [127.0.0.1] out: FATAL: password authentication failed for user protraderwiki [127.0.0.1] out: [127.0.0.1] out: Fatal error: run() received nonzero return code 1 while executing! Requested: /home/tomfoolery/protraderwiki/bin/python /home/tomfoolery/protraderwiki/project/manage.py createdb --noinput --nodata Executed: /bin/bash -l -c cd /home/tomfoolery/protraderwiki/project source /home/tomfoolery/protraderwiki/bin/activate /home/tomfoolery/protraderwiki/bin/python /home/tomfoolery/protraderwiki/project/manage.py createdb --noinput --nodata Aborting. Disconnecting from 127.0.0.1... done. /etc/postgresql/8.4/main/pg_hba.conf ... local all postgres ident # TYPE DATABASEUSERCIDR-ADDRESS METHOD # local is for Unix domain socket connections only local all all md5 # IPv4 local connections: hostall all 127.0.0.1/32 md5 # IPv6 local connections: hostall all ::1/128 md5 I've tried deleting the database and user but I keep getting the same error. Any suggestions would be awesome -- 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.
Re: [mezzanine-users] Keywords and other apps
I only vaguely recall and can't verify right now, but if I recall
correctly, migrations won't be generated with the keywords field with the
latest south/Django versions, and in your case, commenting them out is the
correct approach - this was done in Mezzanine as well when this became the
case.
Sorry I can't provide an exhaustive response - there are many layers to
this which just aren't fresh.
On Mon, Mar 10, 2014 at 8:31 AM, Ross Laird r...@rosslaird.com wrote:
I have read the
descriptionhttps://groups.google.com/forum/#!searchin/mezzanine-users/keywords/mezzanine-users/LGxEfHgxPok/AbsrnPlaIp4J
of
the changes to how Mezzanine handles generic relations, but I don't really
understand the programming aspects well enough to know if I'm going to have
trouble with my approach to removing generic references in other apps (such
as the events app https://github.com/stbarnabas/mezzanine-events). For
example, when I did the initial migration for the events app, I got the
error message about conflicts with South:
Your project contains migrations that include one of the fields
from mezzanine.generic in its Migration.model dict: possibly
KeywordsField, CommentsField or RatingField...
Josh had already given me a hint about that error message, with regard to
another app (my fantastic theme app http://mezzathe.me/, crafted by
Josh), so I just did the same thing as previously: I commented out the line
that referred to the keywords. Here's the line I commented out:
#'keywords': ('mezzanine.generic.fields.KeywordsField', [],
{'object_id_field': 'object_pk', 'to': orm['generic.AssignedKeyword'],\
'frozen_by_south': 'True'}),
After doing this, the events app migrates fine and works fine. But I
suppose I'd like to know if there are likely to be any unintended
(negative) consequences of just arbitrarily knocking out an entire line of
code from an app. I've now done this for two apps, and I expect I might
need to do it again, as I add new things. So, before I go too far down the
road of just blithely commenting out code blocks, I should know a bit about
what might happen.
Can anyone offer any insight about this?
Thanks in advance.
Ross
--
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.
Re: [mezzanine-users] Cartridge: search by product SKU
I have this working locally - it needs a tiny but non-trivial patch in
Mezzanine to support search fields across model relations, which first came
up as an issue couple weeks ago on the mailing list I think.
So with that in place we can define on the Product model:
search_fields = {variations__sku: 100}
and Mezzanine's search will merge all the content+sku fields all together:
Product.objects.get_search_fields()
{u'content': 1, u'title': 5, u'variations__sku': 100, u'keywords_string':
10}
Will push up Mezzanine/Cartridge changes later today.
On Tue, Mar 11, 2014 at 4:31 AM, Eduardo Rivas jerivasmel...@gmail.comwrote:
Hi everybody. Quick question: is it possible to search Cartridge products
by SKU? According to my tests, it isn't. Could you offer any pointers on
what steps to take to make it work? 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.
--
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.
Re: [mezzanine-users] Using a foreign key in Model search_fields?
You can now define search_fields across relations as of:
https://github.com/stephenmcd/mezzanine/commit/a25927b1e4f8aaeaf6a7b85f6cd6d59212024627
On Wed, Feb 19, 2014 at 12:06 AM, step ste...@gmail.com wrote:
Right, that those would be helpful :) Here they are
http://dpaste.com/1633572/https://groups.google.com/d/topic/mezzanine-users/7mAZ1ziWsVY/unsubscribe
http://dpaste.com/1633594/
- S
On Tuesday, February 18, 2014 12:11:47 AM UTC-5, Stephen McDonald wrote:
Don't hoard your tracebacks, set them out free into the world!
(please paste your full tracebacks somewhere)
On Tue, Feb 18, 2014 at 2:48 PM, step ste...@gmail.com wrote:
Hey guys, I can't figure this out. I figured this might be something
worth resolving on the mailing list as a reference.
I'm trying to use a foreignkey in a Model's search_fields (search using
a foreignkey).
Anyone have any idea?
*settings.py*
-
(
# Dotted path to field.
cartridge.shop.models.Product.artist,
# Dotted path to field class.
ForeignKey,
# Positional args for field class.
(app.Artist,),
# Keyword args for field class.
{blank: False},
)
*OPTION 1.*
patches.py
Product.search_fields = {'keywords_string': 10, 'title': 5, 'artist': 5}
results in
Related Field got invalid lookup: icontains
*OPTION 2*
patches.py
Product.search_fields = {'keywords_string': 10, 'title': 5,
'artist__title': 5}
results in
'Product' object has no attribute 'artist__title'
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
--
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/groups/opt_out.
--
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.
Re: [mezzanine-users] Cartridge: search by product SKU
Here's search_fields across relations in Mezzanine: https://github.com/stephenmcd/mezzanine/commit/a25927b1e4f8aaeaf6a7b85f6cd6d59212024627 And here's searchable variation skus in Cartridge: https://github.com/stephenmcd/cartridge/commit/d00228a11e66313c5b06bccfde035b442b8366c4 I've no ETA for releases other than soon. On Tue, Mar 11, 2014 at 1:46 PM, Eduardo Rivas jerivasmel...@gmail.comwrote: Awesome! One more reason to look forward to the next Mezzanine release :-) -- 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.
Re: [mezzanine-users] Cartridge Setup Issue
Potential fix here:
https://github.com/stephenmcd/cartridge/commit/1aa5bf11dcb4e0b8955f4236a3b0c85b2f8b6f1d
On Tue, Mar 11, 2014 at 11:06 PM, Philip Southwell p...@zoothink.comwrote:
Hi there,
I've just started using Mezzanine and I love it (my first Mezzanine site
here http://www.philipsouthwell.com!)
Now I'm trying out Cartridge according to the installation
instructionshttp://cartridge.jupo.org/overview.html#installation.
My problem is that I cannot view the actual site due to a TypeError -
although I can access the admin backend. I'm relatively new to
Python/Django web development and I may have missed something obvious. In
case it matters I'm developing on Windows, and have exactly the same
problem whether I install Cartridge from source or using pip. Any help
would be much appreciated!
Kind Regards, Phil
The error message that I get follows:
TypeError at /
decoding str is not supported
Request Method:GET Request URL:http://127.0.0.1:8000/ Django
Version:1.6.2Exception
Type: TypeErrorException Value:
decoding str is not supported
Exception
Location:c:\Code\venvs\shop\lib\site-packages\cartridge-0.9.2-py3.3.egg\cartridge\shop\templatetags\shop_tags.py
in currency, line 28 Python Executable:
c:\Code\venvs\shop\Scripts\python.exe Python Version:3.3.3Python Path:
['c:\\Code',
'c:\\Code\\shop',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\psycopg2-2.5.2-py3.3-win-amd64.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\cartridge-0.9.2-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\pisa-3.0.33-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\mezzanine-3.0.9-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\pillow-2.3.0-py3.3-win-amd64.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\future-0.9.0-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\requests_oauthlib-0.4.0-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\requests-2.2.1-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\bleach-1.4-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\tzlocal-1.0-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\filebrowser_safe-0.3.2-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\django-1.6.2-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\oauthlib-0.6.1-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\six-1.5.2-py3.3.egg',
'c:\\Code\\venvs\\shop\\lib\\site-packages\\pytz-2013.9-py3.3.egg',
'C:\\Python27',
'C:\\Python27\\Scripts',
'C:\\Python27\\Lib\\site-packages\\django\\bin',
'C:\\windows\\system32\\python33.zip',
'c:\\Code\\venvs\\shop\\DLLs',
'c:\\Code\\venvs\\shop\\lib',
'c:\\Code\\venvs\\shop\\Scripts',
'c:\\python33\\Lib',
'c:\\python33\\DLLs',
'c:\\Code\\venvs\\shop',
'c:\\Code\\venvs\\shop\\lib\\site-packages']
Server time: Tue, 11 Mar 2014 22:25:03 +1030
Error during template rendering
In template
c:\Code\venvs\shop\lib\site-packages\cartridge-0.9.2-py3.3.egg\cartridge\shop\templates\includes\user_panel.html,
error at line *9*
decoding str is not supported 1{% load i18n future shop_tags
mezzanine_tags %} 2 div class=panel panel-default user-panel 3 div
class=panel-body 4 {% spaceless %} 5 a href={% url shop_cart %}
6span class=glyphicon glyphicon-shopping-cart/span
7 {% blocktrans count request.cart.total_quantity as cart_quantity %}1
item{% plural %}{{ cart_quantity }} items{% endblocktrans %} 8 {% trans
in cart %}: 9 {{ request.cart.total_price|currency }}/abr 10 {% if
request.cart.total_quantity != 0 %} 11 a href={% url shop_checkout
%} class=btn btn-primary 12 {% if request.session.order.step %}{%
trans Return to Checkout %}{% else %}{% trans Go to Checkout %}{% endif
%} 13 /abr 14 {% endif %} 15 {% if settings.SHOP_USE_WISHLIST %} 16a
href={% url shop_wishlist %} class=btn-wishlist
17 span class=glyphicon glyphicon-star/span 18 {% blocktrans count
request.wishlist|length as wishlist_count %}Wishlist contains 1 item{%
plural %} Wishlist contains {{ wishlist_count }} items{% endblocktrans
%}/a 19 {% endif %}
--
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.
Re: [mezzanine-users] Re: Cartridge: search by product SKU
Thanks Ed - fixed in https://github.com/stephenmcd/mezzanine/commit/5eed6e4d28be73f59721b959fd7b18a6ebba3550 On Wed, Mar 12, 2014 at 9:21 AM, Eduardo Rivas jerivasmel...@gmail.comwrote: Ok, github is back to normal. And yes, we can now search through relations! However, the problem I'm seeing is that now searching by name returns one search result per variation. For example, searching for the name of a product with four variations returns four identical search results. Can you reproduce? -- 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.
Re: [mezzanine-users] Cartridge: search by product SKU
Sam - related not not the same, those previous changes were for admin search provided by Django, the latest changes are for front-end search provided by Mezzanine. On Wed, Mar 12, 2014 at 9:31 AM, Sam Kingston s...@sjkwi.com.au wrote: Steve, didn't we fix this in cartridge/#170 and mezzanine/#947 ? -- 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] Mezzanine at PyCon Asia-Pacific 2014
Hi all, I'll be giving a talk on Mezzanine at PyCon Asia-Pacific in May: https://tw.pycon.org/2014apac/en/ Hope to see you there! The PyCon APAC site is powered by Mezzanine too, which is really cool. -- 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.
Re: [mezzanine-users] mezzanine poll_twitter
Yes there's an interested flag that gets set against a query each time its tweets are displayed. The management command will only retrieved tweets from twitter for queries with this set. Take a moment to read these and you'll be in the best position to work out your issue: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/twitter/managers.py https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/twitter/management/commands/poll_twitter.py On Wed, Mar 19, 2014 at 7:51 AM, Radomir Wojcik rado...@cldssinc.comwrote: Does the cached query make sense? It won't update even if changed in db. I'm trying to generate a new app and see if I can get it working -- 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.
Re: [mezzanine-users] how to run gunicorn command?
The project name needs to be a valid Python package name, which mezzanine-test isn't since you can't use dashes. Try mezzanine_test. On Wed, Mar 19, 2014 at 2:04 PM, Ziwei Zhou ziweiz...@gmail.com wrote: Hi I have my mezzanine project named as *mezzanine-test* and located at /sites/test/code/mezzanine-test, inside *mezzanine-test* folder following are the files. ubuntu@test:/sites/test/code/mezzanine-test$ ls -l total 156 drwxrwxr-x 3 ubuntu ubuntu 4096 Mar 17 19:27 *deploy* -rwxr-xr-x 1 ubuntu ubuntu 16192 Mar 18 17:55 *fabfile.py* -rw-r--r-- 1 ubuntu ubuntu 17819 Mar 18 17:56 fabfile.pyc -rw-r--r-- 1 ubuntu ubuntu 276 Mar 18 19:28 gunicorn.conf.py -rw-r--r-- 1 root root 6 Mar 18 19:30 gunicorn.pid -rwxr-xr-x 1 ubuntu ubuntu 0 Mar 16 20:18 *__init__.py* -rw-r--r-- 1 ubuntu ubuntu 134 Mar 17 18:54 __init__.pyc -rw-rw-r-- 1 ubuntu ubuntu 738 Mar 16 22:00 local_settings.py -rw-rw-r-- 1 ubuntu ubuntu 703 Mar 17 18:54 local_settings.pyc -rwxr-xr-x 1 ubuntu ubuntu 955 Mar 16 20:18 *manage.py* -rw-r--r-- 1 ubuntu ubuntu 1685 Mar 18 19:22 readme.md -rw-rw-r-- 1 ubuntu ubuntu 401 Mar 18 17:25 requirements.txt -rw-rw-r-- 1 ubuntu ubuntu 16146 Mar 18 18:58 settings.py -rw-rw-r-- 1 ubuntu ubuntu 10311 Mar 18 17:42 settings.pyc drwxrwxr-x 2 ubuntu ubuntu 4096 Mar 17 19:29 *static* drwxr-xr-x 9 ubuntu ubuntu 4096 Mar 17 03:23 *templates* -rwxr-xr-x 1 ubuntu ubuntu 4567 Mar 17 22:17 *urls.py* -rw-r--r-- 1 ubuntu ubuntu 890 Mar 17 18:55 urls.pyc -rwxr-xr-x 1 ubuntu ubuntu 641 Mar 18 19:39 *wsgi.py* If I run following command /sites/test/code/mezzanine-test$*/sites/.virtualenvs/test/bin/gunicorn -c gunicorn.conf.py http://gunicorn.conf.py wsgi:application* The project will run but I got following error message when I try to access the site. Traceback (most recent call last): File /sites/.virtualenvs/test/lib/python3.3/site-packages/gunicorn/workers/sync.py, line 136, in handle_request for item in respiter: File /sites/.virtualenvs/test/lib/python3.3/site-packages/raven/middleware.py, line 35, in __call__ iterable = self.application(environ, start_response) File /sites/.virtualenvs/test/lib/python3.3/site-packages/Django-1.6.2-py3.3.egg/django/core/handlers/wsgi.py, line 187, in __call__ self.load_middleware() File /sites/.virtualenvs/test/lib/python3.3/site-packages/Django-1.6.2-py3.3.egg/django/core/handlers/base.py, line 46, in load_middleware for middleware_path in settings.MIDDLEWARE_CLASSES: File /sites/.virtualenvs/test/lib/python3.3/site-packages/Django-1.6.2-py3.3.egg/django/conf/__init__.py, line 54, in __getattr__ self._setup(name) File /sites/.virtualenvs/test/lib/python3.3/site-packages/Django-1.6.2-py3.3.egg/django/conf/__init__.py, line 49, in _setup self._wrapped = Settings(settings_module) File /sites/.virtualenvs/test/lib/python3.3/site-packages/Django-1.6.2-py3.3.egg/django/conf/__init__.py, line 132, in __init__ % (self.SETTINGS_MODULE, e) *ImportError: Could not import settings 'mezzanine-test.settings' (Is it on sys.path? Is there an import error in the settings file?): No module named 'mezzanine-test'* The wsgi.py file looks like following from __future__ import unicode_literals import os PROJECT_ROOT = os.path.dirname(os.path.abspath(__file__)) settings_module = %s.settings % PROJECT_ROOT.split(os.sep)[-1] os.environ.setdefault(DJANGO_SETTINGS_MODULE, settings_module) from django.core.handlers.wsgi import WSGIHandler application = WSGIHandler() Any help will be greatly appreciated. -- 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.
Re: [mezzanine-users] Cannot save new pages after launching site?
Looks like the error that shows up when the _order field for inlines hasn't been set - that happens via Javascript, so you're probably still not serving static files correctly. On Thu, Mar 20, 2014 at 8:07 AM, Josh Cartmell joshcar...@gmail.com wrote: Glad that we got the error message, but I'm actually not sure myself what caused it. Anyone else have any ideas? On Wed, Mar 19, 2014 at 1:06 PM, Scott Diehl mr.di...@gmail.com wrote: One more thing - the subject of the error email: ERROR (EXTERNAL IP): Internal Server Error: /admin/pages/ On Wednesday, March 19, 2014 1:04:57 PM UTC-7, Scott Diehl wrote: Thanks Josh - good call. I didn't have that set up. I have attached the error message. I'm not sure, but I'm wondering if the error is stemming from the way I have the URLs set up. Would you mind taking a look? Thank you! Scott On Wednesday, March 19, 2014 12:46:15 PM UTC-7, Josh Cartmell wrote: Hey Scott, have you configured the ADMINS setting in your settings.py file? If you have it should email you detailed error reports whenever the site produces a 500 error. Alternatively does anything more verbose show up in your server's logs? On Tue, Mar 18, 2014 at 4:18 PM, Scott Diehl mr.d...@gmail.com wrote: Hey guys, I really appreciate your help on this. So strange, but I finally got mezzanine upgraded - it seems to be running smoothly. However, same thing, when I try creating a new page and hit save, I get an error pagehttp://www.perceptyx.com/er/index.html. Any ideas? Anything else I can try? Thank you! Scott On Monday, February 10, 2014 12:13:55 PM UTC-8, Stephen McDonald wrote: Mezzanine makes use of South to manage changes to its database schema - something that may happen with each new version, and has happened in your case. Have a read up on south before you try and resolve the problem: http://south.aeracode.org/ On Tue, Feb 11, 2014 at 7:05 AM, Scott Diehl mr.d...@gmail.comwrote: Hey Josh, So my local mezzanine is version 1.4.10, and the version on the server is 1.4.9. That might be the problem... However, I have another issue now. As a test, I just ran pip install mezzanine --upgrade on my local version...but I think I broke it. I am getting an operational error: no such column: pages_page.created On Monday, February 10, 2014 11:26:39 AM UTC-8, Josh Cartmell wrote: Hey Scott, can you verify that the versions of Mezzanine are the same between the two environments? Do you have any idea what http://www.perceptyx.com/er/index.htmlis? Mezzanine doesn't use any urls that end in .html so that could be a source of the problem. On Mon, Feb 10, 2014 at 10:22 AM, Scott Diehl mr.d...@gmail.comwrote: Thank you for your help! Here is the error I am getting in my console: event.returnValue is deprecated. Please use the standard event.preventDefault() instead. XMLHttpRequest cannot load http://www.perceptyx.com/er/index.html. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://perceptyx.com' is therefore not allowed access. Looks like click clicking Save triggered our error page. This doesn't happen on my localhost version of the site. Any ideas? thanks again. Scott On Friday, February 7, 2014 1:40:27 PM UTC-8, Stephen McDonald wrote: Look for javascript errors, missing files (eg 404s) etc in the browser's dev console. Nice site btw. On Sat, Feb 8, 2014 at 6:16 AM, Scott Diehl mr.d...@gmail.comwrote: Hey guys, So...I am very new to django/python. I have just built a new mezzanine site (http://www.perceptyx.com), and launched it yesterday. It is working great. However, I am noticing a few weird things started ever since it went live. For example, I am not unable to save new pages? When I click add new page and then click save - nothing happens. I'm thinking maybe I missed a critical step in the launch process...when we switched from the dev URL to the production URL. Maybe? Any ideas? Scott -- 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. For more options, visit https://groups.google.com/groups/opt_out . -- 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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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-use...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Stephen McDonald http
Re: [mezzanine-users] dumpdata filebrowser files
They're stored on the filesystem only, not in the database. Default directory is project/static/media/uploads Use SCP, FTP etc. On Thu, Mar 27, 2014 at 7:43 PM, Cajoline cont...@circonflex.net wrote: Hello, I'm at the stage of deployment my site on my server and I did a dumpdata then loadata for my different applications (pages, forms, etc..), I have a little problem how to migrate data contained files in the filebrowser? 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-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.
Re: [mezzanine-users] Is this what Mezzanine looks like with no static files?
Yes that's how it'd look. Make sure you've correctly configured nginx, and run Django's collectstatic commend - you'll need to do the latter each time you deploy. Note that this is all handled for you automatically from setup to ongoing deploys if you use the bundled fabric script. http://mezzanine.jupo.org/docs/deployment.html On Fri, Mar 28, 2014 at 6:48 AM, Kyle Pennell kpenn...@gmail.com wrote: I'm trying to work out the Gunicorn and Mezzanine tutorials at Digital Ocean. I'm getting further and further. I'm guessing my problem now is that my static files aren't loading. Is the image below indeed what it looks like when you have something awry with Nginx and Gunicorn? Not trying to ask stupid questions...just checking that this in indeed some Nginx issue. https://lh5.googleusercontent.com/-d9NeGh49QzQ/UzSAZAaoE2I/GmA/PFUTdnC0BY4/s1600/mezz+no+static.png -- 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.
Re: [mezzanine-users] Can't figure out why my Static Files won't load
On Fri, Mar 28, 2014 at 8:46 AM, Kyle Pennell kpenn...@gmail.com wrote:
Triple checked my settings and can't find why my static files aren't
loading.
Nginx and Gunicorn are installed and working.
Symbolic Link between sites-available and sites-enabled is made
── sites-available
│ ├── mezzanine_app
│ └── myproject
├── sites-enabled
│ ├── ahalearning - ../sites-available/ahalearning
│ ├── mezzanine_app - ../sites-available/mezzanine_app
│ └── myproject - ../sites-available/myproject
Collectstatic has been run and static files are in place:
├── deploy
│ ├── crontab
│ ├── gunicorn.conf.py
│ ├── live_settings.py
│ ├── nginx.conf
│ └── supervisor.conf
├── dev.db
├── fabfile.py
├── __init__.py
├── __init__.pyc
├── local_settings.py
├── local_settings.pyc
├── manage.py
├── requirements.txt
├── settings.py
├── settings.pyc
├── static
│ ├── admin
│ ├── css
│ ├── filebrowser
│ ├── fonts
│ ├── grappelli
│ ├── img
│ ├── js
│ ├── media
│ ├── mezzanine
│ ├── robots.txt
│ └── test
├── urls.py
├── urls.pyc
└── wsgi.py
STATIC_ROOT in settings.py points to the right folder
(opt/myenv/mezzanine_app/static/)
My nginx server settings point to the right files:
/etc/nginx/sites-available
server {
server_name 107.170.215.138;
access_log off;
location /static/ {
alias /opt/myenv/mezzanine_app/static/;
}
I think this will look for the directory
/opt/myenv/mezzanine_app/static/static/
location / {
proxy_pass http://127.0.0.1:8001;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Real-IP $remote_addr;
add_header P3P 'CP=ALL DSP COR PSAa PSDa OUR NOR ONL UNI COM
NAV';
}
}
Nginx and Gunicorn fire up without problems.
Any idea what I might be missing?
Why are my static files 404'ing?
--
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] Re: form file field upload error
This is finally fixed in https://github.com/stephenmcd/mezzanine/commit/9527662dc3c7d7dfaa6397e01be9ebc999f2646f On Friday, 1 February 2013 14:17:11 UTC+11, Josh Cartmell wrote: I'm getting the following error when I try to submit a Mezzanine form that includes two larger files (the files are about 1.3mb each): Traceback (most recent call last): File .../lib/python2.7/site-packages/django/core/handlers/base.py, line 105, in get_response response = middleware_method(request, callback, callback_args, callback_kwargs) File ...lib/python2.7/site-packages/Mezzanine-1.2.3-py2.7.egg/mezzanine/pages/middleware.py, line 80, in process_view processor_response = processor(request, page) File ...lib/python2.7/site-packages/Mezzanine-1.2.3-py2.7.egg/mezzanine/forms/page_processors.py, line 58, in form_processor f.seek(0) ValueError: I/O operation on closed file After submitting the serving produces a 500 error. The form entries, and files end up in the database, but no emails are sent to people who should get copies. Anyone have any tips or pointers? Thanks, Josh -- 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] Default fabfile deploy, Internal Server Error
I can't reproduce this - just did deploy of Mezzanine 3.0.9 to a fresh ubuntu 12.04 machine without any issue. Only thing I can think of is some mismatch between ALLOWED_HOSTS, Site objects, and NGINX config - triple check those since the behaviour changes with DEBUG False. On Sat, Mar 29, 2014 at 5:25 AM, Josh Cartmell joshcar...@gmail.com wrote: I'm working on putting a dev server up for a client (to show them my progress) and figured I could do that quickly with the bundled fabfile and a VPS from Digital Ocean. I'm using essentially unmodified deploy config (I commented out some SSL stuff in the nginx config) and the VPS is 64 bit Ubuntu 12.0.4. If I set DEBUG = True the site runs fine, but when it is false the site just says Internal Server Error. I've checked the nginx and supervisor logs and nothing shows up in either when the site produces the error. Does gunicorn have a logfile and if so where is it? I also tried 64 bit Debian 7, and that also resulted in Internal Server Errors. 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. -- 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.
Re: [mezzanine-users] Default fabfile deploy, Internal Server Error
As I understand supervisor will log stdout/stderr for any procs it manages under /var/log/supervisord), such as gunicorn. This is why gunicorn's own logging is disabled in the default setup. Maybe it'd be better to configure the opposite (gunicorn logs all and sends nothing to stdout/stderr), personally the log file naming convention supervisor uses is a bit annoying. On Tue, Apr 1, 2014 at 8:02 AM, Doug Evenhouse d...@evenhouseconsulting.com wrote: I'm interested in the gunicorn logging question as well. I had a similar issue as yours Josh and ended up putting the following line in the gunicorn.conf.py file of my project in order to get some logged output that led me to the cause of the error. errorlog = /tmp/gunicorn.error.log On Monday, March 31, 2014 2:35:48 PM UTC-5, Josh Cartmell wrote: Thanks again for the help Steve! I ended up figuring it out and feel a bit silly now, I had some CDN hosted javascript inside the compress template tag resulting in an incompressible file error. My biggest question at this point is which log file should I have found that in. I'm still wondering if gunicorn produces a separate log file from niginx and supervisor. Thanks! On Sun, Mar 30, 2014 at 10:06 PM, Josh Cartmell joshc...@gmail.comwrote: Thanks for giving it a shot Steve! I didn't get it to work yet (since it was just a non production demo I was satisfied to leave it with DEBUG True). I'll triple check those things in the morning and let you know how it goes. By the way, does gunicorn have a log of it's own or is it logged with nginx and/or supervisor? On Sun, Mar 30, 2014 at 4:16 PM, Stephen McDonald st...@jupo.orgwrote: I can't reproduce this - just did deploy of Mezzanine 3.0.9 to a fresh ubuntu 12.04 machine without any issue. Only thing I can think of is some mismatch between ALLOWED_HOSTS, Site objects, and NGINX config - triple check those since the behaviour changes with DEBUG False. On Sat, Mar 29, 2014 at 5:25 AM, Josh Cartmell joshc...@gmail.comwrote: I'm working on putting a dev server up for a client (to show them my progress) and figured I could do that quickly with the bundled fabfile and a VPS from Digital Ocean. I'm using essentially unmodified deploy config (I commented out some SSL stuff in the nginx config) and the VPS is 64 bit Ubuntu 12.0.4. If I set DEBUG = True the site runs fine, but when it is false the site just says Internal Server Error. I've checked the nginx and supervisor logs and nothing shows up in either when the site produces the error. Does gunicorn have a logfile and if so where is it? I also tried 64 bit Debian 7, and that also resulted in Internal Server Errors. 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. 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-use...@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.
Re: [mezzanine-users] Products admin page times out accessing files from S3 on Heroku
Short answer is that the thumbnailing built into Mezzanine really isn't
very compatible with a remote storages backend like S3. I'd suggest using
something else for thumbnailing, while disabling Mezzanine's - quickest way
to do that would be to add your own thumbnail template tag that overrides
Mezzanine's.
Long answer is that Mezzanine will generate thumbnails on the fly, when
they don't exist - in order for that to work with something like Heroku+S3,
it will still generate and store the thumbnails locally if they don't
exist, so that the check will pass each subsequent request, but they're all
thrown out each time you do a new deploy to Heroku, so the first request
after a deploy to each thumbnail will trigger the local regeneration and
re-push to S3.
Interested in others' thoughts on this but I think Mezzanine shouldn't act
like this actually works, and somehow fail fast for remote backends and
simply not do the thumbnail generation, instead just returning the original
image URL.
On Fri, Apr 4, 2014 at 1:25 PM, Paul Becotte pjbeco...@gmail.com wrote:
So, I am up to 63 products on my cartridge site. I am serving images from
S3 using django-storages. The backend is set to use DEFAULT_FILE_STORAGE =
'storages.backends.s3boto.S3BotoStorage'
The problem is that when I access the products menu in the admin site, I
get a Heroku timeout. If I then reload it, it waits for a while and then
loads, and works fine after that. I am assuming this is the caching
working as expected, but I am not sure why it is taking so long to load the
page. The debug toolbar on the first sucessful load (it doesn't report
anything for the unsuccessful one!) shows cp time of 1180ms, SQL of 7
queries in 39ms, but 903 log messages. (If I leave the page and come back,
there are no log messages).
The messages look as follows. I have no idea where to even begin
troubleshooting this- does anyone have any suggestions of what to look at?
DEBUG 10:15:36 04/03/2014botoauth_path=/poppyschips/product/dunes13th.jpg
/app/.heroku/python/lib/python2.7/site-packages/boto/s3/connection.py:622
DEBUG10:15:36 04/03/2014 botoMethod:
HEAD/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:879DEBUG10:15:36
04/03/2014 botoPath:
/product/dunes13th.jpg/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:880DEBUG10:15:36
04/03/2014
botoData:/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:881DEBUG10:15:36
04/03/2014 botoHeaders:
{}/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:882DEBUG10:15:36
04/03/2014 botoHost: poppyschips.s3.amazonaws.com
/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:883
DEBUG10:15:36 04/03/2014 botoPort:
443/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:884DEBUG10:15:36
04/03/2014 botoParams:
{}/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:885DEBUG10:15:36
04/03/2014 botoestablishing HTTPS connection: host=
poppyschips.s3.amazonaws.com, kwargs={'port': 443, 'timeout': 70}
/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:745
DEBUG10:15:36 04/03/2014 botoToken:
None/app/.heroku/python/lib/python2.7/site-packages/boto/connection.py:901DEBUG10:15:36
04/03/2014 botoStringToSign:
HEAD
Fri, 04 Apr 2014 02:15:36 GMT
/poppyschips/product/dunes13th.jpg
/app/.heroku/python/lib/python2.7/site-packages/boto/auth.py:146 DEBUG10:15:36
04/03/2014 botoSignature:
AWS AKIAIPAFU5MCKWR46KCA:Nhinf3DuYX4lMTf5OyvsH8qLjrE=
/app/.heroku/python/lib/python2.7/site-packages/boto/auth.py:150 DEBUG10:15:37
04/03/2014
botopath=/product/dunes13th.jpg/app/.heroku/python/lib/python2.7/site-packages/boto/s3/connection.py:620
--
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.
Re: [mezzanine-users] New Package mezzanine-agenda
Looks good James, thanks a lot for sharing. Might be worth expanding on the original intentions and noting the differences with mezzanine-events at the top of the README - mezzanine-events gets relatively a lot of activity and people might be confused by the choice. I think some notes around that would be really helpful. On Wed, Apr 9, 2014 at 12:58 PM, James Pells james.pe...@gmail.com wrote: I have just uploaded a new Third-party Module to pypi. https://pypi.python.org/pypi/mezzanine-agenda/0.1.1 https://github.com/jpells/mezzanine-agenda mezzanine_agenda implements Events similar to mezzanine.blog.BlogPost I got the idea after using mezzanine_events and hacking it up a lot and decided to make my own events module. Hopefully others can put it to some use. -- 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.
Re: [mezzanine-users] Is there a way to auto-tweet or automatically push tweets and posts to social media sites for all
There isn't, but we have everything in place in Mezzanine already to be able to do this really simply - namely all the key/secret credentials as well as the mezzanine/twitter app itself. I'll add this shortly and it'll be available in the next release: https://github.com/stephenmcd/mezzanine/issues/1001 On Thu, Apr 10, 2014 at 4:11 AM, eric.fr...@mp2kmag.com wrote: Is there a way to auto-tweet or automatically push tweets and posts to social media sites for all new blog posts in Mezzanine? I am thinking of something like one of this plug-ins for Wordpress -- https://managewp.com/automatically-share-blog-posts Thanks! Eric -- 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.
Re: [mezzanine-users] Fabric Settings Path, PROJECT_NAME trouble, Repository not found
I can't stress enough how different your experience would be if you took a step back and read all the fabric documentation, then walked through Mezzanine's fabfile step by step until you understand each of the steps it takes to set up a server with your site deployed on it. It's really just one big sequence of remote commands on your server - install and configure all the things needed, then set up your project from version control, and use it to run the site. Once you empower yourself by understanding each of the steps it takes, you can *easily* debug these problems on your own. This approach requires the most effort from *you* up front, but will ultimately be the most efficient in the long run. What you're doing now, requires almost zero effort from you up front, calls on the effort of *others*, and ultimately does you the greatest injustice in the long run, by not learning how all these things actually work. Sorry if this advice is too blunt, but I think drip feeding you each step is doing you a disservice. On Fri, Apr 11, 2014 at 7:09 AM, Kyle Pennell kpenn...@gmail.com wrote: You get this when you do so: [ahalearning.co] out: You must provide a DEST_DIR [ahalearning.co] out: Usage: virtualenv [OPTIONS] DEST_DIR Sorry for pestering you, Josh. Perhaps someone else in this group has ideas so you don't have to keep trying. On Thursday, April 10, 2014 3:55:45 PM UTC-5, Josh Cartmell wrote: As far as I know the project name can be arbitrary, it can also be left blank and it will be inferred from the repo. Maybe try leaving it blank On Thu, Apr 10, 2014 at 1:51 PM, Kyle Pennell kpen...@gmail.com wrote: $ git clone g...@github.com:kpennell/mezz-digitalocean.git /mezzanine_app/project - [ahalearning.co] out: fatal: could not create leading directories of '/mezzanine_app/project': Permission denied Fatal error: run() encountered an error (return code 128) while executing 'git clone g...@github.com:kpennell/mezz-digitalocean.git /mezzanine_app/project' will have to dig into the permission error. On Thursday, April 10, 2014 3:29:18 PM UTC-5, Kyle Pennell wrote: I do get the space (I think). It's trying to clone from one to another. -- 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. 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.
Re: [mezzanine-users] Adding a simple CRM to Mezzanine
Sounds like a great project and it would make a great addition to the ecosystem if it were open source - haven't heard of anyone doing it before. The approach sounds good and simple - foreign keys to a central customer model. You'd then be able to customise the admin classes for the customer model to include the related data inline. Cartridge already has views for users viewing their previous order history, so have a look at that to start with. On Tue, Apr 15, 2014 at 2:47 PM, Mario Gudelj ma...@twoblokeswithapostie.com wrote: G'day list, I just started using Mezzanine and Cartridge for a new project and I love it. I managed to build a standard ecommerce site with it but now I need to extend it further and I need some guidance. The client wants to be able to manage customer information through the admin and somehow see the orders each customer has made, manage their newsletter subscription lists and see their contact form submissions. So, basically I need to build a simple CRM for them. What would be the best approach here? Should I create a Customer model and foreign key the orders and form submissions to it or is there another way? Also, if I did that and say I'm viewing the customer record, how would I display the list of orders and links to the detail view of those order? Also, I guess I'd extend the User class in this case so that customers can view past orders and form submissions on the frontend. If someone has done it before or if anyone has any ideas they'd like to sure I'd greatly appreciate it. Thanks a million! Mario -- 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.
Re: [mezzanine-users] Re: cartridge and cartridge-payments : help with checkout step
/n2d6SODIF1o/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/groups/opt_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. -- 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.
Re: [mezzanine-users] Mezzanine reset password
Please check the latest unreleased version on github, I believe this is resolved. On Thu, Apr 17, 2014 at 4:40 AM, Radomir Wojcik radzh...@gmail.com wrote: I think the reset password function is broken in mezzanine, probably because django now uses 64 bit, not 36 bit uidb: def password_reset_verify(request, uidb36=None, token=None): user = authenticate(uidb36=uidb36, token=token, is_active=True) if user is not None: auth_login(request, user) return redirect(profile_update) else: error(request, _(The link you clicked is no longer valid.)) return redirect(/) I remember having to change this a while ago in one of my Django apps. So right now it seems that when you send out a password reset request you get an email with the url pointing to the site without the token and uid : You're receiving this e-mail because you requested a password reset for your user account at Default. Please go to the following page and choose a new password: http://127.0.0.1:8000 Your username, in case you've forgotten: rad Thanks for using our site! The Default team Out of the box I was expecting the url to be something like this: http://127.0.0.1:8000/accounts/password/reset/Nw-3qt-c7514bee3aa6be820746/ -- 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] Mezzanine 3.1 and Cartridge 0.9.3 released
Hi all, I've just pushed both Mezzanine 3.1 and Cartridge 0.9.3 to PyPI. This is a huge release! Mezzanine 3.1 is really what 3.0 should have been, which has had quite a rocky road over the last few months - upgrading to Python 3.3, Django 1.6 and Bootstrap 3 all at once brought quite a few bugs along, but these have since been squashed and Mezzanine is very stable. Along with that, we've a bunch of cool new features too. Here's an overview of what 3.1 brings: - Huge overhaul of the admin interface: https://raw.githubusercontent.com/stephenmcd/mezzanine/master/docs/img/dashboard.png - New TweetableAdminMixin class for posting content directly to Twitter (blog uses this by default) - Main content architecture docs have been overhauled: http://mezzanine.jupo.org/docs/content-architecture.html - Thumbnails can now be generated with padded areas + configurable background colours - Extra email recipients in forms builder can now have custom email templates - Improved multi-site support in deployment fabfile - Custom widgets configurable for forms builder via FORMS_EXTRA_WIDGETS setting - Fix for long outstanding bug when uploading large files via forms builder - Search API can now span across model related fields - Ratings can be edited by authenticated users - New default TinyMCE theme: http://thebigreason.com/blog/2008/09/29/thebigreason-tinymce-skin - Select widgets in the admin now use jQuery chosen plugin: http://harvesthq.github.io/chosen/ - Page subclasses can provide their own template names via get_template_name method - Pillow now explicitly installed as a dependency I've also pushed out Cartridge 0.9.3 which has a small set of features and fixes: - Fixed PDF dependencies (replaced pisa with xhtml2pdf) - Products now searchable by SKU - New settings for toggling upsell/related products - Customers or staff can now have receipt emails resent That's it! A massive thanks goes out to everyone who contributed features, fixes, and support on the mailing list. Mezzanine has never been this good, and it's all thanks to you. -- 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.
Re: [mezzanine-users] Re: Mezzanine 3.1 and Cartridge 0.9.3 released
Thanks for the report - I've just push 3.1.1 with a fix. On Sat, Apr 19, 2014 at 12:30 PM, Ziwei Zhou ziweiz...@gmail.com wrote: Thanks for the great work. I installed your update and one thing I noticed is that all the rich text edit field in admin interface did not get upgrade with tinymce https://lh3.googleusercontent.com/-FhjIEskEQnM/U1HftG8NbZI/Hck/IOqUFMcsCzA/s1600/Screen+Shot+2014-04-19+at+10.29.52+AM.png On Saturday, April 19, 2014 8:13:53 AM UTC+8, Stephen McDonald wrote: Hi all, I've just pushed both Mezzanine 3.1 and Cartridge 0.9.3 to PyPI. This is a huge release! Mezzanine 3.1 is really what 3.0 should have been, which has had quite a rocky road over the last few months - upgrading to Python 3.3, Django 1.6 and Bootstrap 3 all at once brought quite a few bugs along, but these have since been squashed and Mezzanine is very stable. Along with that, we've a bunch of cool new features too. Here's an overview of what 3.1 brings: - Huge overhaul of the admin interface: https://raw.githubusercontent. com/stephenmcd/mezzanine/master/docs/img/dashboard.png - New TweetableAdminMixin class for posting content directly to Twitter (blog uses this by default) - Main content architecture docs have been overhauled: http://mezzanine. jupo.org/docs/content-architecture.html - Thumbnails can now be generated with padded areas + configurable background colours - Extra email recipients in forms builder can now have custom email templates - Improved multi-site support in deployment fabfile - Custom widgets configurable for forms builder via FORMS_EXTRA_WIDGETS setting - Fix for long outstanding bug when uploading large files via forms builder - Search API can now span across model related fields - Ratings can be edited by authenticated users - New default TinyMCE theme: http://thebigreason.com/blog/ 2008/09/29/thebigreason-tinymce-skin - Select widgets in the admin now use jQuery chosen plugin: http://harvesthq.github.io/chosen/ - Page subclasses can provide their own template names via get_template_name method - Pillow now explicitly installed as a dependency I've also pushed out Cartridge 0.9.3 which has a small set of features and fixes: - Fixed PDF dependencies (replaced pisa with xhtml2pdf) - Products now searchable by SKU - New settings for toggling upsell/related products - Customers or staff can now have receipt emails resent That's it! A massive thanks goes out to everyone who contributed features, fixes, and support on the mailing list. Mezzanine has never been this good, and it's all thanks to you. -- 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. -- 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.
Re: [mezzanine-users] Product django server : get NoReverseMatch: Reverse for 'login' with arguments '()' .
830, in render
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] bit =
self.render_node(node, context)
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] File
/home/victoria88/webapps/cartridge/lib/python2.7/django/template/base.py,
line 844, in render_node
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] return
node.render(context)
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] File
/home/victoria88/webapps/cartridge/lib/python2.7/django/template/defaulttags.py,
line 285, in render
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] return
nodelist.render(context)
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] File
/home/victoria88/webapps/cartridge/lib/python2.7/django/template/base.py,
line 830, in render
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] bit =
self.render_node(node, context)
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] File
/home/victoria88/webapps/cartridge/lib/python2.7/django/template/base.py,
line 844, in render_node
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] return
node.render(context)
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] File
/home/victoria88/webapps/cartridge/lib/python2.7/django/template/defaulttags.py,
line 426, in render
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] raise e
[Sat Apr 19 10:15:32 2014] [error] [client 127.0.0.1] NoReverseMatch:
Reverse for 'login' with arguments '()' and keyword arguments '{}' not
found.
--
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.
Re: [mezzanine-users] Tests failing
== FAIL: test_gallery_import (mezzanine.galleries.tests.GalleriesTests) -- Traceback (most recent call last): File /home/kevin/mezzanine_dj16/mezzanine/mezzanine/galleries/tests.py, line 27, in test_gallery_import self.assertTrue(images) AssertionError: [] is not true == FAIL: test_thumbnail_generation (mezzanine.galleries.tests.GalleriesTests) -- Traceback (most recent call last): File /home/kevin/mezzanine_dj16/mezzanine/mezzanine/galleries/tests.py, line 48, in test_thumbnail_generation self.assertEqual(os.path.normpath(thumb_image.lstrip(/)), thumb_name) AssertionError: u'image.jpg' != u'.thumbnails/image.jpg/image-24x24.jpg' - image.jpg + .thumbnails/image.jpg/image-24x24.jpg -- Ran 266 tests in 9.232s FAILED (failures=3, skipped=2, expected failures=1) Destroying test database for alias 'default'... (mezz_dj16)kevin@ubuntu:~/mezzanine_dj16/mezzanine$ -- 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.
Re: [mezzanine-users] Amazon EC2 and Thumbnails
Don't have an answer sorry - please keep the list posted if you have a good solution, it'd be quite welcome given the number of times this has come up already. On Mon, Apr 21, 2014 at 2:41 AM, Brad Bode forb...@gmail.com wrote: Stephen, Mezzanine rocks. There are definitely a few sticking points when deploying on Amazon EC2 / Elastic Beanstalk + S3, but most of them I have overcome. The biggest issue is the thumbnail template tag (Not for reasons that are your fault). For the sake of info, here is the issue: Amazon EB and EC2 uses an interesting app deployment mechanism. Each time you update your app it increments a number in a directory, deploys your app into that directory, and starts the server. For instance, if you go with out of the box Mezzanine settings your static and media content goes here: /opt/python/bundle/1/app/static/media On subsequent deploys the new deploy will go here: /opt/python/bundle/2/app/static/media Note the incremental number change. So, the first issue is that the uploaded media disappears with each deploy because it is IN the app directory. The solution was to use django storages with S3 (and help from s3_folder_storage). That fixes the issue for uploading media and not have it be erased across deploys. If you didn't use S3, you could write your own script that runs on each deploy and copies over previous uploaded images. No fun and quite a patch. So that leads me to the final problem. Thumbnails does not work with S3 (you already know this). I understand the issue, but is there any other workaround? I suppose I could monkey patch the tag to do something completely different and upload the thumbnail to S3. Any thoughts on the issue? PS This question was briefly discuss here https://groups.google.com/forum/#!topic/mezzanine-users/WGVaNhD5vRs No clear solution was posted. -- 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.
Re: [mezzanine-users] Re: Mezzanine 3.1 and Cartridge 0.9.3 released
Gonna suggest you've misconfigured something somehow. All of the 404s you referenced are defined with relative paths (eg no leading slash or host). According to the Django docs, media files defined on form widgets (as is the case with tiny_mce_setup.js and keywords_field.js) will automatically be passed through staticfiles handling. My own testing just now shows this works correctly. https://docs.djangoproject.com/en/1.6/topics/forms/media/#paths-in-asset-definitions As for the css files in your second email, those are simply defined in templates, and passed to the static template tag - it's even clearer in this case that they're passed through staticfiles handling. You'll need to work this out yourself, so good luck. If you do make progress but can't resolve it entirely, please start a new thread. It's a terrible shame to be troubleshooting this in the release announcement thread! On Tue, Apr 22, 2014 at 11:49 AM, Ziwei Zhou ziweiz...@gmail.com wrote: https://lh6.googleusercontent.com/-PETB-ntkYiU/U1XKv4pRvxI/HdE/iaSWOLYxS2E/s1600/Screen+Shot+2014-04-22+at+9.49.15+AM.png Same thing happens to the media gallery as well. On Tuesday, April 22, 2014 8:59:14 AM UTC+8, Ziwei Zhou wrote: Thanks for the fix, Stephen. One last thing, it seems the tinymce_setup script is not using static from statifiles library in the admin page. https://lh3.googleusercontent.com/-oVvdsFMv9ak/U1W-wswrQHI/Hc0/77AfsI-rOIk/s1600/Screen+Shot+2014-04-22+at+8.56.02+AM.png On Saturday, April 19, 2014 10:56:01 AM UTC+8, Stephen McDonald wrote: Thanks for the report - I've just push 3.1.1 with a fix. On Sat, Apr 19, 2014 at 12:30 PM, Ziwei Zhou ziwe...@gmail.com wrote: Thanks for the great work. I installed your update and one thing I noticed is that all the rich text edit field in admin interface did not get upgrade with tinymce https://lh3.googleusercontent.com/-FhjIEskEQnM/U1HftG8NbZI/Hck/IOqUFMcsCzA/s1600/Screen+Shot+2014-04-19+at+10.29.52+AM.png On Saturday, April 19, 2014 8:13:53 AM UTC+8, Stephen McDonald wrote: Hi all, I've just pushed both Mezzanine 3.1 and Cartridge 0.9.3 to PyPI. This is a huge release! Mezzanine 3.1 is really what 3.0 should have been, which has had quite a rocky road over the last few months - upgrading to Python 3.3, Django 1.6 and Bootstrap 3 all at once brought quite a few bugs along, but these have since been squashed and Mezzanine is very stable. Along with that, we've a bunch of cool new features too. Here's an overview of what 3.1 brings: - Huge overhaul of the admin interface: https://raw.githubusercontent. com/stephenmcd/mezzanine/master/docs/img/dashboard.png - New TweetableAdminMixin class for posting content directly to Twitter (blog uses this by default) - Main content architecture docs have been overhauled: http://mezzanine.jupo.org/docs/content-architecture.html - Thumbnails can now be generated with padded areas + configurable background colours - Extra email recipients in forms builder can now have custom email templates - Improved multi-site support in deployment fabfile - Custom widgets configurable for forms builder via FORMS_EXTRA_WIDGETS setting - Fix for long outstanding bug when uploading large files via forms builder - Search API can now span across model related fields - Ratings can be edited by authenticated users - New default TinyMCE theme: http://thebigreason.com/blog/2 008/09/29/thebigreason-tinymce-skin - Select widgets in the admin now use jQuery chosen plugin: http://harvesthq.github.io/chosen/ - Page subclasses can provide their own template names via get_template_name method - Pillow now explicitly installed as a dependency I've also pushed out Cartridge 0.9.3 which has a small set of features and fixes: - Fixed PDF dependencies (replaced pisa with xhtml2pdf) - Products now searchable by SKU - New settings for toggling upsell/related products - Customers or staff can now have receipt emails resent That's it! A massive thanks goes out to everyone who contributed features, fixes, and support on the mailing list. Mezzanine has never been this good, and it's all thanks to you. -- 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-use...@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. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine
Re: [mezzanine-users] Re: Thumbnail UnicodeEncodeError
On Tue, Apr 22, 2014 at 3:17 PM, Skyler Dawson foxwoods...@gmail.comwrote: And the error has been found. I had at one point changed my settings to figure out paths using unipath: PROJECT_ROOT = Path(__file__).ancestor(2) MEDIA_ROOT = PROJECT_ROOT.child(media) So in the template tag it was joining a unipath path object to unicode strings, and the path objects decide whether or not to use unicode or str in python 2 based on os.path.supports_unicode_filenames, which is False on posix systems (minus darwin). So MEDIA_ROOT was a str that was trying to be joined with unicode, and as the first element in the sequence errors occurred. I've since moved the path object to another variable and now properly wrap all the settings vars that use it with unicode(). Sorry for the noise, and if someone else setup like I did, hopefully this helps them out. No sweat - thanks for posting the outcome. On Monday, 21 April 2014 21:14:16 UTC-4, Skyler Dawson wrote: Hi all, Probably a configuration issue on my part, but I'm getting to my wits end. Site crashes in the thumbnail template tag on any gallery related portion: UnicodeEncodeError at / 'ascii' codec can't encode character u'\u0301' in position 83: ordinal not in range(128) - /home/foxwoods/.virtualenvs/skylerdawson.com/local/lib/ python2.7/site-packages/mezzanine/core/templatetags/mezzanine_tags.pyhttp://skylerdawson.com/local/lib/python2.7/site-packages/mezzanine/core/templatetags/mezzanine_tags.pyin thumbnail 1. settings.THUMBNAILS_DIR_NAME, image_name) ... ▼ Local vars http://localhost:8000/# Variable Value thumb_name u'A\u0301vila, Spain_2-90x90.jpg' ImageFile module 'PIL.ImageFile' from '/home/foxwoods/.virtualenvs/skylerdawson.com/local/lib/python2.7/site-packages/PIL/ImageFile.pyc' image_prefix u'A\u0301vila, Spain_2' padding_color u'#fff' image_dir u'uploads/gallery' Image module 'PIL.Image' from '/home/foxwoods/.virtualenvs/skylerdawson.com/local/lib/python2.7/site-packages/PIL/Image.pyc' filetype u'JPEG' image_name u'A\u0301vila, Spain_2.jpg' height 90 padding False width 90 image_url 'uploads/gallery/A\u0301vila, Spain_2.jpg' ImageOps module 'PIL.ImageOps' from '/home/foxwoods/.virtualenvs/skylerdawson.com/local/lib/python2.7/site-packages/PIL/ImageOps.pyc' quality 95 top 0.5 image_ext u'.jpg' left 0.5 - /home/foxwoods/.virtualenvs/skylerdawson.com/lib/python2.7/ posixpath.py in join 1. path += '/' + b ... ▶ Local vars http://localhost:8000/# - /home/foxwoods/.virtualenvs/skylerdawson.com/local/lib/ python2.7/site-packages/unipath/abstractpath.pyhttp://skylerdawson.com/local/lib/python2.7/site-packages/unipath/abstractpath.pyin __add__ 1. return self.__class__(resultStr) ... ▶ Local vars http://localhost:8000/# - /home/foxwoods/.virtualenvs/skylerdawson.com/local/lib/ python2.7/site-packages/unipath/abstractpath.pyhttp://skylerdawson.com/local/lib/python2.7/site-packages/unipath/abstractpath.pyin __new__ 1. return _base.__new__(class_, newpath) ... ▶ Local vars http://localhost:8000/# Unicode error hint The string that could not be encoded/decoded was: *ils/Ávila,* On my root page I'm displaying the last 9 gallery images, which currently has the default image data provided as a fixture when creating my sample mezzanine db. So I've read that this could be an issue when I created the database apparently, but my locale seems to be setup properly, and I've tried recreating the DB specifically setting the character encoding as UTF8 (postgresql). Using SHOW ALL; on my database shows all the locales set to en_CA.UTF-8. And the output of locale: foxwoods@FoxwoodsWebDev ~ $ locale LANG=en_CA.UTF-8 LANGUAGE=en_CA.UTF-8 LC_CTYPE=en_CA.UTF-8 LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 LC_MONETARY=en_CA.UTF-8 LC_MESSAGES=en_CA.UTF-8 LC_PAPER=en_CA.UTF-8 LC_NAME=en_CA.UTF-8 LC_ADDRESS=en_CA.UTF-8 LC_TELEPHONE=en_CA.UTF-8 LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION=en_CA.UTF-8 LC_ALL=en_CA.UTF-8 So I'm not sure if this is an error in the template tag code or in my db/environment setup. -- 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
Re: [mezzanine-users] Re: Marking Django Application Pages as Active in the Navigation
Stepping through the page middleware which handles assigning the page
variable will probably shed some light:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/pages/middleware.py#L91-L124
On Tue, Apr 22, 2014 at 6:09 PM, PR pavan.ri...@gmail.com wrote:
On Monday, April 21, 2014 12:30:16 PM UTC-4, Eduardo Rivas wrote:
The blog app defines it's own url patterns. For example, the list view
(showing all blog posts) is mapped to /blog by default.
It seem to be that the blog app defines / to be the list view in its
urls.py. Mezzanine includes the blog's urls.py, adding the BLOG_SLUG prefix.
The app I am integrating also defines it's own urls. I simply included
these in my project's urls.py(above the mezzanine catch-all):
(^pastes/, include('dpaste.urls.dpaste')),
Then I created a RichTextPage with the name Pastes and no parent to
match this url. I can successfully visit the dpaste app from the added
navigation link. When I remove the dpaste url include, I can successfully
visit the RichTextPage.
The trick is in creating a page in the admin with the exact same slug.
You have to do this to get Mezzanine to insert the page variable into your
context. In the end, Mezzanine will merge both the context provided by the
page and the context of your own application.
My problem is that I have created the page with the slug but Mezzanine is
not inserting the page variable into my context, so the navigation link
does not receive an active class.
I've done this in the past with a custom Portfolio app and the
integration is seamless. If you want to inspect your template context, list
of templates and other useful debugging info in your browser, you should
use Django Debug Toolbar. Install it with pip install django-debug-tollbar,
Mezzanine will activate it automatically when it detects it's installed;
you should then get a small button in the top-right corner of your site
when running in the development server.
Yes I've done all this, thats how I was able to see that the template was
not being passed the page context variable...
Here is a related screenshot:
https://lh4.googleusercontent.com/-lKB3QXJ_Ud8/U1YijWBoSOI/AJ0/qqZqhwwT3PU/s1600/2014-04-22-040313_1366x768_scrot.png
You can see that a Pastes page exists and that the browser is visiting
the /pastes/ url, however the Pastes link is not shaded as active(and
yes the theme does define a different color for active tabs, it works
fine for the blog app).
The breadcrumb only exists because I hardcoded it into the template, which
would be unneeded if the page variable was inserted.
--
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.
Re: [mezzanine-users] Tests failing
Looks like all tests are passing. On Tue, Apr 22, 2014 at 7:54 PM, Kevin Golding kevingolding2...@gmail.comwrote: Hi Stephen Thanks for the timely response. When you mentioned the bad/missing Pillow install I recalled that I originally had some issues with Pillow. I think Pillow itself has a number of (possibly undocumented?) dependencies and things go quite wrong if they are not met when you try to install. In the end I started from scratch and created a new VM, and made sure that I had all the dependencies that I could find for Pillow before attempting to install it. Then I followed the steps exactly in your 'Contributing' section with the exception that I specified 'pyflakes==0.6.1 pep8==1.4.1' when installing these bits, as per the test_require line in setup.py. Now when I run the tests it ends up saying OK (skipped=2, expected failures=1). Is this close enough in terms of 'all tests passing'? I don't see anything about failures in the output, though I get a number of warnings about things being deprecated (which is why I'm doing all this in the first place). Regards Kevin On Sunday, April 20, 2014 5:22:36 PM UTC-7, Stephen McDonald wrote: Those all look like dependency issues. Making sure you've got the correct versions of the test dependencies (as per `tests_require` in setup.py) should fix the first failure. The second and third look due to a bad/missing PIL/Pillow install. The failures against Django 1.7 are expected - there's a lot of work to be done there. On Mon, Apr 21, 2014 at 9:48 AM, Kevin Golding kevingol...@gmail.comwrote: Hi all I was planning to make some changes for things that are deprecated in Django1.7, so I forked Mezzanine on bitbucket and did all the steps in the Contributing section to create a development environment (but using my fork on bitbucket instead of the github one listed). However before I made any actual changes I ran the 'manage.py test' command just to see how it worked, and it reported 3 errors. I'm not really sure what to do now. If I make my changes will the pull request be rejected because the tests don't pass for unrelated reasons? I've pasted in the output of the test run below. Note that this is running against Django 1.6.2. I also have an environment set up with Django 1.7, and when I run the tests there I get 8 'errors' in addition to the 3 'failures'. Any suggestions what I should do now? Thanks Kevin = (mezz_dj16)kevin@ubuntu:~/mezzanine_dj16/mezzanine$ ./mezzanine/project_template/manage.py test /home/kevin/mezzanine_dj16/mezzanine/mezzanine/utils/conf.py:51: UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django 1.5 requires. Will fall back to the domains configured as sites. warn(You haven't defined the ALLOWED_HOSTS settings, which /home/kevin/mezzanine_dj16/mezzanine/mezzanine/utils/conf.py:59: UserWarning: TIME_ZONE setting is not set, using closest match: Australia/Sydney warn(TIME_ZONE setting is not set, using closest match: %s % tz) Creating test database for alias 'default'... .x.. .s.. /home/kevin/mezzanine_dj16/mezz_dj16/local/lib/ python2.7/site-packages/django/http/response.py:330: DeprecationWarning: Using mimetype keyword argument is deprecated, use content_type instead super(HttpResponse, self).__init__(*args, **kwargs) ...F..s./home/kevin/mezzanine_dj16/mezz_ dj16/local/lib/python2.7/site-packages/pkg_resources.py:991: UserWarning: /home/kevin/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable). warnings.warn(msg, UserWarning) FF == FAIL: test_syntax (mezzanine.core.tests.CoreTests) -- Traceback (most recent call last): File /home/kevin/mezzanine_dj16/mezzanine/mezzanine/core/tests.py, line 72, in test_syntax self.fail(Syntax warnings!\n\n%s % \n.join(warnings)) AssertionError: Syntax warnings! mezzanine/utils/tests.py:142: visually indented line with same indent as next logical line mezzanine/utils/docs.py:154: visually indented line with same indent as next logical line mezzanine/utils/docs.py:199: visually indented line with same indent as next logical line mezzanine/project_template/settings.py:251: block comment should start with '# ' mezzanine/project_template/settings.py:252: block comment should start with '# ' mezzanine/accounts/forms.py:215: visually indented line with same
Re: [mezzanine-users] How do I stop the sitemap showing local host on the live site?
I think the current school of thought in SEO would suggest only one canonical host, and the other domain can just redirect to the primary one - I usually do this in the nginx config but it'd work equally well with apache or some other web server. On Wed, Apr 23, 2014 at 10:31 AM, Paul Whipp paul.wh...@gmail.com wrote: Absolutely correct. I went to delete it and it wanted to delete all my content. However, editing the existing entry to reflect my main domain paulwhippconsulting.com worked fine. I also use paulwhippconsulting.com.au. This now also has the sitemap for paulwhippconsulting.com. I'm not sure if this matters; I probably would be better off just redirecting were it not for the fact that my Australian customers like to know my business is Australian. I guess I'll have to read more about sites. Thanks for the quick response. On Wednesday, April 23, 2014 10:18:40 AM UTC+10, Stephen McDonald wrote: There's a sites section in the admin for configuring each site record (which most content has a relation to). Guessing you've got one record in there, and its domain is localhost. On Wed, Apr 23, 2014 at 10:16 AM, Paul Whipp paul@gmail.com wrote: I'm having fun with Mezzanine: Using Django 1.6.2, mezzanine 3.0.6 and Python 3; I've just migrated www.paulwhippconsulting.com from an old Joomla 1.5 version. The site is like the 'plumber's dripping tap' and Mezzanine certainly saved me a lot of time now I've finally got around to updating it. I only have one big issue with the site now that it is deployed which I'm investigating but I thought I'd mention it here in case anyone has a quick solution: The sitemap file http://www.paulwhippconsulting.com/sitemap.xml is showing my local development as the host url. -- 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. 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. -- 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.
Re: [mezzanine-users] Tool for drawing mezzanine model graph
It's from django-extensions: http://django-extensions.readthedocs.org/en/latest/graph_models.html On Wed, Apr 23, 2014 at 11:53 AM, Wesley nisp...@gmail.com wrote: Hi all, I am looking at mezzanine docs these days and today I find a page regarding model graph. Here is the graph link: http://mezzanine.jupo.org/docs/_images/graph.png So, anybody know which tool is used to generate this graph, python specific tool? Thanks. Wesley -- 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.
Re: [mezzanine-users] Re: Something wrong with default theme?
The intention's to rip the layout up with your own design - so like Ed said
it's really not a big deal.
Still if someone wants to resolve this in a simple enough way then by all
means go ahead.
On Fri, Apr 25, 2014 at 12:04 AM, Eduardo Rivas jerivasmel...@gmail.comwrote:
Well, I wouldn't call it a bug, it is just a limitation of Bootstrap not
knowing how wide your navbar needs to be. From
http://getbootstrap.com/components/#navbar:
Since Bootstrap doesn't know how much space the content in your navbar
needs, you might run into issues with content wrapping into a second row.
That's exactly what's happening here. It's up to the developer to provide
for cases such as this. You can check out the linked document for some
potential fixes, or come up with your own. If you know your navbar will
always be too wide to fit in a single row, just add body {padding-top:
100px;} to your site's CSS (default padding-top is 50px). A more robust
approach would require media queries to add the extra padding, or some
Javascript that computes the body padding based on navbar height on every
window resize event. Note sure if Steve would like to add something like
that to the core.
--
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.
Re: [mezzanine-users] poll_twitter command triggering log events in Postgres.
In fact I've already committed it, so no need. Thanks again. On Fri, Apr 25, 2014 at 6:24 PM, Stephen McDonald st...@jupo.org wrote: Seems like a reasonable fix - if you'd like to submit a pull request I'll merge it. Thanks On Wed, Apr 23, 2014 at 7:23 PM, Ciaran Bradley ciaran.p.brad...@gmail.com wrote: Hi, I'm not entirely sure whether this is technically a Mezzanine issue or a Django issue. I noticed recently after a deploy (Python 2.7, Mezzanine 3.0.9, Django 1.6, Postgres 9.3 on a Debian 7 box) that I was generating big Postgres log files, filled with this event: https://gist.github.com/ciaranbradley/11207009 I tracked it down to the poll_twitter command running in cron. The command was working as expected, but it would generate a new entry each time it ran. After finding this similar issue: http://stackoverflow.com/questions/16841505/django-resetting-postgres-connection I applied the technique to the poll_twitter command last night and the problem seems to be gone. My poll_twitter now looks like this: https://gist.github.com/ciaranbradley/11207319 The command still seems to be up and running as normal and my log file loves me again. I don't see a specific instruction on Django docs to ensure you close the database connection when you create a command, so it might be fair to assume that the engine should close the connection gracefully after a command is run. Also I note that my deploy is low traffic (just a sandbox at the minute) so I suspect that higher traffic sites might be immune if the command uses an already open persistent connection. But that's just pure speculation on my part. Is anyone else experiencing similar? Thanks Ciaran -- 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 -- 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.
Re: [mezzanine-users] Mezzanine.accounts settings issue
On Sun, Apr 27, 2014 at 5:24 AM, mato...@gmail.com wrote: I have a problem with settings for mezzanine accounts. I would like to have profiles, where user is using mail instead of username. And also I would like to have Full name and What we should call you? instead of First name and Second name according to W3C suggestions. The issue is, if I do those things together: ACCOUNTS_PROFILE_FORM_EXCLUDE_FIELDS = ( first_name, last_name, ) ACCOUNTS_NO_USERNAME = True - it doesn't work. Returned error is: KeyError at /account/signup/ u'first_name' It is in code: try: self.cleaned_data[username] except KeyError: if not self.instance.username: username = %(first_name)s %(last_name)s % self.cleaned_data if not username.strip(): username = self.cleaned_data[email].split(@)[0] qs = User.objects.exclude(id=self.instance.id) user.username = unique_slug(qs, username, slugify(username)) password = self.cleaned_data.get(password1) The exact issue is line: username = %(first_name)s %(last_name)s % self.cleaned_data I think there should be another try to catch if first name doesnt exist and in that case use email or random string. Is the problem really that simple? Or I get it wrong and my issue need different repair? Yes I think you're right here and simply another check to handle no firstname/lastname combo will suffice - you'll see the next few lines already deal with not being able to extract a username from those two fields, in fact I think the intention there was to deal with this very case where those fields are omitted from the profile setup. Please go ahead and submit the fix if you'd like to. If the problem is really in that, I would like to contribute to mezzanine and repair that. Maybe also should be good to have in mezzanine same option for fullname+What should we call you insted of first+second name. What do you think? -- 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] modeltranslations - round 2
Previously we tried to integrate django-modeltranslation with Mezzanine, but the integration was very lightweight and had a lot of edge cases, so without the manpower to get it working properly, it was removed at the time. Now Mathias Ettinger has contributed a new attempt at this, and at a glance it looks much more complete. It will however need extremely thorough testing across all the difference features of Mezzanine before we can consider it. So this is just a general call to arms - if you can help out, please give it a try and see if you can break it (and if so, help fix it). https://github.com/stephenmcd/mezzanine/pull/1019 Thanks -- 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.
Re: [mezzanine-users] Issues in installing mezzanine
Looks like you might have temporarily been able to connect to PyPI at the time. Try again. On Mon, Apr 28, 2014 at 7:41 PM, Neeraj Dhiman neerajd.gh...@gmail.comwrote: I want to install anew copy of mezzanine. I am using virtual environment. I am using pip command for installation* pip install mezzanine *and the error i am getting is Downloading/unpacking mezzanine Downloading Mezzanine-3.1.3.tar.gz (5.9MB): 5.9MB downloaded Running setup.py egg_info for package mezzanine warning: no previously-included files matching '*' found under directory 'docs/build' warning: no previously-included files matching '*' found under directory '*/project_template/static' Downloading/unpacking django=1.4.10,!=1.6.0,1.7 (from mezzanine) Cannot fetch index base URL https://pypi.python.org/simple/ Could not find any downloads that satisfy the requirement django=1.4.10,!=1.6.0,1.7 (from mezzanine) Cleaning up... No distributions at all found for django=1.4.10,!=1.6.0,1.7 (from mezzanine) Storing complete log in /home/ghrix/.pip/pip.log Please tell what is going wrong 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. -- 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.
Re: [mezzanine-users] Amazon EC2 and Thumbnails
That's actually real clean - thanks for sharing. On Wed, Apr 30, 2014 at 4:17 AM, Brad Bode forb...@gmail.com wrote: Solved... for now. Although I wouldn't call it a bug I got the most help out of this bug listing : https://github.com/stephenmcd/mezzanine/issues/530 So the solution for me was two fold. First, I had to make sure all usages of the mezzanine thumbnail tag would work. Ideally this would be done without actually modifying mezzanine code. I chose and test Sorl-Thumbnailhttps://github.com/mariocesar/sorl-thumbnail, which works with S3. I monkey patched the code to replace the implementation of the template tag first. You have to do this so that ALL usages of the template tag defer to the Sorl version (which works with S3). Remember, the app that registers this new tag, must come AFTER the mezzanine core app which registers the original. from django import template from sorl.thumbnail import get_thumbnail from mezzanine.core.templatetags import mezzanine_tags register = template.get_library(mezzanine_tags) @register.simple_tag def thumbnail(image_url, width, height, quality=95, left=0.5, top=0.5): im = get_thumbnail(image_url, %sx%s % (width, height), crop='center', quality=quality) return im.url But in order to get the Mezzanine thumbnails to work in the Admin Interface you will need to replace the method directly (the admin uses a direct method call not the template tag): mezzanine_tags.thumbnail = thumbnail And finally, MAKE SURE that the module that registers this tag is register AFTER mezzanine otherwise it will not overwrite the mezzanine template tag. -- 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.
Re: [mezzanine-users] Re: modeltranslations - round 2
Probably a good question for Mathias on the github thread. On Wed, Apr 30, 2014 at 2:34 AM, Eduardo Rivas jerivasmel...@gmail.comwrote: I've really been looking forward to this one. Hopefully I will have time to try it out with the development version of some sites that currently use alternative translation approaches. Are we going to translate urls at all? Django gives two possible choices: mark the url patterns for translation, or use i18n patterns to prefix the whole site's urls with a lang code (what the Admin currently does). Is Mezzanine going to favor any particular approach? -- 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.
Re: [mezzanine-users] Re: modeltranslations - round 2
+1 on postponing, only for the sake of keeping the iterations as small as possible. On Wed, Apr 30, 2014 at 8:18 AM, Mathias Ettinger mathias.ettin...@gmail.com wrote: Le mardi 29 avril 2014 18:34:58 UTC+2, Eduardo Rivas a écrit : Django gives two possible choices: mark the url patterns for translation, or use i18n patterns to prefix the whole site's urls with a lang code (what the Admin currently does). Is Mezzanine going to favor any particular approach? I tend to prefer solutions that avoid marking slugs for translations since it will require extra tweakings to get every slug auto-populated from the title. I personnally use neither of theses approaches and rely on django sessions to change active language (with a setup very similar to https://docs.djangoproject.com/en/dev/topics/i18n/translation/#the-set-language-redirect-view). It is also possible to use both (translated slug with a lang code prefix) and will only require the same amount of work as translated slugs. Btw, I agree that we need to take a decision: with or without i18n_patterns? and with or without translated slugs? All four choices are valid. It is also possible to postpone this question and integrate translated slug (through a boolean setting?) into an other patch. As a side note, the language selector in the admin is gone in lattest version of mezzanine. Did I miss it somewhere or is the template not rendering it? -- 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.
Re: [mezzanine-users] fabfile deployment: where's the live_settings.py file?
It was renamed recently: https://github.com/stephenmcd/mezzanine/commit/8cb28fc0bd9ee98dfa926defa29b1b448551b124 Just edit deploy/local_settings.template On Sat, May 3, 2014 at 9:35 AM, Jared Nielsen nielsen.ja...@gmail.comwrote: I'm following Josh's instructions for fabfile deployment, here: http://bitofpixels.com/blog/deploying-mezzanine-to-digital-ocean-using-the-included-fabfile/ I started a new mezzanine project to test deployment, but, there's not live_settings.py file in my deploy directory. There is, however, a local_settings.py.template file containing the same information that I should expect to find in live_settings.py. Do I create a live_settings.py? Do I change the name of local_settings.py.template? What's best practice? -- 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.
Re: [mezzanine-users] Using Rich Text Fields in Mezzanine
Should be possible - blog posts use it, and they're not related to pages. What have you tried? On Wed, May 7, 2014 at 1:04 PM, Rafael Reuber rafaelreu...@gmail.comwrote: It's possible tu use a RitchTextField on a django.db.models.Model or just on mezzanine Page object? Em quinta-feira, 2 de janeiro de 2014 21h25min07s UTC-3, Stephen McDonald escreveu: If you'd like a single content field on your model, subclass mezzanine.core.models.RichText, eg: https://github.com/stephenmcd/mezzanine/blob/master/ mezzanine/pages/models.py#L268 If you'd like more control, and want to specify one or more RichText fields yourself, just use mezzanine.core.fields.RichTextField, eg: https://github.com/stephenmcd/mezzanine/blob/master/ mezzanine/core/models.py#L293 On Fri, Jan 3, 2014 at 11:01 AM, Karthik Kannan karthi...@gmail.comwrote: Hello, I'm trying to use a rich text field for one of the text areas in my mezzanine project. Can anyone point to some examples/documentation related to rich text fields? Trying to find examples of its usage but in vain. Thank you for your help. Karthik. -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- Stephen McDonald http://jupo.org -- 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.
Re: [mezzanine-users] Cartridge: All pages are available as Product Categories
I can't reproduce this. It might be worthwhile inspecting the actual database and ensuring that all those pages don't actually exist as product categories. On Fri, May 9, 2014 at 5:54 AM, Eduardo Rivas jerivasmel...@gmail.comwrote: Hello! I'm developing a site with Cartridge and I've noticed that all Pages in my page tree appear as valid categories for a Product. See the attached screenshot. The expected outcome is that only those Pages that start with Collections should be selectable as Categories for a Product (as they are the only ones of type Product Category). Home, Contact Us and all others shouldn't appear as Available product categories. Any ideas on how to fix this? It doesn't seem to be happening in the demo site. https://lh6.googleusercontent.com/-zdX78mABGGw/U2vgxUnVd8I/CFg/Nz3EKfQBb4M/s1600/Shop+Categories.png -- 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.
Re: [mezzanine-users] Re: Adding geodjango fields to the blog
Great stuff.
We (and most open source django apps that implement models) have this
fundamental customization problem. Mezzanine has tried to solve it in
different ways with EXTRA_MODEL_FIELDS and countless other bits of
configuration throughout its apps, but I think the swappable model approach
is spot on. I also think this approach could be applied across more of
Mezzanine - particularly the page model.
Personally I haven't had the space to invest any time in this, so it's
great to see this being done, and if you Hervé or anyone else has space for
continuing it further, that'd be fantastic - I'm out of action over the
next few weeks or so, but after then I'll hopefully be able to take a look
at what's been done and bring it all into a new major version.
Thanks again, and thanks for discussing it to begin with. Here are a few
quick notes on the code so far:
- Given the idea of applying this to other areas, we probably use a
get_post_model() function, instead opting for something like
get_swappable_model() which could live in mezzanine.utils somewhere.
- Prefer to have BlogPost = get_post_model() (or get_swappable_model())
somewhere at the top of each module rather than calling get_post_model()
all throughout the file - it's probably faster, and makes the code read
more like we're dealing with a model class.
- Don't think we need an abstract base model if we're using swappable
models - one seems to make the other redundant.
On Sun, May 11, 2014 at 2:10 AM, bors@gmail.com wrote:
Le samedi 10 mai 2014 13:36:27 UTC+2, bors...@gmail.com a écrit :
So a first step would be to add a BLOG_POST_MODEL setting, probably
using the swappable API.
But copy/pasting Mezzanine code is no fun and complicates maintenance. I
thought of splitting BlogPost into BaseBlogPost (or AbstractBlogPost
#namingthings) being a abstract model and just an empty BlogPost class.
Hi again,
I implemented this idea in a branch:
https://github.com/bors-ltd/mezzanine/tree/swappable_blogpost
And I managed to make a BlogPost model with a geometric field. But there's
a bit more work than expected.
I had to override ADMIN_MENU_ORDER to list theme.BlogPost instead of
blog.BlogPost.
The setting BLOG_POST_MODEL with BlogPost being swappable is working
like a charm. I added a get_post_model for places where BlogPost was
hard-coded.
Here is my BlogPost model:
class BlogPostManager(DisplayableManager, gis_models.GeoManager):
pass
class BlogPost(blog_models.AbstractBlogPost, gis_models.Model):
location = gis_models.PointField(verbose_name=Location, null=True)
objects = BlogPostManager()
The admin:
blogpost_fieldsets = deepcopy(blog_admin.blogpost_fieldsets)
blogpost_fieldsets.insert(1, (Location, {fields: (location,)}))
class BlogPostAdmin(blog_admin.BlogPostAdmin, admin.OSMGeoAdmin):
fieldsets = blogpost_fieldsets
map_width = 925
map_height = 457
The migration is a bit tricky, to pick up the existing posts:
def forwards(self, orm):
db.rename_table(blog_blogpost, theme_blogpost)
db.rename_table(blog_blogpost_categories,
theme_blogpost_categories)
db.rename_table(blog_blogpost_related_posts,
theme_blogpost_related_posts)
db.rename_index(blog_blogpost_pkey, theme_blogpost_pkey)
db.rename_index(blog_blogpost_site_id, theme_blogpost_site_id)
db.rename_index(blog_blogpost_user_id, theme_blogpost_user_id)
Then another migration to add extra fields:
def forwards(self, orm):
# Adding field 'BlogPost.location'
db.add_column('theme_blogpost', 'location',
self.gf
('django.contrib.gis.db.models.fields.PointField')(null=True),
keep_default=False)
So what do you think?
--
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.
Re: [mezzanine-users] Re: Adding geodjango fields to the blog
On Sun, May 11, 2014 at 10:14 AM, Stephen McDonald st...@jupo.org wrote:
Great stuff.
We (and most open source django apps that implement models) have this
fundamental customization problem. Mezzanine has tried to solve it in
different ways with EXTRA_MODEL_FIELDS and countless other bits of
configuration throughout its apps, but I think the swappable model approach
is spot on. I also think this approach could be applied across more of
Mezzanine - particularly the page model.
Personally I haven't had the space to invest any time in this, so it's
great to see this being done, and if you Hervé or anyone else has space for
continuing it further, that'd be fantastic - I'm out of action over the
next few weeks or so, but after then I'll hopefully be able to take a look
at what's been done and bring it all into a new major version.
Thanks again, and thanks for discussing it to begin with. Here are a few
quick notes on the code so far:
- Given the idea of applying this to other areas, we probably use a
get_post_model() function, instead opting for something like
get_swappable_model() which could live in mezzanine.utils somewhere.
Sorry I meant we probably *won't* use a get_post_model() function
- Prefer to have BlogPost = get_post_model() (or get_swappable_model())
somewhere at the top of each module rather than calling get_post_model()
all throughout the file - it's probably faster, and makes the code read
more like we're dealing with a model class.
- Don't think we need an abstract base model if we're using swappable
models - one seems to make the other redundant.
On Sun, May 11, 2014 at 2:10 AM, bors@gmail.com wrote:
Le samedi 10 mai 2014 13:36:27 UTC+2, bors...@gmail.com a écrit :
So a first step would be to add a BLOG_POST_MODEL setting, probably
using the swappable API.
But copy/pasting Mezzanine code is no fun and complicates maintenance. I
thought of splitting BlogPost into BaseBlogPost (or AbstractBlogPost
#namingthings) being a abstract model and just an empty BlogPost class.
Hi again,
I implemented this idea in a branch:
https://github.com/bors-ltd/mezzanine/tree/swappable_blogpost
And I managed to make a BlogPost model with a geometric field. But
there's a bit more work than expected.
I had to override ADMIN_MENU_ORDER to list theme.BlogPost instead of
blog.BlogPost.
The setting BLOG_POST_MODEL with BlogPost being swappable is working
like a charm. I added a get_post_model for places where BlogPost was
hard-coded.
Here is my BlogPost model:
class BlogPostManager(DisplayableManager, gis_models.GeoManager):
pass
class BlogPost(blog_models.AbstractBlogPost, gis_models.Model):
location = gis_models.PointField(verbose_name=Location, null=True)
objects = BlogPostManager()
The admin:
blogpost_fieldsets = deepcopy(blog_admin.blogpost_fieldsets)
blogpost_fieldsets.insert(1, (Location, {fields: (location,)}))
class BlogPostAdmin(blog_admin.BlogPostAdmin, admin.OSMGeoAdmin):
fieldsets = blogpost_fieldsets
map_width = 925
map_height = 457
The migration is a bit tricky, to pick up the existing posts:
def forwards(self, orm):
db.rename_table(blog_blogpost, theme_blogpost)
db.rename_table(blog_blogpost_categories,
theme_blogpost_categories)
db.rename_table(blog_blogpost_related_posts,
theme_blogpost_related_posts)
db.rename_index(blog_blogpost_pkey, theme_blogpost_pkey)
db.rename_index(blog_blogpost_site_id, theme_blogpost_site_id)
db.rename_index(blog_blogpost_user_id, theme_blogpost_user_id)
Then another migration to add extra fields:
def forwards(self, orm):
# Adding field 'BlogPost.location'
db.add_column('theme_blogpost', 'location',
self.gf
('django.contrib.gis.db.models.fields.PointField')(null=True),
keep_default=False)
So what do you think?
--
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
--
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.
Re: [mezzanine-users] Re: Adding geodjango fields to the blog
On Sun, May 11, 2014 at 10:14 AM, Stephen McDonald st...@jupo.org wrote:
Great stuff.
We (and most open source django apps that implement models) have this
fundamental customization problem. Mezzanine has tried to solve it in
different ways with EXTRA_MODEL_FIELDS and countless other bits of
configuration throughout its apps, but I think the swappable model approach
is spot on. I also think this approach could be applied across more of
Mezzanine - particularly the page model.
Personally I haven't had the space to invest any time in this, so it's
great to see this being done, and if you Hervé or anyone else has space for
continuing it further, that'd be fantastic - I'm out of action over the
next few weeks or so, but after then I'll hopefully be able to take a look
at what's been done and bring it all into a new major version.
Thanks again, and thanks for discussing it to begin with. Here are a few
quick notes on the code so far:
- Given the idea of applying this to other areas, we probably use a
get_post_model() function, instead opting for something like
get_swappable_model() which could live in mezzanine.utils somewhere.
- Prefer to have BlogPost = get_post_model() (or get_swappable_model())
somewhere at the top of each module rather than calling get_post_model()
all throughout the file - it's probably faster, and makes the code read
more like we're dealing with a model class.
- Don't think we need an abstract base model if we're using swappable
models - one seems to make the other redundant.
And please forget this last point, I'm quite wrong - we need the abstract
model to define all the base things the custom model being used to swap
with would need to implement.
On Sun, May 11, 2014 at 2:10 AM, bors@gmail.com wrote:
Le samedi 10 mai 2014 13:36:27 UTC+2, bors...@gmail.com a écrit :
So a first step would be to add a BLOG_POST_MODEL setting, probably
using the swappable API.
But copy/pasting Mezzanine code is no fun and complicates maintenance. I
thought of splitting BlogPost into BaseBlogPost (or AbstractBlogPost
#namingthings) being a abstract model and just an empty BlogPost class.
Hi again,
I implemented this idea in a branch:
https://github.com/bors-ltd/mezzanine/tree/swappable_blogpost
And I managed to make a BlogPost model with a geometric field. But
there's a bit more work than expected.
I had to override ADMIN_MENU_ORDER to list theme.BlogPost instead of
blog.BlogPost.
The setting BLOG_POST_MODEL with BlogPost being swappable is working
like a charm. I added a get_post_model for places where BlogPost was
hard-coded.
Here is my BlogPost model:
class BlogPostManager(DisplayableManager, gis_models.GeoManager):
pass
class BlogPost(blog_models.AbstractBlogPost, gis_models.Model):
location = gis_models.PointField(verbose_name=Location, null=True)
objects = BlogPostManager()
The admin:
blogpost_fieldsets = deepcopy(blog_admin.blogpost_fieldsets)
blogpost_fieldsets.insert(1, (Location, {fields: (location,)}))
class BlogPostAdmin(blog_admin.BlogPostAdmin, admin.OSMGeoAdmin):
fieldsets = blogpost_fieldsets
map_width = 925
map_height = 457
The migration is a bit tricky, to pick up the existing posts:
def forwards(self, orm):
db.rename_table(blog_blogpost, theme_blogpost)
db.rename_table(blog_blogpost_categories,
theme_blogpost_categories)
db.rename_table(blog_blogpost_related_posts,
theme_blogpost_related_posts)
db.rename_index(blog_blogpost_pkey, theme_blogpost_pkey)
db.rename_index(blog_blogpost_site_id, theme_blogpost_site_id)
db.rename_index(blog_blogpost_user_id, theme_blogpost_user_id)
Then another migration to add extra fields:
def forwards(self, orm):
# Adding field 'BlogPost.location'
db.add_column('theme_blogpost', 'location',
self.gf
('django.contrib.gis.db.models.fields.PointField')(null=True),
keep_default=False)
So what do you think?
--
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
--
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.
Re: [mezzanine-users] upgrading from 1.4.6 to 3.1.6 south disappears
Can't reproduce this going from a fresh 1.4.6 project and running it against 3.1.4. I've seen this behaviour with Django projects in general before though, where some unrelated issue has the side effect of Django reporting that management commands provided by third-party apps aren't available. While that's not much help, it's doubtful your issue is South related, and I suspect you need to somehow force the real issue to come up - perhaps with Django's own shell or runserver commands, which all have a --traceback option that might prove useful in this case too. Good luck. On Mon, May 12, 2014 at 5:50 AM, Penny Leach penelope.le...@gmail.comwrote: Hi there, I'm trying to upgrade (actually I'm only trying to start running a test upgrade) from 1.4.6 to 3.1.4 and failing before I start because as soon as I switch to using the 3.1.4 mezzanine code, south has disappeared from manage.py output. USE_SOUTH is set to true, and I can literally reproduce the problem thus: - checkout mezzanine to the 1.4.6 branch - manage.py shows south section - checkout mezzanine to the 3.1.4 branch - manage.py shows no south USE_SOUTH seems to be still a valid setting in 3.1.4 because it's there in the project template still, so I can't imagine that is the problem. Has something else changed? Thanks! Penny -- 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.
Re: [mezzanine-users] Trouble with Mezzanine blog drafts/published and post scheduling
You might find that you're seeing this happen while you're logged in as an admin user - in that case, any draft / scheduled content will still be visible to you on the site so that as an author you can preview it. Try logging out or using a second browser to view the site as a regular user would in order to confirm what's actually published. On Tue, May 13, 2014 at 8:24 AM, Amber Grimaldi amber.grima...@gmail.comwrote: Hi, I'm new to mezzanine and my site's blog posts draft/publish options are not working. Every post saved automatically published and the scheduling function and expiration are also disfunctional. Any suggestions where I might be able to look to fix or what I can do? -- 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.
Re: [mezzanine-users] upgrading from 1.4.6 to 3.1.6 south disappears
Nice work tracking that down. The error you're getting looks like a missing library (called future, that link you found is misleading) - how have you installed the latest Mezzanine version? It should automatically install the required dependencies when installing via pip - you can see the future lib references here in the setup: https://github.com/stephenmcd/mezzanine/blob/master/setup.py#L60 On Tue, May 13, 2014 at 2:51 PM, Penny Leach penelope.le...@gmail.comwrote: On Monday, May 12, 2014 3:19:44 AM UTC+2, Stephen McDonald wrote: Can't reproduce this going from a fresh 1.4.6 project and running it against 3.1.4. Thanks for looking into it! I've seen this behaviour with Django projects in general before though, where some unrelated issue has the side effect of Django reporting that management commands provided by third-party apps aren't available. While that's not much help, it's doubtful your issue is South related, and I suspect you need to somehow force the real issue to come up - perhaps with Django's own shell or runserver commands, which all have a --traceback option that might prove useful in this case too. It seems you're right. With further prodding, I managed to yield the following error: ImportError: No module named future.builtins Any ideas? I'm using python 2.7.3 and I found this page: https://docs.python.org/2/library/future_builtins.html but didn't get any further. Thanks! Penny -- 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.
Re: [mezzanine-users] mezzanine.forms - using email field as mail from
This used to be the default behaviour, but changed as this form of faking didn't work with many smtp gateways, and was considered bad form. At that point we changed it to just set the reply-to header of the email. Right now you're best off just modifying those few lines yourself. On Wed, May 14, 2014 at 3:39 AM, Enrico Tröger enrico.troe...@uvena.dewrote: Hi guys, I need your help: on a customers site, I built a simple contact form using mezzanine.forms. Now the customer wants that in the generated mail the From: header is set to the email address entered in the contact form by the visitor. I had a look in mezzanine.forms.page_processors.form_processor() and the information would be available by FormForForm.email_to(). So I could change a few lines to replace the email_from to email_from in the email_copies block. The question is, how do I accomplish this best? So far, I didn't find a clean way to override or disable this page_processor to add a custom one for form processing. Any ideas? Of course, I could simply write a custom app which provides this functionality (rendering a contact form and process the response) but I'm just curious whether there is a Mezzanine way :). Regards, Enrico -- Not sent from my smartphone. -- 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.
