Re: [mezzanine-users] Migration to Jazzband / Code Shelter

[Pete Dermott]

I have created an issue on the jazzband-roadies Github 
<https://github.com/jazzband-roadies/help/issues/178> mentioning Stephen. 
To reiterate again - I'm not trying to step on anyone's toes, I just would 
like to get this moving so we can have a 2.0 compatible release ready for 
when April rolls around and 1.11 is no longer supported.

On Friday, 13 December 2019 10:41:21 UTC, Pete Dermott wrote:
>
> Hi Eduardo,
>
> I've been in contact jezdez - one of the Jazzband roadies to discuss this 
> in the #jazzband IRC channel.
>
> Jazzband exists to lower the barrier of entry for maintenance and remove 
> the single-developer-problem that we currently have. It's not a guarantee 
> of maintenance but it should help simplify releases and would give us the 
> opportunity to get more eyes on the upgrade to 2.2 that we so drastically 
> need.
>
> As a next step he has encouraged us to create an issue 
> <https://jazzband.co/roadies/issue?labels=question> proposing the 
> transfer and mention Stephen and any other contributors that may be 
> interested in helping with the transfer and future maintenance, I expect 
> you or Stephen may be the best person to do this as you will have the 
> required level of access.
>
> On Thursday, 12 December 2019 23:47:47 UTC, Eduardo Rivas wrote:
>>
>> Hi Pete,
>>
>>  
>>
>> Thanks for bringing this over to the mailing list. I’m one of the 
>> contributors to Mezzanine and still use it almost daily. I’m glad others 
>> still want to see the project move forward.
>>
>>  
>>
>> Do Jazzband or Code Shelter have contributors on standby ready to take in 
>> projects and perform maintenance tasks? I’m not entirely clear on how they 
>> work, just want to make sure I understand correctly.
>>
>>  
>>
>> *From: *Pete Dermott
>> *Sent: *Tuesday, December 10, 2019 8:24 AM
>> *To: *Mezzanine Users
>> *Subject: *[mezzanine-users] Migration to Jazzband / Code Shelter
>>
>>  
>>
>> Following on from the discussion on GitHub issue #1928 
>> <https://github.com/stephenmcd/mezzanine/issues/1928>
>>
>>  
>>
>> Throughout 2019 there has been 1 commit to the master Github repo, we 
>> haven't had a full release since August 2018 and there are a number 
>> outstanding changes that are waiting to go into a new release. We still 
>> don't have Django 2 support despite it being released in December 2018 and 
>> Django 3 is now out and available for development.
>>
>>  
>>
>> I use Mezzanine a lot in my day to day projects but I don't feel like I 
>> personally have the skill to take it forward and make it fully compatible 
>> with the changes to Django and jQuery that are required.
>>
>>  
>>
>> Basically, I feel that this project needs a bit of help to keep it 
>> relevant. Thankfully there are maintainer communities in Jazzband 
>> <https://jazzband.co/>and Code Shelter <https://www.codeshelter.co/> 
>> that may be able to help us. I feel that handing the project over to them 
>> should at least ensure that active Mezzanine projects are not left exposed 
>> when 1.11 is deprecated in April 2020.
>>
>>  
>>
>> Also - just to note - this is in no way mean to denigrate the hard work 
>> that Stephen and others have done over the years with this project, it 
>> speaks volumes about the quality of the codebase that Mezzanine is still my 
>> Django CMS of choice after all this time.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Mezzanine Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to mezzani...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mezzanine-users/73f6831d-df8c-4f79-bf12-7c0923fd50b1%40googlegroups.com.

Re: [mezzanine-users] Migration to Jazzband / Code Shelter

[Pete Dermott]

Hi Eduardo,

I've been in contact jezdez - one of the Jazzband roadies to discuss this 
in the #jazzband IRC channel.

Jazzband exists to lower the barrier of entry for maintenance and remove 
the single-developer-problem that we currently have. It's not a guarantee 
of maintenance but it should help simplify releases and would give us the 
opportunity to get more eyes on the upgrade to 2.2 that we so drastically 
need.

As a next step he has encouraged us to create an issue 
<https://jazzband.co/roadies/issue?labels=question> proposing the transfer 
and mention Stephen and any other contributors that may be interested in 
helping with the transfer and future maintenance, I expect you or Stephen 
may be the best person to do this as you will have the required level of 
access.

On Thursday, 12 December 2019 23:47:47 UTC, Eduardo Rivas wrote:
>
> Hi Pete,
>
>  
>
> Thanks for bringing this over to the mailing list. I’m one of the 
> contributors to Mezzanine and still use it almost daily. I’m glad others 
> still want to see the project move forward.
>
>  
>
> Do Jazzband or Code Shelter have contributors on standby ready to take in 
> projects and perform maintenance tasks? I’m not entirely clear on how they 
> work, just want to make sure I understand correctly.
>
>  
>
> *From: *Pete Dermott 
> *Sent: *Tuesday, December 10, 2019 8:24 AM
> *To: *Mezzanine Users 
> *Subject: *[mezzanine-users] Migration to Jazzband / Code Shelter
>
>  
>
> Following on from the discussion on GitHub issue #1928 
> <https://github.com/stephenmcd/mezzanine/issues/1928>
>
>  
>
> Throughout 2019 there has been 1 commit to the master Github repo, we 
> haven't had a full release since August 2018 and there are a number 
> outstanding changes that are waiting to go into a new release. We still 
> don't have Django 2 support despite it being released in December 2018 and 
> Django 3 is now out and available for development.
>
>  
>
> I use Mezzanine a lot in my day to day projects but I don't feel like I 
> personally have the skill to take it forward and make it fully compatible 
> with the changes to Django and jQuery that are required.
>
>  
>
> Basically, I feel that this project needs a bit of help to keep it 
> relevant. Thankfully there are maintainer communities in Jazzband 
> <https://jazzband.co/>and Code Shelter <https://www.codeshelter.co/> that 
> may be able to help us. I feel that handing the project over to them should 
> at least ensure that active Mezzanine projects are not left exposed when 
> 1.11 is deprecated in April 2020.
>
>  
>
> Also - just to note - this is in no way mean to denigrate the hard work 
> that Stephen and others have done over the years with this project, it 
> speaks volumes about the quality of the codebase that Mezzanine is still my 
> Django CMS of choice after all this time.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to mezzani...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mezzanine-users/6d2e5528-9522-480f-bd8d-ea3dd4336a30%40googlegroups.com.

[mezzanine-users] Migration to Jazzband / Code Shelter

[Pete Dermott]

Following on from the discussion on GitHub issue #1928 


Throughout 2019 there has been 1 commit to the master Github repo, we 
haven't had a full release since August 2018 and there are a number 
outstanding changes that are waiting to go into a new release. We still 
don't have Django 2 support despite it being released in December 2018 and 
Django 3 is now out and available for development.

I use Mezzanine a lot in my day to day projects but I don't feel like I 
personally have the skill to take it forward and make it fully compatible 
with the changes to Django and jQuery that are required.

Basically, I feel that this project needs a bit of help to keep it 
relevant. Thankfully there are maintainer communities in Jazzband 
and Code Shelter  that 
may be able to help us. I feel that handing the project over to them should 
at least ensure that active Mezzanine projects are not left exposed when 
1.11 is deprecated in April 2020.

Also - just to note - this is in no way mean to denigrate the hard work 
that Stephen and others have done over the years with this project, it 
speaks volumes about the quality of the codebase that Mezzanine is still my 
Django CMS of choice after all this time.

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mezzanine-users/476a90bc-1e21-4cfe-8039-b72a6e1748eb%40googlegroups.com.

[mezzanine-users] Re: Corruption of page templates when using mezzanine middleware?

[Pete Dermott]

Actually, nevermind.

Literally two minutes posting this I discovered that the 
django.middleware.gzip.GZipMiddleware was the cause of my issue, I've 
disabled that and everything is working perfectly!

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and 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] - Admin links to custom product type no longer work

[Pete Dermott]

Thank you for the reply Stephen. I don't know if I'm missing something but 
I'm still having some problems with this. 

You say: 

> You'll see an "Add product" dropdown list (presumably with only one item 
> in it in your case, namely BaseProduct), which is how you choose which type 
> of product you're adding. 
>

But no matter what I do I don't see any such dropdown, I've created an 
example project based on the guide from 
https://github.com/stephenmcd/cartridge/blob/master/docs/components.rst and 
have pushed this up to a simple github repo at 
https://github.com/petedermott/cartridge-example.

In short, my models.py look like this:

from django.db import models

from cartridge.shop.models import Product

# Create your models here.
class SubclassedProduct(Product):
test = models.CharField(blank=True, null=True, max_length=255)


and my admin.py looks like this:

from django.contrib import admin

from cartridge.shop.admin import ProductAdmin
from test_products.models import SubclassedProduct

# Register your models here.
admin.site.register(SubclassedProduct, ProductAdmin)


Is there something obvious I'm missing?

On Monday, February 6, 2017 at 12:34:37 AM UTC, Stephen McDonald wrote:
>
> Hi there,
>
> Subclassing the product model was previously not a supported feature - I 
> imagine you had to do some extensive hacking to get that working in the 
> actual site. 
>
> It now is a supported feature however, much like the Page model in 
> Mezzanine can be subclasses to create custom page types, custom products 
> now work the same in the development version of Cartridge.
>
> The good news is that what you've done should mostly work now - it's just 
> that your existing products are missing a value that identifies them as 
> your BaseProduct custom product type - if you inspect the DB somehow, 
> you'll see the table for the Product model has a "content_type" field (if I 
> recall correctly), and it stores a string name for the type of product it's 
> related to, in your case I think the value would be "baseproduct", but the 
> best way to know for sure would be to add a new product of "BaseProduct" 
> type, and see what value gets stored for that. 
>
> BTW the redirection is occurring because with this new version, *all* 
> product subclasses in the admin will redirect to one listing page where 
> they all get managed. You'll see an "Add product" dropdown list (presumably 
> with only one item in it in your case, namely BaseProduct), which is how 
> you choose which type of product you're adding. You'll need to use that to 
> perform the check I just mentioned. Given the way the admin works now, 
> you'll also be able to remove BaseProduct from the ADMIN_MENU_ORDER setting 
> you have, since that's redundant.
>
>
>
>
>
> On Thu, Jan 26, 2017 at 1:22 AM, Pete Dermott <peter@gmail.com 
> > wrote:
>
>> Apologies if this this an existing issue or I'm missing something but I 
>> am having a little trouble with my cartridge installation and my custom 
>> product types, I am running on the current versions of Mezzanine and 
>> Cartridge from the GitHub repos.
>>
>> Previously I have declared my custom product type in the settings.py file 
>> as follows:
>>
>> ADMIN_MENU_ORDER = (
>> ...
>> ("My Shop", (
>> "my_shop.BaseProduct",
>> )),
>>
>> ...
>>
>>
>> .. in my models as:
>>
>> from cartridge.shop.models import Product, Category, ProductVariation, 
>> ProductImage
>>
>>
>> ...
>>
>>
>> class BaseProduct(Product):
>> cadfile = fields.FileField(upload_to="product/cadfile", 
>> extensions=(".dwg",), blank=True, null=True, help_text="Format: Files should 
>> be named in all lower case with leading zeros and ONLY product codes e.g 
>> rg09.dwg")
>> pdffile = fields.FileField(upload_to="product/pdffile", blank=True, 
>> null=True, help_text="Format: Files should be named in all lower case with 
>> leading zeros and ONLY product codes e.g pm01.pdf")
>> product_code = models.CharField(max_length=8, help_text="Format: All 
>> caps, no spaces, include leading zero's, e.g DC01B")
>>
>> ...
>>
>>
>>
>> ... and in the admin as:
>>
>> from cartridge.shop.admin import CategoryAdmin, ProductAdmin, 
>> ProductVariation, ProductOption, Order
>>
>>
>> ...
>>
>>
>> class BaseProductAdmin(ProductAdmin):
>> fieldsets = product_fieldsets
>>
>> additional_fieldsets = ("product_height"

[mezzanine-users] [Cartridge] - Admin links to custom product type no longer work

[Pete Dermott]

Apologies if this this an existing issue or I'm missing something but I am 
having a little trouble with my cartridge installation and my custom 
product types, I am running on the current versions of Mezzanine and 
Cartridge from the GitHub repos.

Previously I have declared my custom product type in the settings.py file 
as follows:

ADMIN_MENU_ORDER = (
...
("My Shop", (
"my_shop.BaseProduct",
)),

...


.. in my models as:

from cartridge.shop.models import Product, Category, ProductVariation, 
ProductImage


...


class BaseProduct(Product):
cadfile = fields.FileField(upload_to="product/cadfile", 
extensions=(".dwg",), blank=True, null=True, help_text="Format: Files should be 
named in all lower case with leading zeros and ONLY product codes e.g rg09.dwg")
pdffile = fields.FileField(upload_to="product/pdffile", blank=True, 
null=True, help_text="Format: Files should be named in all lower case with 
leading zeros and ONLY product codes e.g pm01.pdf")
product_code = models.CharField(max_length=8, help_text="Format: All caps, 
no spaces, include leading zero's, e.g DC01B")

...



... and in the admin as:

from cartridge.shop.admin import CategoryAdmin, ProductAdmin, ProductVariation, 
ProductOption, Order


...


class BaseProductAdmin(ProductAdmin):
fieldsets = product_fieldsets

additional_fieldsets = ("product_height", "product_width", 
"product_projection", "product_diameter", "product_length",
"cornice_picture", "cornice_profile_picture", 
"cornice_wall_height",  "cornice_ceiling_projection",
"cornice_pattern_repeat", "internal_height", 
"internal_width", "priority",)

fieldsets.append(
(_("Additional"), {
"fields": tuple(additional_fieldsets),
}))

list_display = product_list_display
list_filter = ("status", "available", "categories", "product_type", 
"updated")

def has_module_permission(self, request):
for (name, items) in settings.ADMIN_MENU_ORDER:
if "stevensons_shop.BaseProduct" in items:
return True
return False


admin.site.register(BaseProduct, BaseProductAdmin)



This used to work fine in previous versions of the system (those installed 
directly from pip), however I wanted to take advantage of some of the fixes 
in newer versions.

However this has had the adverse affect of breaking my admin area. Whereas 
before I could simply click on the "Base product" sidebar link and get 
taken to my admin view I now am immediately redirected to the generic 
/admin/shop/product view that only contains the basic information for my 
product and none of my extended fields, I'm aware that there have been some 
pretty major changes that happened in commit #8d3ac6b 

 however 
I am currently at a loss trying to figure out what I need to do to get this 
working again.

Any suggestions are greatly appreciated.

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

[mezzanine-users] Re: Performance: Filebrowser and S3

[Pete Dermott]

I hate to dig up a very old thread but was there ever any progress on this? 

I'm trying to use S3 on my medium sized Cartridge site which consists of 
around 300 products, each with their own folder containing a couple of 
images, cads and pdf files. Currently the filebrowser is taking around 1.5 
minutes to fetch a page of results on my vagrant box or 25 seconds on a 
basic heroku hosted site.

I really want to use the filebrowser as in theory it can offer a good 
consistent structure for modifying products but in its current state is 
pretty unusable.

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and 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: How to override the name of the product and variations in the cart / checkout?

[Pete Dermott]

Thanks Ryne.

I agree that a cartridge setting for it would be overkill, maybe some 
changes to cartridge to present it a different way would be nice but as 
variation options are so subjective I totally see why it works the way that 
it currently does.

In the end I just monkey patched it to remove the variation from the 
product name. The code to do so was pretty simple, in my_shop/models.py: 

# Monkey patching! This will override the name of the product in the cart to
# produce a version without the variant name, instead this will be shown 
via the SKU field.
def product_variation_str(self):
"""
 Display the option names and values for the variation.
 """
result = u"%s" % (str(self.product))
return result.strip()

ProductVariation.__str__ = product_variation_str

Not ideal but it works well enough.

On Friday, November 4, 2016 at 7:31:25 PM UTC, Ryne Everett wrote:
>
> I agree that the current default behavior isn't great for everybody. I'm 
> not thrilled by it myself but have lived with it so far. 
>
> One approach would be to improve the default behavior in cartridge, 
> though I don't have a proposal for a more generally acceptable format at 
> hand. 
>
> Another approach would be to add a cartridge setting for a function that 
> formats this string, but I'm not sure that can be justified. 
>
> Perhaps monkey-patching the ProductVariation.__str__ method would be the 
> best approach. I don't think I've monkey-patched model methods before 
> but you might come up with a sensible way to do it with experimentation 
> and/or searching the web. 
>
> Please give a report if you come up with anything. 
>
> On 11/02/2016 05:20 AM, Pete Dermott wrote: 
> > Hi Everyone, 
> > 
> > I'm looking to create a Cartridge store that offers the ability for 
> > customers to buy low cost samples of our products, my thought was to 
> > use the variations system to do so. 
> > 
> > However, when I get to the checkout the system puts the items in the 
> > cart as $ProductName $ProductOptionType: $ProductOptionName so for 
> > example, with my product option type of "Shippable" this turns into 
> > "Product Name Shipable: Sample" which isn't really ideal. 
> > 
> > What I would like to do instead is remove the modification of the 
> > product description and show the original description and a separate 
> > field for the products SKU instead. 
> > 
> > I believe the modification to the name is taking place 
> > incartridge.models.ProductVariation file's __str__ method 
> > <
> https://github.com/stephenmcd/cartridge/blob/master/cartridge/shop/models.py#L229>
>  
>
> > but I've got no idea how I can modify this without causing issues with 
> > other parts of the site. 
> > 
> > What is my best option here? 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Mezzanine Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to mezzanine-use...@googlegroups.com  
> > <mailto:mezzanine-users+unsubscr...@googlegroups.com >. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

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