[mezzanine-users] Re: Mezzanine 4.0 is released

2015-07-09 Thread Philip Southwell
What a fantastic accomplishment. I am extremely grateful to the work of all 
of you who have contributed to this release. Thanks again!

Phil

On Friday, July 10, 2015 at 8:35:16 AM UTC+9:30, Stephen McDonald wrote:
>
> Hi all,
>
> The new 4.0 release of Mezzanine is finally up on PyPI after 10 months 
> since the last release - a lot has happened! The project site (
> mezzanine.jupo.org) hasn't been upgraded yet, that will happen shortly. 
> The full changelog is here: 
> https://github.com/stephenmcd/mezzanine/blob/master/CHANGELOG - it has 
> become quite unwieldy given the variety of commit styles (it's 
> automatically generated from them), so one of the housekeeping tasks we 
> identified upon forming the official core team was to go back and redo it 
> manually. If you'd like to volunteer for that you'd be a superstar. Given 
> that, here's a human written overview of what's new:
>
> - The supported Django versions are now 1.7 and 1.8
> - Translatable content is now supported via django-modeltranslation
> - Dropped support for South, given Django 1.7's built-in migrations
> - TinyMCE upgraded to 4.0 (the previous version was around 3 years old!)
> - Major refactor of mezzanine.conf.settings resulting in greatly reduced 
> DB queries, and removal of manual "use_editable()" requirement
> - Major refactor of bundled fabfile, allowing for non-vcs deploys via 
> rsync, plus many more new features
> - We now use the same project layout that Django has for several versions, 
> where manage.py and others live outside the project package
> - A gazillion bugfixes and other minor improvements
>
> There could be more - I've just put that list together by skimming the 
> changelog. If I've missed anything noteworthy, please let everyone know in 
> this thread. Speaking of which, if you have an issue, I'd ask that instead 
> of replying here, you start a new email thread. If you know you've found a 
> real bug (eg can actually confirm the problem in the code), please open a 
> GitHub issue. 
>
> A massive thanks goes out to the newly formed core team who have been the 
> major contributors to all the above, and to everyone else who has chipped 
> in too, on the code base and here on the mailing list with support.
>
> Thanks and enjoy!
>
>
> -- 
> 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: Update to Bootstrap 3?

2015-06-16 Thread Philip Southwell
There may be a problem with the bootstrap 3.0 glyphicons here but I can't 
pin it down. Glyphs work fine for me in development but then only show as 
garble in production. I don't think it's a problem with my setup as all my 
other static files are fine.

Josh, you use font-awesome glyphs on the site you reference so I don't 
think it shows. I've fiddled about with a number of fixes but can't find 
anything that works. I'll let you know if I find a fix.

Phil

 

On Wednesday, January 8, 2014 at 5:58:07 AM UTC+10:30, Stephen McDonald 
wrote:
>
> Merged back in - thanks guys
>
>
> On Wed, Jan 8, 2014 at 5:52 AM, Josh Cartmell  > wrote:
>
>> I used it when I made http://mezzathe.me/preview/tableau/ which uses 
>> BS3.  I didn't encounter any issues with it there but if anyone else wants 
>> to take a look or test it in their own project that would probably be a 
>> good idea.  I also just tested it with the default Mezzanine theme and it 
>> seems to work fine there.  Here's a pull request:
>>
>> https://bitbucket.org/stephenmcd/mezzanine/pull-request/56/add-back-bootstrap-extrasjs/diff
>>
>> The css updates are because bootstrap applies those styles to menu items 
>> that have a parent with the class open.  bootstrap-extras.js takes 1/4 of a 
>> second or so to add the open class to the parent so things looked a little 
>> off with the background color not being changed immediately.
>>
>>
>> On Mon, Jan 6, 2014 at 11:24 AM, Stephen McDonald > > wrote:
>>
>>> Happy to bring it back in if someone wants to test it and create a pull 
>>> request.
>>>
>>>
>>> On Tue, Jan 7, 2014 at 5:47 AM, Josh Cartmell >> > wrote:
>>>
 Gotcha, thanks for the explanation Ed.

 I think just adding bootstrap-extras.js back would fix it.  The other 
 benefit of bootstrap-extras.js (other than multi level dropdowns) was that 
 it made dropdowns stay open for a few hundred milliseconds after a user's 
 mouse left them.  I think that's a win from a usability standpoint.


 On Sun, Jan 5, 2014 at 9:26 PM, Eduardo Rivas >>> > wrote:

> Off the top of my head, I removed it because it only served the 
> purpose of adding the multi-level drop-downs, and Mezzanine 3 uses a pure 
> CSS solution to achieve that. The downside is, as you noted, the submenus 
> are not accessible in mobile. I now remember I actually added it to the 
> "Know Issues" section of my pull request (#777). So yeah, it's a bug and 
> it 
> would be much appreciated if you could contribute a fix. I'd do it 
> myself, 
> but I really don't have the time right now.
>  
> -- 
> 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 
>>>
>>> -- 
>>> 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 
>

-- 
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 Demo content

2015-06-01 Thread Philip Southwell
Hi Ken. Thanks for the answer and thanks for the tip!

Phil

-- 
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 Demo content

2015-06-01 Thread Philip Southwell
Hi Ken. Thanks for the answer and thanks for the ti

-- 
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 Demo content

2015-06-01 Thread Philip Southwell
Hi there. I'm trying to understand how the demo content is loaded at 
createdb and can't sniff out a lead to track it down. If anyone could throw 
me a link to the relevant files in Mezzanine where the work happens that 
would be great!

-- 
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] In-line editing issue with Mezzanine FileField

2015-05-23 Thread Philip Southwell
Sure. Not sure when I'll get it done but I'll give it a shot.

On Sunday, May 24, 2015 at 2:31:53 AM UTC+9:30, Stephen McDonald wrote:
>
> Don't think this has ever been supported. 
>
> Not sure what would be involved, but the best approach might end up just 
> using a regular file upload field that saves to the media library, without 
> trying to suck in admin pages into inline editing.
>
> Are you interested in working on it?
>
>
> On Sat, May 23, 2015 at 2:20 AM, Philip Southwell  > wrote:
>
>> Hi there, I'm having trouble editing FileFields inline. When I attempt it 
>> I'm getting the FileField on the popup, with the normal symbol linking to 
>> the Media Manager, but when I click the image I'm not being taken to the 
>> media manager to select a new image. Nor when I click the "clear" link is 
>> the image being cleared. I'm being allowed to edit the other fields in the 
>> same popup so I know the mechanism's all working fine. 
>>
>> Here's my code:
>>
>>
>> {% editable homepage.banner_image homepage.main_title 
>> homepage.main_subtitle  %}
>> 
>> {{ homepage.main_title }}
>> {{ homepage.main_subtitle }}
>> {% endeditable %}
>>
>> The problem occurs in both Chrome and Firefox for me. I'm working in 
>> Python 3.4 on the development branch.
>>
>> -- 
>> 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.


[mezzanine-users] Re: In-line editing issue with Mezzanine FileField

2015-05-23 Thread Philip Southwell

I also noticed that the featured_image for blogposts are not editable in 
the standard templates. Is this because the feature is not supported?

-- 
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: In-line editing issue with Mezzanine FileField

2015-05-23 Thread Philip Southwell
I also noticed that the featured_image for blogposts are not editable in 
the standard templates. Is this because the feature is not supported?

On Saturday, May 23, 2015 at 6:50:33 PM UTC+9:30, Philip Southwell wrote:
>
> Hi there, I'm having trouble editing FileFields inline. When I attempt it 
> I'm getting the FileField on the popup, with the normal symbol linking to 
> the Media Manager, but when I click the image I'm not being taken to the 
> media manager to select a new image. Nor when I click the "clear" link is 
> the image being cleared. I'm being allowed to edit the other fields in the 
> same popup so I know the mechanism's all working fine. 
>
> Here's my code:
>
>
> {% editable homepage.banner_image homepage.main_title homepage
> .main_subtitle  %}
> 
> {{ homepage.main_title }}
> {{ homepage.main_subtitle }}
> {% endeditable %}
>
> The problem occurs in both Chrome and Firefox for me. I'm working in 
> Python 3.4 on the development branch.
>

-- 
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] In-line editing issue with Mezzanine FileField

2015-05-23 Thread Philip Southwell
Hi there, I'm having trouble editing FileFields inline. When I attempt it 
I'm getting the FileField on the popup, with the normal symbol linking to 
the Media Manager, but when I click the image I'm not being taken to the 
media manager to select a new image. Nor when I click the "clear" link is 
the image being cleared. I'm being allowed to edit the other fields in the 
same popup so I know the mechanism's all working fine. 

Here's my code:


{% editable homepage.banner_image homepage.main_title 
homepage.main_subtitle 
 %}

{{ homepage.main_title }}
{{ homepage.main_subtitle }}
{% endeditable %}

The problem occurs in both Chrome and Firefox for me. I'm working in Python 
3.4 on the development branch.

-- 
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 App to place Galleries as slideshows on other Pages

2015-05-09 Thread Philip Southwell
Hi there,

I've just released my first ever app on pypi called "mezzanine-slideshows". 
It allows the placement of Mezzanine Galleries as slideshows within other 
Mezzanine Pages.

Hopefully it's some help to the community  - I am extremely appreciative of 
the Mezzanine project as a whole.
Find it here on pypi 
, or at its github 
home here .

Phil

-- 
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: Site working perfectly in development, but admin and static pages are crashing in production

2015-04-04 Thread Philip Southwell
This turned out to be a django issue to do with proxy models and user 
permissions. Thanks for the help everyone.

-- 
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: Site working perfectly in development, but admin and static pages are crashing in production

2015-03-15 Thread Philip Southwell

>
> That sounds like a great path Graham. Unfortunately I'll not be able to do 
> that until tomorrow but I'll get back and let you know how it's been. 
> Thanks a lot.
>

Phil 

-- 
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: Site working perfectly in development, but admin and static pages are crashing in production

2015-03-15 Thread Philip Southwell

>
> Thanks Graham - that's where I was looking but I think I have that covered 
> already. My urls.py is below
>

urls.py
from __future__ import unicode_literals

from django.conf.urls import patterns, include, url
from django.conf.urls.i18n import i18n_patterns
from django.contrib.gis import admin

from mezzanine.core.views import direct_to_template

admin.autodiscover()

urlpatterns = i18n_patterns("",
("^admin/", include(admin.site.urls)),
)

urlpatterns += patterns('',
url(r'^advertisers/', include('free2me.urls', namespace="advertiser")),
url(r'^deals/', include('free2me.urls_public', namespace="public")),
url("^$", "free2me.views.deals_home_page", name="home"),

("^", include("mezzanine.urls")),
)
handler404 = "mezzanine.core.views.page_not_found"
handler500 = "mezzanine.core.views.server_error"
 

-- 
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: Site working perfectly in development, but admin and static pages are crashing in production

2015-03-14 Thread Philip Southwell
The page errors only occur when I'm logged in as a user.

-- 
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] Site working perfectly in development, but admin and static pages are crashing in production

2015-03-14 Thread Philip Southwell
Hi there,

I've been trying to sort this out for about 30 hours and it's killing me so 
any help would be appreciated. 

I have a django/mezzanine site which is working *perfectly* in development. 
Now it's deployment time and I'm getting a NoReverseMatch for every 
Mezzanine page and Mezzanine admin page. It's throwing the same error for 
every page not to do with my custom app "free2me". I've created a generic 
mezzanine project successfully with the same virtual environment so I know 
that all the libraries are working as intended.

The home page is fine http://test.free2me.com.au/ (or will be once I can 
get to the admin)
However when I link to any of the Mezzanine pages I get errors like this: 
http://test.free2me.com.au/about/

When I login to the admin I get a variety of similar errors each time I 
refresh, but relating to different models:
http://dpaste.com/1P4DHBZ
http://dpaste.com/1WBS0M9
http://dpaste.com/1AT8H4P

For completeness I've attached settings.py which is overwritten by 
local_settings.py for ADMINS, ALLOWED_HOSTS, DATABASES, MEDIA_ROOT, 
MEDIA_URL, STATIC_ROOT, STATIC_URL and KEYS.

I'm using a mod_wsgi 3.5/Python 3.3 webfaction app with a virtual 
environment. My app uses the geodjango component of django in case this 
matters.

Thanks in advance for any suggestions. This really is driving me crazy.

-- 
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.
from __future__ import absolute_import, unicode_literals

##
#   DEALS SETTINGS   #
##

# Size (kB) of maximum allowed to be uploaded for deals
MAX_IMAGE_SIZE = 1000

# Email address from which notification of Deal is sent
DEAL_NOTIFICATION_SENDER = 'donotre...@freeforme.com.au'

# A list of Email addresses to which notification of Deal is sent
DEAL_NOTIFICATION_RECEIVER = ['donotre...@freeforme.com.au',]


#
# PROJECT SPECIFIC SETTINGS #
#

LOGIN_REDIRECT_URL = '/advertisers/'

ACCOUNTS_VERIFICATION_REQUIRED = True
ACCOUNTS_APPROVAL_REQUIRED = True


##
# MEZZANINE SETTINGS #
##

# The following settings are already defined with default values in
# the ``defaults.py`` module within each of Mezzanine's apps, but are
# common enough to be put here, commented out, for convenient
# overriding. Please consult the settings documentation for a full list
# of settings Mezzanine implements:
# http://mezzanine.jupo.org/docs/configuration.html#default-settings

# Controls the ordering and grouping of the admin menu.
#
# ADMIN_MENU_ORDER = (
# ("Content", ("pages.Page", "blog.BlogPost",
#"generic.ThreadedComment", ("Media Library", "fb_browse"),)),
# ("Site", ("sites.Site", "redirects.Redirect", "conf.Setting")),
# ("Users", ("auth.User", "auth.Group",)),
# )

# A three item sequence, each containing a sequence of template tags
# used to render the admin dashboard.
#
# DASHBOARD_TAGS = (
# ("blog_tags.quick_blog", "mezzanine_tags.app_list"),
# ("comment_tags.recent_comments",),
# ("mezzanine_tags.recent_actions",),
# )

# A sequence of templates used by the ``page_menu`` template tag. Each
# item in the sequence is a three item sequence, containing a unique ID
# for the template, a label for the template, and the template path.
# These templates are then available for selection when editing which
# menus a page should appear in. Note that if a menu template is used
# that doesn't appear in this setting, all pages will appear in it.

# PAGE_MENU_TEMPLATES = (
# (1, "Top navigation bar", "pages/menus/dropdown.html"),
# (2, "Left-hand tree", "pages/menus/tree.html"),
# (3, "Footer", "pages/menus/footer.html"),
# )

# A sequence of fields that will be injected into Mezzanine's (or any
# library's) models. Each item in the sequence is a four item sequence.
# The first two items are the dotted path to the model and its field
# name to be added, and the dotted path to the field class to use for
# the field. The third and fourth items are a sequence of positional
# args and a dictionary of keyword args, to use when creating the
# field instance. When specifying the field class, the path
# ``django.models.db.`` can be omitted for regular Django model fields.
#
# EXTRA_MODEL_FIELDS = (
# (
# # Dotted path to field.
# "mezzanine.blog.models.BlogPost.image",
# # Dotted path to field class.
# "somelib.fields.ImageField",
# # Positional args for field class.
# ("Image",),
# # Keyword args for field class.
# {"blank": True, "upload_to": "blog"},
# ),
# # Example of adding a field to *all* of Mezzanine's content types:
# (
# "mezzanine.pages.models.Page.another_f

Re: [mezzanine-users] How can I stop people making their own accounts?

2014-12-19 Thread Philip Southwell
Thanks Josh.Your solution is the one I took and I don't see any problems with 
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.


[mezzanine-users] How can I stop people making their own accounts?

2014-12-16 Thread Philip Southwell
I'm wondering if there's a built in setting in Mezzanine which stops people 
signing up for their own accounts? All I can see is 
ACCOUNTS_APPROVAL_REQUIRED  but I'd rather people not have the option of 
creating an account if they don't already have one. 

Would I need to change the templates so that option was not available?  

-- 
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: editable.css not styling on production server

2014-05-18 Thread Philip Southwell
When I've changed css files sometimes I've forgotten to run 
"collectstatic". Could this be your trouble?

On Monday, May 19, 2014 3:19:07 AM UTC+9:30, Jared Nielsen wrote:
>
> HI all,
> Encountering strange behavior with the editable regions on a production 
> site while logged in as admin. The editable.css is not styling as expected. 
> It works fine on development and all other styles are rendering as they 
> should. Any thoughts?
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [mezzanine-users] Cartridge Setup Issue

2014-03-12 Thread Philip Southwell
With this fix I can now view the site home page. Thanks a lot for this 
amazingly quick work!

Kind Regards,
Phil

On Wednesday, March 12, 2014 7:51:25 AM UTC+10:30, Stephen McDonald wrote:
>
> Potential fix here:
>
>
> https://github.com/stephenmcd/cartridge/commit/1aa5bf11dcb4e0b8955f4236a3b0c85b2f8b6f1d
>
>
> On Tue, Mar 11, 2014 at 11:06 PM, Philip Southwell 
> 
> > wrote:
>
>> 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 
>> instructions<http://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  3 > class="panel-body"> 4 {% spaceless %} 5  
>> 6  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 }} 10 {% if 
>> request.cart.total_quantity != 0 %} 11 > %}" class="btn btn-primary"> 12 {% if request.session.order.step %}{% 
>> trans "Return to Checkout" %}{% else %}{% trans "Go to Checkout" %}{% endif 
>> %} 13  14 {% endif %} 15 {% if settings.SHOP_USE_WISHLIST %} 16> href="{% url "shop_wishlist" %}" class="btn-wishlist"> 
>> 17  18 {% blocktrans count 
>> request.wishlist|length as wishlist_count %}Wishlist contains 1 item{% 
>> plural %} Wishlist contains {{ wishlist_count }} items{% endblocktrans 
>> %} 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-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.


[mezzanine-users] Re: can anyone suggest me some host which is Australia based and also mezzanine&django friendly?

2014-03-11 Thread Philip Southwell
If you're worried about speed (as opposed to 'buying Australian') I 
recently moved to Webfaction, and chose their Singapore servers when 
signing up. It works quicker than the Australian host which I moved from!


On Monday, March 3, 2014 10:13:43 PM UTC+10:30, lu zou wrote:
>
> As above ,can anyone suggest me some host which is Australia based and 
> also mezzanine&django friendly? :)
>

-- 
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] Cartridge Setup Issue

2014-03-11 Thread Philip Southwell
Hi there,

I've just started using Mezzanine and I love it (my first Mezzanine site 
here !)

Now I'm trying out Cartridge according to the installation 
instructions. 
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:GETRequest 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 28Python 
Executable:c:\Code\venvs\shop\Scripts\python.exePython 
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 supported1{% load i18n future shop_tags mezzanine_tags 
%} 2 3  
4 {% spaceless %} 5  6  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 }} 10 {% if 
request.cart.total_quantity != 0 %} 11  12 {% if request.session.order.step %}{% trans 
"Return to Checkout" %}{% else %}{% trans "Go to Checkout" %}{% endif %} 
13 
14 {% endif %} 15 {% if settings.SHOP_USE_WISHLIST %} 16  17  18 {% blocktrans count request.wishlist|length as 
wishlist_count %}Wishlist contains 1 item{% plural %} Wishlist contains {{ 
wishlist_count }} items{% endblocktrans %} 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.