This has been a long time coming, I do not doubt that there will be more work, but now it is main clean ups. I feel all the functionality is there and really more than anything just needs hammering on.
One of the things that I was concentrating on when doing any bug fixes was to start doing them as Test driven development so I would create a test and then from the test fix the issue. This means that when the new PIFR system comes I will turn on the testing for e-Commerce so that everytime a commit is done, all the tests will be run and everytime a new patch is uploaded it will be applyed and tested so when we get to a new patch we know that it applies, and that it passes all the tests.
There is only a few tests ATM but as time goes by more will be developed, and I am getting faster at developing them so I will add them as I find tests to add, and as I fix issues. If you have any ideas for tests please create an issue and someone will get to them. I would prefer to have too many ideas for tests than not enough.
With all the new and much better things in the Drupal community has to offer I always things how much better it is being within the Drupal community. It is much easier to leverage what we have here than have to set up and maintain my own systems outside the Drupal community.
One of the main areas that I have been working on is to move all the theme_*() out into template files. I have completed the ec_cart module and I am working on others. Anyone wants to help please jump in.
Also the decision to have views do all the reporting is the greatest thing ever. I added a few lines of code and now ec also leverages the drupal search system to allow full text based searches of invoices and receipts. Then added some minor amounts of code for views and we now have a text based search. There were some sticking points with this as having a whole heap of exposed filters at the top of a report is very ugly. Now with some creative form and themes I have them all hidden away in a collapsible fieldset.
I also have a podcast that I am putting the finishing touches on and hope to release some time this week.
See http://drupal.org/node/414432 to download and see more information.
Comments
Upgrading from EC3.x
Very nice work, there are much structural improvements in EC4. Still, there's a lot of work to do in porting payment gateways, postage calculations and grasping all the new concepts.
Can you tell us what the challenges for existing EC 3.x sites in upgrading to EC 4.0 are?
Upgrading
ATM not all the code is there is get a current installation up from 3.6 to 4.0, but that is mainly because I am not 100% sure how to handle the change in module names. But by the time the final version is done I will have this worked out.
Payment Gateways.
Some of the payment gateways have been upgraded, but other have not. I know that from my experience of upgrading the eWay and Authorize.net the new API that I created has made a huge difference in making it so easy to build the payment gateway. The biggest thing is that there is actually very little ec code in a payment gateway and all you really need to do is concentrate on working out the best method of talking to the payment gateways api.
I did some investigation into the the eWay payment gateway and less than 30% of the code was actually talking to Drupal and e-Commerce, the rest was actually talking to the payment gateway.
Also the good thing is that you can take advantage of more features in payment gateways like receipt reversal, inline payments (collecting the money before the transaction is created) and before the final release recuring payments.
Additional Charges
This is a new area which I just resently finished developing. You can still create the charges the old way, but you can now use ec_charges (Additional Charges) to build up the charge without really needing to create code. Basically with a few clicks you can create any basic charge, and because of the plugin system you can extend this very easily to be able to create charges very easily. I need to build up a calculation to calculate the charges for shipping with something like UPS, FedEx or even AusPost just to make sure that I have my thoughts together right, but it should not be too much of a problem.
As I said there is still plenty of work to do, and I am implementing a couple of sites so I am getting closer and closer by the day.
If anyone can help please do, and I will make sure that it is going as good as possible. Even take on the big take of getting the upgrade to work.
Thanks.
--
Gordon Heydon
--
Gordon Heydon
No e-mail sent?
Hi Gordon, thanks for this fabulous module. I've got a problem though, when a customer buys anything at my store, there's no e-mail sent either to him or to me. I've noticed that the ec_mail module does not exist in this last version of e-commerce. So my question is simple : how can I and the customer be notified when a transaction is completed? (BN I haven't configured any method of payment yet).
Thanks very nuch in advance,
Patrick
Hi, ATM I have not put any
Hi,
ATM I have not put any email rules into e-Commerce. I am going to be adding something into the next rc. But this is no longer handled by e-Commerce but is done in rules and you can configure yourself when it is going to happen.
--
Gordon Heydon
--
Gordon Heydon
Mostrar contenido a determinados usuarios.
Hola, que modulo debo utilizar para mostrar paginas a determinados usuarios.
ejemplo tengo page1, page2, page3, quiero mostrar page1 y page2 a invitados y page3 solo a usuarios registrados.
con que modulo o como lo hago, gracias.
Node Access
Puedes ver información en: http://drupal.org/project/nodeaccess y otra en: http://drupal.org/node/270000
Saludos.