Will,

>Salut BenoƮt
>
>On 01.10.2010, at 16:30, Benoit Segaert wrote:
>
>> How do you propose to extend the module?
>General rule of thumb: 
>- If it's useful for all and configurable propose it as patch.
>- If it's only useful for your special case simply subclass 
>DefaultShoppingCart and ShopPage
OK

>E.g. the integration of an external payment service (as Ogone) in the checkout 
>process:
>- If you can configure what payment service handler class to use in the shop 
>configuration, that would be a great patch
>- If you want to hardcode the payment service in the checkout process, I would 
>suggest, you subclass the ShopPage
>
>> We need the following functionalities:
>> 
>> 1) We have to add some fields in the Addresses (VAT number for the 
>> invoicing). How to extend the DefaultShoppingCart?
>> It is Used in ShopPage. Do I extend the ShopPage?
>
>Do you mean the VAT number of the shop (seller)? That should be configured in 
>the shop configuration. Then again you're right: It should also be stored in 
>the shopping cart so that your old invoces are not changed in cases where the 
>shop changes VAT number. So I guess that would be a useful patch.

The VAT number is used to generate an Invoice after the payment.
I will see what we can do.
But I also have to add a Date in product (Publication date for my books).

>> 2) Validation of the form fields.
>> I can propose a modification of the ShopPage.
>
>Sure. As you can see: there are already some validation methods. But the way 
>this is done at the moment sucks. One should be able to configure what values 
>should be validated at what point. Then again this configuration could be a 
>bit complex with multi-step checkout processes. If you have a good solution 
>for this please do propose a patch!
>
>> 3) Add a payment system [Ogone], I have to generate an URL and redirect to 
>> the Ogone site after the "Check your order" step.
>> We can extend the ShopPage.
>
>As said above: A good solution would be to be able to configure a payment 
>service handler class so that it would work with Ogone, Saferpay,...
Ok, I will see what is possible to propose (payment service handler class in 
the eshop config).

>> 4) With a payment system, we have a two-step confirmation. Save the shopping 
>> cart with a flag Confirmation=no in Data module, call the payment system and 
>> set Confirmation=yes when Payment system call the eshop back.
>> We will develop another page for the Ogone confirmation which will change 
>> the status and display the confirmation page (the page can not contain a 
>> parameter command).
>
>Do you need to save the cart in the data module before you get the reply from 
>the payment system?
If you want to avoid that a payment is done without any information about what 
has been bought.
Because it is possible that the user buys something and an error occurs during 
the return from payment system.
But this security could be configured if we have an additional flag 
(confirmation=yes).
I am not sure that we will implement that for my client.

>> 5) The clients have different pricing depending of a category (member, 
>> non-member...). I will use the pricing category but I have to update the 
>> Shopping cart paragraph for the selection of this category and use it for 
>> the cart update command.
>> The extended ShopPage will take into account this modification (+ addition 
>> of this feature in extend shopping cart).
>
>Well, you can already set the price category when you create the shopping 
>cart. What is missing there for you?

I have to select the price category from the Shopping Cart and update all 
product price depending of this category.
How can I activate this functionality?

>> What do you think?
>
>I most likely won't have the time to get the shop "ready for prime time" in 
>the next few weeks, so your extensions / patches / work is more than welcome!
>
>-will
>



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to