[mezzanine-users] Re: new release?
Hi, My current project is working on Django 1.6.1 and mezzanine 3.0.8. This is the first time I am doing package upgrade. I am thinking to upgrade Django 1.8 in steps (first 1.7 then 1.8) and mezzanine to latest version both. What are the things i need to take care to complete upgrade? If you could provide me some insights I will be glad. Regards, Sreedhar On Tuesday, 24 March 2015 04:36:32 UTC+5:30, elguavas 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? 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. -- You received this message because you are 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?
Yay, I just made that change manually in my copy and that fixed it! Thanks! Surely I'm not the first person who ran into that??? On Sunday, May 3, 2015 at 6:41:15 PM UTC-5, Stephen McDonald wrote: 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 javascript: 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-use...@googlegroups.com javascript:. 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] Default account
How does Mezzanine create the default for username: admin, password: default? Possible point in the right direction... -- You received this message because you are 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] Default account
Thanks for the quick reply with the helpful links! Instead of using Fabric to deploy, I am trying to use Docker http://www.docker.com, more specifically, this docker image for Mezzanine https://registry.hub.docker.com/u/noisy/mezzanine-docker-demo/. I took out the --noinput flag on the last manage.py commands (syncdb and migrate) in the Dockerfile because I have a shell script (found on Docker.com for postgres) that I changed a bit to include the db user, name and passwd. However when I run the command to start Mezzanine and link it to the db, it gives me this error: 570 static files copied to '/mezzanine-project/static'. CommandError: Command doesn't accept any arguments Is it because I removed the --noinput from those 2 statements in the Dockerfile? What am I missing here? On Monday, May 4, 2015 at 11:03:34 AM UTC-4, Kenneth Bolton wrote: The values are defined here: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/management/commands/createdb.py#L19-L21 And the method that creates the user is here: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/management/commands/createdb.py#L104-L112 If you use Fabric and the included fabfile, you can define a value for the admin password here: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/local_settings.py.template#L43 hth! -ken On Mon, May 4, 2015 at 10:55 AM, automo...@gmail.com javascript: wrote: How does Mezzanine create the default for username: admin, password: default? Possible point in the right direction... -- You received this message because you are 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 javascript:. 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.
[mezzanine-users] SSL difficulties
Let me preface this by saying I may be missing something obvious =)
In my experience turning on SSL breaks parts of TinyMCE in the backend.
Most (maybe all) of the TinyMCE popups, add link, edit html, etc..,
reference /asset_proxy/ which is not in the list of SSL prefixes. As a
result if the admin is served over SSL, the default behavior when ssl is
enabled, those popups no longer work.
An easy workaround is to add /asset_proxy/ to the SSL prefixes, but this
then breaks TinyMCE inline editing, via the editable tag, on any frontend
page that isn't served over SSL. On those pages /asset_proxy/ is initially
referenced without SSL but then redirected to the secure version, the
redirect breaks the popup.
My suggestion is that the Mezzanine SSLRedirectMiddleware also check a list
of prefixes that should be accessible securely or non securely, i.e. never
redirected. By default I think those would be:
('/asset_proxy/', '/displayable_links.js')
Am I missing something? If not and my suggestion sounds like a good idea I
will put together a pull request.
Thanks!
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] SSL difficulties
Thanks Iain, I should have mentioned it but this only happens when SSL_FORCED_PREFIXES_ONLY is True (which is the default behavior). When it's False things work great, but in the particular situation where I encountered it this time setting that to False isn't a viable option; there are pages that have non ssl iframes on them so they need to only be accessed via an unsecured connection to avoid insecure content warnings/errors in browsers. Thanks! On Mon, May 4, 2015 at 2:20 PM, Iain Mac Donald mezzan...@picturenow.co.uk wrote: I just deployed a 3.1.10 site and didn't encounter the problems you describe with SSL and TinyMCE. Here are the SSL related settings I used: SSL_ENABLED = True SSL_FORCED_PREFIXES_ONLY = False SSL_FORCE_URL_PREFIXES = (/admin,) mezzanine.core.middleware.SSLRedirectMiddleware, Have you tried this in more than one browser? Regards, Iain. -- You received this message because you are 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.
[mezzanine-users] Webfaction fabfile with Django 1.7.7 and development version of Mezzanine
I am just working through the webfaction fabfile written by Jervais (thanks!) https://github.com/jerivas/mezzanine-webf I am using Django 1.7.7, Python 2.7 and the current development version of Mezzanine. I am confused as to which line is causing the problem Either this https://github.com/jerivas/mezzanine-webf/blob/master/fabfile.py#L443 or this https://github.com/jerivas/mezzanine-webf/blob/master/fabfile.py#L444 The stack trace is below... Would welcome any pointers TIA g [108.59.11.112] run: python -c import os; os.environ['DJANGO_SETTINGS_MODULE']='settings';from django.conf import settings;from django.contrib.sites.models import Site;site, _ = Site.objects.get_or_create(id=settings.SITE_ID);site.domain = 'orotau.webfactional.com';site.save(); [108.59.11.112] out: /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/mezzanine/utils/conf.py:59: UserWarning: TIME_ZONE setting is not set, using closest match: UTC [108.59.11.112] out: warn(TIME_ZONE setting is not set, using closest match: %s % tz) [108.59.11.112] out: Traceback (most recent call last): [108.59.11.112] out: File string, line 1, in module [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/manager.py, line 92, in manager_method [108.59.11.112] out: return getattr(self.get_queryset(), name)(*args, **kwargs) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/query.py, line 422, in get_or_create [108.59.11.112] out: return self.get(**lookup), False [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/query.py, line 345, in get [108.59.11.112] out: clone = self.filter(*args, **kwargs) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/query.py, line 691, in filter [108.59.11.112] out: return self._filter_or_exclude(False, *args, **kwargs) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/query.py, line 709, in _filter_or_exclude [108.59.11.112] out: clone.query.add_q(Q(*args, **kwargs)) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1331, in add_q [108.59.11.112] out: clause, require_inner = self._add_q(where_part, self.used_aliases) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1358, in _add_q [108.59.11.112] out: current_negated=current_negated, connector=connector) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1182, in build_filter [108.59.11.112] out: lookups, parts, reffed_aggregate = self.solve_lookup_type(arg) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1120, in solve_lookup_type [108.59.11.112] out: _, field, _, lookup_parts = self.names_to_path(lookup_splitted, self.get_meta()) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/sql/query.py, line 1383, in names_to_path [108.59.11.112] out: field, model, direct, m2m = opts.get_field_by_name(name) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/options.py, line 416, in get_field_by_name [108.59.11.112] out: cache = self.init_name_map() [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/options.py, line 445, in init_name_map [108.59.11.112] out: for f, model in self.get_all_related_m2m_objects_with_model(): [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/options.py, line 563, in get_all_related_m2m_objects_with_model [108.59.11.112] out: cache = self._fill_related_many_to_many_cache() [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/db/models/options.py, line 577, in _fill_related_many_to_many_cache [108.59.11.112] out: for klass in self.apps.get_models(): [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/utils/lru_cache.py, line 101, in wrapper [108.59.11.112] out: result = user_function(*args, **kwds) [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/apps/registry.py, line 168, in get_models [108.59.11.112] out: self.check_models_ready() [108.59.11.112] out: File /home/orotau/.virtualenvs/ve_soul/lib/python2.7/site-packages/django/apps/registry.py, line 131, in check_models_ready [108.59.11.112] out: raise AppRegistryNotReady(Models aren't loaded yet.) [108.59.11.112] out:
[mezzanine-users] Re: Good approaches to doing graphics customization?
You might want to take a look at the section on Modifying the CSS in this tutorial (it's near the bottom): http://rosslaird.com/blog/customizing-mezzanine/ In general, I use a separate CSS file for my customizations (loaded after the bootstrap CSS), and I use either Emacs or Sublime Text (or Vim) to make the actual changes. All work very well. Also, typically the best way to identify elements to change is to use the web development features (or extensions) of your browser. In Chrome, the key for this is Ctrl-Shift-i (that's a letter i). Hope this helps. Ross On Monday, 4 May 2015 12:43:32 UTC-7, Brian Osborne wrote: All, Just starting out with Mezzanine, it's very impressive, and I'm happy that it's Python. Should add, I'm working on Mac OS. I'm more of a coder than a graphics designer. In fact I'm not a designer at all! I want to do some basic graphic customization (change some div or element to a different color, change a button color, and so on). I use Sublime Text, and if I go into Develop mode in Safari and use its Inspect button I'm able to figure out where most of the elements are in the CSS, and then I can modify them in the css/bootstrap.css file. But this is really clunky, and there are still visual elements that I can not find and modify. Can anyone give me advice on effective ways to do this? WYSIWYG or not, commercial or open source. Thank you in advance, Brian O. -- You received this message because you are 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: Good approaches to doing graphics customization?
Wow. Not the greatest of questions, because I haven't even installed ckeditor, let me try that approach right now. Sorry about that! On Monday, May 4, 2015 at 3:43:32 PM UTC-4, Brian Osborne wrote: All, Just starting out with Mezzanine, it's very impressive, and I'm happy that it's Python. Should add, I'm working on Mac OS. I'm more of a coder than a graphics designer. In fact I'm not a designer at all! I want to do some basic graphic customization (change some div or element to a different color, change a button color, and so on). I use Sublime Text, and if I go into Develop mode in Safari and use its Inspect button I'm able to figure out where most of the elements are in the CSS, and then I can modify them in the css/bootstrap.css file. But this is really clunky, and there are still visual elements that I can not find and modify. Can anyone give me advice on effective ways to do this? WYSIWYG or not, commercial or open source. Thank you in advance, Brian O. -- You received this message because you are 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: Good approaches to doing graphics customization?
Hmm.. I'm not sure if this will help you, but as a visually...bad developer, I've gotten quite far by replacing the bundled bootstrap with the LESS or SASS port and then just trying to get as far as possible by just editing variables in there. I find going into here https://github.com/twbs/bootstrap-sass/blob/master/templates/project/_bootstrap-variables.sass and editing variables easier than just hunting for all the relevant classes in the CSS version. On Monday, 4 May 2015 12:43:32 UTC-7, Brian Osborne wrote: All, Just starting out with Mezzanine, it's very impressive, and I'm happy that it's Python. Should add, I'm working on Mac OS. I'm more of a coder than a graphics designer. In fact I'm not a designer at all! I want to do some basic graphic customization (change some div or element to a different color, change a button color, and so on). I use Sublime Text, and if I go into Develop mode in Safari and use its Inspect button I'm able to figure out where most of the elements are in the CSS, and then I can modify them in the css/bootstrap.css file. But this is really clunky, and there are still visual elements that I can not find and modify. Can anyone give me advice on effective ways to do this? WYSIWYG or not, commercial or open source. Thank you in advance, Brian O. -- You received this message because you are 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.
