Re: [mezzanine-users] Does Cartridge has customer center?
Mezzanine has public user accounts with profiles via the mezzanine.accounts app: http://mezzanine.jupo.org/docs/user-accounts.html Cartridge extends it with the ability to view your past orders. On Mon, Oct 13, 2014 at 1:03 AM, Wesley nisp...@gmail.com wrote: Hi guys, I setup a shop based on Mezzanine and Cartridge. Is there any existing page like customer center, I mean, here customer who is buying anything from the shop can maintain his/her our profile, for example, change password, email address, and also can see his/her own order history. I see I can develop such interface, just wanna if there is existing one integrated to Mezzanine/Cartridge. 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] Dealing with a large number of pages
I don't know of one, but I'll just counter one anecdote with another. I generated 1463 pages evenly spread (11 primary pages, each with 11 children, which each have 11 children), and on my macbook air the admin interface takes about 6 seconds to render, the front-end which renders a full tree as well as some limited trees takes about 3 seconds. 90 seconds on your machine vs 10 seconds on a consumer grade laptop seems unreasonable. What type of machine are you running on? You might also like to dig into some profiling tools, like django-debug-toolbar and pycallgraph, but be warned adding these will certainly make things slower, so don't be deceived. On Tue, Oct 14, 2014 at 2:16 AM, Jeff Heard jefferson.r.he...@gmail.com wrote: Is there a mod that dynamically loads or paginates the pages section in the admin? I have 1559 pages and I always get a 504 timeout on rendering. When I don’t, it still takes like a minute and a half to render the pages admin menu... -- You received this message because you are 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] Dealing with a large number of pages
PS: Here's the code I used for generating the page tree. https://gist.github.com/stephenmcd/f0673790525f1c40d2ca On Tue, Oct 14, 2014 at 6:55 AM, Stephen McDonald st...@jupo.org wrote: I don't know of one, but I'll just counter one anecdote with another. I generated 1463 pages evenly spread (11 primary pages, each with 11 children, which each have 11 children), and on my macbook air the admin interface takes about 6 seconds to render, the front-end which renders a full tree as well as some limited trees takes about 3 seconds. 90 seconds on your machine vs 10 seconds on a consumer grade laptop seems unreasonable. What type of machine are you running on? You might also like to dig into some profiling tools, like django-debug-toolbar and pycallgraph, but be warned adding these will certainly make things slower, so don't be deceived. On Tue, Oct 14, 2014 at 2:16 AM, Jeff Heard jefferson.r.he...@gmail.com wrote: Is there a mod that dynamically loads or paginates the pages section in the admin? I have 1559 pages and I always get a 504 timeout on rendering. When I don’t, it still takes like a minute and a half to render the pages admin menu... -- You received this message because you are 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] Dealing with a large number of pages
That's awesome advice Alex.
I took it a bit further and ripped out more template logic, here's my
resulting admin template which renders my 1,400 or so pages in roughly 25%
of the time:
https://gist.github.com/stephenmcd/87a3af5c9a3c66a6c716
- Removed all permission setting/checking
- Removed iterating through all the page types and hard-coded the list of
these (still containing the page_id variable)
- Removed all use of {% url %} template tag, hard-coding admin urls (this
is a huge gain)
- Removed all use of {% static %} template tag, hard-coding paths to static
assests
- Removed cycling through CSS classes (I'm not even sure these are used
anymore)
On Wed, Oct 15, 2014 at 12:43 PM, Alexander Hill alecdu...@gmail.com
wrote:
I've run up against slow page admin rendering too, but nothing as extreme
as 90 seconds – more like what Stephen is reporting, under ten seconds. I
have a hierarchy with a little over a thousand pages, and I think the
maximum depth is five.
I found a lot of time was spent rendering
templates/pages/menus/admin.html, specifically ascertaining permissions and
building the list of models for the Add... menu. The majority of my pages
are of one type that should only have that same type as children, and
everyone should be able to add them, so I've overridden that template to
just render a link instead of a drop down Add... menu which always adds
that page type, instead of iterating over the list of models and checking
permissions for each.
That cuts down my rendering time by about half.
Unfortunately Django templates ARE slow, and rendering a thousand of them
nested is never going to be quick. That said, the times you're seeing are
extreme and I can't think what would cause that in normal operation, so you
probably will need to do some profiling...there is a Django template
timings plugin for the Django debug toolbar which might help you:
https://github.com/orf/django-debug-toolbar-template-timings
Alex
On Wednesday, 15 October 2014 00:46:27 UTC+8, Jefferson Heard wrote:
Stephen, thanks. Would a flatter hierarchy affect things much? It's not
so much the render time as the processing time. I'm getting to 504
timeouts on the server. I'm running in AWS, with an Amazon postgres and a
medium instance running the web application. I suppose a profiling tool
*is* the next step, but I wondered if anyone else had run into this.
On Mon, Oct 13, 2014 at 3:55 PM, Stephen McDonald st...@jupo.org wrote:
I don't know of one, but I'll just counter one anecdote with another.
I generated 1463 pages evenly spread (11 primary pages, each with 11
children, which each have 11 children), and on my macbook air the admin
interface takes about 6 seconds to render, the front-end which renders a
full tree as well as some limited trees takes about 3 seconds.
90 seconds on your machine vs 10 seconds on a consumer grade laptop
seems unreasonable. What type of machine are you running on?
You might also like to dig into some profiling tools, like
django-debug-toolbar and pycallgraph, but be warned adding these will
certainly make things slower, so don't be deceived.
On Tue, Oct 14, 2014 at 2:16 AM, Jeff Heard jefferso...@gmail.com
wrote:
Is there a mod that dynamically loads or paginates the pages section in
the admin? I have 1559 pages and I always get a 504 timeout on rendering.
When I don’t, it still takes like a minute and a half to render the pages
admin menu...
--
You received this message because you are 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] Dealing with a large number of pages
No the dropdown still appears against each page, the list of page models is
hard coded though.
On 16/10/2014 12:54 AM, Josh Cartmell joshcar...@gmail.com wrote:
Would this mean that you could now only add custom page types using the
top drop down?
On Tue, Oct 14, 2014 at 10:13 PM, Stephen McDonald st...@jupo.org wrote:
That's awesome advice Alex.
I took it a bit further and ripped out more template logic, here's my
resulting admin template which renders my 1,400 or so pages in roughly 25%
of the time:
https://gist.github.com/stephenmcd/87a3af5c9a3c66a6c716
- Removed all permission setting/checking
- Removed iterating through all the page types and hard-coded the list of
these (still containing the page_id variable)
- Removed all use of {% url %} template tag, hard-coding admin urls (this
is a huge gain)
- Removed all use of {% static %} template tag, hard-coding paths to
static assests
- Removed cycling through CSS classes (I'm not even sure these are used
anymore)
On Wed, Oct 15, 2014 at 12:43 PM, Alexander Hill alecdu...@gmail.com
wrote:
I've run up against slow page admin rendering too, but nothing as
extreme as 90 seconds – more like what Stephen is reporting, under ten
seconds. I have a hierarchy with a little over a thousand pages, and I
think the maximum depth is five.
I found a lot of time was spent rendering
templates/pages/menus/admin.html, specifically ascertaining permissions and
building the list of models for the Add... menu. The majority of my pages
are of one type that should only have that same type as children, and
everyone should be able to add them, so I've overridden that template to
just render a link instead of a drop down Add... menu which always adds
that page type, instead of iterating over the list of models and checking
permissions for each.
That cuts down my rendering time by about half.
Unfortunately Django templates ARE slow, and rendering a thousand of
them nested is never going to be quick. That said, the times you're seeing
are extreme and I can't think what would cause that in normal operation, so
you probably will need to do some profiling...there is a Django template
timings plugin for the Django debug toolbar which might help you:
https://github.com/orf/django-debug-toolbar-template-timings
Alex
On Wednesday, 15 October 2014 00:46:27 UTC+8, Jefferson Heard wrote:
Stephen, thanks. Would a flatter hierarchy affect things much? It's
not so much the render time as the processing time. I'm getting to 504
timeouts on the server. I'm running in AWS, with an Amazon postgres and a
medium instance running the web application. I suppose a profiling tool
*is* the next step, but I wondered if anyone else had run into this.
On Mon, Oct 13, 2014 at 3:55 PM, Stephen McDonald st...@jupo.org
wrote:
I don't know of one, but I'll just counter one anecdote with another.
I generated 1463 pages evenly spread (11 primary pages, each with 11
children, which each have 11 children), and on my macbook air the admin
interface takes about 6 seconds to render, the front-end which renders a
full tree as well as some limited trees takes about 3 seconds.
90 seconds on your machine vs 10 seconds on a consumer grade laptop
seems unreasonable. What type of machine are you running on?
You might also like to dig into some profiling tools, like
django-debug-toolbar and pycallgraph, but be warned adding these will
certainly make things slower, so don't be deceived.
On Tue, Oct 14, 2014 at 2:16 AM, Jeff Heard jefferso...@gmail.com
wrote:
Is there a mod that dynamically loads or paginates the pages section
in the admin? I have 1559 pages and I always get a 504 timeout on
rendering. When I don’t, it still takes like a minute and a half to
render
the pages admin menu...
--
You received this message because you are 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
Re: [mezzanine-users] Can´t make model searchable
The model you want searched needs to subclass Displayable - your Galeria
model will do that, since it subclasses Page, which subclasses Displayable,
but your Item model does not.
You need to stop and think about what a search result will look like and
actually link to, which is the main idea around search being tied to the
Displayable model - Displayable provides a title and url, which search
results make use of.
You might end up having your Item descriptions somehow feed into a
searchable field on your Galeria model, and have it remain the thing that
is searched and displayed as a distinct search result. Alternatively, it
might be more suitable to make the Item mode subclass Displayable, with
each Item having its own title (which would make your name field
redundant) and url. Perhaps the url field on the Item model isn't strictly
necessary, and you'll need to populate it with the parent Galeria
instance's url somehow.
You'll need to work out which approach best suits your case, and either way
you'll probably need to implement some functionality in one of the model's
save methods in order to populate some data in the other.
Good luck!
On Tue, Oct 28, 2014 at 5:37 AM, Ernesto Palafox palafox.erne...@gmail.com
wrote:
Hi all, im new to mezzanine and I think its awesome.
I am trying to follow the documentation
http://mezzanine.jupo.org/docs/search-engine.html to made searchable my
custon contentype
My models.py looks more or less like this:
class Galeria(Page):
pass
class Item(models.Model):
gallery = models.ForeignKey(Galeria, related_name=gallery)
name = models.CharField(max_length=30)
description_1 = RichTextField(blank=True,null=True)
objects = SearchableManager()
search_fields = (name, description_1 )
I also have {%search_form galeria.Item %}.
However, when i try the search, it returns me nothing. ¿What am i doing
wrong?
--
You received this message because you are 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] M2M With Products
Should the first arg just be shop.Product ? On Wed, Oct 29, 2014 at 9:36 AM, Josh B josh.batche...@wearetopsecret.com wrote: I am trying to tie products to an event, but for some reason I am unable to create a M2M with the Products table. event_products = models.ManyToManyField(cartridge.shop.models.Product, blank=True, verbose_name=_(Products),related_name='event_products', ) Tried a few different ways and I get the following 'products' has an m2m relation with model cartridge.shop.models.Product, which has either not been installed or is abstract. 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] Can´t make model searchable
I think that was part of the idea around previously expecting only
Displayable subclasses to work - that guaranteed having a description field
as well as some accessible URL for the search result to point to.
As part of removing the restriction on subclassing Displayable, you'll see
in that commit above I reworked the search results template to not expect
anything in particular - perhaps someone just wants results to appear that
don't actually link to anything.
But yes, get_absolute_url is needed on the result for it to link somewhere.
On Wed, Oct 29, 2014 at 11:37 AM, Josh Cartmell joshcar...@gmail.com
wrote:
Cool, thanks Steve. To make this work I'm assuming you have to specify a
get_absolute_url on the non Displayable models?
On Tue, Oct 28, 2014 at 5:47 PM, Stephen McDonald st...@jupo.org wrote:
You're right the docs don't match the advice I gave around Displayable.
Reading that, I took a much closer look at why subclassing Displayable is a
strict requirement for a model being searchable, and I don't think that
needs to be the case.
I've made the following change which means that the example in the docs
and the code original posted in this thread should work:
https://github.com/stephenmcd/mezzanine/commit/cfc47424a09b51a92fc44eeca3af0ea58ff8ddf9
On Wed, Oct 29, 2014 at 2:03 AM, Josh Cartmell joshcar...@gmail.com
wrote:
Hey Steve, some of the confusion might come from the docs. The last
example here is almost identical to what Ernesto has done (i.e.
search_fields specified on a non Displayable model):
https://mezzanine.jupo.org/docs/search-engine.html#search-api
Are the docs wrong in that instance, or is something else at play?
On Mon, Oct 27, 2014 at 4:21 PM, Ernesto Palafox
palafox.erne...@gmail.com wrote:
Thanks for your advice Stephen im trying to make a query but i get an
error:
FieldError: Cannot resolve keyword u'name' into field. Choices are:
_meta_title, _order, children, content_model, created, description,
expiry_date, form, gallery, gen_description, homepage, id, in_menus,
in_sitemap, keywords, keywords_string, link, login_required, galeria,
pageimage, parent, publish_date, richtextpage, short_url, site, slide,
slug, status, title, titles, updated
Its like my searchable fields arent recognized. How can i solve this?
Thanks!
El lunes, 27 de octubre de 2014 13:45:17 UTC-6, Stephen McDonald
escribió:
The model you want searched needs to subclass Displayable - your Galeria
model will do that, since it subclasses Page, which subclasses
Displayable,
but your Item model does not.
You need to stop and think about what a search result will look like
and actually link to, which is the main idea around search being tied to
the Displayable model - Displayable provides a title and url, which
search results make use of.
You might end up having your Item descriptions somehow feed into a
searchable field on your Galeria model, and have it remain the thing that
is searched and displayed as a distinct search result. Alternatively, it
might be more suitable to make the Item mode subclass Displayable, with
each Item having its own title (which would make your name field
redundant) and url. Perhaps the url field on the Item model isn't strictly
necessary, and you'll need to populate it with the parent Galeria
instance's url somehow.
You'll need to work out which approach best suits your case, and
either way you'll probably need to implement some functionality in one of
the model's save methods in order to populate some data in the other.
Good luck!
On Tue, Oct 28, 2014 at 5:37 AM, Ernesto Palafox palafox...@gmail.com
wrote:
Hi all, im new to mezzanine and I think its awesome.
I am trying to follow the documentation http://
mezzanine.jupo.org/docs/search-engine.html to made searchable my
custon contentype
My models.py looks more or less like this:
class Galeria(Page):
pass
class Item(models.Model):
gallery = models.ForeignKey(Galeria, related_name=gallery)
name = models.CharField(max_length=30)
description_1 = RichTextField(blank=True,null=True)
objects = SearchableManager()
search_fields = (name, description_1 )
I also have {%search_form galeria.Item %}.
However, when i try the search, it returns me nothing. ¿What am i
doing wrong?
--
You received this message because you are 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.
--
You received this message because you
[mezzanine-users] Drum 0.2.2 released
Hi all, I just released Drum 0.2.2: https://github.com/stephenmcd/drum For those unfamiliar with it, it's a project built with Mezzanine that provides a link sharing + discussion site, just like Hacker News or Reddit. It started out as a simple demo to showcase all the non-CMS features of Mezzanine like ratings, user accounts and threaded comments, and has since grown into a complete project in its own right. I wrote more about that original demo in a lot of detail here: http://blog.jupo.org/2013/04/30/building-social-apps-with-mezzanine-drum/ Relative to Mezzanine, there are probably very few users of Drum, but this is a noteworthy release in that it adds a very cool new feature - the ability to auto-tag new links as they're added to the site. It's fairly simplistic, but it might spark some ideas for other Mezzanine users, as well as possibly working its way into Mezzanine as a feature some day. You can see a full description of how the auto-tagging works in the commit to the documentation: https://github.com/stephenmcd/drum/commit/e84fafdafaa86a509e3668e23d50447f218f2918 I've been automatically feeding programming articles into the Drum demo site for about a year now. You can see here the result of the auto-tagging when applied to the several thousand links that already exist there - it turned out really effective: http://drum.jupo.org/tags/ Lastly, here is the full set of commits that added this feature to Drum for those interested: https://github.com/stephenmcd/drum/compare/4ad137537c...8015c64a7b -- 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] Rendering fields manually Mezzanine Forms
A bit of Googling for how to do this with a regular Django form will yield
an answer - the form object in the code you showed is just a regular Django
form.
On Tue, Nov 11, 2014 at 7:33 AM, Ernesto Palafox palafox.erne...@gmail.com
wrote:
Hi!
I am working with mezzanine forms, and it works like charm, but i was
wondering if i could render manually the fields on the template. I just
want to put some headers between some fields, and make others two or three
fields per row.
¿is it possible to access manually the fields instead of using {%
fields_for form %} tag?
Any advice on this would be appreciated!
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] Re: Django 1.7 support
By all accounts the current state of Mezzanine on both Github and BitBucket works wonderfully with Django 1.7. You can actually specify a commit on either of these sites as an explicit dependency for your project, so using Django 1.7 is possible right now. On Sat, Nov 29, 2014 at 8:06 AM, Radek Svarz radek.sv...@gmail.com wrote: Hi, how can we help to make the new release (Mezzanine v 3.1.11?) with the setup.py listing Django 1.7.x? Radek On Wednesday, October 8, 2014 8:49:00 PM UTC+2, Stephen McDonald wrote: There's an outstanding issue here: https://github.com/stephenmcd/mezzanine/issues/1123 It only affects test data with new projects, so not a real blocker for anyone building a project. On Wed, Oct 8, 2014 at 5:54 PM, elguavas elgu...@gmail.com wrote: so is mezz django 1.7 ready to go yet? pip install mezzanine still seems to be pulling in django 1.6.x . -- 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] Direct POST payments in Cartridge
There was a lengthy mailing list discussion on this years ago where everyone agreed that there shouldn't be unfinished orders floating around in the database. I still agree with that and I'm not particularly keen on the idea of having to maintain this as an option and feature. Cartridge is intentionally very simple and limited compared to the alternatives, I'd rather keep it that way. BTW I naively assumed that Cartridge dealt with credit card handling well enough from a PCI-DSS perspective - the card number doesn't get stored anywhere and is only posted from one checkout step form to the next. On Wed, Dec 10, 2014 at 1:03 PM, Alexander Hill a...@hill.net.au wrote: Hi Josh, I'm interested to hear from Steve too. Since Cartridge was initially written to call payment processors from the server, only creating the orders after payment was submitted makes sense it makes sense – doing so earlier does introduce a bit of extra complexity. Keeping the cart in sync with the order if the customer gets up to the payment step and then adds items, for example. I remember reading through cartridge-payments a couple of years back. I'm a bit wary of side-effects in forms (like saving the order object). That said, it's a clever way of getting it done without any custom view code, which is what I'm doing. I might copy it :) Am I missing something or is the added callback_uuid field not strictly necessary? The order number should uniquely identify the payment anyway. Cheers, Alex On Dec 10, 2014 12:45 AM, Josh Cartmell joshcar...@gmail.com wrote: I like the idea of having an order ID before payment (for the reasons you outlined) but I'd be curious to hear if Steve had any particular reason for not doing this when he originally created Cartridge. Also, in case you haven't seen it you might want to look at https://github.com/explodes/cartridge-payments On Mon, Dec 8, 2014 at 9:39 PM, Alexander Hill a...@hill.net.au wrote: Hi all, I don't want credit card details touching our server for PCI-DSS reasons and have a no-Javascript constraint, so I use direct POST with our payment processor. In my project I create an Order instance before the payment page is displayed, so that I'm able to pass the correct order number to my payment processor. I remember seeing a similar workaround in someone else's payment processing code a long time ago so I assume this kind of thing might be useful to more than just me. It's quite messy to bolt on aftermarket, so I propose integrating it into Cartridge, probably toggled by a new setting, SHOP_CREATE_ORDER_BEFORE_PAYMENT or similar. This change also has the helpful side-effect of allowing one to query incomplete orders – I have a job that sends a daily email summary of incomplete orders to sales staff, for example. Thoughts? Alex -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are 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] MediaFile type
If the repo has been abandoned I'd suggest forking it and bringing it up to date - then we can just update the URL for it in Mezzanine's readme to point to your fork. On Wed, Dec 17, 2014 at 12:38 PM, Diogo Baeder diogobae...@gmail.com wrote: Hi guys, There is a 3rd-party app called Mezzanine File Collections here: https://github.com/thibault/mezzanine-file-collections ; however, this app seems to have been abandoned, and I think Mezzanine could rock even more if it had a MediaFile type - since some other CMSs use to have such feature built-in. Do you think it would be worthwhile to create such a feature for Mezzanine itself, and keep it internally, instead of as a 3rd-party app? If so, I can implement it, just wanted to make sure it will be useful for more people who use Mezzanine. And, of course, congratulations on the CMS, it's my favorite one by far! :-) Thanks, Diogo -- You received this message because you are 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] Time to upgrade jQuery?
Thanks Ed - sounds fine so long as we judiciously test all the third party libraries bundled, I know there have been rough edges around those in the past when upgrading jquery itself. The gallery image lightbox thing, the drag/drop interface within the admin, and there are probably others that don't come to mind. Thanks again. On Thu, Dec 25, 2014 at 10:37 AM, Eduardo Rivas jerivasmel...@gmail.com wrote: Hello everyone! I've started upgrading Mezzanine to the latest version of Bootstrap (v3.3.1) and this would require at least jQuery 1.9.1 [source https://github.com/twbs/bootstrap/blob/master/dist/js/bootstrap.js#L14]. I've encountered this problem before when using third party libraries that don't play along with Mezzanine's three year old version of jQuery (1.7.1, released November 2011 http://blog.jquery.com/2011/11/21/jquery-1-7-1-released/). I would like to ask everybody (and Steve specifically) if you are open to upgrading the version of jQuery to at least 1.9.1. Cheers. -- You received this message because you are 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] Status of next release
Hi all, Merry xmas! Next release isn't quite there yet, as I'm still coming across regressions against Django 1.7 during the infrequent moments I have available to test it. I feel like it's ready now, but that's worth little as that's been the perceived state for quite a while. As for the issue, previously all of the mandatory and optional data Mezzanine and Cartridge would set up in the database when its own createdb command or Django's syncdb command were used, would happen via Django's relevant signal handlers. With Django 1.7's new migrations, it appears these can no longer reliably be hooked into when tables are first created (specifically the created_models argument has been removed from the new post_migrate signal). I've refactored all the data setup to be explicitly part of the createdb command that we've always officially recommended as part of the setup phase. So initial syncdb/migrate commands won't trigger any of that now, but if you've done that you've already gone off the beaten track. https://github.com/stephenmcd/mezzanine/commit/70b0737a1ee128e2e304c5c2d8bc3ecf416eb6eb I'll just repeat the plea for help testing the current development branch against both Django 1.6 and 1.7. That's end to end testing, from creating a new project against different database backends, building custom models, integrating third party apps, using all the features in the admin interface, etc etc etc. Been working for my existing site really doesn't fit the end to end testing bill here either, as only sitting down and purposefully testing everything is the only way picking up things like this latest regression will happen. Thanks to the handful of people who have been testing against 1.7 and contributing fixes over the last couple months - you guys are the ones doing 90% of the work, and keeping Mezzanine going wouldn't be possible without 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.
[mezzanine-users] Mezzanine and Docker
if you're into that sort of thing: https://github.com/stephenmcd/mezzanine/pull/1186 -- 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] Time to upgrade jQuery?
I think it'd be better for the project to just ship with a single version if possible. There shouldn't be anything stopping the developer from using whatever version they like for the public site - if there is, then that's what should be addressed. On Wed, Dec 31, 2014 at 8:11 AM, Eduardo Rivas jerivasmel...@gmail.com wrote: Sorry for the delay guys, I left for a short vacation. J, off the top of my head, the benefits of using newer versions of jQuery are: - Support for the latest versions of Bootstrap (as mentioned in my first email). On the CSS side, Bootstrap gives Mezzanine a theme, grid, form styles, etc; but on the Javascript / jQuery side it provides a complete UI kit, letting you build interactive interfaces with elements such as tabs, accordions, dropdowns, affixes, modal dialogs, etc. More info here: http://getbootstrap.com/javascript/. - We can benefit from security fixes (I don't know of any problems with 1.7.1, but they might exist). Also, general bug fixes and enhancements. - If we migrate to even more recent versions, such as the 2.x family, we would get increased speed and reduced size, because these family drops support for legacy browsers, among other things. http://blog.jquery.com/2013/04/18/jquery-2-0-released/ (see How 2.0 changed). - On the same link you can see how you could create custom versions of jQuery for the 2.x family to cater to the specific needs of your site due to the new modular approach of building it, further reducing the size of the final file. Steve, I also came up with an alternate approach: Stay with 1.7.1 for the Admin, but ship more recent versions for the public site. Perhaps we can create a couple of new settings to substitute JQUERY_FILENAME: for the admin we could have JQUERY_ADMIN_FILENAME and for the general site JQUERY_PUBLIC_FILENAME. This way frontend developers can experiment with the cutting edge without worries of breaking the Admin interface, and we still get the convenience of managing jQuery versions through settings. What do you think? 2014-12-25 13:04 GMT-06:00 Stephen McDonald st...@jupo.org: Thanks Ed - sounds fine so long as we judiciously test all the third party libraries bundled, I know there have been rough edges around those in the past when upgrading jquery itself. The gallery image lightbox thing, the drag/drop interface within the admin, and there are probably others that don't come to mind. Thanks again. On Thu, Dec 25, 2014 at 10:37 AM, Eduardo Rivas jerivasmel...@gmail.com wrote: Hello everyone! I've started upgrading Mezzanine to the latest version of Bootstrap (v3.3.1) and this would require at least jQuery 1.9.1 [ source https://github.com/twbs/bootstrap/blob/master/dist/js/bootstrap.js#L14]. I've encountered this problem before when using third party libraries that don't play along with Mezzanine's three year old version of jQuery (1.7.1, released November 2011 http://blog.jquery.com/2011/11/21/jquery-1-7-1-released/). I would like to ask everybody (and Steve specifically) if you are open to upgrading the version of jQuery to at least 1.9.1. Cheers. -- You received this message because you are 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 a topic in the Google Groups Mezzanine Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/mezzanine-users/jlcdcReUwdM/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] Re: Selective form_field templates?
That sounds like a good enhancement - go for it. On Wed, Dec 31, 2014 at 8:47 AM, Avery Laird laird.av...@gmail.com wrote: PS: I was almost thinking about adding an extra argument to the fields_for tag, which would be which template to use: defaults to templates/includes/form_fields.html but can accept a different template. Is that possible / a good idea? Or is there something I'm missing... On Tuesday, 30 December 2014 13:45:15 UTC-8, Avery Laird wrote: Hello, I had a quick question about the usage of the form_fields template. Is it possible/viable to modify the fields_for tag to use a specific template when rendering a given form? I have a form with rather specific formatting requirements that just won't play nice with the rest of the forms, and have created a separate template for that form. Can I selectively use that template, specifically for that one form, by playing around with the fields_for tag? And if so, is this the cleanest way to do what I'm trying to achieve? Cheers, Avery -- You received this message because you are 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: Selective form_field templates?
Definitely welcome, thanks a lot. To kick things off, I guess the current tag will need to change from an inclusion tag to a regular template tag in order to make the template optional. Then as it's not longer an inclusion tag, the regular template tag would return the result of rendering the template, something like: return get_template(template_name).render(Context(context)) Anyway see how you go - we can discuss the finer details in the pull request comments. Thanks again! On Wed, Dec 31, 2014 at 10:00 AM, Avery Laird laird.av...@gmail.com wrote: I'd be happy to! I was just unsure about whether or not my contribution would be wanted -- I'm not very experienced in submitting code to large projects. I'll make a pull request later today. On Tuesday, 30 December 2014 14:44:07 UTC-8, Stephen McDonald wrote: I don't think that's the right approach - having an optional argument with a default value is a hugely common pattern in Python. Sorry if I was unclear before, I assumed you had planned to create a pull request on Github with the discussed change, but I suppose you might only be referring to modifying your own project. Do you want to refactor the fields_for tag to optionally take a template, and create a pull request for that? On Wed, Dec 31, 2014 at 9:38 AM, Avery Laird laird...@gmail.com wrote: I thought you might not want me mucking with the fields_for tag itself, so I made another tag instead called fields_for_custom which takes the template as an argument. Works fine on my end. On Tuesday, 30 December 2014 13:50:12 UTC-8, Stephen McDonald wrote: That sounds like a good enhancement - go for it. On Wed, Dec 31, 2014 at 8:47 AM, Avery Laird laird...@gmail.com wrote: PS: I was almost thinking about adding an extra argument to the fields_for tag, which would be which template to use: defaults to templates/includes/form_fields.html but can accept a different template. Is that possible / a good idea? Or is there something I'm missing... On Tuesday, 30 December 2014 13:45:15 UTC-8, Avery Laird wrote: Hello, I had a quick question about the usage of the form_fields template. Is it possible/viable to modify the fields_for tag to use a specific template when rendering a given form? I have a form with rather specific formatting requirements that just won't play nice with the rest of the forms, and have created a separate template for that form. Can I selectively use that template, specifically for that one form, by playing around with the fields_for tag? And if so, is this the cleanest way to do what I'm trying to achieve? Cheers, Avery -- You received this message because you are 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. -- 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] New Mezzanine 3.2 version dropping python 2.6 supporting django 1.7.x+ only?
And as for dropping older Django versions - the reason we support these is that I imagine Mezzanine is commonly used with other third party apps that might not necessarily be compatible with the latest Django version, so it's not always as simple as use the latest Mezzanine for the latest Django and everything will just work. Sure the code base would be slightly cleaner, but honestly, supporting multiple Django versions isn't really hard, it's working out how to upgrade Mezzanine to work with newer versions of Django that are incompatible with concepts in Mezzanine that's the hard problem - once that gets solve X number of times for every new version of Django, a few if statements and ImportError catches here and there are all that's required to support older Django versions. It's certainly very tempting from a maintenance perspective, but the problems it may cause people outweighs the ease in which multiple versions can be supported. On Thu, Jan 15, 2015 at 2:26 AM, Josh Cartmell joshcar...@gmail.com wrote: Support for 1.7 is coming, it just isn't quite finished yet. On Wed, Jan 14, 2015 at 1:35 AM, Asif Saifuddin auv...@gmail.com wrote: Hello, I have been thinking about a newer version of mezzanine cms supporting django 1.7+ only and dropping support for python 2.6. This will help to absorb the new django features and with a lot more cleaner modern code base for mezzanine cms. Looking forward to hear about your thoughts on this issue /asif -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] invalid literal for int() with base 10: '' when creating new form (Mezzanine 3.1.10)
This is typically caused by a hidden integer field not receiving input via some JavaScript - for example, the _order field that controls the ordering of the form fields when creating a form. Check the browser's dev console for missing js files, js errors, etc. On Wed, Jan 21, 2015 at 2:30 AM, Jefferson Heard jefferson.r.he...@gmail.com wrote: I know this used to be a bug back in the olden days, but I'm not sure if it continues to be a known issue now. I'm looking to create a new Form, and every time I do I get this. This is a default install of mezzanine 3.1.10 on Django 1.7.3; nothing fancy. I'm also getting it on my install of mezzanine 3.1.10 on Django 1.6.2. -- You received this message because you are 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: Widgets for FORM_EXTRA_FIELDS
There's already a FORM_EXTRA_WIDGETS settings: http://mezzanine.jupo.org/docs/configuration.html#forms-extra-widgets On Fri, Feb 20, 2015 at 4:59 AM, Dave Bauer dave.ba...@gmail.com wrote: I am back again. I suspect I will ultimately need to solve this problem. Anyone got any hints? Thanks On Wednesday, February 26, 2014 at 8:49:03 PM UTC-5, Dave Bauer wrote: Hi, Would it be feasible to add an optional 4th element to the sequences for FORM_EXTRA_FIELDS to add a widget for the new field? Trying to find the simplest way to use django-datetimewidget with a Form Field date. Thanks Dave -- You received this message because you are 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] Getting started with Git
Nice post Graham, thanks! On Fri, Feb 20, 2015 at 1:07 PM, Graham Oliver greenbay.gra...@gmail.com wrote: Hi there I have been attempting to get my head around Git and here is a blog post sharing my learning. Thanks to Stephen McDonald and Ross Laird for the inspiration. Mezzanine rocks! http://gitstarted.blogspot.co.nz/2015/02/git-for-one.html Graham -- You received this message because you are 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] Google Analytics - Does footer_scripts.html need updating ?
There's a recent relevant discussion here:
https://github.com/stephenmcd/mezzanine/pull/1191
Apparently the code should work fine as is.
On Wed, Jan 28, 2015 at 7:19 PM, Mark Doukidis mdouki...@gmail.com wrote:
Having trouble getting Google Analytics to acknowledge a sites tracking
code.
I can see it in the generated pages and looks okay.
Have noticed that the code in Mezzanine was last updated in 2012 and
wondered if it needs updating as it appears quite different from the
suggested code from Google.
Google's suggestion:
script
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js
','ga');
ga('create', 'UA-XX-1', 'auto');
ga('send', 'pageview');
/script
Mezzanine's code:
script
{% if settings.GOOGLE_ANALYTICS_ID and not request.user.is_staff %}
var _gaq = _gaq || [['_trackPageview']];
_gaq.unshift(['_setAccount', '{{ settings.GOOGLE_ANALYTICS_ID }}']);
(function(d, t) {
var g = d.createElement(t),
s = d.getElementsByTagName(t)[0];
g.async = true;
g.src = '//www.google-analytics.com/ga.js';
s.parentNode.insertBefore(g, s);
})(document, 'script');
{% endif %}
/script
Anyone experiencing any issues with the code ?
regards
mark
--
You received this message because you are 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] No visual feedback after selecting gallery images
That's a bug introduced in a recent change to filebrowser-safe - users should see a thumbnail instantly after selecting an image. I've now fixed it and released a new version of filebrowser-safe, so upgrading that should resolve it. Here's the actual JS file and its fix that you can look for on your own project, to verify that you've actually upgraded successfully in case you have any issues (browser caching, gaps in your deploy process, etc): https://github.com/stephenmcd/filebrowser-safe/commit/0f53f3742abf00c18e14b1ad4ad2da5369586c03 Thanks for the report! On Tue, Jan 27, 2015 at 7:23 AM, Pieter Rogaar binnenpre...@gmail.com wrote: Hi all, The behaviour of the gallery page type confuses my (non-technical) staff users. When they try to add a new image to a gallery, the media library opens. They select an image in the image library. However, when they are returned to the Change Gallery admin page, there is no visual feedback to show that they have selected an image. No thumbnail, no text description, no path is shown. They think the image was not successfully added. After they click 'Save', the thumbnail and description are automatically generated and shown. I think it is preferable that some form of feedback is given, to let users know that they have successfully selected an image for that particular slot. Is this something that could be changed in Mezzanine or Filebrowser-safe? Or can I do that myself - and if so, how? Kind regards, Pietet -- You received this message because you are 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: Product filtering form
Here's how you create a dict, mapping option types to options, which you could use to build your form, with fields option1, option2, etc options = defaultdict(list) for option in ProductOption.objects.all(): options[option%s % option.type].append(option.name) Then filtering looks like: Product.objects.filter(option1=request.POST[option1]) The product categories in Cartridge can be dynamic - look for product filters in the admin when creating a category. There you can control the product options that a category is filtered by. I based the above code on the code that controls the category filtering. You can look at cartridge.shop.managers.ProductOptionManager.as_fields() and cartridge.shop.models.Category.filters() for much more detail. On Sun, Jan 11, 2015 at 2:06 AM, Maxim mshi...@gmail.com wrote: Hello, I'm sure there should be some easy way to add products filtering(by product fields) form to products list view. It is quite common task. I tried to search and read documentation, but didn't find anything specific. What is the best way to implement this with cartridge? 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.
[mezzanine-users] Minor security issue in filebrowser
Hi all, I've just pushed a new version of the filebrowser-safe package Mezzanine uses for its media library which addresses a minor security issue. You can upgrade it right away via pip install -U filebrowser-safe, or by updating your requirements file accordingly. The issue is that certain parent path traversals were not being checked (eg foo/../bar), and if the MEDIA_ROOT setting is contained under the STATIC_ROOT setting, (eg www.site.com/static/media), as is the default for Mezzanine, an authenticated admin user could rename/delete files that were under STATIC_ROOT, but not under MEDIA_ROOT. While this issue is regarded as minor, as its only exploitable by authenticated staff members, and limited to files found under STATIC_ROOT, you should upgrade as soon as possible. There aren't any expected compatibility issues in doing so. Big thanks to Pieter Rogaar for reporting the issue privately. As usual, if you think you may have discovered a possible security issue like this, please report it privately to secur...@jupo.org to allow it to be resolved before being made public. Now also serves as a good time to remind everyone about the private mezzanine-security announcement mailing list. Any critical issues (unlike this one) will be made available there with upgrade instructions prior to the issue being made public, giving site owners a chance to upgrade before the issue is made public. Please subscribe if you have a production Mezzanine site, which you'll need to provide details of before subscribing: https://groups.google.com/forum/#!forum/mezzanine-security 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] Odd test database behaviour
Wild guess - you can edit south migrations to define which other migrations they depend on. You might need to do that in your own migrations. On Wed, Jan 7, 2015 at 9:11 AM, Avery Laird laird.av...@gmail.com wrote: Hello, I ran into an issue while trying to create a test database: django.db.utils.ProgrammingError: relation pages_page does not exist I have an theme app (called theme) that uses the mezzanine page model, so I assume it must have something to do with that; sure enough, the top of the traceback includes a failed SQL operation involving the table theme_homepage,homepage being a model in my theme app that inherits from mezzanine.pages.models.Page. To see if my hunch is correct, I change the order of my installed apps to have mezzanine.pages before theme. Sure enough, when running python manage.py test the error is now: django.db.utils.ProgrammingError: relation pages_page already exists I know there must be some overlap between apps causing the issue, one which I fixed before by fiddling with south. The problem is, I can't fiddle with a test database, and at any rate I would rather do things the right way then have a fragile database. The models.py from theme is included below: from django.db import models from django.utils.translation import ugettext_lazy as _ from mezzanine.core.fields import FileField, RichTextField from mezzanine.core.models import RichText, Orderable, Slugged from mezzanine.pages.models import Page from mezzanine.utils.models import upload_to class HomePage(Page, RichText): The homepage header = models.CharField(max_length=140) subheader = models.CharField(max_length=140) splash = FileField(verbose_name=_(Splash Image), upload_to=upload_to(theme.HomePage.splash, splash), format=Image, max_length=255, null=True, blank=True) class Meta: verbose_name = _(Home Page) verbose_name_plural = _(Home Pages) class Slide(Orderable): ''' Homepage slider images ''' homepage = models.ForeignKey(HomePage, related_name=slides) image = FileField(verbose_name=_(Image), upload_to=upload_to(theme.Slide.image, slider), format=Image, max_length=255, null=True, blank=True) class ExtendedBlog(Page, RichText): RichText page, but with an optional splash image splash = FileField(verbose_name=_(Splash Image), upload_to=upload_to(theme.ExtendedBlog.splash, splash), format=Image, max_length=255, null=True, blank=True) class Meta: verbose_name = _(Extended Blog) verbose_name_plural = _(Extended Blogs) Thanks for any ideas/help! Cheers, Avery -- You received this message because you are 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] Trying to get Mezzanine + Cartridge + Stripe up and running
Looks like it's this issue which is fixed but potentially isn't released: https://github.com/readevalprint/cartridge-stripe/pull/5 At a guess, you could try installing cartridge-stripe directly from source on Github. On Tue, Jan 13, 2015 at 11:22 AM, Andres Douglas i.andres.doug...@gmail.com wrote: Testing out a number of e-commerce solutions for a project with a twist of crowdsourcing. Seems like Mezzanine is the only one with Stripe support out of the box. Managed to get everything installed, which is more than I can say for most other e-commerce django solutions. Followed instructions for https://github.com/readevalprint/cartridge-stripe https://github.com/GoodCloud/django-zebra#installation And for some reason it kept on saying it was not able to find the stripe module, so I installed that one manually. Things run smoothly, until I try to check out, at which point, we have fail. Any pointers? This is what happens: Environment: Request Method: GET Request URL: http://127.0.0.1:8000/shop/checkout/ Django Version: 1.6.9 Python Version: 2.7.6 Installed Applications: (u'mezzanine.boot', u'django.contrib.auth', u'django.contrib.contenttypes', u'django.contrib.redirects', u'django.contrib.sessions', u'django.contrib.sites', u'django.contrib.sitemaps', u'django.contrib.staticfiles', u'cartridge_stripe', u'cartridge.shop', u'mezzanine.conf', u'mezzanine.core', u'mezzanine.generic', u'mezzanine.blog', u'mezzanine.forms', u'mezzanine.pages', u'mezzanine.galleries', u'zebra', u'filebrowser_safe', u'grappelli_safe', u'django.contrib.admin', u'django.contrib.comments') Installed Middleware: (u'django.contrib.sessions.middleware.SessionMiddleware', u'django.middleware.locale.LocaleMiddleware', u'django.contrib.auth.middleware.AuthenticationMiddleware', u'django.contrib.redirects.middleware.RedirectFallbackMiddleware', u'django.middleware.common.CommonMiddleware', u'django.middleware.csrf.CsrfViewMiddleware', u'django.contrib.messages.middleware.MessageMiddleware', u'cartridge.shop.middleware.ShopMiddleware', u'mezzanine.core.request.CurrentRequestMiddleware', u'mezzanine.core.middleware.TemplateForDeviceMiddleware', u'mezzanine.core.middleware.TemplateForHostMiddleware', u'mezzanine.core.middleware.AdminLoginInterfaceSelectorMiddleware', u'mezzanine.core.middleware.SitePermissionMiddleware', u'mezzanine.pages.middleware.PageMiddleware') Traceback: File /Users/andres/.virtualenvs/[...]-mezzanine/lib/python2.7/site-packages/django/core/handlers/base.py in get_response 105. response = middleware_method(request, callback, callback_args, callback_kwargs) File /Users/andres/.virtualenvs/-mezzanine/lib/python2.7/site-packages/mezzanine/pages/middleware.py in process_view 103. return view_func(request, *view_args, **view_kwargs) File /Users/andres/.virtualenvs/-mezzanine/lib/python2.7/site-packages/django/views/decorators/cache.py in _wrapped_view_func 52. response = view_func(request, *args, **kwargs) File /Users/andres/.virtualenvs/-mezzanine/lib/python2.7/site-packages/cartridge/shop/views.py in checkout_steps 225. form_class = import_dotted_path(settings.SHOP_CHECKOUT_FORM_CLASS) File /Users/andres/.virtualenvs/-mezzanine/lib/python2.7/site-packages/mezzanine/utils/importing.py in import_dotted_path 25. raise ImportError(Could not import the name: %s: %s % (path, e)) Exception Type: ImportError at /shop/checkout/ Exception Value: Could not import the name: cartridge_stripe.forms.OrderForm: cannot import name 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-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] Script for install bleeding-edge Mezzanine/cartridge with Python3+Django 1.7
Nice one Sam. Hopefully we won't need this soon once I get some time to do a new release :-) On Mon, Jan 12, 2015 at 5:12 PM, Sam Kingston s...@sjkwi.com.au wrote: Hi everyone, Just thought I would share a script that will install Mezzanine and Cartridge in a Python3 environment with Django 1.7. It pulls the latest master and pins the install at that. It was useful to me, I hope it's useful to someone else too! It just takes two arguments: ~/ $ ./setup_new_mezz_cartridge_django17_proj.sh Usage: ./setup_new_mezz_cartridge_django17_proj.sh env project_name You can find it at: http://pastebin.com/raw.php?i=vsCS1T3G (suitable for wget'ing) No warranty! 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/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: status of django.contrib.sites in mezzanine
This probably doesn't have much chance of being included - it will most likely introduce an unwarranted increase in the complexity of how the page tree works. For example, all of a sudden you need to deal with the ordering of shared pages in the context of each site. Certainly not unsolvable, but probably not in a clean and simple way. Just some food for thought before embarking on anything. :-) On Mon, Feb 16, 2015 at 12:55 PM, Alexander Kominek alexander.komi...@gmail.com wrote: Hey Josh, I'm trying to set up M2M for sites on one of my current sites and I stumbled across this thread. Has any more work been completed on this in the last year to bring it up to date with the latest version of Mezzanine? If not, I'll probably end up updating it, but I just wanted to make sure I'm not duplicating any work. Thanks! On Monday, January 7, 2013 at 3:28:15 PM UTC-7, Josh Cartmell wrote: Thanks again Steve, that blog post and your pointers helped me figure out a good direction to take. For anyone else tracking along I moved the migrations into a separate app which is here: https://bitbucket.org/joshcartme/mezz_sites_m2m One thing to note is that I had to change the calls to the orm since the migrations no longer reside in the app they modify. If this ever makes it into Mezzanine core we would probably want to change the orm calls back to the way they were. On Mon, Jan 7, 2013 at 8:56 AM, Josh Cartmell joshc...@gmail.com wrote: Thanks Steve, that post is pretty useful. I'll give it a go. On Sun, Jan 6, 2013 at 12:06 PM, Stephen McDonald st...@jupo.org wrote: Luke Miller (ex-colleague of mine) wrote a good post on how he does it: http://dodgyville.tumblr.com/post/23028930440/new-fields- in-mezzanine-without-editing-or-creating-a On Mon, Jan 7, 2013 at 7:05 AM, Josh Cartmell joshc...@gmail.com wrote: Thanks Steve, I didn't realize I could put migrations in a different app so that's very helpful! On Sat, Jan 5, 2013 at 3:01 PM, Stephen McDonald st...@jupo.org wrote: I haven't had a chance to look at this yet myself. As for the migrations, you could probably put your one into a separate app, and if/when your changes get merged into the main project, just fake the (redundant) migration for it. On Sat, Jan 5, 2013 at 12:00 PM, Josh Cartmell joshc...@gmail.com wrote: Hey everyone, I just wanted to check in and see if this is still on the radar at all? I'm about to use this in a project so if it's not does anyone have any suggestions for how I should manage migrations? Would I just need to always edit every future migration to reflect the divergent db schemas? Thanks for all the feedback thus far. On Nov 19 2012, 12:42 pm, Josh Cartmell joshcar...@gmail.com wrote: Sounds good, thanks Steve! On Mon, Nov 19, 2012 at 11:54 AM, Stephen McDonald st...@jupo.org wrote: I haven't gone over the code in detail yet, just waiting for some space to be able to do that. But as far as what we've discussed so far I'm all in favour of the feature and approach. On Tue, Nov 20, 2012 at 6:51 AM, Josh Cartmell joshcar...@gmail.comwrote: In regards to the changes I have made I just did a little performance profiling (using Django debug toolbar) and surprisingly the same number of queries are executed to render the About page of a vanilla Mezzanine project regardless of whether you are using a foreign key or the m2m versions of sites that I implemented. I'm wondering if Django's current site manager does some sort of performance tweaking since it is specifically built to handle m2m's or foreignkeys. I haven't made any improvements in regards to performance. With that in mind the changes I have made so far may be basically ready to be pulled. What do you think Steve et al? On Fri, Nov 16, 2012 at 4:06 PM, Stephen McDonald st...@jupo.org wrote: Previously discussed here just for reference: https://groups.google.com/group/mezzanine-users/browse_ thread/thread/... On Sat, Nov 17, 2012 at 8:07 AM, Robert Moggach r...@dashing.tv wrote: It doesn't instinctively make sense if you only have 3 or 4 one off pages that are 1 or 2 deep but if you're dealing with big datasets and multiple sites it starts to make alot of sense. It wouldn't affect small sites adversely to implement, only add flexibility. If you start to have page structures that are 5 or 6 deep with many siblings at each level, it's a clear winner to use modified preorder tree traversal. http://en.wikipedia.org/wiki/Tree_traversal Take a look at how feinCMS implements their menu structure using MPTT... Abstracting the presentation logic from the content logic is a good thing. On Fri, Nov 16, 2012 at 10:32 AM, Robert Moggach r...@dashing.tvwrote: performance and flexibility Sent from my iPhone. On Nov 16, 2012, at 12:25 AM, Ahmad Khayyat akhay
Re: [mezzanine-users] custom Form processor
What kind of initial data? You can actually use template code in the
Default value field for each form field, eg {{ request.user.username }}
or some such - so anything available in the template context.
On Fri, Mar 6, 2015 at 1:17 PM, Thomas thomasmo...@gmail.com wrote:
Hi all,
First post here, super framework, really enjoying it and still finding
awesome new features!
I have created a custom Form processor and I am wondering if it is
possible to pre-load the form fields dynamically with initial data using
something like;
form = FormForForm(page.form, RequestContext(request), initial=user_data)
where user_data is a key-value dictionary containing the initial form
field data, e.g.; {'field_name': 'field_value',}
I have tried the scenario above but, the form fields are not pre-populated
on page load. Also I am cannot bind the form to the data in user_data
dictionary as it only contains a sub-set of the form fields and triggers
validation errors for the remaining fields!
Any help appreciated,
Thanks,
Thomas.
--
You received this message because you are 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 release?
Apologies for the delay, I'm currently on vacation overseas with my wife and children over the next month. On Tue, Mar 24, 2015 at 10:06 AM, elguavas elgua...@gmail.com wrote: given that django 1.8 will be released soon, how are things going for a new pip installable release of mezzanine that supports django 1.7? The so-far skipping of an official release against Django 1.7 is a valid concern. Basically as Ed mentioned, the breaking changes from Django 1.6 to 1.7 were much larger than normal. I vaguely recall that around the time the first Django 1.8 alpha release was made, we still had outstanding 1.7 incompatibilities, so at that point the question (in my head at least) was raised around how worthwhile it would be to spend time on working toward an official release against 1.7 given that the 1.8 release would be coming soon. The alternative being that we just focus effort on compatibility with 1.8, and hopefully everything would line up compatibility-wise in time for the official 1.8 release. As of a few weeks ago, we actually have 1.8 compatibility working - that may have changed since then, but given that sign, it appears that the transition from 1.7 to 1.8 will require much less effort. As Ken said this would normally not be a consideration right now, but given how things have turned out, we will most likely release Mezzanine 3.2 with support for Django 1.7 and 1.8, along with the new modeltranslation work, right after the release of Django 1.8. i'm also very interested in the new fabfile stuff for shared host installs. i'm also wondering, with mezz almost missing a whole django version without a pip installable release, are things on the mezz release front likely to continue to be very slow in staying up to date with changes in mezz git? not intending to be critical, not at all, just looking for an honest assessment of how the project is faring with respect to official releases. cheers. I don't mean to sound critical either, and I appreciate the desire for some clarity here, but I always find this type of question misguided. There's no corporate entity behind Mezzanine with a fixed schedule of time and resources that can be dedicated to it, which is precisely what would be required to answer this question definitively. Its development relies on the always-varying amount of free time myself and the other contributors can make available to it. I simply don't have a crystal ball I can peek into to provide you with any more clarity than that. As mentioned above, the move from Django 1.6 to 1.7 required a non-trivial amount of effort, which was a huge setback. Meanwhile the move from 1.7 to 1.8 has been almost seamless. So really you could flip a coin as to what the future looks like - we're really at the mercy of Django's development. That said, there are a couple of things *you* can do to make our timelines less erratic. As often requested, please help out in resolving these incompatibilities when new alphas/betas/RCs of Django are made available. If enough people were to identify and resolve these issues earlier on, sailing would be much smoother. Another idea is that we only really see these problems very late into the Django development cycle. What we really need is a voice within the Django development space - if someone was there early on enough to say hey this is going to be a huge breaking change, perhaps more care for backward compatibility could be taken. I hope this doesn't sound like a criticism of Django, they can't know what they're breaking if no one tells them. Thanks for bringing this up - I hope I've been able to make things a tiny bit clearer for everyone who has been questioning the lapse in releasing. -- You received this message because you are 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 make some user fields on registration form optional
There's a setting which allows you to define your own form class: http://mezzanine.jupo.org/docs/configuration.html#accounts-profile-form-class Your form class can subclass the provided one, and customise it as you've described. On Tue, Mar 3, 2015 at 3:53 PM, River Satya burn2sh...@gmail.com wrote: Hi all! I have a client who wants to make the first and last name fields on the registration form optional. I've dug into the Mezzanine (3.1.9) codebase, and it appears that all fields on the Django User model object are made mandatory in accounts.forms.ProfileForm (accounts/forms: line 100/101): if field in user_fields: self.fields[field].required = True This is contrary to my client's requirement, and commenting out these two lines seems to make things work as required. Is there a non-hacky way to achieve this end? Thanks for the help! River -- You received this message because you are 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: Alternate Fabfile for deploying to VPS
Hi all, I've just merged this in. Please read back through this thread, as well as the previously mentioned PR for full details. Huge thanks to Ed for all the work that went into this, and for working with me through all the feedback. On Tue, Feb 17, 2015 at 12:36 PM, Eduardo Rivas jerivasmel...@gmail.com wrote: Ok, PR sent :) https://github.com/stephenmcd/mezzanine/pull/1216 -- You received this message because you are 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: Multilingual Content Has Landed
BTW if you have any feedback or issues to report, please go ahead and leave a message on the Github PR I linked to. Thanks! On Thu, Mar 5, 2015 at 4:51 PM, Stephen McDonald st...@jupo.org wrote: Hi all, Some time ago (seemingly years) we introduced a USE_MODELTRANSLATION setting which provided integration with the django-modeltranslation package, allowing for content in Mezzanine to be provided in multiple languages. It was honestly half-baked with lots of issues, so it was quickly removed and only survived one brief version of Mezzanine way back then. Now almost a year ago, a much more complete integration with django-modeltranslation was started on, and since then it has been tested and refined over many iterations as per this thread: https://github.com/stephenmcd/mezzanine/pull/1019 I've now merged that work in, so the development (master/default) branch now contains full support for multi-lingual content! I'd ask everyone interested in this feature and Mezzanine in general to please give it a test drive. A huge thanks goes to Mathias Ettinger for the bulk of the work, to long time contributor Eduardo Rivas for a huge amount of help and shepherding, and everyone else who provided feedback along the way. -- 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.
[mezzanine-users] Multilingual Content Has Landed
Hi all, Some time ago (seemingly years) we introduced a USE_MODELTRANSLATION setting which provided integration with the django-modeltranslation package, allowing for content in Mezzanine to be provided in multiple languages. It was honestly half-baked with lots of issues, so it was quickly removed and only survived one brief version of Mezzanine way back then. Now almost a year ago, a much more complete integration with django-modeltranslation was started on, and since then it has been tested and refined over many iterations as per this thread: https://github.com/stephenmcd/mezzanine/pull/1019 I've now merged that work in, so the development (master/default) branch now contains full support for multi-lingual content! I'd ask everyone interested in this feature and Mezzanine in general to please give it a test drive. A huge thanks goes to Mathias Ettinger for the bulk of the work, to long time contributor Eduardo Rivas for a huge amount of help and shepherding, and everyone else who provided feedback along the way. -- 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 Progress
It's a great idea, but I don't think providing different options around configuring parts of bootstrap is really within scope - ideally a project throws bootstrap out and implements their own design from scratch. If any changes need to be made to cartridge to expose the data needed, then sure - but I think that's already available via the step variable if memory serves me correctly. Why not go ahead and create it as a plugin? On Thu, Feb 26, 2015 at 1:32 PM, Avery Laird laird.av...@gmail.com wrote: Hi all, Over the past few weeks I have been toying with the idea of creating a progressbar for showing your location in the cartridge checkout process. I'm imagining a templatetag with multiple options like colour, striped/non-striped, animated, etc (using the bootstrap progressbars http://getbootstrap.com/components/#progress by default, but allowing custom templates to be specified) with each checkout step as a progressbar segment. Is this a feature people would want/use? If so, I can open an issue on github for everyone to contribute ideas/suggestions and get started. Cheers, Avery -- You received this message because you are 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] invalid literal for int() with base 10: '' when creating new form (Mezzanine 3.1.10)
I'll reply to the other discussion instead of doing the same thing twice. https://github.com/stephenmcd/mezzanine/issues/1232 On Thu, Mar 19, 2015 at 5:39 AM, Jefferson Heard jefferson.r.he...@gmail.com wrote: Unfortunately I get this in a debug server as well. I can manage to create the form, but adding fields is not working. On Wednesday, January 21, 2015 at 4:44:28 PM UTC-5, Stephen McDonald wrote: Just saw the other email thread you started also mentioning this, along with issues around missing files due to S3 integration - missing static files would almost certainly the cause of the Django exception you've posted in this thread. On Thu, Jan 22, 2015 at 7:20 AM, Stephen McDonald st...@jupo.org wrote: This is typically caused by a hidden integer field not receiving input via some JavaScript - for example, the _order field that controls the ordering of the form fields when creating a form. Check the browser's dev console for missing js files, js errors, etc. On Wed, Jan 21, 2015 at 2:30 AM, Jefferson Heard jefferso...@gmail.com wrote: I know this used to be a bug back in the olden days, but I'm not sure if it continues to be a known issue now. I'm looking to create a new Form, and every time I do I get this. This is a default install of mezzanine 3.1.10 on Django 1.7.3; nothing fancy. I'm also getting it on my install of mezzanine 3.1.10 on Django 1.6.2. -- You received this message because you are 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 -- 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] Disable Cartridge Shipping
Those are all driven by templates - you can override those and omit the shipping line. On Sat, Mar 7, 2015 at 6:47 AM, Frizzi Ii fabrizio@gmail.com wrote: Hello mezzanine list, I'm building an ecommerce website with cartridge and I have several products that are downloadable so there is no need for shipping features. Do you know if there is a way to exclude shipping from checkout process and from invoice resume or to disable that feature? Thanks, Fabrizio -- You received this message because you are 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] Will Mezzanine have the same directory structure as Django?
It's in progress here: https://github.com/stephenmcd/mezzanine/pull/1265 Looking for assistance in testing it in conjunction with the built-in fabfile if anyone familiar with it has time available On Fri, Apr 24, 2015 at 1:50 AM, Tang yltan...@gmail.com wrote: As Django has already employed a directory structure in which there is a main app with the same name as the project, as follows: /projName manage.py /projName settings.py urls.py wsgi.py Just curious. Is Mezzanine going to have the same structure in the future release? When? I am really looking forward to 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] I corrected replacing this:
You shouldn't need to edit your installed version of the library if the change has been made already in the Github repo. Look at how you can specify a Github repo as a Python dependency with pip. On Sun, Apr 26, 2015 at 3:23 AM, Ronald Espinoza ing.ronaldespin...@gmail.com wrote: wishlist = ProductVariation.objects.filter (** f) .select_related (depth = 1) by: wishlist = ProductVariation.objects.filter (** f) .select_related ( product ) As I found on GitHub repository then would have to do in all virtual environments. How I can no longer make this happen? -- You received this message because you are 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] clearing or updating .thumbnail directory
Running this command in the root directory where files are uploaded to will delete all thumbnails, which will then be regenerated on next load: find . -name \*.thumbnails -delete On Fri, May 1, 2015 at 7:20 PM, nic n...@engineeredarts.co.uk wrote: Hi, Using mezzanine for our site management, but we lost our web developer, so lack Django expertise - sorry in advance for the naive question! Am doing some minor edits to image files, and realised we also have to rename the files before upload, since (some) are slotted into the page templates automatically from the thumbnail directory, which is grabbing the existing auto-generated thumbnails rather than generating new ones. This isn't a horrible pain, but also isn't optimal - is there a quick way to clear the thumbnail directory manually, preferably from the browser interface? cheers nic -- You received this message because you are 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: new release?
This looks like a packaging issue with the comments app, I've provided them with a fix here: https://github.com/django/django-contrib-comments/pull/40 If you'd like to make use of that now, you can specify my fork of the comments app in the above PR as your dependency. On Mon, May 4, 2015 at 12:46 AM, Micah Yoder yod...@gmail.com wrote: Hi, I've been trying to test out the upstream master code. I have a Python 3.4.3 virtualenv with django 1.8. When getting to the createdb step I'm getting this error: File /home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py, line 174, in build_graph self.load_disk() File /home/micah/testsite/venv/lib/python3.4/site-packages/django/db/migrations/loader.py, line 91, in load_disk for name in os.listdir(directory): NotADirectoryError: [Errno 20] Not a directory: '/home/micah/testsite/venv/lib/python3.4/site-packages/django_contrib_comments-1.6 .0-py3.4.egg/django_comments/migrations' That egg file definitely exists and the django_comments/migrations directory exists within it. I asked on IRC a few days ago and Stephen helpfully replied that I needed the git master version of django-contrib-comments. I grabbed that and installed it and indeed that resolved the issue. However, I then hit another error, representing an out-of-sync between Mezzanine and django-contrib-comments, which Stephen quickly fixed. Nice! Unfortunately, after I installed it, the above error came back. And that's where I still am. :/ Yes, I've re-installed the django-contrib-comments. In fact I just now pulled the latest mezzanine and django-contrib-comments, installed them in that order, and I still get it. Any idea what's up/ Thanks! Not a django expert but would like to get there. :) -- You received this message because you are 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] I need to put editable sections in my home page.
You have a couple of problems:
1) The homepage isn't managed by a page object by default, as to the why
and how to get that working, see here:
http://mezzanine.jupo.org/docs/frequently-asked-questions.html#why-isn-t-the-homepage-a-page-object-i-can-edit-via-the-admin
2) You've misunderstood the way the editable tags work - in your example
you've hard-coded the text Clean, Crisp, Powerful and Responsive Web
Design rather than using the model field that will be edited. If you read
the docs carefully you'll see how this works:
http://mezzanine.jupo.org/docs/inline-editing.html#template-configuration
On Thu, Apr 30, 2015 at 1:22 AM, Ronald Espinoza
ing.ronaldespin...@gmail.com wrote:
Excuse josh.
I could not interpret correctly to do according to your suggestion. My home
page does not appear in the admin. At this page I'm getting you a custom
design through free theme flat. Simiilar to want to do something that can
be done in django-cms, which establish the area where I want to edit the
html. So that the user can change that part when you want.
In django-cms it would be something like this:
{% block contentleft %}
{% placeholder contentleft2 %}
{% endblock contentleft %}
Probe everything I could in documenting mezzanine and I failed, I need to
do so urgently.
http://orotau-docs-mezzanine.readthedocs.org/en/latest/inline-editing.html#template-configuration
2015-04-28 10:00 GMT-05:00 Josh Cartmell joshcar...@gmail.com:
Hi Ronald, if page is a mezzanine page, it doesn't have any content. The
content would be added by a subclass, for example RichTextPage. Take a
look at the RichTextPage template for a good example:
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/pages/templates/pages/richtextpage.html
On Tue, Apr 28, 2015 at 9:38 AM, Ronald Espinoza
ing.ronaldespin...@gmail.com wrote:
I already tried with documentation Mezzanine, And there have been good
results.
h2 class=boxed animation animated-item-1
{% editable page.content %}
Clean, Crisp, Powerful and Responsive Web Design
{% endeditable %}
/h2
https://lh3.googleusercontent.com/-Qg0slm4xBlg/VT-Mnquf8OI/HnM/-Km9odoeZSo/s1600/parte%2Beditable.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.
--
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/SkPAg4XfVKM/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] Whipped up something quick for Buffer integration... (mezzanine-buffer)
That's actually really impressive Alex, thanks a lot for sharing it! On Mon, May 4, 2015 at 1:32 PM, Alex Tsai caffod...@gmail.com wrote: Hi all, I whipped up something quick for Buffer http://buffer.com (buffer.com) integration - it's intended as a replacement for the mezzanine.twitter BlogPost publish and allows you to take advantage of some of Buffer's features, such as supporting multiple social network profiles, automatically scheduling your updates (spacing them apart) and scheduling updates in the future. It's a bit primitive right now and has a fairly annoying bug in that it doesn't actually work from the list view for BlogPosts, and my documentation is more or less nonexistent, but since I'm probably done working on this for the weekend, figured I'd share it. You will need to create a Buffer account and also create an app https://buffer.com/developers/apps/create to obtain an access token. You can install it with: pip install mezzanine-buffer --process-dependency-links Unfortunately, the buffer-python library is outdated on pypi (and in fact, that version 1.07 is actually broken in that it's missing subpackages when installed) so the --process-dependency-links is required to install it from github master. This may be useful to you if you are interested in publishing your blog posts to multiple social networks (really anything Buffer supports should be supported) and if you're interested in spacing out your tweets. pypi link - https://pypi.python.org/pypi/mezzanine-buffer github link - https://github.com/caffodian/mezzanine-buffer boring history behind this - we were doing this at work with a mezzanine driven blog to publish tweets and updates. Our content writers tended to work within 9-5 so we needed some way to space them out, as well as handle tweeting for future-published content. Some of us already use Buffer personally so it seemed like a good fit to take care of these issues. My in office implementation was even dumber than this, so I rewrote everything from scratch as a reusable app over the course of today. :) cheers, alex -- You received this message because you are 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] Official Docker Repo
Cool, I don't know much about Docker myself and probably won't for the foreseeable future. Is this something you'd like to work on? On Thu, May 7, 2015 at 5:48 AM, Flavio Barros flaviomargar...@gmail.com wrote: Yes, but i'm talking about an official repo. I tested a lot of repos, but none of them ready for production. The idea of an official image is something that could be deployed with a docker run, and up to date with the main project source code. [image: photo] *Flavio Barros* Doutorando, Unicamp w:www.flaviobarros.net https://www.linkedin.com/profile/public-profile-settings?trk=prof-edit-edit-public_profile Meu Blog Dockerizing a Shiny App http://feedproxy.google.com/~r/FlavioBarros/~3/31w35KHlQus/ To accomplish great things, we must not only act, but also dream; not only plan, but also believe. - Anatole France https://www.quotesdaddy.com/quote/38274/anatole-france/to-accomplish-great-things-we-must-not-only-act-but Get a signature like this: https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 Click here! https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 On Wed, May 6, 2015 at 4:09 PM, Stephen McDonald st...@jupo.org wrote: This might exist already - do a google search for mezzanine docker, there are a ton of results. On Thu, May 7, 2015 at 3:19 AM, Flavio Barros flaviomargar...@gmail.com wrote: I just saw this post at Docker blog: http://blog.docker.com/2015/05/two-new-official-images-added-in-april/#more-5385 What about a Mezzanine's official repo? -- You received this message because you are 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. -- You received this message because you are 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] Official Docker Repo
This might exist already - do a google search for mezzanine docker, there are a ton of results. On Thu, May 7, 2015 at 3:19 AM, Flavio Barros flaviomargar...@gmail.com wrote: I just saw this post at Docker blog: http://blog.docker.com/2015/05/two-new-official-images-added-in-april/#more-5385 What about a Mezzanine's official repo? -- You received this message because you are 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] Official Docker Repo
Awesome! Please let us know how you go. On Thu, May 7, 2015 at 5:55 AM, Flavio Barros flaviomargar...@gmail.com wrote: Well, i can try. It would be nice. [image: photo] *Flavio Barros* Doutorando, Unicamp w:www.flaviobarros.net https://www.linkedin.com/profile/public-profile-settings?trk=prof-edit-edit-public_profile Meu Blog Dockerizing a Shiny App http://feedproxy.google.com/~r/FlavioBarros/~3/31w35KHlQus/ To accomplish great things, we must not only act, but also dream; not only plan, but also believe. - Anatole France https://www.quotesdaddy.com/quote/38274/anatole-france/to-accomplish-great-things-we-must-not-only-act-but Get a signature like this: https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 Click here! https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 On Wed, May 6, 2015 at 4:50 PM, Stephen McDonald st...@jupo.org wrote: Cool, I don't know much about Docker myself and probably won't for the foreseeable future. Is this something you'd like to work on? On Thu, May 7, 2015 at 5:48 AM, Flavio Barros flaviomargar...@gmail.com wrote: Yes, but i'm talking about an official repo. I tested a lot of repos, but none of them ready for production. The idea of an official image is something that could be deployed with a docker run, and up to date with the main project source code. [image: photo] *Flavio Barros* Doutorando, Unicamp w:www.flaviobarros.net https://www.linkedin.com/profile/public-profile-settings?trk=prof-edit-edit-public_profile Meu Blog Dockerizing a Shiny App http://feedproxy.google.com/~r/FlavioBarros/~3/31w35KHlQus/ To accomplish great things, we must not only act, but also dream; not only plan, but also believe. - Anatole France https://www.quotesdaddy.com/quote/38274/anatole-france/to-accomplish-great-things-we-must-not-only-act-but Get a signature like this: https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 Click here! https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 On Wed, May 6, 2015 at 4:09 PM, Stephen McDonald st...@jupo.org wrote: This might exist already - do a google search for mezzanine docker, there are a ton of results. On Thu, May 7, 2015 at 3:19 AM, Flavio Barros flaviomargar...@gmail.com wrote: I just saw this post at Docker blog: http://blog.docker.com/2015/05/two-new-official-images-added-in-april/#more-5385 What about a Mezzanine's official repo? -- You received this message because you are 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. -- You received this message because you are 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. -- You received this message because you are 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] Real Time update of orders
Hi there, real time is incredibly vague and begs for a stricter definition. The true meaning indicates a guaranteed response time, which is most likely not what your client means (http://en.wikipedia.org/wiki/Real-time_computing). What they most likely mean is submits without reloading the page, in which case, rather than introducing a whole separate moving part into your stack (a websocket server), along with what appears to be another framework, you could achieve the desired result simply by making an AJAX request in the checkout process. If unfortunately your client actually means has to use websockets, then you might be able monkey-patch the relevant model doing something like: Foo.__bases__ = (SelfPublishModel,) + Foo.__bases__ But before you go down that path I think you'd do yourself and your client a favour by educating them on using the best tool for the job rather than having them dictate your architecture to you :-) Good luck! On Sat, May 9, 2015 at 2:57 PM, Andrew Fam andrew.fa...@gmail.com wrote: I'm thinking of using mezzanine but a client wants a real time update of orders. http://swampdragon.net/documentation/quick-start/ from django.db import modelsfrom swampdragon.models import SelfPublishModelfrom .serializers import FooSerializer class Foo(SelfPublishModel, models.Model): serializer_class = FooSerializer text = models.CharField(max_length=100) Got this off the swampdragon page and they require an addition of SelfPublishModel to any object that you need realtime support. Any idea how to do this with cartridge? Best regarsd, Andrew -- You received this message because you are 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 App to place Galleries as slideshows on other Pages
Awesome Philip - that feature's been requested previously before, now users have somewhere to go :-) Thanks for sharing. On Sun, May 10, 2015 at 12:22 AM, Philip Southwell p...@zoothink.com wrote: 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 https://pypi.python.org/pypi/mezzanine-slideshows/0.2.1, or at its github home here https://github.com/philipsouthwell/mezzanine-slideshows. 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. -- 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] Introducing Mezzanine's Core Development Team
Hi all, Today I'm thrilled to announce the introduction of a core development team for Mezzanine. I've written a detailed post about it, please heave a read: http://blog.jupo.org/2015/05/11/introducing-mezzanines-core-development-team/ TLDR: The new team consists of myself, Josh Cartmell, Ken Bolton, Alex Hill, Ed Rivas, Mathias Ettinger, who have each made huge contributions to the project over several years. Please join me in welcoming them! -- 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] I have a SiteRelated model, how to add on admin simple per column ordering ?
Hi there, I guess you're talking about the Django admin. I wholeheartedly recommend reading its docs, and before even touching Mezzanine, reading the entire Django docs from top to bottom - the difference in your experience working with Mezzanine will be black and white. https://docs.djangoproject.com/en/1.8/ref/contrib/admin/ On Thu, May 7, 2015 at 7:37 PM, diob...@gmail.com wrote: Ok, maybe I didn't explain myself, it's related to the gui. On django I can do a per field ordering, on a mezannine site related I can't On Wednesday, May 6, 2015 at 7:39:35 PM UTC+1, Josh Cartmell wrote: Hi Dio, I don't think you should need to do anything different than what you would normally do for a Django model. The CurrentSiteManager that SiteRelated uses takes care of restricting objects to the current site! On Wed, May 6, 2015 at 12:56 PM, dio...@gmail.com wrote: Hi there, I'm starting to use mezzanine now, could you give me some pointers how to add on the admin page on a siterelated model, simple per column ordering? Best Regards, Dio -- You received this message because you are 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] a small app : mezzanine-onepage
Nice one Luc! There's also a SingletonAdmin class in Mezzanine that you can use for managing the case where only a single instance of a model should exist. It might also be useful in the case of single page apps, but lots of other cases too. No one really knows about it since it's never been documented, so I've done that just now: https://github.com/stephenmcd/mezzanine/commit/1ef03c40d40cf9893b3423ff873d51d3541bd204 On Tue, May 12, 2015 at 5:16 PM, Luc Milland l...@hekenet.com wrote: Hello there, last year I had to build a website and the client wanted it to be in a one page style. Nothing wrong with that, but I wanted to stick with Mezzanine and the Page philosophy is not really plug-and-play for this kind of sites. I worked around this using Renyi's mezzanine-blocks app and some Gist by Josh to provide an ajax contact form. Today I have to build another one page website and this approach will not fit, since I want the user be able to use all the functions that comes with Pages without overloading the admin UI. So here is this piece of code which allows to nest any page content in a section id=slugified_page_title of any page. It's the up to the developer to hide/show/animate the sections, build custom menus... All the user needs to do is to tick a box to see the page nested in it's parent. It works with rich text pages, gallery and forms (ajax inside). here is the thing, fresh and barely tested (but it seems to work pretty well) : https://github.com/lucmilland/mezzanine-onepage comments welcome :) regards, Luc -- You received this message because you are 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 3.2
Please try the Github master branch out. On Tue, May 12, 2015 at 6:48 PM, Wim Feijen w...@go2people.nl wrote: Hello, First of all, congratulations to the core team! Nice that it is official now. :) Great to see a one-man project evolve and thanks for all your contributions! Second, I'm looking forward to using Mezzanine 3.2. Like Django, can I install a release candidate which I can try? Or should I use master? Thanks for your help. Wim -- You received this message because you are 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] Real Time update of orders
Well thanks for actually clarifying what you're trying to do. As others said if you can get away with AJAX it'll be a lot easier. Otherwise if the __bases__ hacks I mentioned don't work, it's certainly feasible to create a tiny websocket pubsub server using gevent+gunicorn+redis without any frameworks. I've done it on a handful of projects and the following code is the basic shell of what I use: https://gist.github.com/stephenmcd/d7551ba68d01b1d889d2 Provided as is without any support, but everything you need is there :-) On Thu, May 14, 2015 at 10:03 AM, Andrew Fam andrew.fa...@gmail.com wrote: Hey Stephen thanks for this. Yes I understand AJAX and a real time update. The store Im working with sells quite fast moving products and needed a consolidated orders view that would be automatically updated once orders came in. So, instead of having to click refresh the page to see the new orders, I was looking for a way for the page to update once a new order came in. Best regards, Andrew On Sunday, May 10, 2015 at 7:03:58 AM UTC+8, Stephen McDonald wrote: Hi there, real time is incredibly vague and begs for a stricter definition. The true meaning indicates a guaranteed response time, which is most likely not what your client means (http://en.wikipedia.org/wiki/Real-time_computing ). What they most likely mean is submits without reloading the page, in which case, rather than introducing a whole separate moving part into your stack (a websocket server), along with what appears to be another framework, you could achieve the desired result simply by making an AJAX request in the checkout process. If unfortunately your client actually means has to use websockets, then you might be able monkey-patch the relevant model doing something like: Foo.__bases__ = (SelfPublishModel,) + Foo.__bases__ But before you go down that path I think you'd do yourself and your client a favour by educating them on using the best tool for the job rather than having them dictate your architecture to you :-) Good luck! On Sat, May 9, 2015 at 2:57 PM, Andrew Fam andrew...@gmail.com wrote: I'm thinking of using mezzanine but a client wants a real time update of orders. http://swampdragon.net/documentation/quick-start/ from django.db import modelsfrom swampdragon.models import SelfPublishModelfrom .serializers import FooSerializer class Foo(SelfPublishModel, models.Model): serializer_class = FooSerializer text = models.CharField(max_length=100) Got this off the swampdragon page and they require an addition of SelfPublishModel to any object that you need realtime support. Any idea how to do this with cartridge? Best regarsd, Andrew -- You received this message because you are 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] Add more of TinyMCE?
Have a look at the TINYMCE_SETUP_JS setting as per http://mezzanine.jupo.org/docs/admin-customization.html#wysiwyg-editor On Thu, May 14, 2015 at 4:04 AM, automotive...@gmail.com wrote: Been searching and looking for a way to add more text editing tools for TinyMCe for Rich Text pages? Is there a setting in settings.py or in the admin area that I am missing? -- You received this message because you are 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] A RESTful Web API for Mezzanine (mezzanine-api)
Wow! This looks really cool. There's a similar piece of work going on here with the intention of residing in Mezzanine itself: https://github.com/stephenmcd/mezzanine/pull/1210 Not sure if there's anything the two bits of work can leverage off each other, or how that might turn out, but what you've done looks great. On Thu, May 14, 2015 at 5:14 AM, Geo djgeor...@gmail.com wrote: Hi all, I have recently been working on a RESTful web API for Mezzanine which can help empower developers to automate, extend and combine Mezzanine with other services. This may be particularly useful to you if you are interested in working on an innovative front end for your blog/CMS using a modern framework such as Ember.js. The project is currently in its early stages. Version 0.2 has just been released which features: * REST API resources for posts, pages, users, and categories * Apply filters and search queries to narrow down results * OAuth 2.0 allows users to authorize and revoke access to third party applications without the need for those applications to request the user's credentials * Web browsable API * Endpoints documented with Swagger UI * Leverages Django Rest Framework There is also a roadmap for the future which at the time of writing includes: * More endpoints * Writeable API access * Test Suite * Further documentation You can install it with: pip install mezzanine-api And then go to PyPi or Github to follow the rest of the setup procedure: PyPi: https://pypi.python.org/pypi/mezzanine-api Github: https://github.com/gcushen/mezzanine-api Let me know if you have any feedback and feel free to discuss the API here :) Cheers, George -- You received this message because you are 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] A RESTful Web API for Mezzanine (mezzanine-api)
Hey no harm in all in having a separate project, so don't worry! I even added it to the list of third party apps just now: https://github.com/stephenmcd/mezzanine/commit/b4ef263f163d38465ce2d8591a753910859eb1de I found a couple of threads where we talked about it. Here's the first mention from a couple years ago: https://groups.google.com/forum/#!searchin/mezzanine-users/drf/mezzanine-users/EpHIx7fTkmY/Suo2X2z2e7gJ Not much info there, but then later last year we started a real discussion here: https://groups.google.com/forum/#!searchin/mezzanine-users/drf/mezzanine-users/BW0Xjn5Zwvg/kqoonBOP3ikJ I wrote a longer reply around the middle of that thread with a rough idea on what we might do with DRF inside Mezzanine itself. On Thu, May 14, 2015 at 6:48 AM, Geo djgeor...@gmail.com wrote: That's interesting. I'm very surprised to hear that. When I was researching, I found a huge number of requests for an API but no proper implementations whatsoever. About the closest thing I found was a post by Stephen on Github Issues from about 8 months ago stating something along the lines of a REST API would definitely not be included in Mezzanine itself and anyone who attempts it should design it as a third party app. I did not find any such third party apps. I guess your vision suddenly changed sometime since then. Anyway, I can still see a number of benefits to the one I'm developing, especially in relation to Oauth2 authentication, working on writable access features, documentation and testing. As well as being available now as an easy to use add-on. I might be interested to discuss combining our efforts on this. Although the projects have some differences and might have different roadmaps and goals - I could not find in that Github Convo you referenced what those are exactly for you and what your intentions are with regards to an API? Cheers, George On Wednesday, 13 May 2015 20:41:54 UTC+1, Stephen McDonald wrote: Wow! This looks really cool. There's a similar piece of work going on here with the intention of residing in Mezzanine itself: https://github.com/stephenmcd/mezzanine/pull/1210 Not sure if there's anything the two bits of work can leverage off each other, or how that might turn out, but what you've done looks great. On Thu, May 14, 2015 at 5:14 AM, Geo djge...@gmail.com wrote: Hi all, I have recently been working on a RESTful web API for Mezzanine which can help empower developers to automate, extend and combine Mezzanine with other services. This may be particularly useful to you if you are interested in working on an innovative front end for your blog/CMS using a modern framework such as Ember.js. The project is currently in its early stages. Version 0.2 has just been released which features: * REST API resources for posts, pages, users, and categories * Apply filters and search queries to narrow down results * OAuth 2.0 allows users to authorize and revoke access to third party applications without the need for those applications to request the user's credentials * Web browsable API * Endpoints documented with Swagger UI * Leverages Django Rest Framework There is also a roadmap for the future which at the time of writing includes: * More endpoints * Writeable API access * Test Suite * Further documentation You can install it with: pip install mezzanine-api And then go to PyPi or Github to follow the rest of the setup procedure: PyPi: https://pypi.python.org/pypi/mezzanine-api Github: https://github.com/gcushen/mezzanine-api Let me know if you have any feedback and feel free to discuss the API here :) Cheers, George -- You received this message because you are 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] The Orderable move buttons
On Fri, May 15, 2015 at 10:17 AM, Danny molo...@gmail.com wrote: On 15 May 2015 at 09:21, Stephen McDonald st...@jupo.org wrote: On Fri, May 15, 2015 at 7:45 AM, Danny molo...@gmail.com wrote: Hi all, I'm doing a new development using Mezzanine master and Django 1.8.1, and I've got a model that derives from Orderable, with appropriate admin stuff set up for it too. In Mezzanine 3.1.10, the _order field was just an integer, so it was easy to edit, but with the latest mezzanine, it's now been replaced with the wonderful drag-and-drop arrows. Except, for my new model, they don't drag and drop! These have always been drag/drop - the previous behaviour you've seen was a bug. Likely candidate is JavaScript not being hosted correctly. Anyway you're now seeing what should have always worked :-) Yeah, I realised that - but the bug earlier made it easy to modify the order :D Is there something I'm missing with respect to admin setup, or templates/css/js that I need to add so that the new model has the same drag/drop functionality as e.g. pages or the inlines for form fields? Take a look at the models and admin classes in mezzanine.forms that makes full use of this, particularly the admin class for your inlines: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/forms/admin.py#L38 I think the problem I'm facing is that the Orderable object is a top-level model, not something that's inlined within another model - That is a problem - the admin support is only designed for inlines. I think there was a thread on here just the other day about a third party lib for top-level ordering. so it doesn't need the Add another part that the Tabular/Stacked Inline Admin templates provide, nor do I need to do the re-ordering within another model. It's probably more akin to Pages, but without the need for the nested hierarchy. I've a feeling I may need to create a new template/javascript that behaves like the inline ordering js, but works on items that are not inlines. I'll do some more investigation. Seeya. Danny. I did have a look at, e.g. https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js#L43 but am not sure if there's something subtle I'm missing that I need to do to make it work. Is it possible I need to install grapelli_safe from github master as well? (I haven't done that yet, just using what's on PyPi) Thanks, Seeya. Danny. -- You received this message because you are 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. -- *Danny Sag* Chairperson Round World Events SA, Inc City of Small Gods Terry Pratchett Fan Club - http://cityofsmallgods.org.au *Nullus Anxietas VI - The Australian Discworld Convention* - http://ausdwcon.org The Discworld Grand Tour - Adelaide SA, August 4-6, 2017 -- You received this message because you are 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] The Orderable move buttons
On Fri, May 15, 2015 at 7:45 AM, Danny molo...@gmail.com wrote: Hi all, I'm doing a new development using Mezzanine master and Django 1.8.1, and I've got a model that derives from Orderable, with appropriate admin stuff set up for it too. In Mezzanine 3.1.10, the _order field was just an integer, so it was easy to edit, but with the latest mezzanine, it's now been replaced with the wonderful drag-and-drop arrows. Except, for my new model, they don't drag and drop! These have always been drag/drop - the previous behaviour you've seen was a bug. Likely candidate is JavaScript not being hosted correctly. Anyway you're now seeing what should have always worked :-) Is there something I'm missing with respect to admin setup, or templates/css/js that I need to add so that the new model has the same drag/drop functionality as e.g. pages or the inlines for form fields? Take a look at the models and admin classes in mezzanine.forms that makes full use of this, particularly the admin class for your inlines: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/forms/admin.py#L38 I did have a look at, e.g. https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/static/mezzanine/js/admin/dynamic_inline.js#L43 but am not sure if there's something subtle I'm missing that I need to do to make it work. Is it possible I need to install grapelli_safe from github master as well? (I haven't done that yet, just using what's on PyPi) Thanks, Seeya. Danny. -- You received this message because you are 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] moving data from development to production and the twitter model
Django docs state the flush command installs any initial data - in Mezzanine that equates to a few demo pages and default user account. https://docs.djangoproject.com/en/1.8/ref/django-admin/#flush There's no development to production migration of data occurring. The only correlation with the twitter app is that there is no initial data to install. On Sat, May 16, 2015 at 9:27 AM, Graham Oliver greenbay.gra...@gmail.com wrote: Hello all I am just working through the process of moving data from development to production (which I will document at some point) I notice that after I do a 'flush' command various bits of data spring back to life. Doing some research I see that this is because of something called a post_migrate signal... I have a few questions 1. Is there a reason why the twitter model is the only model in Mezzanine to be affected by this? 2. Can you point me to the lines of code where this happens (the post_migrate actions for the twitter model) 3. When I run the 'flush' command with verbosity 3, I see this comment '[108.59.11.112] out: Creating example.com Site object'. Would it be a good idea to have something similar for the twitter objects that are created? TIA Graham -- You received this message because you are 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: Dokku and Docker
See here: https://github.com/stephenmcd/mezzanine/pull/1186 On Fri, Apr 17, 2015 at 4:48 AM, Flavio Barros flaviomargar...@gmail.com wrote: Sorrym Ctrl+Enter... Well, anyone trying to use docker or dokku? I have a 10G digitalocean VPS where i have two Wordpress installations running. I would like to deploy a mezzanine instance as well. Someone has tried something like this? OBS: Just personal blogs. Em quinta-feira, 16 de abril de 2015 15:44:56 UTC-3, Flavio Barros escreveu: I [image: photo] *Flavio Barros* Doutorando, Unicamp w:www.flaviobarros.net https://www.linkedin.com/profile/public-profile-settings?trk=prof-edit-edit-public_profile Meu Blog Handwritten digit recognition – Part1 http://feedproxy.google.com/~r/FlavioBarros/~3/dlnBN09FQAI/ If ever there is tomorrow when we're not together.. there is something you must always remember. you are braver than you believe, stronger than you s... https://www.quotesdaddy.com/quote/280037/winnie-the-pooh/if-ever-there-is-tomorrow-when-were-not-together-there Get a signature like this: http://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 Click here! http://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9 -- You received this message because you are 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] Checking for foreign key in clean method - Django 1.77 vs 1.8
Not sure myself, but it might be a better question for the much wider
django-users list.
On Thu, Apr 16, 2015 at 12:36 PM, Graham greenbay.gra...@gmail.com wrote:
Hi guys
I have some code in a clean() method that works ok on Django 1.77 but
stops working in 1.8
The scenario
class Span(models.Model):
happening = models.ForeignKey('Happening', blank = True, null = True)
soul_class = models.ForeignKey('SoulClass', blank = True, null = True)
In the clean() method of the Span class I have a check as follows
if self.happening:
foo
if self.soul_class:
bar
This was working fine in Django up to 1.77 but when I upgrade to Django
1.8 both self.happening *and* self.soul_class are None.
The primary difference appears to be the value of _soul_class_cache as
follows.
The Span object in 1.77 looks like
{'end_date': None, 'id': None, '_state': django.db.models.base.ModelState
object at 0x7ff046ac1320, 'start_date': datetime.date(2015, 4, 16),
'soul_class_id': None, 'end_time': datetime.time(14, 12), 'happening_id':
None, '_happening_cache': None, 'start_time': datetime.time(14, 12),
'_soul_class_cache': SoulClass: Chi Kung}
In 1.8
{'start_time': datetime.time(14, 0), 'end_date': None, 'soul_class_id':
None, '_state': django.db.models.base.ModelState object at
0x7f88d698d2e8, 'happening_id': None, '_happening_cache': None,
'_soul_class_cache': None, 'end_time': datetime.time(15, 0), 'id': None,
'start_date': datetime.date(2015, 4, 16)}
Any ideas?
Cheers
g
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 modal announcements
Something like that, I really can't recall the details. On Fri, Apr 17, 2015 at 10:33 AM, Josh Cartmell joshcar...@gmail.com wrote: Thanks Sam, let me know if you have any questions or ideas for improvement. Pull requests are welcome! Thanks Steve, so that command would make github master track the tip of the mercurial repo? I figured out that I could manually update the master bookmark in the mercurial repo On Thu, Apr 16, 2015 at 8:04 PM, Stephen McDonald st...@jupo.org wrote: Josh that's really cool, thanks a lot! For hg-github, you might need to run: `hg bookmark -r default master -f` I forget why, but something to do with the underlying hg-git lib it uses. On Thu, Apr 16, 2015 at 12:01 PM, Josh Cartmell joshcar...@gmail.com wrote: Hey all, I've opened up a site announcement package I've used on a couple of Mezzanine sites. You can see the code at https://github.com/joshcartme/mezzanine-modal-announcements/tree/1.1.3 or https://bitbucket.org/joshcartme/mezzanine-modal-announcements/src (I haven't figured out how to get hg-github to update master so the master branch on github is quite a few commits back). On that page are instructions on how to use it. Once installed you set up announcements in the backend and they will pop up to users on the frontend of your site. You can control how often a particular user would see announcements and there are configuration options to determine if/when a particular announcement is shown. There might still be some rough edges, so send me some pull requests if you fix bugs! Good luck! -- You received this message because you are 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. -- You received this message because you are 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] Comments on pages
You'll need a new page type, you could call it CommentsPage - that's so you can add a comments field (mezzanine.generic.fields.CommentsField) to it. You'll then need to add handling in the page template too. See the blog model/templates for examples. On Fri, Apr 17, 2015 at 5:58 AM, Iván-Benjamín García Torà ivanicl...@gmail.com wrote: Hi everyone, I am missing something, or it isn't possible to configure Mezzanine to add comments on pages? If it isn't, should i make a new Page type or extend the current one to add this capability? 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/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 is opinionated - It makes choices for you
I think that statement doesn't refer to any specific example, but instead it refers to Mezzanine as a whole. It makes the most sense when you think about the task a developer has at hand when they first set out to build a content managed website with Django. Django gives you all the plumbing to build this, but gives you nothing actually built out of the box in terms of website features, therefore inherently being entirely unopinionated. With Mezzanine you actually have a lot of the functionality built from the start that websites need (and in some cases, *all* the features needed) - navigation structure, blog, forms, accounts, galleries, file management, etc (those are your examples if you really want them). Everything it provides is an opinion on how these things should be built *in the context of Django*. The developer building a content managed website with Django no longer needs to make a decision on whether they should source these components from libraries or build them themselves, and often painfully, how they'll all glue together - this is all done for you, inherently in an opinionated way. On Mon, Apr 13, 2015 at 12:28 PM, Graham greenbay.gra...@gmail.com wrote: Hello everyone I am going to talk about Mezzanine to the Python User Group here in Auckland (New Zealand) and I have been preparing my slides by looking at Stephen's PyCon APAC talk in Taiwan. http://blog.jupo.org/2014/08/21/pycon-apac-keynote-mezzanine/ In it he says 'Mezzanine is opinionated - it makes choices for you' 52 mins and 37 secs in Does anyone have an example of that? TIA Graham -- You received this message because you are 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] NZ Python User Group - Presentation - Grappling with Mezzanine
Looks great Graham - good luck with the talk! On Mon, Apr 13, 2015 at 2:59 PM, Graham greenbay.gra...@gmail.com wrote: Hi there Here is the 'beta' version https://docs.google.com/presentation/d/1-6lalwADM4CcPKmL567WEWbR3vWNIkk eUTawlFnPXrM/edit?usp=sharing Feel free to comment if you wish... Take Care G -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] PostgreSQL version on terminal
This worked as expected on Python 2 but not Python 3. The version formatting code divides those version numbers to get the simplified output, and so the root cause of this is due to the way division changed between Python 2 and 3. Thanks for the fix. On Sat, Apr 18, 2015 at 12:40 PM, Graham greenbay.gra...@gmail.com wrote: Well its not a major but running SHOW server_version gives 9.3.6 SHOW server_version_num gives 90306 The Mezzanine code is here https://github.com/stephenmcd/mezzanine/blob/90912aff8a2858ac4466d8d4677e5be5d9da149f/mezzanine/core/management/commands/runserver.py#L56 So we end up with a tuple (9.0306, 3.06, 6) which is then '.'joined to give 9.0306.3.06.6 I am guessing that the desired outcome is 9.3.6 I will have a look to see if I can see a solution and report back g On 18/04/15 13:27, Ken Bolton wrote: If my memory serves - Server version: 9.0306.3.06.6 Client, aka psql, version: 9.3.6 hth, ken On Fri, Apr 17, 2015 at 9:14 PM, Graham Oliver greenbay.gra...@gmail.com wrote: Just started using PostgreSQL and notice that on the terminal when I execute the runserver command the PostgreSQL version comes up as PostgreSQL 9.0306.3.06.6 When I run psql --version I get 9.3.6 ot sure if they should match or not g -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- T : 021 081 71732 -- You received this message because you are 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: new release? - TypeError at /search/ unsupported operand type(s) for |=:
Good find Graham, thanks a lot for tracking it down.
That's fixed now:
https://github.com/stephenmcd/mezzanine/commit/3ad1a6a9ce049e14fe9d120be1226844ad201baf
On Tue, Apr 14, 2015 at 5:55 PM, Graham Oliver greenbay.gra...@gmail.com
wrote:
no problems in 1.7.7
Here is the return from the [m._meta.get_parent_list() for m in models] in
1.7.7
[{class 'mezzanine.pages.models.Page'}, {class
'mezzanine.pages.models.Page'}, {class 'mezzanine.pages.models.Page'},
set(), {class 'mezzanine.pages.models.Page'}, set(), {class
'mezzanine.pages.models.Page'}, {class 'mezzanine.pages.models.Page'},
{class 'mezzanine.pages.models.Page'}]
Here is the same return in 1.8
[[class 'mezzanine.pages.models.Page'], [class
'mezzanine.pages.models.Page'], [class 'mezzanine.pages.models.Page'],
[], [class 'mezzanine.pages.models.Page'], [], [class
'mezzanine.pages.models.Page'], [class 'mezzanine.pages.models.Page'],
[class 'mezzanine.pages.models.Page']]
cheers
g
My best guess is that it is something to do with
On Tuesday, 14 April 2015 19:00:18 UTC+12, Graham Oliver wrote:
Python 3.4 Django 1.8
Request Method: GET Request URL: http://192.168.1.81:8000/
search/?q=samoa Django Version: 1.8 Exception Type: TypeError Exception
Value:
unsupported operand type(s) for |=: 'list' and 'list'
Exception Location: /home/graham/Virtual-Environments/test-py3-dj1.8/
lib/python3.4/site-packages/mezzanine/core/managers.py in search, line
265 Python Executable: /home/graham/Virtual-Environments/test-py3-dj1.8/
bin/python
I will do some digging
g
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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: Upgrading to the latest version of Bootstrap - 3.3.4
Thanks for looking at this Graham. I'll just add that on top of simply swapping out the relevant files, part of this work requires going over the default front-end site with a fine-toothed comb once the upgrade is made, and checking for any visual regressions. This can be a bit subjective, but hopefully the things that are really broken stand out. Things like the image gallery, form fields, error message, etc. Testing with a project that uses Cartridge is a super-charged way of doing this as well, as it has a lot more complex ui elements that depend on bootstrap - product pages, cart, checkout forms, etc. On Wed, Apr 15, 2015 at 2:27 AM, Eduardo Rivas jerivasmel...@gmail.com wrote: Yep, Josh's description is spot-on. Just bear in mind that the version of jQuery currently being shipped with Mezzanine is not supported by the latest version of Bootstrap. This is discussed here: https://groups.google.com/forum/#!searchin/mezzanine-users/upgrade$20jquery/mezzanine-users/jlcdcReUwdM/YjQ6pJPj3z8J -- You received this message because you are 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] Testing an existing app in the new (Django 1.7 / 1.8 / Mezzanine environment) - seeking guidance
To be clear, Graham has actually posted lots of feedback in the thread mentioned, he's just done the right thing by posting a new thread here asking for help in getting set up. To answer the original question, you should just need the relevant virtualenv activated, then run your existing project as usual. On Wed, Apr 8, 2015 at 10:18 AM, Mario Gudelj ma...@twoblokeswithapostie.com wrote: I believe that Mezzanine still doesn't support 1.7 and 1.8. There's a recent thread in this group about it. On Wed, Apr 8, 2015 at 8:52 AM, Graham greenbay.gra...@gmail.com wrote: Hi there I am already developing a Mezzanine app using the *existing* version of Mezzanine. I would like to be able to test it using the new (Django 1.7 / 1.8 / Mezzanine environment). I have set up a new vanilla Django 1.7 / 1.8 / Mezzanine environment but I can't work out how to move the existing application to the new vanilla environment. Any guidance / pointers would be appreciated. TIA g -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] new release?
Just a status update on the next release. I've just removed all support for South and Django 1.6 and earlier. Please help me with a review and fixing anything I may have overlooked: https://github.com/stephenmcd/mezzanine/commit/955488361b17959df80ae64e2cb9a2830d7f4540 https://github.com/stephenmcd/mezzanine/commit/90912aff8a2858ac4466d8d4677e5be5d9da149f I'm currently getting an error with the `createdb` command against 1.8 (but not 1.7) - if anyone wants to try and work that out it'd be awesome. Again, could *really* use help in testing the current dev branch against Django 1.7 and 1.8 - let's get this next release bullet proof against them! Once the above is sorted, I'll release the official new version, supporting Django 1.7 and 1.8. Perhaps we'll call it Mezzanine 4 rather than 3.2, it feels large enough to warrant a magical bump in the major version number. On Wed, Mar 25, 2015 at 1:47 PM, Stephen McDonald st...@jupo.org wrote: Apologies for the delay, I'm currently on vacation overseas with my wife and children over the next month. On Tue, Mar 24, 2015 at 10:06 AM, elguavas elgua...@gmail.com wrote: given that django 1.8 will be released soon, how are things going for a new pip installable release of mezzanine that supports django 1.7? The so-far skipping of an official release against Django 1.7 is a valid concern. Basically as Ed mentioned, the breaking changes from Django 1.6 to 1.7 were much larger than normal. I vaguely recall that around the time the first Django 1.8 alpha release was made, we still had outstanding 1.7 incompatibilities, so at that point the question (in my head at least) was raised around how worthwhile it would be to spend time on working toward an official release against 1.7 given that the 1.8 release would be coming soon. The alternative being that we just focus effort on compatibility with 1.8, and hopefully everything would line up compatibility-wise in time for the official 1.8 release. As of a few weeks ago, we actually have 1.8 compatibility working - that may have changed since then, but given that sign, it appears that the transition from 1.7 to 1.8 will require much less effort. As Ken said this would normally not be a consideration right now, but given how things have turned out, we will most likely release Mezzanine 3.2 with support for Django 1.7 and 1.8, along with the new modeltranslation work, right after the release of Django 1.8. i'm also very interested in the new fabfile stuff for shared host installs. i'm also wondering, with mezz almost missing a whole django version without a pip installable release, are things on the mezz release front likely to continue to be very slow in staying up to date with changes in mezz git? not intending to be critical, not at all, just looking for an honest assessment of how the project is faring with respect to official releases. cheers. I don't mean to sound critical either, and I appreciate the desire for some clarity here, but I always find this type of question misguided. There's no corporate entity behind Mezzanine with a fixed schedule of time and resources that can be dedicated to it, which is precisely what would be required to answer this question definitively. Its development relies on the always-varying amount of free time myself and the other contributors can make available to it. I simply don't have a crystal ball I can peek into to provide you with any more clarity than that. As mentioned above, the move from Django 1.6 to 1.7 required a non-trivial amount of effort, which was a huge setback. Meanwhile the move from 1.7 to 1.8 has been almost seamless. So really you could flip a coin as to what the future looks like - we're really at the mercy of Django's development. That said, there are a couple of things *you* can do to make our timelines less erratic. As often requested, please help out in resolving these incompatibilities when new alphas/betas/RCs of Django are made available. If enough people were to identify and resolve these issues earlier on, sailing would be much smoother. Another idea is that we only really see these problems very late into the Django development cycle. What we really need is a voice within the Django development space - if someone was there early on enough to say hey this is going to be a huge breaking change, perhaps more care for backward compatibility could be taken. I hope this doesn't sound like a criticism of Django, they can't know what they're breaking if no one tells them. Thanks for bringing this up - I hope I've been able to make things a tiny bit clearer for everyone who has been questioning the lapse in releasing. -- You received this message because you are 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
Re: [mezzanine-users] new release?
Absolutely, I totally forgot to mention that. On Sun, Apr 5, 2015 at 3:16 PM, Graham greenbay.gra...@gmail.com wrote: ok How about Python versions? 2.7.9 and 3.4.3 Does that sound right? g On 05/04/15 17:08, Stephen McDonald wrote: Thanks Graham - I guess it mostly involves working with a virtualenv for each Django version, as well as using pip in each of those to install Mezzanine directly from Github or BitBucket. There's probably a ton of info online that better describes how to do that. With that in place, next step is to create a project in each, run them, do things to them. Wild things. Try and break it. Use your existing projects. Use all the features from an end use perspective. Make custom content types, the works. I really can't be too prescriptive here, all I'd do is repeat my own process which would be redundant. Be creative. On Sun, Apr 5, 2015 at 3:02 PM, Graham greenbay.gra...@gmail.com wrote: Hi Stephen When you say 'Again, could *really* use help in testing the current dev branch against Django 1.7 and 1.8' Is there anything I can look at to know how to do this? TIA Graham On 05/04/15 16:59, Stephen McDonald wrote: Just a status update on the next release. I've just removed all support for South and Django 1.6 and earlier. Please help me with a review and fixing anything I may have overlooked: https://github.com/stephenmcd/mezzanine/commit/955488361b17959df80ae64e2cb9a2830d7f4540 https://github.com/stephenmcd/mezzanine/commit/90912aff8a2858ac4466d8d4677e5be5d9da149f I'm currently getting an error with the `createdb` command against 1.8 (but not 1.7) - if anyone wants to try and work that out it'd be awesome. Again, could *really* use help in testing the current dev branch against Django 1.7 and 1.8 - let's get this next release bullet proof against them! Once the above is sorted, I'll release the official new version, supporting Django 1.7 and 1.8. Perhaps we'll call it Mezzanine 4 rather than 3.2, it feels large enough to warrant a magical bump in the major version number. On Wed, Mar 25, 2015 at 1:47 PM, Stephen McDonald st...@jupo.org wrote: Apologies for the delay, I'm currently on vacation overseas with my wife and children over the next month. On Tue, Mar 24, 2015 at 10:06 AM, elguavas elgua...@gmail.com wrote: given that django 1.8 will be released soon, how are things going for a new pip installable release of mezzanine that supports django 1.7? The so-far skipping of an official release against Django 1.7 is a valid concern. Basically as Ed mentioned, the breaking changes from Django 1.6 to 1.7 were much larger than normal. I vaguely recall that around the time the first Django 1.8 alpha release was made, we still had outstanding 1.7 incompatibilities, so at that point the question (in my head at least) was raised around how worthwhile it would be to spend time on working toward an official release against 1.7 given that the 1.8 release would be coming soon. The alternative being that we just focus effort on compatibility with 1.8, and hopefully everything would line up compatibility-wise in time for the official 1.8 release. As of a few weeks ago, we actually have 1.8 compatibility working - that may have changed since then, but given that sign, it appears that the transition from 1.7 to 1.8 will require much less effort. As Ken said this would normally not be a consideration right now, but given how things have turned out, we will most likely release Mezzanine 3.2 with support for Django 1.7 and 1.8, along with the new modeltranslation work, right after the release of Django 1.8. i'm also very interested in the new fabfile stuff for shared host installs. i'm also wondering, with mezz almost missing a whole django version without a pip installable release, are things on the mezz release front likely to continue to be very slow in staying up to date with changes in mezz git? not intending to be critical, not at all, just looking for an honest assessment of how the project is faring with respect to official releases. cheers. I don't mean to sound critical either, and I appreciate the desire for some clarity here, but I always find this type of question misguided. There's no corporate entity behind Mezzanine with a fixed schedule of time and resources that can be dedicated to it, which is precisely what would be required to answer this question definitively. Its development relies on the always-varying amount of free time myself and the other contributors can make available to it. I simply don't have a crystal ball I can peek into to provide you with any more clarity than that. As mentioned above, the move from Django 1.6 to 1.7 required a non-trivial amount of effort, which was a huge setback. Meanwhile the move from 1.7 to 1.8 has been almost seamless. So really you could flip a coin as to what the future looks like - we're really at the mercy
Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'
Big thanks to Alex Hill who's worked out the fix for the issue last
reported here - if you're testing, please pull the latest in again and give
it a whirl.
On Thu, Apr 9, 2015 at 3:02 PM, Stephen McDonald st...@jupo.org wrote:
My apologies, I was wrong earlier - looks like this code's really broken
in 1.8. I'm not across so I'm not sure why, but I'll open an issue for it.
Thanks a lot.
On Thu, Apr 9, 2015 at 2:34 PM, Graham greenbay.gra...@gmail.com wrote:
Hi Stephen
I think I am using the up to date version of the code, namely
try:
# Django = 1.8
find_template_loader = context.engine.find_template_loader
except AttributeError:
# Django = 1.7
print (hello)
from django.template.loaders import find_template_loader
prints hello
This does not fit the logic of the comments because the Django version
is 1.8
g
On 09/04/15 15:59, Stephen McDonald wrote:
That was resolved a few months ago:
https://github.com/stephenmcd/mezzanine/commit/
a50de50699bb6a24bfb5f118449991aa7608b426
It looks like you're using the current 3.1.10 release of Mezzanine,
rather than the development branch from Github.
On 4/9/15, Graham Oliver greenbay.gra...@gmail.com wrote:
Django 1.8
Python 3.4.3
Accessing the admin
ImportError at /admin/login/
cannot import name 'find_template_loader'
Request Method: GET Request URL:
http://127.0.0.1:8000/admin/login/?next=/admin/ Django Version: 1.8
Exception
Type: ImportError Exception Value:
cannot import name 'find_template_loader'
Exception Location:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
site-packages/mezzanine/template/loader_tags.py
in find_template, line 62 Python Executable:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python Python Version:
3.4.3
Python
Path:
['/home/graham/Dropbox/mp-soul-2',
'/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
'/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
site-packages',
'/home/graham/Dropbox']
Server time: Thu, 9 Apr 2015 15:19:14 +1200
Error during template rendering
In template
/home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
error at line *1*
cannot import name 'find_template_loader' 1 {% overextends
admin/base_site.html %}
--
You received this message because you are subscribed to the Google
Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Stephen McDonald
http://jupo.org
--
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: new release? - cannot import name 'find_template_loader'
I've actually added a new issue label called release blockers to the
issue tracker, which contains the new issue just discussed here.
https://github.com/stephenmcd/mezzanine/issues?q=is%3Aopen+is%3Aissue+label%3A%22release+blocker%22
So now we can track exactly what's left to do before the next release.
Thanks again Graham!
On Thu, Apr 9, 2015 at 2:34 PM, Graham greenbay.gra...@gmail.com wrote:
Hi Stephen
I think I am using the up to date version of the code, namely
try:
# Django = 1.8
find_template_loader = context.engine.find_template_loader
except AttributeError:
# Django = 1.7
print (hello)
from django.template.loaders import find_template_loader
prints hello
This does not fit the logic of the comments because the Django version is
1.8
g
On 09/04/15 15:59, Stephen McDonald wrote:
That was resolved a few months ago:
https://github.com/stephenmcd/mezzanine/commit/
a50de50699bb6a24bfb5f118449991aa7608b426
It looks like you're using the current 3.1.10 release of Mezzanine,
rather than the development branch from Github.
On 4/9/15, Graham Oliver greenbay.gra...@gmail.com wrote:
Django 1.8
Python 3.4.3
Accessing the admin
ImportError at /admin/login/
cannot import name 'find_template_loader'
Request Method: GET Request URL:
http://127.0.0.1:8000/admin/login/?next=/admin/ Django Version: 1.8
Exception
Type: ImportError Exception Value:
cannot import name 'find_template_loader'
Exception Location:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
site-packages/mezzanine/template/loader_tags.py
in find_template, line 62 Python Executable:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python Python Version:
3.4.3
Python
Path:
['/home/graham/Dropbox/mp-soul-2',
'/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
'/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/
site-packages',
'/home/graham/Dropbox']
Server time: Thu, 9 Apr 2015 15:19:14 +1200
Error during template rendering
In template
/home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
error at line *1*
cannot import name 'find_template_loader' 1 {% overextends
admin/base_site.html %}
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Stephen McDonald
http://jupo.org
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Re: new release? - cannot import name 'find_template_loader'
That was resolved a few months ago:
https://github.com/stephenmcd/mezzanine/commit/a50de50699bb6a24bfb5f118449991aa7608b426
It looks like you're using the current 3.1.10 release of Mezzanine,
rather than the development branch from Github.
On 4/9/15, Graham Oliver greenbay.gra...@gmail.com wrote:
Django 1.8
Python 3.4.3
Accessing the admin
ImportError at /admin/login/
cannot import name 'find_template_loader'
Request Method: GET Request URL:
http://127.0.0.1:8000/admin/login/?next=/admin/ Django Version: 1.8
Exception
Type: ImportError Exception Value:
cannot import name 'find_template_loader'
Exception Location:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages/mezzanine/template/loader_tags.py
in find_template, line 62 Python Executable:
/home/graham/.pyenv/versions/py3.4.3-dj1.8/bin/python Python Version: 3.4.3
Python
Path:
['/home/graham/Dropbox/mp-soul-2',
'/home/graham/.pyenv/versions/3.4.3/lib/python34.zip',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/plat-linux',
'/home/graham/.pyenv/versions/3.4.3/lib/python3.4/lib-dynload',
'/home/graham/.pyenv/versions/py3.4.3-dj1.8/lib/python3.4/site-packages',
'/home/graham/Dropbox']
Server time: Thu, 9 Apr 2015 15:19:14 +1200
Error during template rendering
In template
/home/graham/Dropbox/mp-soul-2/soulapp2/templates/admin/base_site.html,
error at line *1*
cannot import name 'find_template_loader' 1 {% overextends
admin/base_site.html %}
--
You received this message because you are 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] Support for Different or Multiple Email Sending Addresses
Yep, fixed a few months ago here: https://github.com/stephenmcd/cartridge/issues/225 Yet to be released - soon! On Mon, May 18, 2015 at 12:42 PM, Josh Cartmell joshcar...@gmail.com wrote: Hi vikraw, I'm wondering if this is something that was fixed in Cartridge at some point. Take a look at the current invoice_resend_email, https://github.com/stephenmcd/cartridge/blob/master/cartridge/shop/views.py#L415 redirect_to is definitely assigned to outside of the if condition. Is that what your invoice_resend_email looks like? On Sat, May 16, 2015 at 7:40 AM, vikraw vik...@gmail.com wrote: Ok, your suggestion works for me. Thanks. But I saw another issue with resending email from User Accounts for Past Orders. When i go to the user account and View Past Orders - there is option to Resend Email here is how the link looks like for me - http://127.0.0.1:8000/shop/invoice/142/resend/?next=/account/orders/; When I click it there is an error - local variable 'redirect_to' referenced before assignment I tried to figure and I see in the view invoice_resend_email there is a condition if request.method == POST: For me this is never satisfied while I am in the View Past Orders. if I remove the condition of POST request, it works. Any thoughts on this Or shall i start another thread for it On Friday, May 15, 2015 at 11:14:41 PM UTC+5:30, Josh Cartmell wrote: If you go to the settings area of a gmail account (or google email account for your own domain) you can set up the ability to send mail as a different address, i.e. the ord...@abc.com account can be allowed to send mail as con...@abc.com. I'm not sure if that's called an alias, definitely may be. Good luck! On Fri, May 15, 2015 at 1:40 PM, vikraw vik...@gmail.com wrote: Josh, Thanks a lot. I will look into it and update if i can get it to work. So what you are suggesting is like creating an alias. On Friday, May 15, 2015 at 9:20:33 PM UTC+5:30, Josh Cartmell wrote: Hi vikraw, I don't think there is an easy way to specify multiple email users/backends like you have. Instead, I would recommend making it so that con...@abc.com can send mail as ord...@abc.com (or vice versa). I know that specifically with Google email this is fairly easy to set up. Then mail can be sent as either address through the same smtp connection. On Fri, May 15, 2015 at 8:39 AM, vikraw vik...@gmail.com wrote: How can I get Mezzanine/Cartridge to send emails from different email addresses for various purposes? - When the user submits the contact-form email should go from con...@abc.com - When the user makes a purchase, order receipt should go from ord...@abc.com In Settings-Shop section there is 'From Email' where I put the ord...@abc.com address. BUT there is no field to specify the password and other email settings In Contact-Us page there is 'From email' where I put the con...@abc.com address. Here also there is no field to specify the password and other email settings However, in *settings.py* file. I use the following, as business accounts with gmail. But the email always arrives from the email setting later in order in the file EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'con...@abc.com' EMAIL_HOST_PASSWORD = 'password' EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_USER = 'ord...@abc.com' EMAIL_HOST_PASSWORD = 'password' Please help. Need to make it look business purpose -- You received this message because you are 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-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. -- You received this message because you are 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
Re: [mezzanine-users] Domains without www not working after deploy.
I'd suggest having www never touch the Django app, and redirect all its
requests via nginx:
server {
listen 80;
server_name www.foo.com;
rewrite ^(.*) http://foo.com$1 permanent;
}
On Mon, May 18, 2015 at 11:26 AM, taedori redleopar...@gmail.com wrote:
Thanks for reply
Actual address is
www.taedori-staging.com.
and can you try taedori-staging.com.
and I set up DNS A Record.
www and @ for my server ip address.
--
You received this message because you are 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] 404 - absolute link in the github README
Thanks - that'll automatically fix itself soon. On Tue, May 19, 2015 at 8:11 AM, Federico Bruni fedel...@gmail.com wrote: Hi all If you go here: https://github.com/stephenmcd/mezzanine and click on Multi-lingual-sites you get a 404, as it searches in jupo.org, where there's still version 3.1.10 and that page is still missing. Better change this absolute link to readthedocs.org (where page is updated regularly)? http://mezzanine.readthedocs.org/en/latest/multi-lingual-sites.html -- You received this message because you are 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] PyTexas talk
Likewise, feel free to also use content from my talk that Graham linked to, and please post back videos/slides when you're done! Good luck On Tue, Jun 9, 2015 at 8:52 AM, Graham greenbay.gra...@gmail.com wrote: Hi Micah Well I won't be going, too far from New Zealand :-) Sounds like you are the ideal person for the job! Here is a presentation I did for the Python User Group in Auckland http://goo.gl/qeFrwy , feel free to plagiarise. It was based on Stephen's talk that he did to the PyCon APAC in 2014, https://vimeo.com/103614826 and my own experiences. Good luck Graham On 09/06/15 09:02, Micah Yoder wrote: Hi, Any Mezzanine folks planning to be at PyTexas this year and talk about it? I'm thinking of submitting a talk proposal to introduce Mezzanine as the hidden gem of the django ecosystem, but I'm sure I'm the least qualified person on this list to talk about it, so I don't want to step on anyone's toes! That said, I think I can give a decent introduction. (I spoke there last year about PostgreSQL's jsonb data type.) If anyone else here will be there, go ahead and talk about Mezzanine (if you want), and I'll find a different topic! If so it will be cool to see you. 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. -- T : 021 081 71732 -- You received this message because you are 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] Suggestions for PyCon talk on Mezzanine
Those are all great ideas, thanks Ed. On Thu, Jun 4, 2015 at 12:01 PM, Eduardo Rivas jerivasmel...@gmail.com wrote: Congrats, Steve! How about you speak about Cartridge this time, or Drum? Or perhaps going a little more meta, about what it is to see your project grow into something used around the world and that has spawned a whole ecosystem. Could be a great talk for anyone involved in Python and open source. I think there's a lot that can be said about Mezzanine on a technical level (page processors, editable settings, automated deployments, etc), but considering this is a Pycon, not a DjangoCon, some attendants might not know much about Django, which is key to understand Mezzanine's technical innards. You could try posting this same question to the Django mailing list too. -- You received this message because you are 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 mezzanine version
It's been discussed recently on this mailing list as well as the issue tracker. On Wed, Jun 24, 2015 at 4:04 AM, lajarre alexandre.haj...@gmail.com wrote: Hello! It's been more than 2 years I am a mezzanine user, and I don't understand why there is no new version since 10 months. Is there something I am missing in this story? 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.
[mezzanine-users] TinyMCE 4
Hi all, I've just merged into Mezzanine the work Alex Hill has done on upgrading TinyMCE to version 4 - it looks a lot better! Please help out by grabbing the latest dev branch and testing it. I've already ironed out a handful of issues, and AFAICT it works really well. This should be the last of a many new features that will make up the next release, Mezzanine 4.0! -- 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] Duplicate site permissions when saving a user at staff level
Yes, specifically the latest commit of the master branch on Github (or default branch on Bitbucket, which should refer to the same commit). On Wed, May 27, 2015 at 11:33 AM, Craig craigdub...@gmail.com wrote: By development branch do u mean the dev branch? On Wednesday, May 27, 2015 at 8:23:55 AM UTC-7, Stephen McDonald wrote: It's not clear, but it sounds like you replicated the change I linked to, and didn't actually pull in the latest development branch. Since there might be other changes involved (I know there is a field change and migration that triggered the need for that change), please make sure you've pulled in the latest development branch as I mentioned. You should also test with a fresh database, since the data you're working with may be in a state that was actually caused by the issue. On Tue, May 26, 2015 at 1:10 PM, Craig craig...@gmail.com wrote: I patched the package with your suggest fix. It did not seem to resolve the issue. Please let me know if you have any other ideas. On Saturday, May 23, 2015 at 2:19:57 PM UTC-7, Stephen McDonald wrote: Can you try the development version? I believe that's fixed: https://github.com/stephenmcd/mezzanine/commit/b8c5732bcefce5c3b7310c4e96881485da21c4e1 On Thu, May 21, 2015 at 12:57 PM, Craig craig...@gmail.com wrote: I am using Mezzanine==3.0.9. With a blank project I am having an issue with creating a user. Here are the steps: 1. Add sites to my sites record dev.local.com dev.local.com.br dev.local.de dev.local.es dev.local.fr dev.local.it dev.local.jp 2. Go to add user, create a user by the name, save and continue editing 3. Set the user to staff level and select a site to give them permissions to 4. Click save and continue You will notice that it creates two Site permissions fields. When the created user logs in it throws an error MultipleObjectsReturned: get() returned more than one SitePermission -- it returned 2! -- You received this message because you are 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 -- 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] Duplicate site permissions when saving a user at staff level
It's not clear, but it sounds like you replicated the change I linked to, and didn't actually pull in the latest development branch. Since there might be other changes involved (I know there is a field change and migration that triggered the need for that change), please make sure you've pulled in the latest development branch as I mentioned. You should also test with a fresh database, since the data you're working with may be in a state that was actually caused by the issue. On Tue, May 26, 2015 at 1:10 PM, Craig craigdub...@gmail.com wrote: I patched the package with your suggest fix. It did not seem to resolve the issue. Please let me know if you have any other ideas. On Saturday, May 23, 2015 at 2:19:57 PM UTC-7, Stephen McDonald wrote: Can you try the development version? I believe that's fixed: https://github.com/stephenmcd/mezzanine/commit/b8c5732bcefce5c3b7310c4e96881485da21c4e1 On Thu, May 21, 2015 at 12:57 PM, Craig craig...@gmail.com wrote: I am using Mezzanine==3.0.9. With a blank project I am having an issue with creating a user. Here are the steps: 1. Add sites to my sites record dev.local.com dev.local.com.br dev.local.de dev.local.es dev.local.fr dev.local.it dev.local.jp 2. Go to add user, create a user by the name, save and continue editing 3. Set the user to staff level and select a site to give them permissions to 4. Click save and continue You will notice that it creates two Site permissions fields. When the created user logs in it throws an error MultipleObjectsReturned: get() returned more than one SitePermission -- it returned 2! -- You received this message because you are 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 -- 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] Theming best practice: Bootstrap or bare-bones?
Agree with Tom, use bootstrap if it helps you. I just wanted to point out though that nothing in Mezzanine really depends on bootstrap - if you wanted to start from scratch, using an alternative framework or none at all, you certainly can. On Wed, May 27, 2015 at 9:46 AM, Simon Griffee si...@hypertexthero.com wrote: Thanks, Tom. It does help, and I think you're right! I'll get to work now. Design: www.hypertexthero.com Photography: www.simongriffee.com Email: si...@hypertexthero.com Phone: +1 (347) 498-5369 On Wed, May 27, 2015 at 12:39 PM, Tom Lockhart tlockhart1...@gmail.com wrote: On May 27, 2015, at 9:16 AM, Simon Griffee simongrif...@gmail.com wrote: I'm beginning work on a Mezzanine theme focussed on blog writing and reading that I want to publish on PyPi. Mezzanine's templates are currently heavily Bootstrap-dependent and I'm wondering if I should embrace the framework in my theme. I am leaning toward starting from scratch with simple, minimal HTML and CSS and little-to-no JavaScript, but thought I’d ask here whether this is a fool's errand as I do want to maintain compatibility with future versions of Mezzanine. You can choose to leave out references to bootstrap in your templates, which will give you “minimal html and css”. But you’ll end up using bootstrap since it is awesome. Build on top of a body of work rather than try to replicate the thousands of hours of work embodied in bootstrap. hth - Tom -- 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/bdqjepkhtzc/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] SiteRelated Products and Categories
They're already SiteRelated - import inspect inspect.getmro(Product) (class 'cartridge.shop.models.Product', class 'mezzanine.core.models.Displayable', class 'mezzanine.core.models.Slugged', class 'mezzanine.core.models.SiteRelated', class 'mezzanine.core.models.MetaData', class 'mezzanine.core.models.TimeStamped', class 'cartridge.shop.models.Priced', class 'mezzanine.core.models.RichText', class 'django.db.models.base.Model', class 'mezzanine.utils.models.AdminThumbMixin', type 'object') inspect.getmro(Category) (class 'cartridge.shop.models.Category', class 'mezzanine.pages.models.Page', class 'mezzanine.pages.models.BasePage', class 'mezzanine.core.models.Orderable', class 'mezzanine.core.models.Displayable', class 'mezzanine.core.models.Slugged', class 'mezzanine.core.models.SiteRelated', class 'mezzanine.core.models.MetaData', class 'mezzanine.core.models.TimeStamped', class 'mezzanine.core.models.RichText', class 'django.db.models.base.Model', type 'object') If they're not acting as such, you may have misconfigured your Site records On Sat, May 30, 2015 at 8:14 AM, Andrew Fam andrew.fa...@gmail.com wrote: Trying to build a multitenanted ecommerce platform. Any idea how to add SiteRelated to the Product and Category? I tried the following below but the migrations don't register from django.db import models from cartridge.shop.models import Product from cartridge.shop.models import Category from mezzanine.core.models import SiteRelated Product.__bases__ += (SiteRelated,) Category.__bases__ += (SiteRelated,) -- You received this message because you are 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] Theming best practice: Bootstrap or bare-bones?
in your projects static folder with current versions, since the ones included in mezzanine are somewhat outdated (3.0.3 fro D Am Mittwoch, 27. Mai 2015 19:06:49 UTC+2 schrieb Simon Griffee: Thanks, Stephen — understood. Once I have something to show I'll post a link here. Design: www.hypertexthero.com Photography: www.simongriffee.com Email: si...@hypertexthero.com Phone: +1 (347) 498-5369 On Wed, May 27, 2015 at 12:55 PM, Stephen McDonald st...@jupo.org wrote: Agree with Tom, use bootstrap if it helps you. I just wanted to point out though that nothing in Mezzanine really depends on bootstrap - if you wanted to start from scratch, using an alternative framework or none at all, you certainly can. On Wed, May 27, 2015 at 9:46 AM, Simon Griffee si...@hypertexthero.com wrote: Thanks, Tom. It does help, and I think you're right! I'll get to work now. Design: www.hypertexthero.com Photography: www.simongriffee.com Email: si...@hypertexthero.com Phone: +1 (347) 498-5369 On Wed, May 27, 2015 at 12:39 PM, Tom Lockhart tlockh...@gmail.com wrote: On May 27, 2015, at 9:16 AM, Simon Griffee simong...@gmail.com wrote: I'm beginning work on a Mezzanine theme focussed on blog writing and reading that I want to publish on PyPi. Mezzanine's templates are currently heavily Bootstrap-dependent and I'm wondering if I should embrace the framework in my theme. I am leaning toward starting from scratch with simple, minimal HTML and CSS and little-to-no JavaScript, but thought I’d ask here whether this is a fool's errand as I do want to maintain compatibility with future versions of Mezzanine. You can choose to leave out references to bootstrap in your templates, which will give you “minimal html and css”. But you’ll end up using bootstrap since it is awesome. Build on top of a body of work rather than try to replicate the thousands of hours of work embodied in bootstrap. hth - Tom -- 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/bdqjepkhtzc/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/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-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 a topic in the Google Groups Mezzanine Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/mezzanine-users/bdqjepkhtzc/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/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. -- T : 021 081 71732 -- 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/bdqjepkhtzc/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] Re: Design to extend cartridge with global location selection
Might even be able to do something simple using locations as categories. On Fri, May 29, 2015 at 11:12 PM, Mathias Ettinger mathias.ettin...@gmail.com wrote: Hi, I’d rather not use a variation option to store the location: - it can be costly to retrieve every one of them when filtering products for a given category; - it will display on the product page and can be redundant if you have a dropdown elsewhere. Instead, I’d rather use EXTRA_MODEL_FIELDS to inject a CharField (or better, a ForeignKey or a ManyToMany, depending on your needs, to a custom model storing locations and may be other metadata) into cartridge.shop.models.Product You can then write a custom @processor_for(Category) to filter the products according to your needs. Check out https://github.com/stephenmcd/cartridge/blob/master/cartridge/shop/page_processors.py for an example of how to achieve that. Le jeudi 28 mai 2015 10:55:55 UTC+2, Wesley a écrit : Hi guys, This is not an problem but just here to consult with you guys. When coding these days, I happen to think about that how to add a functionality that dynamic display products by user's location selection. That is, on my homepage, there is one location select, e.g. New York, Boston .etc When users select New York, all product list related shows only products that are availabe for New York. So, if I code, I will: 1. Add one product option to Product, maybe named as location, and values are those city names, e.g. New York, Boston .etc 2. Add the selected location variable to request.session 3. Within those product list templates or view functions returning queryset to product list pages, filter products Is above idea correct? or do you guys has some better suggestions? 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] Theming best practice: Bootstrap or bare-bones?
BTW don't feel disheartened, I never found a complete and thorough tutorial documenting this either (that's not to say there isn't one). The official docs are incredibly dense too. I just worked it all out through trial and error. The good thing is that once you get everything working, you never really need to go through it again. I just copy and paste from one project to the next. On Fri, May 29, 2015 at 11:31 PM, Stephen McDonald st...@jupo.org wrote: You've also got files in there that shouldn't be in the repo: https://github.com/hypertexthero/mezzanine-robotonotebook/blob/master/templates/.DS_Store That tutorial doesn't seem to deal with including non-Python files in your package, which you'll need to do to include your templates and other static files. I can't do a proper tutorial justice by trying to document the steps here, but these are normally handled by a MANIFEST file, look at Mezzanine's for example: https://github.com/stephenmcd/mezzanine/blob/master/MANIFEST.in Your setup.py should include references to necessary dependencies - again, no way of telling without seeing it, but since you describing installing them manually in the readme file, presumably this step has been omitted too. On Fri, May 29, 2015 at 11:27 PM, Stephen McDonald st...@jupo.org wrote: I'd suggest finding some open source Django apps and studying their structure on Github. Also following the tutorial you linked to before more closely, you've steered away from it it seems. - The virtualenv directory isn't relevant - You've split out a package directory and the git repo, with duplicate content, these should be the same thing, including setup.py etc - Once you've got everything on Github, people can then at least see your setup.py and look to see if it has problems, at the moment it's hidden on your computer - At a guess, the project's showing up on PyPI as you did the register step, but possibly you forgot the upload step. On Fri, May 29, 2015 at 8:26 PM, Simon Griffee si...@hypertexthero.com wrote: Hi Graham, Those are the instructions I followed, and they seem to have worked — my package is listed on PyPI and from what I can see the `setup.py` file should be inside the same folder containing the package, and not in the package itself. This brings up the question of whether there is a 'best practice' for packaging Django apps in development (I'm a novice). My current foldersetup is as follows: mezzanine-roboto-notebook-env--- My virtualenv ├── bin ├── include ├── lib ├── mezzanine-roboto-notebook │ ├── ... │ ├── robotonotebook--- THE git repo which I develop on and push to https://github.com/hypertexthero/mezzanine-robotonotebook │ │ ├── LICENSE.txt │ │ ├── README.md │ │ ├── __init__.py │ │ ├── static │ │ └── templates │ ├── ... ├── package--- THE package pushed to PyPI using the instructions you mentioned │ ├── LICENSE.txt │ ├── README.md │ ├── robotonotebook │ │ ├── __init__.py │ │ ├── static │ │ └── templates │ ├── setup.cfg │ └── setup.py └── pip-selfcheck.json I'm going to get some sleep now — back sometime tomorrow! Simon Simon Griffee www.hypertexthero.com On Fri, May 29, 2015 at 10:59 PM, Graham greenbay.gra...@gmail.com wrote: Hi Simon I have had a look at this blog post http://peterdowns.com/posts/first-time-with-pypi.html It says that you need a setup.py file which I am not seeing on your repo... cheers g On 30/05/15 13:22, Simon Griffee wrote: Thanks, Mathias. I've gone ahead and tried making something *without* using Bootstrap to begin with. If people like this I will make a version that uses Bootstrap, too. My reasoning for this is that I want to : 1. Focus on the simplest code when learning something and… 2. Improve performance by reducing the amount of CSS files, especially as I'm referencing a typeface in the design — I'm a fan of minimalist design :) Here is version 0.0.1: https://github.com/hypertexthero/mezzanine-robotonotebook https://pypi.python.org/pypi/mezzanine-robotonotebook/0.0.1 This was my first time publishing anything on PyPI, and for some reason when I try to `pip install mezzanine-robotonotebook` I get an error message: Exception: Traceback (most recent call last): File /Users/simon/Projects/mezt-env/lib/python2.7/site-packages/pip/basecommand.py, line 223, in main status = self.run(options, args) File /Users/simon/Projects/mezt-env/lib/python2.7/site-packages/pip/commands/install.py, line 268, in run wheel_cache File /Users/simon/Projects/mezt-env/lib/python2.7/site-packages/pip/basecommand.py, line 268, in populate_requirement_set wheel_cache=wheel_cache File /Users/simon/Projects/mezt-env/lib/python2.7/site-packages/pip/req/req_install.py
Re: [mezzanine-users] Re: How to get order final total price in views function?
You're kind of mimicking the _order_totals function which gets used in
template tags:
https://github.com/stephenmcd/cartridge/blob/master/cartridge/shop/templatetags/shop_tags.py#L34
You could probably do something like:
from cartridge.shop.templatetags.shop_tags import _order_totals
order_vars = _order_totals({request: request})
print order_vars[order_total]
On Wed, May 27, 2015 at 6:01 PM, Wesley nisp...@gmail.com wrote:
Hi,
I am trying to get this guy jus in a regular view.
My scenario is:
Within checkout confirmation page, when click on 'next' to complete the
order, raises a ajax request to a regular view to do something,and in this
view function(only request available) I need ordr total.
But, currently in the confirmation page, order is not setup or saved, so
no order object available now.
BTW, you mentioned, combine request.session[shipping_total] and
request.cart.total_price(), then, what about tax and discount, these two
guys cover the latter two valuation?
Currently, I use the following snippet to get the total price(changed the
source code, so it's not a good idea...), don't know if it's exactly
correct but haven't hit any issue yet:
Model Order:
def get_tmp_total(self, request):
added by wni.
for weixin pay, on confirm page, need to get total for weixin
order creation.
#self.key = request.session.session_key
#self.user_id = request.user.id
for field in self.session_fields:
if field in request.session:
setattr(self, field, request.session[field])
total = request.cart.total_price()
if self.shipping_total is not None:
total += Decimal(str(self.shipping_total))
if self.discount_total is not None:
total -= Decimal(self.discount_total)
if self.tax_total is not None:
total += Decimal(self.tax_total)
return total
In view function:
tmp_order = form.save(commit=False)
request.session['wni_wxpay_total'] = tmp_order.get_tmp_total(request)
Wesey
Hi,
Where are you trying to get this value? Is it a step handler like
SHOP_HANDLER_PAYMENT or SHOP_HANDLER_ORDER? Or a regular view?
If you have an order object then it should be available in order.total,
given that you are “far enought” in the checkout process so it has been
computed. If you just have a request, try request.session[shipping_total]
combined with request.cart.total_price().
Le mercredi 27 mai 2015 13:49:51 UTC+2, Wesley a écrit :
Sorry missing one that:
I am trying to get the price from checkout confirmation page, I mean,
when click Next on the page.
Hi guys,
In one of my views function, I wanna get final total price of the
order.
I tried to get from request.session['order']['total'] or
request.session['cart']['something'] but all failed.
I print order and cart getting this sample:
order is:
{'card_name': u'', u'delivery_type': u'', 'remember': True, 'pay_type':
u'\u5fae\u4fe1\u652f\u4ed8', 'billing_detail_street': u'\u6d4b\u8bd5',
'shipping_detail_first_name': u'\u502a\u6770', 'shipping_detail_street':
u'\u6d4b\u8bd5', u'additional_instructions': u'', 'card_type': u'', 'step':
2, 'same_billing_shipping': True, u'prefer_time':
u'\u7acb\u5373\u9001\u9910', 'shipping_detail_phone': u'11211',
'billing_detail_email': u'whatever here', 'billing_detail_phone': u'11211',
'billing_detail_first_name': u'\u502a\u6770'}
cart is:544
So, no something like 'total' in order object, and cart is id.
Maybe I can get price to query database according to the cart's id, but
is there any easy way to get the total price?
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] tinymce and django compressor?
If you're using the released version of Mezzanine, see if the latest
development branch incidentally solves this - it's using a newer version of
TinyMCE as of yesterday.
On Sun, Jun 28, 2015 at 5:02 PM, Lee H. popov.gh...@gmail.com wrote:
I find that if I put the `{% include includes/footer_scripts.html %}`
within the django-compressor `{% compress js %}` block, I get quite a few
404s.
These are for plugins that tinymce wants to use, e.g.
`plugins/fullscreen/editor_plugin.js`.
The problem seems to be that with compression on the tinymce script looks
for the plugin relative to whatever the current page is;
for example `
http://www.mysite.com/blog/myblogpost//plugins/fullscreen/editor_plugin.js`
http://www.mysite.com/blog/myblogpost//plugins/fullscreen/editor_plugin.js,
and not relative to the tinymce script itself.
I can also see in the javascript cmd console that `tinyMCE.baseURL` is
http://www.mysite.com/blog/myblogpost/; with compression on, whereas
without including it within the compress block the
`tinyMCE.baseURL` is
https://mybucket.s3.amazonaws.com/static/grappelli/tinymce/jscripts/tiny_mce;,
as it should be.
I can obviously fix this by taking the `{% include
includes/footer_scripts.html %}`, outside the {% compress %} block,
but then I probably lose the benefits of compression for these scripts.
Any other ideas? I'm not quite sure how the tinymce js
determines the base URL or moving the script to CACHE through compressor
is causing the baseURL to change to the current
page of my site (I wouldn't have been surprised if it changed the baseURL
to the CACHE of static root)
--
You received this message because you are 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] TESTING, South, Django-Redirects, and OPTIONAL_APPS
I believe none of this occurs anymore in the development version. On Thu, Jul 2, 2015 at 4:19 AM, shawn.vanitter...@appdynamics.com wrote: When running manage.py test, Mezzanine's utils/conf.py automatically sets settings.TESTING = True. A few lines later, it forks based on the TESTING setting: If TESTING is False, then South and OPTIONAL_APPS are added to INSTALLED_APPS. If TESTING is True, then those apps are NOT added, and furthermore django.contrib.redirects is removed from INSTALLED_APPS. 1. What is the rationale for removing django.contrib.redirects during testing? 2. What is the rationale for removing South during testing? 3. Why aren't the optional apps loaded during testing? 4. How can we override or prevent these configurations? Thanks, Shawn -- You received this message because you are 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] Little bug with blog post related posts template block?
Right you are, fixed here: https://github.com/stephenmcd/mezzanine/commit/69fcdac74d6d283d9284f5e75b6869b27c81734d Thanks! On Fri, Jul 3, 2015 at 4:33 PM, Lee H. popov.gh...@gmail.com wrote: The template block for related posts in the blog detail template has `for post in blog_post.related_posts.all`, shouldn't it be `for post in blog_post.related_posts.published` (or rather published for that user...)? The way things are now, if a related post is unpublished it still gets linked at the bottom of a blog post, and hence the user can click it to arrive at a 404. -- You received this message because you are 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: s3 and Bad Request 400 + thumbnails with s3
Ok cool, we might leave it for now since the new release is almost here - but thanks so much for documenting all your findings, no doubt it'll be useful. On Wed, Jul 1, 2015 at 1:01 PM, Lee H. popov.gh...@gmail.com wrote: Regarding a fix. I guess there a few points: 1) This was all in Django 1.6 with the latest stable release of Mezzanine (not the master dev branch). In Django 1.6, the suspicious operation gets swallowed, but in later version of Django 1.6, a technical 500 response is returned if the user has DEBUG True. The `django.core.handlers.base` code was changed to be if settings.DEBUG: return debug.technical_500_response(request, *sys.exc_info(), status_code=400) so the user gets a debug screen with Exception Type: SuspiciousOperation Exception Value: Attempted access to '/path/to/my/project/temp_media/uploads/' denied. and full trace, which makes identifying the issue A LOT easier (I verified this on the latest Mezzanine master branch and django 1.8). Hence there is an argument that nothing should be done, and that in future version Mezzanine that bind to django 1.6 the user will get this nicer debug screen anyway. 2) Whilst if I'd been using django 1.6 I wouldn't have had the headache. I'd personally say there is still room to make this more transparent for an end user who wants to use Mezzanine and s3. A user could quite easily forget to set `MEDIA_ROOT= ''` perhaps, and then be greeted with the above SuspiciousOperation and trace, which requires digging through a little bit to realise it's down to the MEDIA_ROOT. Could there perhaps be a misconfiguration warning coming in at the filebrowser-safe S3BotoStorageMixin level if MEDIA_ROOT is not ' ' . Or the test using self.location of S3BotoStorage and MEDIA_ROOT could be performed in the mixin. Typically say, self.location = media for a custom S3Storage media class, and MEDIA_ROOT might be naively set by the user as '/path/to/project/temp_media`, so comparing these two could also raise an error which asks the user to check the value of their MEDIA_ROOT setting if it looks like the filepath (generated using MEDIA_ROOT) is going to be outside of the location (in a very similar way to the check safe_join is currently doing, but with an exception that is more specific to this scenario, and more transparent: we can say it's not SuspciousOperation; it's just the user is mixing a cloud location with local filesystem MEDIA_ROOT). -- You received this message because you are 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] Link model - external vs internal URLs
Hi all, We're looking at fixing some issues around the Link model. Its original intention was for external links (to other websites), but people currently use it with internal links as well to achieve different scenarios with site navigation. If you have other examples of this that you depend on, could you chime in here: https://github.com/stephenmcd/mezzanine/issues/1345#issuecomment-118676898 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] Price Rounding Off Issues
Well you've resolved it for yourself but surely someone else will hit this. So which payment processor was it? On Mon, May 25, 2015 at 9:45 AM, vikraw vik...@gmail.com wrote: Looks like it is resolved for now. One of the payment processor libs had getcontext().prec = 2. After commenting it out, things looks ok. Once the flow reached that code, i had issues. But still not clear why it hasn't happening on dev environment On Monday, May 25, 2015 at 2:46:19 AM UTC+5:30, Danny S wrote: Is it possible that you are running with different versions of python between the runserver and nginx/gunicorn versions of your website? I've noticed before in other work that e.g. Python 2.7 has slightly different precision on floats than Python 2.6... But yeah, weird problem. On 25/05/2015 3:45 AM, vikraw wrote: The staged server have the locale correctly set ( see at end of my message the settings). Steps on my Staged server - Amazon Ec2 - Ubuntu 14 - stopped supervisor and nginx on my staged machine - switched my staged machine to run using - python manage runserver 0.0.0.0:8000 - put printf value statement in the currency filter under shop_tags.py now when i browse (using windows machine) the site running on ec2 machine I have NO issues with the Product prices, Cart total etc..Both the Browser and the printf values match However, when I switch the machine to nginx and start browsing from windows machine, i start getting the incorrect prices (alternate between correct and wrong) when - I press the different products or go back and forth from cart to product pages - Switching between incorrect price and correct prices happens everytime when I goto my payment processor and click the back button again to website (neglecting browser warnings that page has expired). BUT this doesn't happens when site running from python manage runserver ex: Rs.249 is displayed as Rs.250 and Rs.349 as Rs.350. clicking the same link toggles between those 2 values Help is greatly appreciated as i am near completion and can't figure this ambiguous behavior. My development is on Local Machine a Ubuntu 12.01LTS and I was testing using python manage runserver on 127.0.0.0:8000... This is working as expected locale command on ubuntu-14 amazon-ec2 LANG=en_IN LANGUAGE=en_IN:en LC_CTYPE=en_IN LC_NUMERIC=en_IN LC_TIME=en_IN LC_COLLATE=en_IN LC_MONETARY=en_IN LC_MESSAGES=en_IN LC_PAPER=en_IN LC_NAME=en_IN LC_ADDRESS=en_IN LC_TELEPHONE=en_IN LC_MEASUREMENT=en_IN LC_IDENTIFICATION=en_IN LC_ALL= The currencies symbol is correctly shown on the browser. However, i the prices change sometimes alternately and sometimes randomly. Correct price is 249. it switches between 249 and 250 when i click the same page or cart button. the cart total is updated On Saturday, May 23, 2015 at 10:59:37 PM UTC+5:30, Stephen McDonald wrote: It looks like you're calculating the correct value being stored in the DB, and only getting the error on output. Each currency value gets passed through the currency template tag, which is where the problem likely is. It also deals with machine specific locale settings, which will vary per machine - also making it a likely candidate for the error. Here's the source for it - https://github.com/stephenmcd/cartridge/blob/master/cartridge/shop/templatetags/shop_tags.py#L17-L41 Have you consistently defined (and installed) the correct locale? (defined with the SHOP_CURRENCY_LOCALE setting). Can you debug what happens in the currency template tag on your deployed machine? That might entail adding some logging to it, making a copy of it in your own project, printing out values while manually running it in a terminal, whatever works for you. On Sat, May 23, 2015 at 3:26 AM, vikraw vik...@gmail.com wrote: Hi Almost near launching a site. But running into Price rounding issues today when I fab deployed to AWS ec2 instance. Never had those issues before on ec2. My Development environment is working great with no issues. However on deployed machine -Prices are getting rounded off in various places ex: 249 was rounded off to 250 in cart.html, as well as HTML invoice, PDF invoice. Unit Price was displaying correctly as 249 But Total Price was showing 250 Also, facing rounding off issues in PDF invoice and View Invoice in browser. The amounts are accurate in email invoice though. Even the amounts sent to payment gateway are correct. When the account user goes to history of orders, the amounts are correctly displayed in the columns. Only issues are cart, html invoice, pdf templates. I have a tax_handler where i calculate tax as follows - TAX_RATE = 0.05 tax_total = Decimal(amount_to_tax) * Decimal(str(settings.TAX_RATE)) See attached files - 366.45 is the correct amount being shown in Order-History page, but invoice is generated or 370. -- You received this message because you are subscribed to the Google Groups Mezzanine
Re: [mezzanine-users] Re: The Readme on Github - I would like to give it a revamp
It's just a regular Mezzanine project - there aren't any special instructions. On Sun, May 24, 2015 at 3:08 PM, Graham greenbay.gra...@gmail.com wrote: Thanks Brandon I will get going with the feedback I have. Stephen, could you please give me the instructions on how to install the 'project site' on my local development machine. I can do the git clone but I am a bit hazy after that. Thanks g On 24/05/15 21:41, Brandon Keith Biggs wrote: Hello, I believe most people who read the readme on github have already seen the website. So they would like to know technical stuff and how to get started and do basic and essential things. Perhaps a link to Dgango's guide and then instructions on how to get started and instructions on how to deploy. thanks, Brandon Keith Biggs http://www.brandonkeithbiggs.com/ On 5/24/2015 11:20 AM, Graham wrote: Hello all... I am also interested in the 'who' and the 'why' and this may help us decide what should go in the README... *Who* are we designing the README for? *Why* would the reader of the README choose to become involved, what would 'hook them in'? *Why* choose Mezzanine over any other 'similar' project? *Who* would we like to attract to the project / to use Mezzanine? Is there a minimum skill level that we want to mention? Clearly I have my own responses to these questions, but interested to hear others points of view before I unduly influence anyone! Cheers g On 24/05/15 05:40, Stephen McDonald wrote: On Fri, May 22, 2015 at 11:14 PM, Mathias Ettinger mathias.ettin...@gmail.com wrote: Why not swap it entirely with doc/overview.rst? I think this will be the general approach - move stuff out of the README, and directly into the docs, and adding links in the README back to the docs for these moved pieces. Here's my initial thoughts on each section, feedback welcome. Overview - leave as is Features - leave as is Dependencies - move to end of installation section Installation - move to overview in docs, and link from README Themes - move to overview in docs, no link needed from README Browser support - move to overview in docs, no link needed from README Contributing - leave as is Multi-lingual sites - already has a docs section, merge into that or remove Third party plugins - move to overview in docs, and link from README Donating - leave as is Support - leave as is, but move up to a more prominent spot (the number of invalid issues opened when posting to the mailing list would suffice is overwhelming) Sites using Mezzanine - move to overview in docs, and link from README (refactoring demo site required) Quotes - leave as is This way, what relies on README.rst today can rely on overview.rst tomorow without breaking anything. Or is the point to shorten both? Le vendredi 22 mai 2015 22:32:01 UTC+2, Stephen McDonald a écrit : It's a good idea. Please keep in mind there's some functionality of the project site dependent on the format of the readme, particularly those lists we'll probably remove: https://github.com/stephenmcd/mezzanine.jupo.org/blob/master/demo/__init__.py On Fri, May 22, 2015 at 1:26 PM, Geo djge...@gmail.com wrote: +1 Mezzanine's Readme is, at the time of writing, 795 lines long - pretty much an essay! The GH Readme for Django itself is short and sweet at just 44 lines. That's a massive 94% reduction in lines. If you are looking for a python CMS to use, you want to read about 3 key features of Mezzanine that make it stand out from all the others, that's all. Then one could link to the Mezzanine website and documentation website for further details and even for installation steps etc. Just my thoughts. Interesting to hear what the core devs think... On Friday, 22 May 2015 10:43:37 UTC+1, Graham Oliver wrote: Hi all I would like to have a go at revamping the readme on GitHub https://github.com/stephenmcd/mezzanine/blob/master/README.rst Initial thoughts - Make it way shorter - Put the 'third party plugins' and 'sites using Mezzanine' lists in separate documents - Add details of 'Core Development Team' Possibly also something for people (relatively) new to the Open Source thing. All feedback appreciated... This one I quite like (apart from the crypto stuff) http://svn.apache.org/repos/asf/httpd/httpd/trunk/README Take Care g -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-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
Re: [mezzanine-users] Price Rounding Off Issues
Ok, seems like nothing to do then - please consider publishing a version that works with Mezzanine at some point though! On Mon, May 25, 2015 at 9:21 PM, vikraw vik...@gmail.com wrote: here is the link - https://github.com/payu-india/PayU-Integration-Kit-Django But that package didn't work out of the box and it needed lots of tweaking. So that statement must have been introduced then, as their code doesn't has that. Payu-India support for django is not very extensive and as a small business our focus is on making things up and running first, perfection comes later. Also, I don't know how to make that package install automatically using pip/fabric. Currently, i manually copy the package and then run their install and then sync the code changes. On Tuesday, May 26, 2015 at 1:25:38 AM UTC+5:30, Stephen McDonald wrote: Well you've resolved it for yourself but surely someone else will hit this. So which payment processor was it? On Mon, May 25, 2015 at 9:45 AM, vikraw vik...@gmail.com wrote: Looks like it is resolved for now. One of the payment processor libs had getcontext().prec = 2. After commenting it out, things looks ok. Once the flow reached that code, i had issues. But still not clear why it hasn't happening on dev environment On Monday, May 25, 2015 at 2:46:19 AM UTC+5:30, Danny S wrote: Is it possible that you are running with different versions of python between the runserver and nginx/gunicorn versions of your website? I've noticed before in other work that e.g. Python 2.7 has slightly different precision on floats than Python 2.6... But yeah, weird problem. On 25/05/2015 3:45 AM, vikraw wrote: The staged server have the locale correctly set ( see at end of my message the settings). Steps on my Staged server - Amazon Ec2 - Ubuntu 14 - stopped supervisor and nginx on my staged machine - switched my staged machine to run using - python manage runserver 0.0.0.0:8000 - put printf value statement in the currency filter under shop_tags.py now when i browse (using windows machine) the site running on ec2 machine I have NO issues with the Product prices, Cart total etc..Both the Browser and the printf values match However, when I switch the machine to nginx and start browsing from windows machine, i start getting the incorrect prices (alternate between correct and wrong) when - I press the different products or go back and forth from cart to product pages - Switching between incorrect price and correct prices happens everytime when I goto my payment processor and click the back button again to website (neglecting browser warnings that page has expired). BUT this doesn't happens when site running from python manage runserver ex: Rs.249 is displayed as Rs.250 and Rs.349 as Rs.350. clicking the same link toggles between those 2 values Help is greatly appreciated as i am near completion and can't figure this ambiguous behavior. My development is on Local Machine a Ubuntu 12.01LTS and I was testing using python manage runserver on 127.0.0.0:8000... This is working as expected locale command on ubuntu-14 amazon-ec2 LANG=en_IN LANGUAGE=en_IN:en LC_CTYPE=en_IN LC_NUMERIC=en_IN LC_TIME=en_IN LC_COLLATE=en_IN LC_MONETARY=en_IN LC_MESSAGES=en_IN LC_PAPER=en_IN LC_NAME=en_IN LC_ADDRESS=en_IN LC_TELEPHONE=en_IN LC_MEASUREMENT=en_IN LC_IDENTIFICATION=en_IN LC_ALL= The currencies symbol is correctly shown on the browser. However, i the prices change sometimes alternately and sometimes randomly. Correct price is 249. it switches between 249 and 250 when i click the same page or cart button. the cart total is updated On Saturday, May 23, 2015 at 10:59:37 PM UTC+5:30, Stephen McDonald wrote: It looks like you're calculating the correct value being stored in the DB, and only getting the error on output. Each currency value gets passed through the currency template tag, which is where the problem likely is. It also deals with machine specific locale settings, which will vary per machine - also making it a likely candidate for the error. Here's the source for it - https://github.com/stephenmcd/cartridge/blob/master/cartridge/shop/templatetags/shop_tags.py#L17-L41 Have you consistently defined (and installed) the correct locale? (defined with the SHOP_CURRENCY_LOCALE setting). Can you debug what happens in the currency template tag on your deployed machine? That might entail adding some logging to it, making a copy of it in your own project, printing out values while manually running it in a terminal, whatever works for you. On Sat, May 23, 2015 at 3:26 AM, vikraw vik...@gmail.com wrote: Hi Almost near launching a site. But running into Price rounding issues today when I fab deployed to AWS ec2 instance. Never had those issues before on ec2. My Development environment is working great with no issues. However on deployed machine -Prices are getting rounded off in various places ex: 249
