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,
+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/m
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
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).
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
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 thi
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 w
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.
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
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_KE
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 b
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 co
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 dr
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
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
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 codepe
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 a
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?
18 matches
Mail list logo
