Re: [mezzanine-users] first steps with fabric deployment
Hi, I have just deployed my first Mezzanine project and I agree with what you say: the deployment was clearly the most difficult part. I used fabric too, but it's not very easy but once it works it really saves you a lot of time. I have the feeling that when a step goes wrong in fab deploy, it begins to do strange things. So, instead running fab all, I run: * fab install * fab create * fab deploy When one of these failed, I looked in the fabfile and copy/paste in a terminal to see where it failed. Step by step I managed to make it works. Hope it helps. ++ On Tuesday, February 25, 2014 3:34:00 AM UTC+1, Federico Bruni wrote: > > 2014-02-23 20:24 GMT+01:00 Ken Bolton >: > >> You might have luck with the Django's dumpdata and loaddata management >> commands. Alternatively, django-extensions has a dumpscript command that >> may work. >> > > Ok, I've used dumpdata and loaddata to move from sqlite to postgresql. > Now I'm still trying to make fabric work. I'm not that far away.. Now I > have the project folder copied inside the virtualenv, the postgresql > database on the server is set. > I've launched 'fab all', which _should_ have installed all the needed > packages. Then I launch 'fab deploy' and I get this error: > > File "", line 1, in > [xxx.xxx.xxx.xxx] out: ImportError: No module named django.conf > [xxx.xxx.xxx.xxx] out: > > I see that the virtualenv doesn't have any django package. fab failed? I > guess it was supposed to install also the pypi packages according to the > requirements file. In my settings.py the path is defined correctly: > "REQUIREMENTS_PATH": "requirements.txt" > > Anyway, I decided to do it manually on the server. > But I'm still far away from the end and tons of questions on how to make > the deploy. Now I have just 4 hours to sleep. > > I thought that deploying was the easier part. I was really wrong! > > -- 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: FileSystemEncodingChanged exceptions
+10 on this comment - spent most of a day setting LC_* to en_US.UTF-8 all
over the place, didn't help. Deleted
./static/media/uploads/gallery/Ávila, Spain.jpg
./static/media/uploads/gallery/Düsseldorf, Germany.jpg
./static/media/uploads/gallery/.thumbnails/Ávila, Spain-60x60.jpg
./static/media/uploads/gallery/.thumbnails/Düsseldorf, Germany-60x60.jpg
and all worked again. Note that the system always worked on the Python 3.3
dev. environment, the problem with the above was on the Python 2.7 deploy
environment.
Thanks Bartosz!
On Wednesday, September 18, 2013 3:17:26 PM UTC-5, Bartosz Wiklak wrote:
>
> I had similar problem, but I wasn't using supervisor. A file name in
> /media/uploads/gallery has strange character encoding (the folder contains
> jspeg Austin, Athens, Amsterdam ...), I wasn't uploading anything there,
> suppose this files are uploaded by mezzanine. My locale is pl_PL.UTF8.
> The exception description is a little bit misleading.
>
> On Sunday, November 25, 2012 10:51:38 PM UTC+1, Doug Evenhouse wrote:
>>
>> I'm spinning my wheels a bit with an FileSystemEncodingChanged exception
>> that is thrown whenever I try to browse media files. I was happily
>> uploading images and all was well for awhile. Now I cannot open the file
>> browser at all without this exception being thrown. I don't believe I have
>> created any folders nor uploaded any files with unusual encoding or names.
>> As far as I can nothing would have changed with regard to locale settings.
>> I removed the entire project and recreated it to no avail. The exceptions
>> occur on both a staging server and a production server running Ubuntu
>> 12.04, and deployed using vanilla fabric settings with Mezzanine 1.2.4.
>> LC_ALL appears to be set correctly to "en_US.UTF-8".
>>
>> Anyone have advice as to possible root causes and/or troubleshooting
>> steps to take?
>>
>> Traceback and request settings from the exception email - this is running
>> on our internal staging server):
>>
>> File
>> "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/site-packages/django/core/handlers/base.py",
>>
>> line 105, in get_response
>> response = middleware_method(request, callback, callback_args,
>> callback_kwargs)
>>
>> File
>> "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/site-packages/mezzanine/pages/middleware.py",
>>
>> line 45, in process_view
>> return view_func(request, *view_args, **view_kwargs)
>>
>> File
>> "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/site-packages/django/contrib/admin/views/decorators.py",
>>
>> line 16, in _checklogin
>> return view_func(request, *args, **kwargs)
>>
>> File
>> "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/site-packages/django/views/decorators/cache.py",
>>
>> line 89, in _wrapped_view_func
>> response = view_func(request, *args, **kwargs)
>>
>> File
>> "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/site-packages/filebrowser_safe/views.py",
>>
>> line 116, in browse
>> elif fileobject.filetype == 'Folder' and fileobject.is_empty:
>>
>> File
>> "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/site-packages/filebrowser_safe/base.py",
>>
>> line 134, in _is_empty
>> raise FileSystemEncodingChanged()
>>
>> FileSystemEncodingChanged: Access was attempted on a file that contains
>> unicode characters in its path, but somehow the current locale does not
>> support utf-8. You may need to set 'LC_ALL' to a correct value, eg:
>> 'en_US.UTF-8'.
>>
>>
>> > path:/admin/media-library/browse/,
>> GET:,
>> POST:,
>> COOKIES:{'__utma':
>> '74311563.372776308.1351892605.1351898182.1351966440.4',
>> '__utmz':
>> '74311563.1351892605.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)',
>> 'csrftoken': 'l754gpeXgo6WrMKmH5gQ0UpsG96acn41',
>> 'messages': '
>> 81375d9cdb262e44aff2f71e2a66e74c9742ea2a$[["__json_message",40,"The
>> requested Folder does not exist."]]',
>> 'mezzanine-admin-toolbar': '',
>> 'sessionid': '4fbd7d0d1511a2c157fe2bdc60aed3cf'},
>> META:{'CSRF_COOKIE': 'l754gpeXgo6WrMKmH5gQ0UpsG96acn41',
>> 'HTTP_ACCEPT':
>> 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8',
>> 'HTTP_ACCEPT_CHARSET': 'ISO-8859-1,utf-8;q=0.7,*;q=0.3',
>> 'HTTP_ACCEPT_ENCODING': 'gzip,deflate,sdch',
>> 'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.8',
>> 'HTTP_CONNECTION': 'close',
>> 'HTTP_COOKIE':
>> '__utma=74311563.372776308.1351892605.1351898182.1351966440.4;
>> __utmz=74311563.1351892605.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
>>
>> sessionid=4fbd7d0d1511a2c157fe2bdc60aed3cf; mezzanine-admin-toolbar=;
>> csrftoken=l754gpeXgo6WrMKmH5gQ0UpsG96acn41;
>> messages="81375d9cdb262e44aff2f71e2a66e74c9742ea2a$[[\\"__json_message\\"\\05440\\054\\"The
>>
>> requested Folder does not exist.\\"]]"',
>> 'HTTP_HOST': 'hccs-website.evenhouseconsulting.local',
>> 'HTTP_REFERER': '
>> http://hccs-website.evenhouseconsulting.local/admin/people/person/add/',
>> 'HT
Re: [mezzanine-users] Re: FileSystemEncodingChanged exceptions
Hi Terry,
If you look at the fabfile.py,
https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L339-L354,
you can see how the system should be configured to handle the demonstrative
gallery images included in Mezzanine.
hth,
ken
On Tue, Feb 25, 2014 at 11:54 AM, Terry Brown wrote:
> +10 on this comment - spent most of a day setting LC_* to en_US.UTF-8 all
> over the place, didn't help. Deleted
>
> ./static/media/uploads/gallery/Ávila, Spain.jpg
> ./static/media/uploads/gallery/Düsseldorf, Germany.jpg
> ./static/media/uploads/gallery/.thumbnails/Ávila, Spain-60x60.jpg
> ./static/media/uploads/gallery/.thumbnails/Düsseldorf, Germany-60x60.jpg
>
> and all worked again. Note that the system always worked on the Python
> 3.3 dev. environment, the problem with the above was on the Python 2.7
> deploy environment.
>
> Thanks Bartosz!
>
> On Wednesday, September 18, 2013 3:17:26 PM UTC-5, Bartosz Wiklak wrote:
>>
>> I had similar problem, but I wasn't using supervisor. A file name in
>> /media/uploads/gallery has strange character encoding (the folder contains
>> jspeg Austin, Athens, Amsterdam ...), I wasn't uploading anything there,
>> suppose this files are uploaded by mezzanine. My locale is pl_PL.UTF8.
>> The exception description is a little bit misleading.
>>
>> On Sunday, November 25, 2012 10:51:38 PM UTC+1, Doug Evenhouse wrote:
>>>
>>> I'm spinning my wheels a bit with an FileSystemEncodingChanged exception
>>> that is thrown whenever I try to browse media files. I was happily
>>> uploading images and all was well for awhile. Now I cannot open the file
>>> browser at all without this exception being thrown. I don't believe I have
>>> created any folders nor uploaded any files with unusual encoding or names.
>>> As far as I can nothing would have changed with regard to locale settings.
>>> I removed the entire project and recreated it to no avail. The exceptions
>>> occur on both a staging server and a production server running Ubuntu
>>> 12.04, and deployed using vanilla fabric settings with Mezzanine 1.2.4.
>>> LC_ALL appears to be set correctly to "en_US.UTF-8".
>>>
>>> Anyone have advice as to possible root causes and/or troubleshooting
>>> steps to take?
>>>
>>> Traceback and request settings from the exception email - this is
>>> running on our internal staging server):
>>>
>>> File "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/
>>> site-packages/django/core/handlers/base.py", line 105, in get_response
>>> response = middleware_method(request, callback, callback_args,
>>> callback_kwargs)
>>>
>>> File "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/
>>> site-packages/mezzanine/pages/middleware.py", line 45, in process_view
>>> return view_func(request, *view_args, **view_kwargs)
>>>
>>> File "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/
>>> site-packages/django/contrib/admin/views/decorators.py", line 16, in
>>> _checklogin
>>> return view_func(request, *args, **kwargs)
>>>
>>> File "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/
>>> site-packages/django/views/decorators/cache.py", line 89, in
>>> _wrapped_view_func
>>> response = view_func(request, *args, **kwargs)
>>>
>>> File "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/
>>> site-packages/filebrowser_safe/views.py", line 116, in browse
>>> elif fileobject.filetype == 'Folder' and fileobject.is_empty:
>>>
>>> File "/home/doug/virtualenvs/hccs_website/local/lib/python2.7/
>>> site-packages/filebrowser_safe/base.py", line 134, in _is_empty
>>> raise FileSystemEncodingChanged()
>>>
>>> FileSystemEncodingChanged: Access was attempted on a file that contains
>>> unicode characters in its path, but somehow the current locale does not
>>> support utf-8. You may need to set 'LC_ALL' to a correct value, eg:
>>> 'en_US.UTF-8'.
>>>
>>>
>>> >> path:/admin/media-library/browse/,
>>> GET:,
>>> POST:,
>>> COOKIES:{'__utma': '74311563.372776308.1351892605.1351898182.
>>> 1351966440.4',
>>> '__utmz': '74311563.1351892605.1.1.utmcsr=(direct)|utmccn=(
>>> direct)|utmcmd=(none)',
>>> 'csrftoken': 'l754gpeXgo6WrMKmH5gQ0UpsG96acn41',
>>> 'messages': '
>>> 81375d9cdb262e44aff2f71e2a66e74c9742ea2a$[["__json_message",40,"The
>>> requested Folder does not exist."]]',
>>> 'mezzanine-admin-toolbar': '',
>>> 'sessionid': '4fbd7d0d1511a2c157fe2bdc60aed3cf'},
>>> META:{'CSRF_COOKIE': 'l754gpeXgo6WrMKmH5gQ0UpsG96acn41',
>>> 'HTTP_ACCEPT': 'text/html,application/xhtml+
>>> xml,application/xml;q=0.9,*/*;q=0.8',
>>> 'HTTP_ACCEPT_CHARSET': 'ISO-8859-1,utf-8;q=0.7,*;q=0.3',
>>> 'HTTP_ACCEPT_ENCODING': 'gzip,deflate,sdch',
>>> 'HTTP_ACCEPT_LANGUAGE': 'en-US,en;q=0.8',
>>> 'HTTP_CONNECTION': 'close',
>>> 'HTTP_COOKIE': '__utma=74311563.372776308.1351892605.1351898182.
>>> 1351966440.4;
>>> __utmz=74311563.1351892605.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
>>> sessionid=4fbd7d0d1511a2c157fe2bdc60aed3cf; mezzanine-admin-toolb
Re: [mezzanine-users] Admin navigation
Ok, I took a look and I did create a codepen so that anyone can look
at/edit it really easily. Here is the pen (you can edit it by clicking the
link in the bottom left):
http://codepen.io/joshcartme/full/wIcxp
(I hotlinked the css/js files from the dev site, hopefully that's not a big
deal Steve).
So far my only css change is:
.dropdown-menu{
overflow: auto;
height: 100%;
}
To make it so there is only a scrollbar if needed and so that the sidebar
spans the full page width. I also moved the language selector dropdown to
the top and made it an element in the ul.
Thoughts?
On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald wrote:
> Guess not. You can probably just fork and start committing.
>
> BTW I've pushed up the latest commits to the demo site (
> http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can login
> to its admin and see the current state of the new menu plus other visual
> tweaks - so if anyone who has a moment to try out their particular browser
> (eg I've no idea how this renders in IE) and provide any feedback that'd be
> great!
>
>
> On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell wrote:
>
>> Well, it looks like you guys worked this out in the meantime (I haven't
>> tried it yet myself) so I'm guessing jsfiddle/codepen would be unnecessary
>> at this point?
>>
>> Thanks Josh!
>>
>>
>> On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald wrote:
>>
>>> Nothing comes to mind but if you have any ideas where we can easily (eg
>>> with a light touch) improve the usability and look of it then definitely
>>> bring them up!
>>>
>>> I had my eye on this style of left-hand nav that the wordpress admin
>>> uses for quite a while, and recently I saw a comment on reddit or some site
>>> describing Mezzanine's admin + grappelli as looking tired and old compared
>>> to newer CMSes and I couldn't help but agree. So the left-hand nav is an
>>> attempt to improve things there. You might notice I also tried to increase
>>> font sizes everywhere, but I tried to do this in a way where I didn't touch
>>> anything in grappelli which was only partially successful. I think one of
>>> the main usability issues currently is the tiny fonts everywhere.
>>>
>>>
>>> On Mon, Feb 24, 2014 at 4:24 PM, Josh B <
>>> josh.batche...@wearetopsecret.com> wrote:
>>>
Sounds good, besides the collapsible menu is there other things you
want to do to the admin?
On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald wrote:
> Yep but I've just fixed that locally and will push in a sec so don't
> sweat it.
>
> Thanks again, really exciting to give the admin a dress up!
>
>
> On Mon, Feb 24, 2014 at 4:21 PM, Josh B > wrote:
>
>> Did you want it to butt up to the top or?
>>
>>
>> On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald
>> wrote:
>>
>>> Ahhh I'm sorry, I just cleared my cache and it mostly looks right:
>>>
>>> http://cl.ly/image/1s2j3B121Q3U
>>>
>>>
>>>
>>>
>>> On Mon, Feb 24, 2014 at 4:17 PM, Josh B >> wearetopsecret.com> wrote:
>>>
My bad, forgot to fix the error message once logged in. Give me a
minute.
On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen McDonald
wrote:
> Thanks a lot Josh!
>
> Not sure if it's intended bit it still looks a bit off on my end:
> http://cl.ly/image/1q2H0E1Y1w0w
>
> My browser is Chrome 34.0.1847.3
>
>
>
>
> On Mon, Feb 24, 2014 at 4:10 PM, Josh B wearetopsecret.com> wrote:
>
>> I just opened a Pull Request for the messages issue. Haven't had
>> a chance to look into the collapsing navigation. Let me know if you
>> have
>> time to take care of that Josh. If not I might have some time
>> tomorrow.
>>
>>
>> On Sunday, February 23, 2014 4:05:51 PM UTC-7, Stephen McDonald
>> wrote:
>>
>>> Sounds like a great idea, wanna kick it off?
>>>
>>>
>>> On Mon, Feb 24, 2014 at 9:08 AM, Josh Cartmell <
>>> joshc...@gmail.com> wrote:
>>>
I'd like to try to help as well, would there be any way to put
a static version up on jsfiddle or codepen so that we could easily
play
with the js and iterate?
On Sat, Feb 22, 2014 at 6:44 PM, Stephen McDonald <
st...@jupo.org> wrote:
> Don't really have one - is there any reason not to modify
> it? If not, go for it.
>
>
> On Sun, Feb 23, 2014 at 1:42 PM, Josh B wearetopsecret.com> wrote:
>
>> Stephen, what is your stance on modifying the admin/base.html?
>>
>>
Re: [mezzanine-users] Admin navigation
I said "so that the sidebar spans the full page width", I meant full page
height.
On Tue, Feb 25, 2014 at 10:33 AM, Josh Cartmell wrote:
> Ok, I took a look and I did create a codepen so that anyone can look
> at/edit it really easily. Here is the pen (you can edit it by clicking the
> link in the bottom left):
> http://codepen.io/joshcartme/full/wIcxp
> (I hotlinked the css/js files from the dev site, hopefully that's not a
> big deal Steve).
>
> So far my only css change is:
> .dropdown-menu{
> overflow: auto;
> height: 100%;
> }
> To make it so there is only a scrollbar if needed and so that the sidebar
> spans the full page width. I also moved the language selector dropdown to
> the top and made it an element in the ul.
>
> Thoughts?
>
>
> On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald wrote:
>
>> Guess not. You can probably just fork and start committing.
>>
>> BTW I've pushed up the latest commits to the demo site (
>> http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can login
>> to its admin and see the current state of the new menu plus other visual
>> tweaks - so if anyone who has a moment to try out their particular browser
>> (eg I've no idea how this renders in IE) and provide any feedback that'd be
>> great!
>>
>>
>> On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell wrote:
>>
>>> Well, it looks like you guys worked this out in the meantime (I haven't
>>> tried it yet myself) so I'm guessing jsfiddle/codepen would be unnecessary
>>> at this point?
>>>
>>> Thanks Josh!
>>>
>>>
>>> On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald wrote:
>>>
Nothing comes to mind but if you have any ideas where we can easily (eg
with a light touch) improve the usability and look of it then definitely
bring them up!
I had my eye on this style of left-hand nav that the wordpress admin
uses for quite a while, and recently I saw a comment on reddit or some site
describing Mezzanine's admin + grappelli as looking tired and old compared
to newer CMSes and I couldn't help but agree. So the left-hand nav is an
attempt to improve things there. You might notice I also tried to increase
font sizes everywhere, but I tried to do this in a way where I didn't touch
anything in grappelli which was only partially successful. I think one of
the main usability issues currently is the tiny fonts everywhere.
On Mon, Feb 24, 2014 at 4:24 PM, Josh B <
josh.batche...@wearetopsecret.com> wrote:
> Sounds good, besides the collapsible menu is there other things you
> want to do to the admin?
>
>
> On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald wrote:
>
>> Yep but I've just fixed that locally and will push in a sec so don't
>> sweat it.
>>
>> Thanks again, really exciting to give the admin a dress up!
>>
>>
>> On Mon, Feb 24, 2014 at 4:21 PM, Josh B > wearetopsecret.com> wrote:
>>
>>> Did you want it to butt up to the top or?
>>>
>>>
>>> On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald
>>> wrote:
>>>
Ahhh I'm sorry, I just cleared my cache and it mostly looks right:
http://cl.ly/image/1s2j3B121Q3U
On Mon, Feb 24, 2014 at 4:17 PM, Josh B >>> wearetopsecret.com> wrote:
> My bad, forgot to fix the error message once logged in. Give me a
> minute.
>
>
> On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen McDonald
> wrote:
>
>> Thanks a lot Josh!
>>
>> Not sure if it's intended bit it still looks a bit off on my end:
>> http://cl.ly/image/1q2H0E1Y1w0w
>>
>> My browser is Chrome 34.0.1847.3
>>
>>
>>
>>
>> On Mon, Feb 24, 2014 at 4:10 PM, Josh B > wearetopsecret.com> wrote:
>>
>>> I just opened a Pull Request for the messages issue. Haven't had
>>> a chance to look into the collapsing navigation. Let me know if you
>>> have
>>> time to take care of that Josh. If not I might have some time
>>> tomorrow.
>>>
>>>
>>> On Sunday, February 23, 2014 4:05:51 PM UTC-7, Stephen McDonald
>>> wrote:
>>>
Sounds like a great idea, wanna kick it off?
On Mon, Feb 24, 2014 at 9:08 AM, Josh Cartmell <
joshc...@gmail.com> wrote:
> I'd like to try to help as well, would there be any way to put
> a static version up on jsfiddle or codepen so that we could
> easily play
> with the js and iterate?
>
>
> On Sat, Feb 22, 2014 at 6:44 PM, Stephen McDonald <
> st...@jupo.org> wrote:
>
>> Don't really have one - is there any reaso
[mezzanine-users] Stripe payments
I saw here https://groups.google.com/d/msg/mezzanine-users/hFQeqVJP1S8/5C0fvvNpFg8J a mention of a stripe payment handler Suggestions where to go next? Any other pointers to code or docs? Just trying to wrap my head around security, auth, oauth and checkout needs for an app.. and among other things stripe seems to be able to use oauth, and not sure how or if I want to?? -- 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] Admin navigation
Nice, I had a ton of trouble with the full height and scrollbars so glad
that's better.
I think the lang and site selectors should probably go up into the existing
top nav on the right-hand side but to the left of the existing buttons.
Easiest way to do that might be at the top of navigation.js where we are
already moving a bunch of elements around using jQuery rather than trying
to repurpose the layers of templates between django/grappelli/mezzanine.
On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell wrote:
> Ok, I took a look and I did create a codepen so that anyone can look
> at/edit it really easily. Here is the pen (you can edit it by clicking the
> link in the bottom left):
> http://codepen.io/joshcartme/full/wIcxp
> (I hotlinked the css/js files from the dev site, hopefully that's not a
> big deal Steve).
>
> So far my only css change is:
> .dropdown-menu{
> overflow: auto;
> height: 100%;
> }
> To make it so there is only a scrollbar if needed and so that the sidebar
> spans the full page width. I also moved the language selector dropdown to
> the top and made it an element in the ul.
>
> Thoughts?
>
>
> On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald wrote:
>
>> Guess not. You can probably just fork and start committing.
>>
>> BTW I've pushed up the latest commits to the demo site (
>> http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can login
>> to its admin and see the current state of the new menu plus other visual
>> tweaks - so if anyone who has a moment to try out their particular browser
>> (eg I've no idea how this renders in IE) and provide any feedback that'd be
>> great!
>>
>>
>> On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell wrote:
>>
>>> Well, it looks like you guys worked this out in the meantime (I haven't
>>> tried it yet myself) so I'm guessing jsfiddle/codepen would be unnecessary
>>> at this point?
>>>
>>> Thanks Josh!
>>>
>>>
>>> On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald wrote:
>>>
Nothing comes to mind but if you have any ideas where we can easily (eg
with a light touch) improve the usability and look of it then definitely
bring them up!
I had my eye on this style of left-hand nav that the wordpress admin
uses for quite a while, and recently I saw a comment on reddit or some site
describing Mezzanine's admin + grappelli as looking tired and old compared
to newer CMSes and I couldn't help but agree. So the left-hand nav is an
attempt to improve things there. You might notice I also tried to increase
font sizes everywhere, but I tried to do this in a way where I didn't touch
anything in grappelli which was only partially successful. I think one of
the main usability issues currently is the tiny fonts everywhere.
On Mon, Feb 24, 2014 at 4:24 PM, Josh B <
josh.batche...@wearetopsecret.com> wrote:
> Sounds good, besides the collapsible menu is there other things you
> want to do to the admin?
>
>
> On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald wrote:
>
>> Yep but I've just fixed that locally and will push in a sec so don't
>> sweat it.
>>
>> Thanks again, really exciting to give the admin a dress up!
>>
>>
>> On Mon, Feb 24, 2014 at 4:21 PM, Josh B > wearetopsecret.com> wrote:
>>
>>> Did you want it to butt up to the top or?
>>>
>>>
>>> On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald
>>> wrote:
>>>
Ahhh I'm sorry, I just cleared my cache and it mostly looks right:
http://cl.ly/image/1s2j3B121Q3U
On Mon, Feb 24, 2014 at 4:17 PM, Josh B >>> wearetopsecret.com> wrote:
> My bad, forgot to fix the error message once logged in. Give me a
> minute.
>
>
> On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen McDonald
> wrote:
>
>> Thanks a lot Josh!
>>
>> Not sure if it's intended bit it still looks a bit off on my end:
>> http://cl.ly/image/1q2H0E1Y1w0w
>>
>> My browser is Chrome 34.0.1847.3
>>
>>
>>
>>
>> On Mon, Feb 24, 2014 at 4:10 PM, Josh B > wearetopsecret.com> wrote:
>>
>>> I just opened a Pull Request for the messages issue. Haven't had
>>> a chance to look into the collapsing navigation. Let me know if you
>>> have
>>> time to take care of that Josh. If not I might have some time
>>> tomorrow.
>>>
>>>
>>> On Sunday, February 23, 2014 4:05:51 PM UTC-7, Stephen McDonald
>>> wrote:
>>>
Sounds like a great idea, wanna kick it off?
On Mon, Feb 24, 2014 at 9:08 AM, Josh Cartmell <
joshc...@gmail.com> wrote:
> I'd like to try to help as wel
[mezzanine-users] Re: Using a foreign key in Model search_fields?
I couldn't get this to work :(
Path of least resistance was to just add the field data to self.description
On Monday, February 17, 2014 10:48:21 PM UTC-5, step wrote:
>
> Hey guys, I can't figure this out. I figured this might be something
> worth resolving on the mailing list as a reference.
> I'm trying to use a foreignkey in a Model's search_fields (search using a
> foreignkey).
>
> Anyone have any idea?
>
> *settings.py*
> -
> (
> # Dotted path to field.
> "cartridge.shop.models.Product.artist",
> # Dotted path to field class.
> "ForeignKey",
> # Positional args for field class.
> ("app.Artist",),
> # Keyword args for field class.
> {"blank": False},
> )
>
> *OPTION 1.*
>
> patches.py
>
> Product.search_fields = {'keywords_string': 10, 'title': 5, 'artist': 5}
>
> results in
>
> "Related Field got invalid lookup: icontains"
>
>
> *OPTION 2*
>
> patches.py
>
> Product.search_fields = {'keywords_string': 10, 'title': 5,
> 'artist__title': 5}
>
> results in
>
> "'Product' object has no attribute 'artist__title'"
>
--
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] Admin navigation
Yeah, although it ended up being a small CSS change it took me quite a bit
of messing around to get it looking like that.
I think putting the selectors in the top bar is a great idea and using the
js to do it sounds like a simple enough solution.
Is anyone working on collapsible nav at this point? I'll take a stab at it
if not.
On Tue, Feb 25, 2014 at 11:25 AM, Stephen McDonald wrote:
> Nice, I had a ton of trouble with the full height and scrollbars so glad
> that's better.
>
> I think the lang and site selectors should probably go up into the
> existing top nav on the right-hand side but to the left of the existing
> buttons.
>
> Easiest way to do that might be at the top of navigation.js where we are
> already moving a bunch of elements around using jQuery rather than trying
> to repurpose the layers of templates between django/grappelli/mezzanine.
>
>
> On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell wrote:
>
>> Ok, I took a look and I did create a codepen so that anyone can look
>> at/edit it really easily. Here is the pen (you can edit it by clicking the
>> link in the bottom left):
>> http://codepen.io/joshcartme/full/wIcxp
>> (I hotlinked the css/js files from the dev site, hopefully that's not a
>> big deal Steve).
>>
>> So far my only css change is:
>> .dropdown-menu{
>> overflow: auto;
>> height: 100%;
>> }
>> To make it so there is only a scrollbar if needed and so that the sidebar
>> spans the full page width. I also moved the language selector dropdown to
>> the top and made it an element in the ul.
>>
>> Thoughts?
>>
>>
>> On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald wrote:
>>
>>> Guess not. You can probably just fork and start committing.
>>>
>>> BTW I've pushed up the latest commits to the demo site (
>>> http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can
>>> login to its admin and see the current state of the new menu plus other
>>> visual tweaks - so if anyone who has a moment to try out their particular
>>> browser (eg I've no idea how this renders in IE) and provide any feedback
>>> that'd be great!
>>>
>>>
>>> On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell wrote:
>>>
Well, it looks like you guys worked this out in the meantime (I haven't
tried it yet myself) so I'm guessing jsfiddle/codepen would be unnecessary
at this point?
Thanks Josh!
On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald wrote:
> Nothing comes to mind but if you have any ideas where we can easily
> (eg with a light touch) improve the usability and look of it then
> definitely bring them up!
>
> I had my eye on this style of left-hand nav that the wordpress admin
> uses for quite a while, and recently I saw a comment on reddit or some
> site
> describing Mezzanine's admin + grappelli as looking tired and old compared
> to newer CMSes and I couldn't help but agree. So the left-hand nav is an
> attempt to improve things there. You might notice I also tried to increase
> font sizes everywhere, but I tried to do this in a way where I didn't
> touch
> anything in grappelli which was only partially successful. I think one of
> the main usability issues currently is the tiny fonts everywhere.
>
>
> On Mon, Feb 24, 2014 at 4:24 PM, Josh B <
> josh.batche...@wearetopsecret.com> wrote:
>
>> Sounds good, besides the collapsible menu is there other things you
>> want to do to the admin?
>>
>>
>> On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald
>> wrote:
>>
>>> Yep but I've just fixed that locally and will push in a sec so don't
>>> sweat it.
>>>
>>> Thanks again, really exciting to give the admin a dress up!
>>>
>>>
>>> On Mon, Feb 24, 2014 at 4:21 PM, Josh B >> wearetopsecret.com> wrote:
>>>
Did you want it to butt up to the top or?
On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald
wrote:
> Ahhh I'm sorry, I just cleared my cache and it mostly looks right:
>
> http://cl.ly/image/1s2j3B121Q3U
>
>
>
>
> On Mon, Feb 24, 2014 at 4:17 PM, Josh B wearetopsecret.com> wrote:
>
>> My bad, forgot to fix the error message once logged in. Give me a
>> minute.
>>
>>
>> On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen McDonald
>> wrote:
>>
>>> Thanks a lot Josh!
>>>
>>> Not sure if it's intended bit it still looks a bit off on my
>>> end: http://cl.ly/image/1q2H0E1Y1w0w
>>>
>>> My browser is Chrome 34.0.1847.3
>>>
>>>
>>>
>>>
>>> On Mon, Feb 24, 2014 at 4:10 PM, Josh B >> wearetopsecret.com> wrote:
>>>
I just opened a Pull Request for the messages issue. Haven't
had a chance
Re: [mezzanine-users] Stripe payments
Hey Tom, is this for use with Cartridge or something else?
If something else I have used something like the following.
in the template:
https://checkout.stripe.com/checkout.js";>
$(document).ready(function() {
var handler = StripeCheckout.configure({
key: '{{ settings.STRIPE_PUBLIC_KEY }}',
image: '{% static "whatever_image.png" %}',
token: function(token, args) {
$('#checkout-button').prop('disabled', true);
$('#id_stripe_token').val(token.id);
$('#id_email').val(token.email);
$('#hourly-form').submit();
}
});
document.getElementById('checkout-button').addEventListener('click',
function(e) {
amount = cost();
// Open Checkout with further options
if (amount){
handler.open({
name: '{{ settings.SITE_TITLE }}',
amount: amount,
billingAddress: true
});
} else {
alert('You must choose at least one service')
}
e.preventDefault();
});
});
Then in the forms clean method:
stripe.api_key = settings.STRIPE_SECRET_KEY
token = cleaned_data['stripe_token']
try:
cleaned_data['charge'] = stripe.Charge.create(
amount=amount, # amount in cents, again
currency="usd",
card=token,
)
except stripe.CardError:
raise forms.ValidationError("The card has been declined")
Some of the above is a bit specific to my case (so it'll require a bit of
editing) and I'm using the stripe checkout custom integration which is
slightly more complicated but lets you specify custom buttons/images and
other options.
Hopefully that helps.
On Tue, Feb 25, 2014 at 11:21 AM, Tom Brander wrote:
> I saw here
> https://groups.google.com/d/msg/mezzanine-users/hFQeqVJP1S8/5C0fvvNpFg8Ja
> mention of a stripe payment handler
> Suggestions where to go next?
> Any other pointers to code or docs?
> Just trying to wrap my head around security, auth, oauth and checkout
> needs for an app.. and among other things stripe seems to be able to use
> oauth, and not sure how or if I want to??
>
> --
> 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.
>
--
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] Admin navigation
I haven't been able to jump back on it. So feel free.
On Tuesday, February 25, 2014 2:07:11 PM UTC-7, Josh Cartmell wrote:
>
> Yeah, although it ended up being a small CSS change it took me quite a bit
> of messing around to get it looking like that.
>
> I think putting the selectors in the top bar is a great idea and using the
> js to do it sounds like a simple enough solution.
>
> Is anyone working on collapsible nav at this point? I'll take a stab at
> it if not.
>
>
> On Tue, Feb 25, 2014 at 11:25 AM, Stephen McDonald
>
> > wrote:
>
>> Nice, I had a ton of trouble with the full height and scrollbars so glad
>> that's better.
>>
>> I think the lang and site selectors should probably go up into the
>> existing top nav on the right-hand side but to the left of the existing
>> buttons.
>>
>> Easiest way to do that might be at the top of navigation.js where we are
>> already moving a bunch of elements around using jQuery rather than trying
>> to repurpose the layers of templates between django/grappelli/mezzanine.
>>
>>
>> On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell
>>
>> > wrote:
>>
>>> Ok, I took a look and I did create a codepen so that anyone can look
>>> at/edit it really easily. Here is the pen (you can edit it by clicking the
>>> link in the bottom left):
>>> http://codepen.io/joshcartme/full/wIcxp
>>> (I hotlinked the css/js files from the dev site, hopefully that's not a
>>> big deal Steve).
>>>
>>> So far my only css change is:
>>> .dropdown-menu{
>>> overflow: auto;
>>> height: 100%;
>>> }
>>> To make it so there is only a scrollbar if needed and so that the
>>> sidebar spans the full page width. I also moved the language selector
>>> dropdown to the top and made it an element in the ul.
>>>
>>> Thoughts?
>>>
>>>
>>> On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald
>>>
>>> > wrote:
>>>
Guess not. You can probably just fork and start committing.
BTW I've pushed up the latest commits to the demo site (
http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can
login to its admin and see the current state of the new menu plus other
visual tweaks - so if anyone who has a moment to try out their particular
browser (eg I've no idea how this renders in IE) and provide any feedback
that'd be great!
On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell
> wrote:
> Well, it looks like you guys worked this out in the meantime (I
> haven't tried it yet myself) so I'm guessing jsfiddle/codepen would be
> unnecessary at this point?
>
> Thanks Josh!
>
>
> On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald
>
> > wrote:
>
>> Nothing comes to mind but if you have any ideas where we can easily
>> (eg with a light touch) improve the usability and look of it then
>> definitely bring them up!
>>
>> I had my eye on this style of left-hand nav that the wordpress admin
>> uses for quite a while, and recently I saw a comment on reddit or some
>> site
>> describing Mezzanine's admin + grappelli as looking tired and old
>> compared
>> to newer CMSes and I couldn't help but agree. So the left-hand nav is an
>> attempt to improve things there. You might notice I also tried to
>> increase
>> font sizes everywhere, but I tried to do this in a way where I didn't
>> touch
>> anything in grappelli which was only partially successful. I think one
>> of
>> the main usability issues currently is the tiny fonts everywhere.
>>
>>
>> On Mon, Feb 24, 2014 at 4:24 PM, Josh B <
>> josh.ba...@wearetopsecret.com > wrote:
>>
>>> Sounds good, besides the collapsible menu is there other things you
>>> want to do to the admin?
>>>
>>>
>>> On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald
>>> wrote:
>>>
Yep but I've just fixed that locally and will push in a sec so
don't sweat it.
Thanks again, really exciting to give the admin a dress up!
On Mon, Feb 24, 2014 at 4:21 PM, Josh B >>> wearetopsecret.com> wrote:
> Did you want it to butt up to the top or?
>
>
> On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald
> wrote:
>
>> Ahhh I'm sorry, I just cleared my cache and it mostly looks right:
>>
>> http://cl.ly/image/1s2j3B121Q3U
>>
>>
>>
>>
>> On Mon, Feb 24, 2014 at 4:17 PM, Josh B > wearetopsecret.com> wrote:
>>
>>> My bad, forgot to fix the error message once logged in. Give me
>>> a minute.
>>>
>>>
>>> On Sunday, February 23, 2014 10:14:29 PM UTC-7, Stephen McDonald
>>> wrote:
>>>
Thanks a lot Josh!
Not sure if it's intended bit it still l
Re: [mezzanine-users] Cartridge and Product Option Type Choices
Couple of ideas I have been batting around: No matter what I think we need to move all product option types to the database. a. Allow a user to create a option group. ie. Shirt options, which would include Size and Color (or whatever the user chooses). Each time a new product is created you could select what product options you need and then essentially copy them to the new instance of the product. You could also add product specific colors or sizes. b. Have product options only live at a product level. On Tuesday, February 25, 2014 12:04:30 AM UTC-7, Stephen McDonald wrote: > > All I can say at this stage is that the current design around how options > work certainly has quite a few limitations, most notably the fact that > migrations need to occur if the number change, but also including what > you've raised here. > > It could certainly use some re-thinking/re-writing! > > > On Tue, Feb 25, 2014 at 7:57 AM, Josh B > > > wrote: > >> Working on a couple of projects where each product will have a unique set >> of options. With that I am building a seller admin where a seller can >> create a product, create options, inventory etc. Then the site admin will >> approve it and mark it ready for purchase, etc. >> >> 1. Has anyone come up with a good solution for handling dynamic shop >> option type choices? >> 2. Is there a reason why they are currently static and set in the >> settings file? >> >> a. Could this be moved to be a dynamic setup? >> >> >> With the handful of Cartridge sites i have built, the current product >> options become bloated when you have a diverse set of products. Thoughts, >> opinions? >> >> -- >> 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 . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > 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/groups/opt_out.
Re: [mezzanine-users] Admin navigation
Ok, just added some js, take a look at
http://codepen.io/joshcartme/full/wtkrF (that's a different url than the
first one because I was running into some sort of caching issue with
codepen).
JS hides all the dropdowns to start, then clicking a heading either takes
you to it's link or opens it's dropdown (if it has any). If you click a
heading of an open dropdown it goes to the link of that heading. Clicking
a different heading closes any currently open dropdowns.
How does this look?
On Tue, Feb 25, 2014 at 1:21 PM, Josh B
wrote:
> I haven't been able to jump back on it. So feel free.
>
>
> On Tuesday, February 25, 2014 2:07:11 PM UTC-7, Josh Cartmell wrote:
>
>> Yeah, although it ended up being a small CSS change it took me quite a
>> bit of messing around to get it looking like that.
>>
>> I think putting the selectors in the top bar is a great idea and using
>> the js to do it sounds like a simple enough solution.
>>
>> Is anyone working on collapsible nav at this point? I'll take a stab at
>> it if not.
>>
>>
>> On Tue, Feb 25, 2014 at 11:25 AM, Stephen McDonald wrote:
>>
>>> Nice, I had a ton of trouble with the full height and scrollbars so glad
>>> that's better.
>>>
>>> I think the lang and site selectors should probably go up into the
>>> existing top nav on the right-hand side but to the left of the existing
>>> buttons.
>>>
>>> Easiest way to do that might be at the top of navigation.js where we are
>>> already moving a bunch of elements around using jQuery rather than trying
>>> to repurpose the layers of templates between django/grappelli/mezzanine.
>>>
>>>
>>> On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell wrote:
>>>
Ok, I took a look and I did create a codepen so that anyone can look
at/edit it really easily. Here is the pen (you can edit it by clicking the
link in the bottom left):
http://codepen.io/joshcartme/full/wIcxp
(I hotlinked the css/js files from the dev site, hopefully that's not a
big deal Steve).
So far my only css change is:
.dropdown-menu{
overflow: auto;
height: 100%;
}
To make it so there is only a scrollbar if needed and so that the
sidebar spans the full page width. I also moved the language selector
dropdown to the top and made it an element in the ul.
Thoughts?
On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald wrote:
> Guess not. You can probably just fork and start committing.
>
> BTW I've pushed up the latest commits to the demo site (
> http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can
> login to its admin and see the current state of the new menu plus other
> visual tweaks - so if anyone who has a moment to try out their particular
> browser (eg I've no idea how this renders in IE) and provide any feedback
> that'd be great!
>
>
> On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell wrote:
>
>> Well, it looks like you guys worked this out in the meantime (I
>> haven't tried it yet myself) so I'm guessing jsfiddle/codepen would be
>> unnecessary at this point?
>>
>> Thanks Josh!
>>
>>
>> On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald wrote:
>>
>>> Nothing comes to mind but if you have any ideas where we can
>>> easily (eg with a light touch) improve the usability and look of it then
>>> definitely bring them up!
>>>
>>> I had my eye on this style of left-hand nav that the wordpress admin
>>> uses for quite a while, and recently I saw a comment on reddit or some
>>> site
>>> describing Mezzanine's admin + grappelli as looking tired and old
>>> compared
>>> to newer CMSes and I couldn't help but agree. So the left-hand nav is an
>>> attempt to improve things there. You might notice I also tried to
>>> increase
>>> font sizes everywhere, but I tried to do this in a way where I didn't
>>> touch
>>> anything in grappelli which was only partially successful. I think one
>>> of
>>> the main usability issues currently is the tiny fonts everywhere.
>>>
>>>
>>> On Mon, Feb 24, 2014 at 4:24 PM, Josh B >> wearetopsecret.com> wrote:
>>>
Sounds good, besides the collapsible menu is there other things you
want to do to the admin?
On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald
wrote:
> Yep but I've just fixed that locally and will push in a sec so
> don't sweat it.
>
> Thanks again, really exciting to give the admin a dress up!
>
>
> On Mon, Feb 24, 2014 at 4:21 PM, Josh B wearetopsecret.com> wrote:
>
>> Did you want it to butt up to the top or?
>>
>>
>> On Sunday, February 23, 2014 10:19:31 PM UTC-7, Stephen McDonald
>> wrote:
>>
>>> Ahhh I'm sorry, I just cleared my cach
Re: [mezzanine-users] first steps with fabric deployment
2014-02-25 11:47 GMT+01:00 : > I have just deployed my first Mezzanine project and I agree with what you > say: the deployment was clearly the most difficult part. > I used fabric too, but it's not very easy but once it works it really > saves you a lot of time. I have the feeling that when a step goes wrong in > fab deploy, it begins to do strange things. > So, instead running fab all, I run: > * fab install > * fab create > * fab deploy Thank you, it helped a lot. I'm trying to make 'fab create' work until the end. I've made many step forward, but now I'm getting this error: django.db.utils.OperationalError: fe_sendauth: no password supplied This is probably because I haven't defined DB_PASS in settings.py. What's the secure way to define these sensible variables (passwords, secret keys, etc.) out of the source repository (even if it's private)? Another important question: if 'fab create' fails and I want to run it again, it seems that I have no other option than accepting the removal and start again from the beginning. A huge waste of time and resources. There's no other way? -- 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] Admin navigation
That's awesome - I think next we'd need to figure out how to have the
current section you're on open by default.
On Wed, Feb 26, 2014 at 8:42 AM, Josh Cartmell wrote:
> Ok, just added some js, take a look at
> http://codepen.io/joshcartme/full/wtkrF (that's a different url than the
> first one because I was running into some sort of caching issue with
> codepen).
>
> JS hides all the dropdowns to start, then clicking a heading either takes
> you to it's link or opens it's dropdown (if it has any). If you click a
> heading of an open dropdown it goes to the link of that heading. Clicking
> a different heading closes any currently open dropdowns.
>
> How does this look?
>
>
> On Tue, Feb 25, 2014 at 1:21 PM, Josh B > wrote:
>
>> I haven't been able to jump back on it. So feel free.
>>
>>
>> On Tuesday, February 25, 2014 2:07:11 PM UTC-7, Josh Cartmell wrote:
>>
>>> Yeah, although it ended up being a small CSS change it took me quite a
>>> bit of messing around to get it looking like that.
>>>
>>> I think putting the selectors in the top bar is a great idea and using
>>> the js to do it sounds like a simple enough solution.
>>>
>>> Is anyone working on collapsible nav at this point? I'll take a stab at
>>> it if not.
>>>
>>>
>>> On Tue, Feb 25, 2014 at 11:25 AM, Stephen McDonald wrote:
>>>
Nice, I had a ton of trouble with the full height and scrollbars so
glad that's better.
I think the lang and site selectors should probably go up into the
existing top nav on the right-hand side but to the left of the existing
buttons.
Easiest way to do that might be at the top of navigation.js where we
are already moving a bunch of elements around using jQuery rather than
trying to repurpose the layers of templates between
django/grappelli/mezzanine.
On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell wrote:
> Ok, I took a look and I did create a codepen so that anyone can look
> at/edit it really easily. Here is the pen (you can edit it by clicking
> the
> link in the bottom left):
> http://codepen.io/joshcartme/full/wIcxp
> (I hotlinked the css/js files from the dev site, hopefully that's not
> a big deal Steve).
>
> So far my only css change is:
> .dropdown-menu{
> overflow: auto;
> height: 100%;
> }
> To make it so there is only a scrollbar if needed and so that the
> sidebar spans the full page width. I also moved the language selector
> dropdown to the top and made it an element in the ul.
>
> Thoughts?
>
>
> On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald wrote:
>
>> Guess not. You can probably just fork and start committing.
>>
>> BTW I've pushed up the latest commits to the demo site (
>> http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can
>> login to its admin and see the current state of the new menu plus other
>> visual tweaks - so if anyone who has a moment to try out their particular
>> browser (eg I've no idea how this renders in IE) and provide any feedback
>> that'd be great!
>>
>>
>> On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell wrote:
>>
>>> Well, it looks like you guys worked this out in the meantime (I
>>> haven't tried it yet myself) so I'm guessing jsfiddle/codepen would be
>>> unnecessary at this point?
>>>
>>> Thanks Josh!
>>>
>>>
>>> On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald wrote:
>>>
Nothing comes to mind but if you have any ideas where we can
easily (eg with a light touch) improve the usability and look of it
then
definitely bring them up!
I had my eye on this style of left-hand nav that the wordpress
admin uses for quite a while, and recently I saw a comment on reddit or
some site describing Mezzanine's admin + grappelli as looking tired
and old
compared to newer CMSes and I couldn't help but agree. So the
left-hand nav
is an attempt to improve things there. You might notice I also tried to
increase font sizes everywhere, but I tried to do this in a way where I
didn't touch anything in grappelli which was only partially
successful. I
think one of the main usability issues currently is the tiny fonts
everywhere.
On Mon, Feb 24, 2014 at 4:24 PM, Josh B >>> wearetopsecret.com> wrote:
> Sounds good, besides the collapsible menu is there other things
> you want to do to the admin?
>
>
> On Sunday, February 23, 2014 10:22:37 PM UTC-7, Stephen McDonald
> wrote:
>
>> Yep but I've just fixed that locally and will push in a sec so
>> don't sweat it.
>>
>> Thanks again, really exciting to give the admin a dress up!
>>
>>
Re: [mezzanine-users] Admin navigation
Ok, I think I've got that working as well,
http://codepen.io/joshcartme/full/wtkrF.
The js now checks through the navigation links to see if any of them are a
substring of the current path. If a match is found it opens the
corresponding section. I've simulated this by adding a link to the codepen
to the Content section, thus causing the content section to open.
On Tue, Feb 25, 2014 at 4:18 PM, Stephen McDonald wrote:
> That's awesome - I think next we'd need to figure out how to have the
> current section you're on open by default.
>
>
> On Wed, Feb 26, 2014 at 8:42 AM, Josh Cartmell wrote:
>
>> Ok, just added some js, take a look at
>> http://codepen.io/joshcartme/full/wtkrF (that's a different url than the
>> first one because I was running into some sort of caching issue with
>> codepen).
>>
>> JS hides all the dropdowns to start, then clicking a heading either takes
>> you to it's link or opens it's dropdown (if it has any). If you click a
>> heading of an open dropdown it goes to the link of that heading. Clicking
>> a different heading closes any currently open dropdowns.
>>
>> How does this look?
>>
>>
>> On Tue, Feb 25, 2014 at 1:21 PM, Josh B <
>> josh.batche...@wearetopsecret.com> wrote:
>>
>>> I haven't been able to jump back on it. So feel free.
>>>
>>>
>>> On Tuesday, February 25, 2014 2:07:11 PM UTC-7, Josh Cartmell wrote:
>>>
Yeah, although it ended up being a small CSS change it took me quite a
bit of messing around to get it looking like that.
I think putting the selectors in the top bar is a great idea and using
the js to do it sounds like a simple enough solution.
Is anyone working on collapsible nav at this point? I'll take a stab
at it if not.
On Tue, Feb 25, 2014 at 11:25 AM, Stephen McDonald wrote:
> Nice, I had a ton of trouble with the full height and scrollbars so
> glad that's better.
>
> I think the lang and site selectors should probably go up into the
> existing top nav on the right-hand side but to the left of the existing
> buttons.
>
> Easiest way to do that might be at the top of navigation.js where we
> are already moving a bunch of elements around using jQuery rather than
> trying to repurpose the layers of templates between
> django/grappelli/mezzanine.
>
>
> On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell wrote:
>
>> Ok, I took a look and I did create a codepen so that anyone can look
>> at/edit it really easily. Here is the pen (you can edit it by clicking
>> the
>> link in the bottom left):
>> http://codepen.io/joshcartme/full/wIcxp
>> (I hotlinked the css/js files from the dev site, hopefully that's not
>> a big deal Steve).
>>
>> So far my only css change is:
>> .dropdown-menu{
>> overflow: auto;
>> height: 100%;
>> }
>> To make it so there is only a scrollbar if needed and so that the
>> sidebar spans the full page width. I also moved the language selector
>> dropdown to the top and made it an element in the ul.
>>
>> Thoughts?
>>
>>
>> On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald wrote:
>>
>>> Guess not. You can probably just fork and start committing.
>>>
>>> BTW I've pushed up the latest commits to the demo site (
>>> http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can
>>> login to its admin and see the current state of the new menu plus other
>>> visual tweaks - so if anyone who has a moment to try out their
>>> particular
>>> browser (eg I've no idea how this renders in IE) and provide any
>>> feedback
>>> that'd be great!
>>>
>>>
>>> On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell
>>> wrote:
>>>
Well, it looks like you guys worked this out in the meantime (I
haven't tried it yet myself) so I'm guessing jsfiddle/codepen would be
unnecessary at this point?
Thanks Josh!
On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald
wrote:
> Nothing comes to mind but if you have any ideas where we can
> easily (eg with a light touch) improve the usability and look of it
> then
> definitely bring them up!
>
> I had my eye on this style of left-hand nav that the wordpress
> admin uses for quite a while, and recently I saw a comment on reddit
> or
> some site describing Mezzanine's admin + grappelli as looking tired
> and old
> compared to newer CMSes and I couldn't help but agree. So the
> left-hand nav
> is an attempt to improve things there. You might notice I also tried
> to
> increase font sizes everywhere, but I tried to do this in a way where
> I
> didn't touch anything in grappelli which was only partially
> successful. I
Re: [mezzanine-users] Admin navigation
I like where this is headed. I'm not a front-end pro either, but here are
a couple usability things I noticed:
#1: Having "cursor: pointer" on ".dropdown-menu > li" is confusing since
clicking the list-item doesn't do anything. You have to click the anchors
to get any actions to fire. Can you add the click() action to the top
level list-item instead of the anchor? Or both?
#2: I always like to see some kind of chevron indicator next to expandable
items to give me an indication that clicking them will collapse/expand
something instead of take me to a new page.
This is looking great!
--
Cameron Moore
On Tue, Feb 25, 2014 at 6:49 PM, Josh Cartmell wrote:
> Ok, I think I've got that working as well,
> http://codepen.io/joshcartme/full/wtkrF.
>
> The js now checks through the navigation links to see if any of them are a
> substring of the current path. If a match is found it opens the
> corresponding section. I've simulated this by adding a link to the codepen
> to the Content section, thus causing the content section to open.
>
>
> On Tue, Feb 25, 2014 at 4:18 PM, Stephen McDonald wrote:
>
>> That's awesome - I think next we'd need to figure out how to have the
>> current section you're on open by default.
>>
>>
>> On Wed, Feb 26, 2014 at 8:42 AM, Josh Cartmell wrote:
>>
>>> Ok, just added some js, take a look at
>>> http://codepen.io/joshcartme/full/wtkrF (that's a different url than
>>> the first one because I was running into some sort of caching issue with
>>> codepen).
>>>
>>> JS hides all the dropdowns to start, then clicking a heading either
>>> takes you to it's link or opens it's dropdown (if it has any). If you
>>> click a heading of an open dropdown it goes to the link of that heading.
>>> Clicking a different heading closes any currently open dropdowns.
>>>
>>> How does this look?
>>>
>>>
>>> On Tue, Feb 25, 2014 at 1:21 PM, Josh B <
>>> josh.batche...@wearetopsecret.com> wrote:
>>>
I haven't been able to jump back on it. So feel free.
On Tuesday, February 25, 2014 2:07:11 PM UTC-7, Josh Cartmell wrote:
> Yeah, although it ended up being a small CSS change it took me quite a
> bit of messing around to get it looking like that.
>
> I think putting the selectors in the top bar is a great idea and using
> the js to do it sounds like a simple enough solution.
>
> Is anyone working on collapsible nav at this point? I'll take a stab
> at it if not.
>
>
> On Tue, Feb 25, 2014 at 11:25 AM, Stephen McDonald wrote:
>
>> Nice, I had a ton of trouble with the full height and scrollbars so
>> glad that's better.
>>
>> I think the lang and site selectors should probably go up into the
>> existing top nav on the right-hand side but to the left of the existing
>> buttons.
>>
>> Easiest way to do that might be at the top of navigation.js where we
>> are already moving a bunch of elements around using jQuery rather than
>> trying to repurpose the layers of templates between
>> django/grappelli/mezzanine.
>>
>>
>> On Wed, Feb 26, 2014 at 5:33 AM, Josh Cartmell wrote:
>>
>>> Ok, I took a look and I did create a codepen so that anyone can look
>>> at/edit it really easily. Here is the pen (you can edit it by clicking
>>> the
>>> link in the bottom left):
>>> http://codepen.io/joshcartme/full/wIcxp
>>> (I hotlinked the css/js files from the dev site, hopefully that's
>>> not a big deal Steve).
>>>
>>> So far my only css change is:
>>> .dropdown-menu{
>>> overflow: auto;
>>> height: 100%;
>>> }
>>> To make it so there is only a scrollbar if needed and so that the
>>> sidebar spans the full page width. I also moved the language selector
>>> dropdown to the top and made it an element in the ul.
>>>
>>> Thoughts?
>>>
>>>
>>> On Mon, Feb 24, 2014 at 11:02 PM, Stephen McDonald
>>> wrote:
>>>
Guess not. You can probably just fork and start committing.
BTW I've pushed up the latest commits to the demo site (
http://mezzanine.jupo.org/admin/ user/pass: demo/demo), so you can
login to its admin and see the current state of the new menu plus other
visual tweaks - so if anyone who has a moment to try out their
particular
browser (eg I've no idea how this renders in IE) and provide any
feedback
that'd be great!
On Tue, Feb 25, 2014 at 4:33 AM, Josh Cartmell
wrote:
> Well, it looks like you guys worked this out in the meantime (I
> haven't tried it yet myself) so I'm guessing jsfiddle/codepen would be
> unnecessary at this point?
>
> Thanks Josh!
>
>
> On Sun, Feb 23, 2014 at 9:29 PM, Stephen McDonald
> wrote:
>
>> Nothing comes to mind but if you have any ideas wh
[mezzanine-users] If I can't inherit from Form what can I do?
So I tried to create a Model that inherits from Form and got pretty far, but finally it didn't work and i noticed the documentation says this is not supported. Not any reason why though, and it seems to almost work, so i am not sure why. What would be a way to extend the behavior of form then? I want to add attributes to the form and permissions etc. I don't want to duplicate all the form code in a new subclass of Page. Thanks Dave -- 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.
