Re: [mezzanine-users] new release?
I thing could be maiking 3.1.x series LTS and Having a 3.2 release after 1.8 release and other work arrounds. like wagtail-cms team is doing. enjoy the vacation! Thank you for all your effort behind mezzanine. Kind regards On Wed, Mar 25, 2015 at 8:47 AM, 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://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/_QWfFVB3RVc/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
[mezzanine-users] Filetypes for Media Library
Hi all, Probably a very simple question, but where are the filetypes for the Media Library defined, and can I override them? If I go into my Media Library, and choose to Upload a file, the file browser window I'm presented with has the following options: *.html; *.py; *.js; *.css; *.jpg; *.jpeg; ... and several more However, some useful ones are missing (like MS Word's docx) and even this selected list fails to show up PDFs in my current directory even though *.pdf is one of the options (I suspect it's too long for Windows liking). The other bad thing is that the file type drop down doesn't have the All Files (*.*) option that you may be used to seeing. I'm sure that there would be a nice easy setting somewhere that controls this, the question is: where is it? Thanks, Seeya. Danny. -- Email: molo...@gmail.com -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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] Hosted solutions for Mezzanine
On Tuesday, March 24, 2015 at 7:40:28 PM UTC, Graham Oliver wrote: On a more general level, the issue of who Mezzanine is for, is something that I am trying to get clear in my own mind. I know from listening to Stephen McDonald talk about the birth of Mezzanine - https://vimeo.com/103614826 https://www.google.com/url?q=https%3A%2F%2Fvimeo.com%2F103614826sa=Dsntz=1usg=AFQjCNGKZjTWp3ZDvp7rxWqo6T5u6cBdJQ that it was in response to his management wanting to 'go with Wordpress' My working hypothesis is that creating websites with Mezzanine is *not* for non-developers. Other things would be better... Having something that functioned as a WordPress replacement would be awesome. I'm trying to weigh up whether Mezzanine could be that. At the moment, I'm still at a loss for what to say to people who just want a website with a simple CMS. For the typical person, WordPress is going to give huge problems with security etc. - I couldn't sleep at night if I was recommending it or using it for clients. Alternative web site builders like weebly.com get people so far, but you've essentially got to start from scratch when you outgrow what they provide. Regards, Luke -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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] Filetypes for Media Library
Thanks Josh, super helpful :D Works like a charm - the name of the settings to put in my own settings.py are FILEBROWSER_EXTENSIONS and FILEBROWSER_SELECT_FORMATS but that was fairly obvious from the code you pointed to. I find it somewhat curious that, for, e.g. the Media Library upload, the file dialog shows a concatenation of all the EXTENSIONS available (rather than just say All Files), whereas if you choose to upload an image for a product, it actually gives All Files rather than restricting it to images... Haven't tried the Gallery, but given your pointer to the code, I'd assume there it's restricted to Images... Seeya. Danny. On 26/03/2015 12:53 AM, Josh Cartmell wrote: Hi Danny, they are defined here: https://github.com/stephenmcd/filebrowser-safe/blob/master/filebrowser_safe/settings.py#L43 You can override either EXTENSIONS or SELECT_FORMATS or both in your projects settings.py file. The SELECT_FORMS are what filebrowser uses to determine what are valid extensions for a particular FileField. For example, in Mezzanine's galleries, https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/galleries/models.py#L120, the format of the image FileField is set to Image. Good luck! On Wed, Mar 25, 2015 at 2:34 AM, Danny molo...@gmail.com mailto:molo...@gmail.com wrote: Hi all, Probably a very simple question, but where are the filetypes for the Media Library defined, and can I override them? If I go into my Media Library, and choose to Upload a file, the file browser window I'm presented with has the following options: *.html; *.py; *.js; *.css; *.jpg; *.jpeg; ... and several more However, some useful ones are missing (like MS Word's docx) and even this selected list fails to show up PDFs in my current directory even though *.pdf is one of the options (I suspect it's too long for Windows liking). The other bad thing is that the file type drop down doesn't have the All Files (*.*) option that you may be used to seeing. I'm sure that there would be a nice easy setting somewhere that controls this, the question is: where is it? Thanks, Seeya. Danny. -- Email: molo...@gmail.com mailto:molo...@gmail.com -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscribe@__googlegroups.com mailto:mezzanine-users%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com mailto:mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Email: molo...@gmail.com -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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?
I hope this doesn't sound like a criticism of Django, they can't know what they're breaking if no one tells them. yep, it's hard to question a lot of things about other libre/open source projects without seeming ungrateful. i'm a libre software developer myself so i'm keenly aware of all the problems resulting from the reality of time strapped volunteers and trying to release in a timely fashion. I hope I've been able to make things a tiny bit clearer for everyone who has been questioning the lapse in releasing. i can't speak for anyone else but for me the question was really is it thought the current release situation with mezz an anomaly or that the pace of django change is gonna cause ongoing problems?, so that's been fully and clearly addressed by Ed and yourself. thanks. and i echo Asif's sentiments with please enjoy your holiday and thanks a huge bunch for all your fantastic effort on mezz so far, it's great software. ;) -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
