[mezzanine-users] Re: Issues with page processors in Mezzanine

[Eduardo Rivas]

Hello Neeraj. I've done what you're trying to accomplish several times in 
the past. The solution is to create a template tag that loads your custom 
Articles into the template context. Mezzanine has the {% blog_recent_posts 
%}tag
 that does the same. Mezzanine's implementation goes the extra mile and 
adds author and category filters, but a bare implementation should look 
like this:

First, create a folder "templatetags" in your app folder, with a file 
called news_tags.py and another one called __init__.py. Let's say your app 
is called News and your model is also called News. You should have 
news/templatetags/news_tags.py and __init__.py. The init file is empty and 
exists only to indicate that the templatetags folder should be treated as a 
Python module.

# news_tags.py
from mezzanine import template

from news.models import News

register = template.Library()


@register.as_tag
def recent_news(limit=4):
"""
Put a list of recently published News into the template context.
Usage: {% recent_news 3 as recent_news %}
"""
news = News.objects.published()
return list(news[:limit])

The template tag let's you get the latest (published) News objects sliced 
to a custom limit. You can further extend the tag to apply sorting and 
filtering.

# templates/index.html
{% load news_tags %}

{% recent_news 5 as recent_news %}
{% for news in recent_news %}
{{news.title}}
{{news.publish_date|date}}
{% endfor %}

This will render the 5 most recent news displaying a link to the full 
article and the publish date. This assumes your News model has such fields 
(it will if you've extended Displayable). Again, you can extend it to your 
liking displaying any of the fields available to the News model.

Check out the Django docs on template 
tagsand 
Mezzanine's Displayable 
model.
 
Please notice Mezzanine overrides some parts of Django's template tag 
environment, which explains the difference in writing a template tag for 
Mezzanine and Django.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Internal links in the MCE editor

[Eduardo Rivas]

Wow, thank you very much Steve! This will be really handy.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Update to Bootstrap 3?

[Eduardo Rivas]

Off the top of my head, I removed it because it only served the purpose of 
adding the multi-level drop-downs, and Mezzanine 3 uses a pure CSS solution 
to achieve that. The downside is, as you noted, the submenus are not 
accessible in mobile. I now remember I actually added it to the "Know 
Issues" section of my pull request (#777). So yeah, it's a bug and it would 
be much appreciated if you could contribute a fix. I'd do it myself, but I 
really don't have the time right 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/groups/opt_out.

[mezzanine-users] Re: How to hide certain specific pages from search?

[Eduardo Rivas]

I would say you should uncheck the "Show in sitemap" checkbox in each page 
and add a Disallow entry in robots.txt. Bear in mind that if any other site 
(or your own) links to this page, it might get crawled anyways.

-- 
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/groups/opt_out.

[mezzanine-users] Localization features in site upgraded from 1.4 to 3.0

[Eduardo Rivas]

Hi everyone. I have several sites running on Mezzanine 1.4.16 and would 
like to migrate them to 3.0.4, mostly because the admin localization 
features would be useful to me. I've completed the upgrade but cannot get 
the localization to work. This is what I've done:

   1. Add the LANGUAGES tuple to settings.py. In my case I've included two 
   languages.
   2. Add LocaleMiddleware to MIDDLEWARE_CLASSES.
   3. Wrap the admin patterns in i18n_patterns in the main url conf.

Basically, my urls.py and settings.py are identical to what currently sits 
in the development branch. I do get the dropdown in the admin listing the 
two languages I've added (English and Spanish), but selecting any option 
always results in English. Am I missing something?

-- 
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/groups/opt_out.

[mezzanine-users] Re: Localization features in site upgraded from 1.4 to 3.0

[Eduardo Rivas]

In fact, I've also started a blank project with 3.0.4 and get the same 
results. Can anyone confirm?

-- 
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/groups/opt_out.

[mezzanine-users] Re: Localization features in site upgraded from 1.4 to 3.0

[Eduardo Rivas]

Oh snap! Yes, that fixes it. 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/groups/opt_out.

[mezzanine-users] Restricting shop to active users only

[Eduardo Rivas]

Hello Mezzaniners and Cartridgers (??).
I have some very specific requirements for a project I'm working in. I 
would like to have shop categories available to all visitors of the site 
(they can browse all categories and see which products are included in 
each, just a thumbnail and short description). However, unauthenticated or 
inactive users should not be able to access the product detail page (they 
can't make orders either, of course). Ideally this would only require 
toggling a setting such as SHOP_CHECKOUT_ACCOUNT_REQUIRED, but I don't 
think something like that exists. My questions are:

   1. Can this be done without modifying Cartridge views to check for user 
   auth? (Monkey patch solution)
   2. Would you (Steve) be open to adding a setting to control this 
   behavior in shop.views.product, just as shop.views.checkout_steps does now? 
   (Proper, long-term solution IMO)

What do you guys think? Do you see any other solution?

-- 
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/groups/opt_out.

[mezzanine-users] Re: Restricting shop to active users only

[Eduardo Rivas]

Ok, thanks. I'll give it a shot and report back.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Looking for Developer to create a site in mezzanine based on my current site

[Eduardo Rivas]

Hey Moltra. You may also be interested in using a platform built for hiring 
freelancers, like www.odesk.com. Bear in mind that the brief you provide 
and the rates you offer will determine the quality of the developer that 
will take your project.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Mezzanine 3.0.7 released

[Eduardo Rivas]

Hey Stephen, could you expand a little bit on "Improved support for custom 
user models"? 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/groups/opt_out.

[mezzanine-users] Re: Mezzanine 3.0.7 released

[Eduardo Rivas]

Oh, ok, I understand now. Thank you.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Looking for Developer to create a site in mezzanine based on my current site

[Eduardo Rivas]

Hmm, $20 a month for hosting seems a little expensive to me. You should 
take a look a Digital Ocean (VPS for $5/mo) or Webfaction (shared (managed) 
hosting for $9/mo). They are both great for hosting Django projects, and 
I'm sure others can also suggest low-priced alternatives.

-- 
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/groups/opt_out.

[mezzanine-users] Omitting empty fields from form email

[Eduardo Rivas]

Hello all. I've created some Mezzanine forms in the admin to capture user 
input and send it by email. I'm using some JS to hide form fields depending 
on what a user selects in one of the fields. In other words, fields are 
shown/hidden depending on conditions determined by the form itself while 
interacting with the user. As such, depending on what the user does, some 
fields will be left blank. I would like to have these blank fields not 
appear in the email report. Any ideas on how to achieve that?

Or going to an upper level, could you suggest an alternative approach? 
Maybe use multiple forms in one page?

-- 
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/groups/opt_out.

[mezzanine-users] Re: Mezzanine 3.0.8 released

[Eduardo Rivas]

Thanks to all contributors! Really excited to see vanilla Grappelli 
support. Already trying it out.

-- 
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/groups/opt_out.

[mezzanine-users] Re: serve media files on my local development server

[Eduardo Rivas]

As Stephen said, it is recommended you only use STATIC_ROOT to contain 
files rounded up by collectstatic when deploying. The directory "/static" 
is listed in .gitignore and .hgignore for this same reason. Just in case 
someone is wondering what to do with files that don't belong to any app, 
this is what I do:

   1. Create "assets/" (or whatever you want to name it) in your project 
   root. Dump your general purpose static resources there.
   2. In settings.py define STATICFILES_DIRS = (os.path.join(PROJECT_ROOT, 
   "assets"),). This will tell Django to see "assets/" as a valid location for 
   static files.
   3. Access your files in the templates. For example, "assets/style.css" 
   will be accessed by {% static "style.css" %}.

Just my two cents :)

-- 
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/groups/opt_out.

[mezzanine-users] Re: Omitting empty fields from form email

[Eduardo Rivas]

Thanks Josh! I ended up not needing this but your solution is definitely 
the way to go.

-- 
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/groups/opt_out.

[mezzanine-users] Why is PIL/Pillow not a dependency?

[Eduardo Rivas]

Hi everyone. Every time I try to create a new project with some initial 
data I run:

python manage.py createdb --noinput

Which fails with the following error:
django.core.exceptions.ImproperlyConfigured: Neither Pillow nor PIL could 
be imported: No module named Image

That is very explicit and simply requires running pip install pillow to get 
if fixed. However, my questions are: Why is pillow needed during the 
createdb process? How necessary is it to Mezzanine? Shouldn't it be a 
dependency? I don't know if I've found a bug, or maybe there's some obvious 
reason I'm overlooking.

-- 
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/groups/opt_out.

Re: [mezzanine-users] Why is PIL/Pillow not a dependency?

[Eduardo Rivas]

I tried it in a blank venv:

mkvirtualenv foobar

pip install mezzanine cartridge
...
Successfully installed mezzanine bleach requests-oauthlib django tzlocal 
future grappelli-safe filebrowser-safe requests six html5lib oauthlib 
pytz cartridge pisa


mezzanine-project -a cartridge foobar
cd foobar/
python manage.py createdb --noinput

And I get the same error as before. If I start the project with 
Mezzanine's default template (no -a cartridge option), I get another 
error from mezzanine_tags.py, but also related to Image.


Can you reproduce the steps? Is it something only in my end?

--
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/groups/opt_out.

Re: [mezzanine-users] Why is PIL/Pillow not a dependency?

[Eduardo Rivas]

I tried it without venvwrapper and still the same, no pillow when 
installing from pip.


virtualenv foobar
source foobar/bin/activate
pip install mezzanine

Could it be the version of virtualenv or the env's pip?
virtualenv --version
1.11.2
pip --version
pip 1.5.2 from foobar/local/lib/python2.7/site-packages (python 2.7)

BTW, the "--distribute" option has been deprecated. See the third list 
item here: 
http://www.virtualenv.org/en/latest/news.html?highlight=distribute#id5


--
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/groups/opt_out.

[mezzanine-users] Re: about the security of the shopping website using the mezzanine(cartridge) framework

[Eduardo Rivas]

Hi Lu. A good place to start is HTTPS. Make sure you get a valid SSL 
certificate and install it to your site. This ensures all communication 
between your site and users is encrypted. I will not go into details on how 
to get the certificate itself and enable HTTPS, but this page describes 
some specifics of Django: 
https://docs.djangoproject.com/en/dev/topics/security/#ssl-https. You will 
probably need additional info from your hosting provider too.

You may want to read the whole page as it explains how Django protects you 
from several forms of attack (clickjacking, cross-site reference forgery, 
SQL injection, etc). You've taken huge steps towards securing your site 
just by building it on Django/Mezzanine, but an SSL cert is a must! 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/groups/opt_out.

[mezzanine-users] Re: please recommend a host that would best suit a mezzanine/cartridge framework based shopping website

[Eduardo Rivas]

In case you'd like a VPS, you can go with Digital Ocean or Servermania, 
last time I checked they were less expensive than Webfaction, but the 
maintenance burden is on you.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Restricting shop to active users only

[Eduardo Rivas]

I investigated a little and apparently the login decorator is for views, 
not url patterns. I ended up using this little 
middlewarethat lets me conveniently 
define a list of url patterns for which login is 
required.

Related question: is it possible to hide products from the sitemap without 
needing to manually uncheck the "Show in sitemap" box in every existing and 
new product?

-- 
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/groups/opt_out.

[mezzanine-users] Re: Restricting shop to active users only

[Eduardo Rivas]

Excellent! I think that's what Steve meant from the beginning. Regarding 
the sitemap, I was overriding Mezzanine's sitemap and returning a 
Product-free list, but signals seem like the right way to go here. Thanks a 
lot.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Admin navigation

[Eduardo Rivas]

Wow guys, excellent work you've done here! It's amazing how different the 
admin looks with this tweaks. Now, I have a few questions:

   1. Would you be interested in using an alternate theme for TinyMCE? I've 
   been using this for several projects: 
   http://thebigreason.com/blog/2008/09/29/thebigreason-tinymce-skin. It only 
   involves dropping a folder into the TinyMCE files and changing a string in 
   tinymce_setup.js.
   2. Should we open a ticket to iron out the issues? The discussion is 
   alive and well here, but Github might be better for tracking progress and 
   referencing commits, etc.
   3. I'm running the latest master branch from github in Firefox on my 
   Linux box and a couple of issues are evident:
  1. The font being used throughout the admin is now the system's 
  default "sans-serif" font. It looks weird and huge, Arial looked better 
  IMO. Perhaps what we are looking for is a better font stack, like 
Helvetica 
  > Arial > sans-serif. That way we can get users in Mac, Linux and Windows 
  to get the same look.
  2. The scrollbar is always visible in the navigation pane.
   
I attach some screenshots to demonstrate the issues. I can contribute on 
all the issues above if you like :)



-- 
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/groups/opt_out.

[mezzanine-users] Re: Admin navigation

[Eduardo Rivas]

Ok, I've fixed the scrollbar, the font, and opened a new issue to track 
progress here: https://github.com/stephenmcd/mezzanine/pull/970.

I'm working on the collapse functionality right now, I'll keep you posted! 
:)

-- 
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/groups/opt_out.

[mezzanine-users] Re: Admin navigation

[Eduardo Rivas]

Wait a second, are menu sections supposed to be collapsible? Because that's 
not working for me in the official demo site or local dev server. Am I 
missing something? 

-- 
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/groups/opt_out.

[mezzanine-users] Re: Admin navigation

[Eduardo Rivas]

Sorry about the noise. I just noticed it depends on a setting.

-- 
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/groups/opt_out.

[mezzanine-users] Re: Admin navigation

[Eduardo Rivas]

But wait, there's more! :) I have something that narrow screen users will 
appreciate. The panel now can be hidden to give the content full width. 
Only problem is panel state won't persist between page loads. I'm thinking 
on adding a cookie to the session and check it to determine the panel 
state. Will be ready soon.

-- 
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/groups/opt_out.

[mezzanine-users] Re: step by step mezzanine deployment

[Eduardo Rivas]

Hi Federico. The DATABASE setting that is applied is the one in 
live_settings.py. In production, this file is renamed to local_settings.py 
by Fabric (the local_settings.py in your dev machine should NOT be in 
version control). You'll see at the end of settings.py that it imports 
everything from local_settings.py, thus overriding the DATABASE from 
settings.py.

-- 
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: Best way to show user-specific info?

[Eduardo Rivas]

Hi Niels. Quick question: have you given User Profiles a shot? You need to 
do two things: tell Mezzanine which model you want use as user profile with 
settings.AUTH_PROFILE_MODULE = "path.to.your.model" and secondly, enable 
user profiles with settings.ACCOUNTS_PROFILE_VIEWS_ENABLED = True. This 
will get all fields from your user profile plus the fields from the normal 
User object and give your users both a view-only public profile 
(/users/username) and an editable form to update their info 
(/accounts/update/). This page from Mezzanine's docs describes this 
approach http://mezzanine.jupo.org/docs/user-accounts.html.

If you'd rather continue with your current approach, you should make 
CustomerPage subclass Displayable and create your own views and url patters 
to fetch users by username or any key you like. This qualifies as "Non-page 
Content", more here: 
http://mezzanine.jupo.org/docs/content-architecture.html#non-page-content.

-- 
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: step by step mezzanine deployment

[Eduardo Rivas]

To he honest I don't know why the DATABASE setting is left in settings.py, 
it definitely can be confusing.

I believe the reason databases are not synced by the fabfile is because 
that's not a very common (or advised) operation. Most of the time 
developers want to keep production and development DBs completely 
separated. However, I can think of a few situations where this could be 
useful, and the general algorithm for a Fabric task would be:

   1. Run pg_dump in your dev machine, output to file.
   2. Upload file to the project folder in the server.
   3. (Optional) Backup current production DB.
   4. Run pg_restore in the server from the latest uploaded SQL dump.
   

-- 
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: step by step mezzanine deployment

[Eduardo Rivas]

That's great, Ken! Maybe you can share some of your tasks with Federico?

I've gone down the fixture path, and the two things I needed to get it 
working were:


1. Always use the --natural flag.
2. Don't do a huge, all-apps dump; rather specify the apps you wish to
   dump to the fixture. Off the top of my head, if you need all Page
   entries from the db: python manage.py dumpdata --natural pages forms
   galleries. Combine this with the fact that the fabfile creates the
   site and user objects for you, and it might be all you need to sync.

--
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] Cartridge: search by product SKU

[Eduardo Rivas]

Hi everybody. Quick question: is it possible to search Cartridge products 
by SKU? According to my tests, it isn't. Could you offer any pointers on 
what steps to take to make it work? 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] Cartridge: search by product SKU

[Eduardo Rivas]

Awesome! One more reason to look forward to the next Mezzanine release :-)

-- 
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: Cartridge: search by product SKU

[Eduardo Rivas]

I'm trying to try out the new features, but Github seems to be having some 
issues and I can't pull in the changes. Will try later.

Is there any release-blocking bug/feature we can help with?

-- 
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: Cartridge: search by product SKU

[Eduardo Rivas]

Ok, github is back to normal. And yes, we can now search through relations! 
However, the problem I'm seeing is that now searching by name returns one 
search result per variation. For example, searching for the name of a 
product with four variations returns four identical search results. Can you 
reproduce?

-- 
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: Cartridge: search by product SKU

[Eduardo Rivas]

Ha! When I saw the duplicate results I thought it would require some 
horrible queryset mess to fix it, turns out databases and Django do it out 
of the box. Thanks a lot Steve, Mezzanine is not only a great CMS but also 
an incredible learning platform.

-- 
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: How and where to create sitemap.xml and robot.txt

[Eduardo Rivas]

Well that's a new one for me! I know sitemaps are automatically generated 
from Displayable instances, but never knew robots.txt was being inserted in 
production. It's weird, my sites return a 404 when I look for robots.txt. 
May I suggest we provide an option to modify robots.txt from the Site 
settings? That'd be pretty handy.

-- 
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: How and where to create sitemap.xml and robot.txt

[Eduardo Rivas]

Ah! There it is! I'm not using the default Nginx config. Thanks a lot.

--
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] 404 errors and multilingual installations

[Eduardo Rivas]

Hello everyone. I've been seeing a strange behavior with 404 error pages 
recently. To reproduce:

   1. Enable localization (settings.i18n = True).
   2. Define a few values in LANGUAGES.
   3. Make sure you're reporting your preferred browser language as other 
   than the site default.
   4. Visit a page that doesn't exist.
   
You can actually check this in the demo site. Visit this non-existent url 
(or any other): http://mezzanine.jupo.org/blog/foobar/. In my browser set 
to Mexican Spanish, I get redirected immediately to 
http://mezzanine.jupo.org/es-mx/blog/foobar. Notice the site has rewritten 
the url to include the lang code. It's like the 404 page is under i18n 
patterns. This is annoying because when I get 404 errors in my production 
site they actually happen twice: first when /blog/foobar raises 404, and 
then when the redirect to es-mx/blog/foobar raises another 404. Any idea 
why this might 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.

[mezzanine-users] Re: 404 errors and multilingual installations

[Eduardo Rivas]

Apparently Django does this in LocaleMiddleware when it finds 404 error 
codes in the response. No idea why. 
https://github.com/django/django/blob/master/django/middleware/locale.py#L48-L51

-- 
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: Marking Django Application Pages as Active in the Navigation

[Eduardo Rivas]

The blog app defines it's own url patterns. For example, the list view 
(showing all blog posts) is mapped to /blog by default. The trick is in 
creating a page in the admin with the exact same slug. You have to do this 
to get Mezzanine to insert the page variable into your context. In the end, 
Mezzanine will merge both the context provided by the page and the context 
of your own application.

I've done this in the past with a custom Portfolio app and the integration 
is seamless. If you want to inspect your template context, list of 
templates and other useful debugging info in your browser, you should use 
Django Debug Toolbar. Install it with pip install django-debug-tollbar, 
Mezzanine will activate it automatically when it detects it's installed; 
you should then get a small button in the top-right corner of your site 
when running in the development server.

-- 
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] Task List: Test that need to be written

[Eduardo Rivas]

Hello everyone. I've setup a task 
listof tests that need to 
be written for Mezzanine. If you can think of any 
feature that needs to be protected from unintentional breaking, please 
comment on the issue (or here) to have it added to the list, or contribute 
the test itself! Hopefully this will make Mezzanine more robust and stable 
from one release to the other. It will also create a centralized space for 
new contributors to tackle issues. Looking forward to listening at your 
ideas.

The link again: https://github.com/stephenmcd/mezzanine/issues/1012

-- 
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: Something wrong with default theme?

[Eduardo Rivas]

Hi Niels. Could you please elaborate on what you mean with "the header is 
hidden"? Mezzanine uses Bootstrap 3 to theme the frontend, and is 
configured to collapse the navigation on small screens, creating a new 
button where you can toggle the navigation. Additionally, the site tagline 
(the string that says: "An open-source content management system") is 
hidden in narrow screens, but the site title is always kept visible.

You can learn more about Bootstrap, and specifically about the grid options 
and breakpoints at: http://getbootstrap.com/css/#grid-options

-- 
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: Something wrong with default theme?

[Eduardo Rivas]

Well, I wouldn't call it a bug, it is just a limitation of Bootstrap not 
knowing how wide your navbar needs to be. From 
http://getbootstrap.com/components/#navbar:

Since Bootstrap doesn't know how much space the content in your navbar 
> needs, you might run into issues with content wrapping into a second row.


That's exactly what's happening here. It's up to the developer to provide 
for cases such as this. You can check out the linked document for some 
potential fixes, or come up with your own. If you know your navbar will 
always be too wide to fit in a single row, just add "body {padding-top: 
100px;}" to your site's CSS (default padding-top is 50px). A more robust 
approach would require media queries to add  the extra padding, or some 
Javascript that computes the body padding based on navbar height on every 
window resize event. Note sure if Steve would like to add something like 
that to the core.

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

I've really been looking forward to this one. Hopefully I will have time to 
try it out with the development version of some sites that currently use 
alternative translation approaches.

Are we going to translate urls at all? Django gives two possible choices: 
mark the url patterns for translation, or use i18n patterns to prefix the 
whole site's urls with a lang code (what the Admin currently does). Is 
Mezzanine going to favor any particular approach? 

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Mathias, if you've upgraded from pre 3.1.1 make sure you have USE_L10N = 
True in your settings module. I fell for that too after upgrading but 
Stephen cleared it up.

-- 
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] Cartridge: All pages are available as Product Categories

[Eduardo Rivas]

Hello! I'm developing a site with Cartridge and I've noticed that all Pages 
in my page tree appear as valid categories for a Product. See the attached 
screenshot. The expected outcome is that only those Pages that start with 
"Collections" should be selectable as Categories for a Product (as they are 
the only ones of type "Product Category"). Home, Contact Us and all others 
shouldn't appear as Available product categories. Any ideas on how to fix 
this? It doesn't seem to be happening in the demo site.



-- 
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: Cartridge: All pages are available as Product Categories

[Eduardo Rivas]

I checked out the DB and the "content_model" of those pages is not 
"category", but rather "richtextpage", "form" or "link", as expected. 
However, the table "shop_category" did have some demo categories with ids 
matching those of the pages in question. I will test later if deleting 
Product Categories from the Page admin is leaving orphan entries in the 
category DB table. Hopefully this has only been a really weird fluke :P

-- 
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] Cartridge: Applying sales to a Product Category

[Eduardo Rivas]

As I understand, Sales can be applied either to individual Products, or to 
whole Categories. However, there's something about Category-wide Sales that 
confuses me. If you create a Sale from the Sales admin and apply it to a 
Category, the changes are ignored until you go to the Page admin and 
manually attach the Sale to a Category instance. Is this the intended 
behavior? I would like to let staff members create Sales, but without 
giving them access to editing Product Categories. It seems it's currently 
not possible to do so.

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Ok, I finally got some time to try this out. I've never used Model 
Transaltion, so maybe I'm making some noob mistake. This is what I've done:

mkvirtualenv modeltranslation
git clone https://github.com/Kniyl/mezzanine.git mt-mezzanine
cd mt-mezzanine
pip install -e .
pip install south django-modeltranslation django-debug-toolbar
# cd to other folder
mezzanine-project mt_test
# Edit settings.py. Add USE_I18N = True, USE_L10N = True, add entries to 
LANGUAGES
python manage.py createdb --noinput

At this point, createdb fails with the following error: 
modeltranslation.translator.NotRegistered: The model "RichTextPage" is not 
registered for translation. See full traceback
.

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Just before running createdb, one has to "cd mt_test", of course.

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Yep, that's it. Removing debug toolbar fixes it.

I'll continue testing and reporting back anything I find. Thanks a lot for 
this!

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Thanks Mathias, it is working now. I've used the site a little bit more and 
my first impressions are that translation is working like a charm! I've 
only found some minor issues/implementation details:


   1. Form submit button is not being translated.
   2. How do frontend users change the language? Perhaps we need a dropdown 
   similar to the one in the admin for the public site.
   3. Are keywords going to be translated? Not sure if this is just a 
   matter of registering the Keywords field for translation.
   4. Slugs are generated from the active language, not the default 
   language. This only applies to new items which have their Title set in more 
   than one language. For example, let's say we are logged into the admin in 
   Spanish (default is English), and we have a new Page, and fill the Title 
   with "Hello world!" (English) and "¡Hola mundo!" (Spanish). The Page will 
   get the Slug "hola-mundo" instead of "hello-world".
   5. Site tagline and site title; should they be made translatable?

-- 
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

[Eduardo Rivas]

Sorry, I didn't understand your explanation on point 1. Could you 
elaborate a little bit more? The issue I was describing is that the 
Submit button is not showing the active language text in the form, but 
rather the default language value.


About number 2, I actually had this working a while back using Django's 
set_language 
 
view. I created a gist 
 with some code 
that can go directly into base.html or (even better) in a small template 
in includes/. Please note that settings.USE_I18N must be included in 
TEMPLATE_ACCESSIBLE_SETTINGS.


Finally, the reason I brought up #5 was because some Settings are indeed 
model instances stored in the database. See: 
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/conf/models.py. 
However, they are a special case, as we wouldn't want to translate all 
Settings instances. It would be good to include it in the ToDo just to 
keep it in mind.


--
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

[Eduardo Rivas]

Aaaahh, I get what you mean for #1, and yes, changing the value in 
non-default languages to something other than the direct translation of 
"Submit" fixes it.


#2 and #4 look like they've been fixed, thanks a lot.

#5 is looking pretty great. However, I don't thinks SHOP_CURRENCY_LOCALE 
should be translatable, since it is not editable, and non-editable 
settings don't have DB entries (I think). The other problem I see is 
that users will have to run "python manage.py schemamigration conf 
--auto" every time they add a new language. Also, these migrations seem 
to be stored in Mezzanine's source so they might be a problem for 
upgrades and deployment. At least that's what I had to do to get rid of 
a "column does not exist" error. Am I missing something?


--
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] LANGUAGE_CODE in URL problem "/en-us/admin/"

[Eduardo Rivas]

Hi! This is Mezzanine using i18n_patterns in the admin. If you're building a 
multilingual site, you can enable a language selector in the admin by doing 
USE_I18N = True and USE_L10N = True in your settings.py. You also need to 
populate the LANGUAGES tuple with the languages you wish to enable. 

If you want your site to use one language, set it in LANGUAGE_CODE and disable 
the prior settings. 

-- 
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: editable.css not styling on production server

[Eduardo Rivas]

Have you collected your static files? Make sure you run collectstatic on 
every deployment, and all Mezzanine resources will be made available for 
production.

-- 
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: editable.css not styling on production server

[Eduardo Rivas]

Actually, the CACHE directory and the files with random letters and numbers 
are created by Django Compressor (via the {% compress %} template tag). It 
bundles all your static assets and serves them in a single file to avoid 
multiple HTTP requests. You might want to disable it to get your files 
served individually and check if editable.css has actually been picked up 
by collecstatic.

Another option is to check your static directory in production and manually 
verify that editable.css exists 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.

[mezzanine-users] Re: modeltranslations - round 2

[Eduardo Rivas]

I've ran into similar situations with ugettext and ugettext_lazy. For 
example, when defining model methods to be called in the Django Admin, 
plain ugettext works better. The official docs recommend using the lazy 
option when dealing with most things model-related 
(https://docs.djangoproject.com/en/1.6/topics/i18n/translation/#lazy-translations).

My approach is to use ugettext_lazy by default in most of the backend, and 
use ugettext when problems like this arise. I don't think we should move 
everything to plain ugettext.

PS: Looking forward to reading what Steve has to say on all progress 
Mathias has made in this front.

-- 
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

[Eduardo Rivas]

Oops, I forgot to share the link to the task list:
https://github.com/stephenmcd/mezzanine/issues/1012


2014-05-19 19:10 GMT-06:00 Eduardo Rivas :

> Hey Mathias, a couple of points here. First, do you plan on working on the
> admin controls for toggling the different translations fields? I'm asking
> because I'll have some free time in the coming weeks, but I don't want to
> jump into it if you're planning on doing it yourself.
>
> Secondly, I wanted to share with you that recently an effort has started
> to improve Mezzanine's test coverage. It'd be great if you could write some
> tests for the features you've contributed; but if you're short on time,
> just coming up with a list of pending tests for model translation will be
> of great help. You can share it with me or Steve and they'll be added to
> the task list. Thanks a lot!
>
>
> 2014-05-19 10:04 GMT-06:00 Mathias Ettinger :
>
> I read a bit on ugettext and ugettext_lazy and I agree that we should not
>> move everything to plain ugettext. Using ugettext for the default value
>> seems perfectly acceptable though. Since pregenerated content into the
>> database is populated using the default language translation, it is exactly
>> the same behavior. And django-modeltranslation will copy value based on
>> that translation anyway. (./manage.py update_translation_fields)
>>
>> I found the time to make a last change to the settings admin page. It’s
>> far from perfect, I have an idea on how to make it more like pages with
>> every fields exposed but not much time for that. And at least it’s better
>> than nothing.
>>
>> --
>> 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/VXVfCU8OFGk/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.

Re: [mezzanine-users] Re: modeltranslations - round 2

[Eduardo Rivas]

Hey Mathias, a couple of points here. First, do you plan on working on the
admin controls for toggling the different translations fields? I'm asking
because I'll have some free time in the coming weeks, but I don't want to
jump into it if you're planning on doing it yourself.

Secondly, I wanted to share with you that recently an effort has started to
improve Mezzanine's test coverage. It'd be great if you could write some
tests for the features you've contributed; but if you're short on time,
just coming up with a list of pending tests for model translation will be
of great help. You can share it with me or Steve and they'll be added to
the task list. Thanks a lot!


2014-05-19 10:04 GMT-06:00 Mathias Ettinger :

> I read a bit on ugettext and ugettext_lazy and I agree that we should not
> move everything to plain ugettext. Using ugettext for the default value
> seems perfectly acceptable though. Since pregenerated content into the
> database is populated using the default language translation, it is exactly
> the same behavior. And django-modeltranslation will copy value based on
> that translation anyway. (./manage.py update_translation_fields)
>
> I found the time to make a last change to the settings admin page. It’s
> far from perfect, I have an idea on how to make it more like pages with
> every fields exposed but not much time for that. And at least it’s better
> than nothing.
>
> --
> 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/VXVfCU8OFGk/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.

Re: [mezzanine-users] Re: modeltranslations - round 2

[Eduardo Rivas]

Great! Hopefully your commits will be merged soon and I'll work over that.

--
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

[Eduardo Rivas]

I should have read the whole Stack Overflow thread! It looks like Django
has built in ways of doing it.
https://docs.djangoproject.com/en/1.6/topics/testing/tools/#overriding-settings

-- 
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

[Eduardo Rivas]

I think you can access the settings module like every other place in the code 
base. This example recommends the setup and teardown methods for modifying 
settings in unit tests: http://stackoverflow.com/a/913596. Hope that helps :-) 

-- 
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: Mobile site menu

[Eduardo Rivas]

Hi Paullo. There are a few things that might be useful to know regarding 
mezzanine.mobile. First off, "vanilla" Mezzanine (without mezzanine.mobile) 
is responsive because it's based on Bootstrap 3, which provides a wide 
variety of responsive utilities. This means you will get a mobile menu and 
page layout without activating mezzanine.mobile.

So, what's the use of mezzanine.mobile, you may ask. Well, mezzanine.mobile 
allows the server to respond to mobile users with custom templates (or any 
other custom logic, for that matter). The difference is that 
mezzanine.mobile serves completely different and independent HTML 
templates, while Bootstrap takes your standard HTML template and adapts it 
to mobile devices with CSS and Javascript.

Depending on your application, you will want to go with one approach or the 
other. My advice for newcomers: leave mezzanine.mobile off and use 
Bootstrap for your responsive needs, it will suffice most of the 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.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Re: modeltranslations - round 2

[Eduardo Rivas]

Hey everybody. I've been trying out Mathias master branch and everything is 
working smoothly. As I said, I'm also exploring ways to enable toggling 
translation fields in the Admin. Turns out Model Translation (MT) provides 
two admin classes (docs 
)
 
to include the required static resources for this purpose: 
TabbedTranslationAdmin 
and TabbedExternalJqueryTranslationAdmin. The first one seems to fail as it 
uses Django's jQuery, but the second one works as expected (though it looks 
kinda ugly in Grappelli) by using external jQuery resources.

I have a couple of questions at this point:

   1. Should we use these classes or create our own (considering Mezzanine 
   already includes jQuery and jQuery UI)?
   2. Should we create a toggle for each field (as MT does), or just a 
   "global" toggle to hide/show all fields of a specified language? I favor 
   the second option, as giving each field it's own toggle seems overly messy 
   and confusing for the end user.

Hope to hear from you soon. BTW, if you want to try out MT's default 
implementation, simply replace all occurrences of TranslationAdmin with 
TabbedExternalJqueryTranslationAdmin 
in mezzanine.core.admin.

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Odd, I just created a project without issue. This is my venv:

Django==1.6.5
Mezzanine==3.1.3 #From Mathias' branch
Pillow==2.4.0
South==0.8.4
argparse==1.2.1
bleach==1.4
django-debug-toolbar==1.2.1
django-modeltranslation==0.7.3
filebrowser-safe==0.3.3
future==0.9.0
grappelli-safe==0.3.10
html5lib==0.999
oauthlib==0.6.1
psycopg2==2.5.3
pytz==2014.4
requests==2.3.0
requests-oauthlib==0.4.0
six==1.6.1
sqlparse==0.1.11
tzlocal==1.0
wsgiref==0.1.2

I ran mezzanine-project and createdb --noinput. Have you done any other 
changes to settings?

-- 
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: Mezzanine 3.1.5 and Cartridge 0.9.4 released

[Eduardo Rivas]

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

[Eduardo Rivas]

Ah, I see. That's a clever way to integrate thumbnails into the Rich 
Text field. 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.

[mezzanine-users] Fabric file and related resources for deploying Mezzanine to Webfaction

[Eduardo Rivas]

Hello everyone! Since I started with Mezzanine/Django I've been deploying 
my sites to Webfaction  
(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 
 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.

[mezzanine-users] Re: Fabric file and related resources for deploying Mezzanine to Webfaction

[Eduardo Rivas]

Thanks for the interest guys. Ibn, I recommend you take a look at the 
Webfaction docs and read the fabfile to have an idea of what it does. Some 
knowledge of Postgres and Git will also be useful. Finally, when you 
deploy, keep in mind many settings have default values in fabsettings.py, 
so just comment out any particular setting to use the default. This will 
maintain the settings you actually need to touch to a minimum.

-- 
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: Fabric file and related resources for deploying Mezzanine to Webfaction

[Eduardo Rivas]

Well, a Webfaction account is essentially a VPS with limited permissions 
and a bunch of stuff preinstalled, so what you can do with it depends on 
how well you use your RAM, bandwidth and disk space. A good thing about 
Webfaction is that the database server (Postrges or MySQL) and Nginx server 
don't add up to your total consumption, as they are shared by all accounts 
on a machine. Add to this that you can run memcached to lessen the burden 
of your app and something like Cloudflare as a CDN and your possibilities 
expand. Mezzanine-Webf does all these things (except for Cloudflare, that's 
handled at DNS level).

-- 
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: Fabric file and related resources for deploying Mezzanine to Webfaction

[Eduardo Rivas]

I couldn't tell. Webfaction is the only hosting provider I've used so 
far.


--
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: Mezzanine 3.1.6 released

[Eduardo Rivas]

Just saw 3.1.7 got pushed to PiPy. Any news on that? :)

-- 
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.6 released

[Eduardo Rivas]

Great, thank you.

-- 
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: Django Compressor does not minify files

[Eduardo Rivas]

Hey Luigi. By default, Django Compressor will simply concatenate (join) 
your static files. This is good because it will save HTTP requests to your 
site, and your visitors will get all your static files in one request 
(instead of many). If you also want to minify your files (remove whitespace 
and newlines, mostly), you need to define the following setting (for CSS 
files):

COMPRESS_CSS_FILTERS = 
['compressor.filters.css_default.CssAbsoluteFilter',  
'compressor.filters.cssmin.CSSMinFilter']

This will get your CSS files minified. You can do fancier stuff like 
compile LESS files and minify JS, but that'd require other dependencies and 
configuring other settings related to binary file locations and more. The 
docs go in great detail about this: 
http://django-compressor.readthedocs.org/en/latest/settings/#backend-settings

-- 
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: Email confirmation for admin-created users?

[Eduardo Rivas]

Hi Matt. Mezzanine supports user access control in a "self-service" 
configuration that might be useful for you. You can have your users request 
an account (fill in their details and password), but they will not be 
granted access to the site (they can't log in) until an authorized member 
clears their request. You can define a list of email addresses that will be 
notified when new users request accounts. This way you don't have to 
manually enter every user's details, but you still have complete control 
over all of them. If you grant permission to a user, he/she will get an 
email notification to let them now they can use the site (complete with a 
log in link).

This requires you set ACCOUNTS_APPROVAL_REQUIRED = True in settings.py. 
Then you have to configure the emails that will be notified on new account 
requests in the Settings section of the Admin interface. The setting is 
called "Account approval email addresses" under the "Miscellaneous" section.

To approve a new user, simply login to the Admin site (you need to have 
permission to change User objects), look for the user in question (you'll 
receive a direct link with the notification email), and check the "Active" 
box, then Save. This will notify the new user and let them log in to your 
site.

I've been using this method for an online store I'm working in where only 
registered users can order products, and we want to screen them all. Hope 
that helps.

-- 
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: Email confirmation for admin-created users?

[Eduardo Rivas]

Also, my explanation is really just a rephrasing of what you can find in 
the official docs: 
http://mezzanine.jupo.org/docs/user-accounts.html#account-approval. In that 
page you'll also find info about the more traditional "Click here to verify 
your account" approach, and details on Mezzanine's implementation of user 
accounts, which is pretty flexible and capable out of the box.

Lastly, remember you must have your email settings set correctly to be able 
to send notifications to your users and yourself. For example, you can use 
a Gmail account:
EMAIL_HOST_USER = 'exam...@gmail.com'
EMAIL_USE_TLS = True
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_HOST_PASSWORD = 'GmailPassword'
EMAIL_PORT = 587
SERVER_EMAIL = EMAIL_HOST_USER

These go into settings.py and you only need to change your gmail address 
and password. Of course, other SMTP servers will work fine with their own 
settings.

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Hi Paul. It seems like you sorted out the issue you were linking too. Are 
there any others?

I finally found some time to come back to this, and noticed the front-end 
language selector is gone. The problem is in the condition for rendering the 
template 
,
 
as settings.USE_MODELTRANSLATION won't be available in the template context 
unless explicitly added to TEMPLATE_ACCESSIBLE_SETTINGS, thus, it always 
returns False and the template is never rendered. Relevant page 

 
in the official docs.

While we are at this, I'm unsure how contributions to forks work. It seems 
I cannot make pull requests to Mathias' fork. Maybe because it has never 
been merged into Steve's repo (the "upstream" repo)? Anyways, I've made the 
necessary edits here 
,
 
guess you'll have to manually copy it to your repo, Mathias. I'm not sure 
if core.defaults is the best place to put this, let me know what you guys 
think.

-- 
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: modeltranslations - round 2

[Eduardo Rivas]

Yeah, I've got the pull request ready, but the dropdown on which you select 
the repo you want to compare your changes with won't list Mathias' fork of 
Mezzanine.

-- 
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] Let's translate the official docs!

[Eduardo Rivas]

Hello everyone. I've been speaking with another member of the 
Spanish-speaking Mezzanine community (Jesús Anaya) and he came up with 
several ideas to boost Mezzanine's popularity in said language, one of 
which is translating the official docs. Of course, this opens the gates for 
other languages too and I believe it'll mark a milestone for Mezzanine as a 
project.

My questions are:

   - Are there other developers in other languages interested in 
   translating the docs?
   - How should we do this? Separate repos? PRs to Steve's repo?
   
Any advice in documentation-writing in general is welcome :) 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.

[mezzanine-users] Re: Let's translate the official docs!

[Eduardo Rivas]

I don't have experience with Sphinx, but I found this 
. Apparently you can generate translation 
catalogs in gettext, so we could use Transifex as we already do with 
Mezzanine. Here is a blogpost 

 
with a quick overview of the process and some scripts for automating the 
process of generating the files.

-- 
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: Let's translate the official docs!

[Eduardo Rivas]

Thanks a lot Steve for setting everything up! I'll give it a shot as 
soon as I can.


--
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: deployment issue --- gunicorn

[Eduardo Rivas]

Hello everyone. I created a fabfile that deploys Mezzanine sites to 
Webfaction. It is not a drop-in replacement for the one provided with 
Mezzanine (I'm planning on releasing one since I've moved to hosting my 
sites on a VPS). Anyways, the point is that I've managed to drop 
gunicorn_django (since it's deprecated) and use vanilla gunicorn. Maybe it 
will help people having trouble 
https://github.com/jerivas/mezzanine-webf/blob/master/deploy/supervisorctl.conf#L2.

-- 
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: Let's translate the official docs!

[Eduardo Rivas]

Ok, so I got some free time and started working on this. I have now 
generated all the .po files and completely translated one of them. I 
created a pull request  
for Steve and others to see how it's coming. What are the next steps after 
translating the .po files? How can I build and test the docs locally?

-- 
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: Let's translate the official docs!

[Eduardo Rivas]

By the way, the page I've translated so far is "Admin Customization".


2014-08-21 4:44 GMT-06:00 Stephen McDonald :

> Awesome! I'll try and work out how to build html from that shortly.
>
>
> On Thu, Aug 21, 2014 at 9:47 AM, Eduardo Rivas 
> wrote:
>
>> Ok, so I got some free time and started working on this. I have now
>> generated all the .po files and completely translated one of them. I
>> created a pull request
>> <https://github.com/stephenmcd/mezzanine/pull/1101> for Steve and others
>> to see how it's coming. What are the next steps after translating the .po
>> files? How can I build and test the docs locally?
>>
>> --
>> 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/4o104Uohg2E/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.

[mezzanine-users] Re: Django 1.7 support

[Eduardo Rivas]

Hey, so Django 1.7 has just been officially released. From what I gather 
from the GitHub issue linked by Steve, all works fine in Mezzanine. I 
wanted to ask how are migrations going to work now. Since we are supporting 
Django 1.5 and 1.6, does that mean we will support both South and the new 
built-in migrations? Also, is Mezzanine making use of the new App loading 
features?

For a quick overview of what's new in Django 1.7: official announcement 
.

-- 
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

[Eduardo Rivas]

Just noticed Django supports having both types of migrations coexist. 
Apparently all that needs to be done is renaming migrations to 
south_migrations. 
https://docs.djangoproject.com/en/1.7/topics/migrations/#libraries-third-party-apps


--
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: Django 1.7 support

[Eduardo Rivas]

Thanks for your answer, Thomas. I'll try to migrate some of my sites to 1.7 
and report back how it goes.

-- 
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: Django 1.7 support

[Eduardo Rivas]

Hey Stephen, I tried the latest version of Mezzanine with one of my sites 
and all went smoothly. It just required following Django's instructions 

 
for the new built-in migrations. After that, the database was up to date 
with Mezzanine's models and my own.

-- 
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: Django 1.7 support

[Eduardo Rivas]

Just to clarify, I followed Django's instructions in my own project, didn't 
have to touch Mezzanine at all.

-- 
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: Can I use django-bootstrap-themes in Mezzanine?

[Eduardo Rivas]

At the end of the day, theming a Mezzanine/Django site is a matter of 
loading the correct scripts and stylesheets. It seems like 
django-bootstrap-themes uses some custom template tags to do so. The demo 
website (http://mezzanine.jupo.org/blog/) used to have a theme-switching 
widget, perhaps Steve can share how it's done.

-- 
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

[Eduardo Rivas]

Currently only the development version. You'll need to clone from the repo
to get Django 1.7 support.

-- 
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: About deployment with fabric

[Eduardo Rivas]

I did a quick test and commenting line 2 works alright.

-- 
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: Multilanguage support

[Eduardo Rivas]

The work that needs to be done is mostly on the Admin side, I would say the 
actual translation of models is pretty much done. If you are in urgent need 
I suggest you merge this branch 
(https://github.com/stephenmcd/mezzanine/pull/1019) into the latest version 
of Mezzanine. Be wary since a few months have passed since changes were 
last made. I believe this is the most in-depth log of all the work that has 
been done: 
https://groups.google.com/forum/#!topic/mezzanine-users/VXVfCU8OFGk

-- 
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] Time to upgrade jQuery?

[Eduardo Rivas]

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 
]. 
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 ). 
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.

Re: [mezzanine-users] Time to upgrade jQuery?

[Eduardo Rivas]

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 :

> 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 
> 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.

[mezzanine-users] Re: Child pages for page

[Eduardo Rivas]

>From skimming the docs, it seems settings.ADD_PAGE_ORDER can help you 
define which subtypes of Page are allowed in the dropdown. Give it a try. 
http://mezzanine.jupo.org/docs/configuration.html#add-page-order

-- 
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.