On Tue, 2009-05-19 at 02:38 -0700, Ken Wasetis [Contextual Corp.] wrote:
> Tim,
> 
> That's really great news.  A for-pay subscription option for a
> remember/membrane-based, workflowable (?) member registration process
> is something a lot of people need.  I've had clients in the past ask
> whether something like this existed already for Plone, and at the
> time, there really wasn't anything to just plug-and-play with, but
> hopefully, you're new getpaid-enabled member subscription will
> continue to get improved by others who leverage it.  I hope to be one
> of them ;)  Great job!

Thanks, I'd like to release it as open source. Just need to confirm with
the client that this is ok. I'm sure it will be, though, as I did ask
them this in the past and they were positive about it.

The only things that I'm not too happy about in the implementation at
the moment are:
      * I have hardcoded the mappings in config.py for the vocabulary of
        subscription levels (selectable from the registration page and
        member prefs) and the mapping of these to prices and associated
        roles.
      * The roles are also hardcoded into rolemap.xml.
      * When the payment is successfully 'charged' I assign the local
        role to the user, which can then be assigned permissions via
        workflow of course. Not sure if this is the best approach
        either?
      * The member has to be granted logon access to the site in order
        to allow the member object to be 'purchased' but I have an event
        subscriber for initial logon that redirects them straight away
        to the payment processor (in this case PayPal), though, they do
        theoretically have access to the site at this stage. I'll need
        to create some tests to check this properly.

I've also created a separate permission for viewing the user profile as
the client wanted anonymous visitors to the site to be able to see
members in search results but not be able to view the profile (just
created a browser view with this permission assigned to control this).

I've created functional tests for the main usecases but obviously it
could do with more.
> 
It is hard to make something like this very pluggable so would be good
to hear some ideas along these lines.

Thanks,
Tim

> Ken
> 
>         -------- Original Message --------
>         Subject: RE: Buyable content with prices for anonymous and
>         logged on
>         users
>         From: Tim Knapp <[email protected]>
>         Date: Tue, May 19, 2009 4:33 am
>         To: [email protected]
>         
>         
>         Hi Ken,
>         
>         Thanks for this. I guess I've just gotten lazy as I need to
>         complete the
>         project I'm currently working on this Thursday and I was
>         hoping to use
>         an existing package for this functionality. I was just going
>         to create 2
>         separate pieces of content (hackish I know) and use a custom
>         view and
>         perhaps workflow to display the right one to user. This is the
>         game plan
>         at this stage, quick and dirty.
>         
>         As an aside, I've just about completed my pay-for-subscription
>         package
>         which incorporates Remember and PloneGetPaid. It also allows
>         users to
>         not only register with the site and be whisked away to pay for
>         their
>         subscription but also to renew their subscription. Currently
>         its
>         designed specifically for PayPal but it shouldn't be too
>         difficult to
>         get it going with Google Checkout and really any payment
>         processor - it
>         just specifically displays a 'buy now' button to the user when
>         they
>         first logon, but there's no reason the user couldn't instead
>         be
>         redirected to the checkout page or whatever.
>         
>         Thanks,
>         Tim
>         
>         On Tue, 2009-05-19 at 00:33 -0700, Ken Wasetis [Contextual
>         Corp.] wrote:
>         > Tim,
>         > 
>         > There's an example product named GetPaidJob that Kapil did
>         the initial
>         > work on for us that's in svn. You could follow this model
>         for
>         > extending whatever content type you want to have its own
>         custom
>         > pricing based upon whatever calculation and upon whatever
>         properties
>         > you want. Look at browser.py and getPostingPrice() method.
>         We could
>         > have coded whatever complex algorhythm we wanted to in that
>         method and
>         > set it as the price on the item.
>         > 
>         > See the example product at: http://tinyurl.com/prwdsb
>         > 
>         > I know it's a bit of work to create an entire separate
>         product that
>         > extends some existing type (or adapts it and adds a custom
>         pricing
>         > method via the browser.py), but it's at least doable.
>         > 
>         > For more flexible per-object pricing, it might be nice to
>         adapt
>         > IBuyable to support a PythonField (as PloneFormGen does)
>         that could
>         > optionally be used rather than the simple numeric entry
>         field for the
>         > price, so that a site admin could just plug-in a quick
>         Python
>         > line/block/script call that provides the ad-hoc pricing
>         algorhythm for
>         > that particular buyable content item (but not necessarily
>         affect
>         > others of the same type), but maybe also allow (in a Site
>         Setup
>         > configlet) the ability to provide the same and apply it to
>         all
>         > instances of content items of that type. Just spit-balling
>         here, but
>         > I think it'd be great and I don't think it'd be too
>         difficult to do. 
>         > 
>         > I haven't kept up with getpaid in a few months, so maybe it
>         already
>         > has been?
>         > 
>         > Ken
>         > 
>         > 
>         > 
>         > 
>         > 
>         > 
>         > -------- Original Message --------
>         > Subject: Re: Buyable content with prices for anonymous and
>         > logged on
>         > users
>         > From: Rob LaRubbio <[email protected]>
>         > Date: Mon, May 18, 2009 10:10 pm
>         > To: [email protected]
>         > 
>         > Nope, getpaid.discount is fairly limted in what it can do.
>         > Out of the box it lets you mark anything for sale on your
>         site
>         > as 'discountable', 'discountable w/ code', or 'buy x get y'.
>         > 
>         > Discountable is for temporary price reductions. It shows the
>         > new lower price to all visitors. You can set the price as a
>         > pct. off, or dollars off
>         > 
>         > Buy x get y I'm not that sure about. I didn't look into it
>         > when I was adding the discountable w/ code. I think after
>         you
>         > buy a certain amount the next one is free.
>         > 
>         > Discountable w/ code allows you to set a code and a price
>         for
>         > the product for users with the code. Only users who enter
>         the
>         > code in the cart get the discount.
>         > 
>         > Hope that helps.
>         > 
>         > -Rob
>         > 
>         > On Mon, May 18, 2009 at 12:48 PM, Tim Knapp
>         > <[email protected]> wrote:
>         > 
>         > Hi,
>         > 
>         > I've got a requirement whereby the client wants a
>         > piece of content to
>         > have 1 price for logged on users and another for
>         > anonymous - can I use
>         > the discount package to achieve this?
>         > 
>         > Thanks,
>         > Tim
>         > 
>         > 
>         > 
>         > 
>         > 
>         > 
>         > 
>         > > 
>         
>         
>         
>         
> 
> > 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"getpaid-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to