[mezzanine-users] Mezzanine-Cartridge Problem when view product image
Not sure what went wrong and where to start. I have Cartridge==0.9.3 Django==1.6.4 Mezzanine==3.1.4 Problem: When click on product image in a full site, I do not get a floating/overlay image window as seen in the Mezzanine demo site. Instead, I get the display image, see attached, added on top of the current view pushing down all other content. https://lh5.googleusercontent.com/-u75J_-oLjRE/U5WuTi5Bh3I/BRQ/oS-pMW5IjPI/s1600/image.tiff Any suggestion on where I should start looking would be much appreciated. Thank you 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.
[mezzanine-users] Mezzanine / Filebrowser Media Root issue
I have a bit of a strange one with where Filebrowser Mezzanine is locating media. In production, MEDIA_ROOT and FILEBROWSER_MEDIA_ROOT both point to the correct place: /web/sites/Project/project/static/media However Filebrowser's media library and mezzanine is locating media in: /var/www/media/ seemingly neglecting to join media_root to the path it uses for it's media library and when uploading files. Running on Mezzanine 3.14 with django 1.6. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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-Cartridge Problem when view product image
I suggest you look at the Javascript console in your browser and look for errors. A best-guess is that some of the Javascript libraries are not loading properly. On Mon, Jun 9, 2014 at 8:55 AM, green yupo...@gmail.com wrote: Not sure what went wrong and where to start. I have Cartridge==0.9.3 Django==1.6.4 Mezzanine==3.1.4 Problem: When click on product image in a full site, I do not get a floating/overlay image window as seen in the Mezzanine demo site. Instead, I get the display image, see attached, added on top of the current view pushing down all other content. https://lh5.googleusercontent.com/-u75J_-oLjRE/U5WuTi5Bh3I/BRQ/oS-pMW5IjPI/s1600/image.tiff Any suggestion on where I should start looking would be much appreciated. Thank you 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. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Re: modeltranslations - round 2
Ok, changes are done. I tried something for inlines admin classes (mezzanine.core.admin), but I’m not sure wether it sounds right or not, let me know. Le lundi 9 juin 2014 02:37:44 UTC+2, Stephen McDonald a écrit : On Sun, Jun 8, 2014 at 6:15 PM, Mathias Ettinger mathias@gmail.com javascript: wrote: You’re pretty right, some design choices sound really bad when put like this. I’ll move the admin classes, the code_list and the frontend language selector somewhere else. Not bad per se, it's common for these things to involve some iterations :-) As for the TRANSLATED setting, I don’t recall exactly why I tied it with USE_I18N. If I’m correct, it is because django-modeltranslation deactivates itself when USE_I18N is False. So we can’t relly solely on USE_MODELTRANSLATION to know when translations are activated. I’ll check that by tomorow and let you know. But if it is the case, what is your suggested approach ? Force the USE_I18N to True if USE_MODELTRANSLATION is True ? Tighten TRANSLATED into settings instead of a global var ? So if modeltranslations needs USE_I18N then that's fine - let's just comment that in the code where we deal with it. I guess what I was getting at was that we should try and have this configurable via a single point, namely USE_MODELTRANSLATION - we can handle all the rest in set_dynamic_settings. There we can check if USE_MODELTRANSLATION is True and if so, also check that we can import modeltranslations, and then with that in place we can do the rest - set USE_I18N to True, and add modeltranslations to INSTALLED_APPS if missing. After that we can reliably use mezzanine.conf.settings.USE_MODELTRANSLATION *everywhere* to control integration (such as which admin class to use, what appears on the front-end, etc). Le samedi 7 juin 2014 12:09:02 UTC+2, Stephen McDonald a écrit : Ok I spent a bit of time going over the pull request and testing it, it's really good. I think we can tighten things up a little, for example we have `class SomeAdmin(TRANSLATED and TranslationAdmin or admin.ModelAdmin)` all through each of the admin modules. I think we could have a single BaseAdmin class with this logic that everything subclasses, rather than having conditions all throughout the code base. With that in place I figure it'd be pretty easy for us to modify that base class to include a snippet of jQuery with a single toggle (eg per screen, not per field, as Ed suggested) that shows/hides all the language fields. Also confused about the end of mezzanine/conf/__init__: TRANSLATED = settings.USE_MODELTRANSLATION and settings.USE_I18N CODE_LIST = [lang[0] for lang in settings.LANGUAGES] This isn't where settings should simply be dumped. CODE_LIST could possibly be a function in mezzanine.utils.translation. Does Django not have this already? More importantly I don't understand the relationship between USE_MODELTRANSLATION and USE_I18N, and why these get combined into another setting (which isn't consistently used throughout the PR, in same cases this combo of settings get checked separately again). Can't everything just check the USE_MODELTRANSLATION settings? If USE_I18N is needed for this to work, then that's what's set_dynamic_settings is for - fixing up missing things that the developer has intended to have working by providing a single point of configuration that hides away all the various bits that need configuring. In set_dynamic_settings we should simply check for USE_MODELTRANSLATION and if True, add modeltranslation app if missing, and if USE_I18N actually needs to be True for modeltranslation to work, set it to True as well. modeltranslation shouldn't be in INSTALLED_APPS by default either. Lastly we probably don't want the language chooser for the front-end site in the top nav, there's really no room there. Perhaps it could sit on the right-hand panel at the top somewhere along with the login bits, conditionally, if USE_MODELTRANSLATION is True. All of this stuff should be turned off by default which means USE_MODELTRANSLATION defaults to False and *everything* else stems from that. If I've stupidly overlooked anything please let me know. This looks real promising and I'm hoping this along with django-rest-framework integration will make a compelling offering for the next major release 3.2. I'm going to push 3.1.5 shortly with some bug fixes, and hopefully that'll be the last 3.1.x release. Thanks Mathias and Ed for working this all out, it looks really really good. On Sat, Jun 7, 2014 at 2:31 PM, Stephen McDonald st...@jupo.org wrote: Real odd, works fine for me now and no matter what I try I can't reproduce the error I had. On Sat, Jun 7, 2014 at 2:09 PM, Eduardo Rivas jeriva...@gmail.com wrote: Odd, I just created a project without issue. This is my venv: Django==1.6.5 Mezzanine==3.1.3 #From Mathias' branch
[mezzanine-users] Re: Mezzanine 3.1.5 and Cartridge 0.9.4 released
Awesome news, and really looking forward for 3.2! I have some questions regarding thumbnails in RichText fields. What size will they be? Can they be configured in some way by content editors, or developers? I made a quick search on the docs (which already report as 3.1.5) for thumbnail and couldn't find anything besides the function's docstring. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Re: Mezzanine 3.1.5 and Cartridge 0.9.4 released
It just uses the width/height attributes found on the image tag itself, which should always be present for the target use case, eg Filebrowser - TinyMCE. So it's actually the content author who defines it using whatever WYSIWYG editor is configured. You can see the code here which is pretty minimal: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/utils/html.py#L41-L61 On Tue, Jun 10, 2014 at 2:54 PM, Eduardo Rivas jerivasmel...@gmail.com wrote: Awesome news, and really looking forward for 3.2! I have some questions regarding thumbnails in RichText fields. What size will they be? Can they be configured in some way by content editors, or developers? I made a quick search on the docs (which already report as 3.1.5) for thumbnail and couldn't find anything besides the function's docstring. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Fabric file and related resources for deploying Mezzanine to Webfaction
Nice work Ed, that's awesome. Webfaction's always been one of the most popular deployment targets, yet suffers from some inconsistencies with vanilla virtual servers - awesome to have a tool that solves that problem. Do you want to add a link in the list of apps in Mezzanine's README, and to the Mezzanine grid on Django Packages ( https://www.djangopackages.com/grids/g/mezzanine/)? If not I'll do it. On Tue, Jun 10, 2014 at 3:27 PM, Eduardo Rivas jerivasmel...@gmail.com wrote: Hello everyone! Since I started with Mezzanine/Django I've been deploying my sites to Webfaction http://www.webfaction.com?affiliate=jerivas (that's a referral link). Even though their one-click installers are great, they make it hard to keep your Django version up to date and automate the deployment process. For that you need to go beyond the official docs (however, tutorials are not hard to find). I decided to create my own version of the Fabric script that ships with Mezzanine and automate the whole deployment process using the Webfaction API (knowing that Webfaction accounts don't have root access to install stuff). And so, Mezzanine-WebF https://github.com/jerivas/mezzanine-webf was born. I have used it internally for months and others have given it a shot, providing valuable feedback and bug fixes, so I'm confident it's reached an acceptable stability. So, if you would like to automate deployment of Mezzanine sites to a Webfaction shared hosting account, this is the tool for the job. Feel free to report any bugs you find on Github's issue tracker and contribute fixes if you can. Please note you should be familiar enough with Django/Mezzanine, Fabric, and Webfaction to use the tool, and please read the README. I hope it helps a few. Here's the link again: https://github.com/jerivas/mezzanine-webf. -- You received this message because you are subscribed to the Google Groups Mezzanine Users group. To unsubscribe from this group and 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.
