Salut Benoît
Sorry for the late reply.
On 06.10.2010, at 17:22, Benoit Segaert wrote:
> But I also have to add a Date in product (Publication date for my books).
Without looking at the code I would say you have two options there:
a) extending the Product class
-> This will help you in your current special case
b) let the Product class implement a Map interface
-> This might help in an arbitrary case (e.g. for color, size etc.
attributes)
I wonder how KonaKart or other e-commerce systems solve that problem.
>> 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).
We might look at a PayPal integration in about a month.
>>> 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.
If I recall correctly you pass some generated + encoded ID to the payment
service, right? And you will get an encoded ID back. I think last time I did
this I simply left the shopping cart in the session and was able to pick it up
after the control control came back from the payment gateway. This way I did
not have to save any unconfirmed shopping cart.
>>> 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?
If I understand you correctly you need to be able to change the price category
on a cart which is already containing products? The cart does not support this
at the moment. On the other hand that should not be overly complex to
implement. Simply update all cart items in the carts setter method of the price
category.
Let me know if you have any show stoppers. As mentioned above we will most
likely continue our work on the shop in about a month.
-will
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
