I can't see how mezzanine has anything to do with ddos. But you can safely
set this to true. You credit cart processor will stop the fake orders. I
haven't had issues with this.
On 31/03/2015 1:19 am, "Wesley" wrote:
> Hi all,
>I just have a question here regarding SHOP_CHECKOUT_ACCOUNT_REQUI
Just ignorance on my part Mathias
I thought in my head 'I am searching the *total* Mezzanine code base', when
in fact I neglected to include the other parts such as filebrowser_safe.
Thanks for the heads up.
g
On 31 March 2015 at 00:38, Mathias Ettinger
wrote:
> Why searching for a filebrowser_s
Awesome Josh thanks
g
On 31/03/15 04:41, Josh Cartmell wrote:
a) no, they look good on the iPhone because they are being resized by
css, so it's just the browser rendering a larger image smaller
b) potentially more customization or easier logic separation between
mobile/desktop, realistically I
If that snippet of code is really wrapped in ''' then you have essentially
made it a comment. Maybe try removing those?
On Sun, Mar 29, 2015 at 9:59 PM, 传承 wrote:
> I want to use the function of account approval
>
> I config as follow
> '''
> ACCOUNTS_APPROVAL_REQUIRED = true
> EMAIL_BACKEND =
a) no, they look good on the iPhone because they are being resized by css,
so it's just the browser rendering a larger image smaller
b) potentially more customization or easier logic separation between
mobile/desktop, realistically I wouldn't recommend using them as responsive
websites seem to be b
Hi Pushkar, for you and anyone else who comes across this, you do not have
to delete your db and migrations to add fields from EXTRA_MODEL_FIELDS
The correct way to add the image field to BlogPost would be:
python manage.py schemamigration mezzanine.blog --auto --stdout >
path/to_store_the/migrat
Hi all,
I just have a question here regarding SHOP_CHECKOUT_ACCOUNT_REQUIRED.
I see that this guy defaults to False, thus, customer can finish one
checkout process without signup/sign in.
Actually, many customers like this style, and I tried to set this setting
to True, then, many customers s
Why searching for a filebrowser_safe issue in the mezzanine code base?
The issue is thrown by the delete function in filebrowser_safe.views but
there are 2 possible situations that can lead to this message. Either the
path of the file failed to be normalized or the OS failed to delete the
file
Did you try what I suggested for :
https://groups.google.com/forum/#!topic/mezzanine-users/CBqb6srpmqU ?
The issue seems the same: using a relationship field with a string
parameter in the EXTRA_MODEL_FIELDS both relies on the class_prepared
signal. Re-raising it should help.
Le vendredi 20 m
