I know I can step through my database and add url paths to all of my
database entries, but is there a way to have web2py process every
image as an upload (since it's an upload field), and properly store in
the uploads folder for sake of consistency? It would be a lot better
than a year from now fig
> import glob
> for filename in glob.glob('*.png'):
> db.image.insert(file=db.image.file.store(open(filename,'rb')))
>
> On Jan 2, 10:55 am, vapirix wrote:
>
>
>
>
>
>
>
> > I know I can step through my database and add url paths to all of
I read in the docs about request.folder and not changing directory
with os.path. Since I have literally no idea how and what in python is
(and is not) thread safe, is the following thread safe? Do I need to
be using os.path.join anywhere in there?
if not os.path.exists(images+directory+resource):
I'm attempting to test out the CIM XML method of working with
authorize.net, and I'm not entirely sure how to even display the
response I'm getting. I've tried a few tricks I know, but everything
is breaking. I know at this point it's gotta' be a simple thing, but
my unfamiliarity with python (stil
I'm using CIM, not AIM, though.
On Jun 3, 1:25 pm, Massimo Di Pierro
wrote:
> from gluon.contrib.AuthorizeNet import process
>
> look into
>
> gluon/contrib/AuthorizeNet.py
>
> for examples
>
> On Jun 3, 12:03 pm, vapirix wrote:
>
>
>
>
>
>
>
Brilliant. :)
Thank you, I'm going to give this a shot.
On Jun 3, 3:33 pm, howesc wrote:
> skip the XML, use SOAP. that's my solution:
>
> profile_id = 42
> merchantAuthentication={'name':api_login_id,
> 'transactionKey':transaction_key}
>
> from pysimplesoap.cl
I've looked for a good solution to this, and so far it seems the only
answer is to roll my own method of registration. I just want to add a
single "key" field more or less to user registration, so only people
who know the key may register. Is there any simple way to integrate
that without implement
The only problem with that is that then the clients will be able to
edit that in their profile. =D
It's ok, I'll just roll my own registration page, it's not much work.
On Aug 10, 11:06 pm, pbreit wrote:
> Might be easiest to display an additional page before the registration page.
>
> Otherwise
Sure, but then how can I have them input the key on registration if
writable is false? =D
On Aug 11, 10:41 am, Marin Pranjic wrote:
> They will not if you set writable = false.
>
> Marin
>
> On 11 Aug 2011 17:16, "vapirix" wrote:
>
> The only problem with that i
Brilliant. This is why I check these boards. =D Thank you, Marin.
On Aug 11, 10:51 am, Marin Pranjic wrote:
> Make it True on registration form, and false in login form.
>
> If reguest.args(0) == 'register': db.auth_user.xyz.writable = true
> else: ...= false
>
> On
So I'm attempting to set up the usage scenario of:
domain1.com -> load app 1
domain2.com -> load app 2
etc. etc.
I need domain1 to NOT have access to app 2, 3, 4, 5, etc.
That all works using the router's "domain" settings. Obviously you run
into the problem of: domain1.com loads app1, but domai
OR can maybe somebody point me in a different direction to achieve the
same thing without a hilariously complicated config process that I
won't want to do every time? =)
On Aug 16, 5:07 pm, vapirix wrote:
> So I'm attempting to set up the usage scenario of:
>
> domain
in. I'll look at it when I get home later.
>
> On Aug 17, 2011, at 12:57 PM, vapirix wrote:
>
>
>
>
>
>
>
> > OR can maybe somebody point me in a different direction to achieve the
> > same thing without a hilariously complicated config process that I
>
tunately I'm using wsgi, and I have no idea how I would go
about setting up your separate application directory idea. If anybody
DOES know, I'm all ears. =)
On Aug 17, 10:46 pm, Jonathan Lundell wrote:
> On Aug 17, 2011, at 4:29 PM, vapirix wrote:
>
> > That would be truly ex
14 matches
Mail list logo
