Symphony.

We could extend the status field to be used as a payment processing extension with external libraries for the different payment options.

I noticed you created an empty repository on Github. Is this where the complete ensemble will go? I guess we have to create a new extension/repository for the payment extension. This is how I see the timemap:

1. Create default Symphony Setup
2. Think about a setup for multiple categories/sub-categories/products sections and implement it.
3. Create shopping cart system to add products to your cart (I guess the shopping cart extension is good enough for this)
4. Think about a checkout-system (required login? anonymous checkout? which extension to use for member management?) and implement it offcourse
5. Process payment (vague cloud with thunderbolts and lightning)

Optional things could be:

• Login to check your order status / change your details.
• Order tracking (this would be a whole other extension, possible future work)
• Pop a beer when the thing is finished (not quite optional)

I think step 1 to 3 or 4 could already be implemented. Now we only need volunteers so we can get started with this project and divide the tasks on who is going to do what. Anyone?

Yeah, I created the repo in a rush attempt to get busy, but other things became a priority.

I have a data model laid out for the sections (attached), with a list of required extensions for the sections only (incomplete). It relies on the Members extension to do the customer bits, so I guess basic build until that is available.

With the little time I have, I've been looking at whether each extension is compatible with 2.2 but must say I haven't got far with that either (lame).

Lots of work to do, but have a look at the document...

Attachments:

ecomms-data-model.xls

This is totally off topic but bear with me please.

@designermonkey

In your .xls on Page Layout sheet you have:

/galleries              
  /$pagi                
    /$gallery         ||  Redirects to /gallery/$gallery        ||  "From: //galleries/([a-z-]+)  ->  To: /gallery/$1"
    /$gallery/$image  ||  Redirects to /gallery-image/$gallery  ||  "From: //galleries/([a-z-]+)/([a-z-]+)  ->  To: /gallery-image/$1/$2"

What's with the redirects? Why do you use them?

Well, I'm a sucker for canonical URLs and I intend to use the URL Router extension to do some heavy work rewriting urls for me.

I want the user to be able to go to /gallery and see a list of the first paginated page of galleries. From that URL, if they go to /gallery/2 (or maybe /gallery/page-2 they see the second page etc etc.

But in my insane canonical clean world, I want them to also be able to go to /gallery/my-gallery and see a single gallery page of images, and thus /gallery/my-gallery/my-image for an image page with details about that image.

The regex's will determine whether it is an 'integer' (or page-'integer') (pagination) or a 'word' (gallery).

To be honest, I'm not sure whether it will actually work yet. I may have to beef up the extension to allow for this kind of behaviour. Nick has done similar before. I also want to incorporate the Root Page Params extension too, so my psuedo pages come straight off the root, but both together may be an infinite loop nightmare.

Still, I dream...

I heavily believe in making things as simple and clean for the visitor as possible, irrespective of the complexity in the development.

Edit: I once got told that something I wanted to do like this with URLs couldn't be done at all, by a guy who had been doing coding for near 20 years, and I proved him wrong with Symphony. I hate being told I can't do something. After all, it's only logic...

Thanks for explaining it. It's good to see how others put it.

I just thought I would add my 2 cents worth on the payment gateways, as we are about to scope out a subscription-based service using symphony cms.

I agree with Comment #17 - I was heading towards building something like the email gateway extension, but for payment gateways. At this point, it is just an idea, and may not be viable. Thoughts?

I started with a similar concept awhile back and produced PGI (Payment Gateway Interface) Loader. I hooked it up with Securepay and eWay. The idea was to have one interface that could be used in extensions that didn't rely on a particular gateway.

Perhaps it's useful as a base? Either to be forked or just for inspiration.