This is properly because the webservice isnt updated but epay is just sending the data anyway and break old implementations. That might be my quess. Sp try and update the webservice reference and see if that fixes it. And then maybe call ePay and tell them they broke it :)

Hmm okay, Ill try and update the webservices on the payment providers and see if it works, ill ofc send a pull req if it does.

Else i might need a bit more info if im to call them.

Hmm so i forked the 1.x branch (https://bitbucket.org/Rasmusfjord/tea-commerce-tea-commerce-payment-providers) and i have update the reference, both on epay and authorizenet.

But now i get this error ?

ethod 'GenerateForm' in type 'TeaCommerce.PaymentProviders.AuthorizeNet' from assembly 'TeaCommerce.PaymentProviders, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.

[TypeLoadException: Method 'GenerateForm' in type 'TeaCommerce.PaymentProviders.AuthorizeNet' from assembly 'TeaCommerce.PaymentProviders, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.]
   System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type) +0
   System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase) +73
   System.Reflection.Assembly.GetType(String name) +22
   TeaCommerce.Data.PaymentProvider.GetPaymentProviders() +508

I just cloned the 1.x branch. All builds

Sorry there friend, its me who's not telling the full story. 

Ive updated the services, build it and uploaded the new paymentprovider dll,when i then tries to enter edit upon an order the above error is what im getting.

You dont have a custom provider in your own website project that isnt build with the new payment provider api?

Nope :/

We only use epay, I can also see and remember that Ive done the same procedure when viabell bugged the payment provider on the 5th of december 2013. We dont even reference the TeaCommerce.PaymentProviders.dll in the small class library.

Last time i did it i just uploaded a new TeaCommerce.PaymentProviders.dll after updating the services and it worked.

will try with 1.4.4.5, we are running 1.4.4.4

It worked :) 

Thanks again!

I thought I had it working but i didnt. 

So here is what ive done so far:

1. Ive updated Teacommerce to 1.4.4.5 so its running all the current dlls.

2. Ive forked the 1.x branch of the Payment provider.

3. Updated references, set to release and build.

4. Uploaded the new TeaCommerce.PaymentProviders.dll

5.it crashes with the this error http://pastebin.com/XVZL5fyp

6. I reupload the 1.4.4.5 TeaCommerce.PaymentProviders.dll

7. Now i can access the order again that i couldnt access before.

I cannot seem to find a pattern in it.

It could be because the TC dll files in the payment provider project isnt updated to the latest of Tea Commerce. V1 is pretty old so cant remember all the things and how it works :) But I dont think the latest of Tea Commerce is committed and build using the v1 branch of the payment providers. So it could be that we should release an 1.4.4.6 version :)

Kind regards
Anders

It would be awesome :)

And yeah it is pretty old i know, but its hard to convince the customer to "upgrade/redo" the site for the upgrade of software :/ 

You need to do that with Umbraco 6 and 7+ projects as well :)

Im a big teacommerce fan and user but i do not totally agree.

The TC 1 >> 2 process is largely a redo of the webshop, and an hourly expensive one if there is a few custom elements(discountsystem/coupons/deducting from the backend/postdk integration and a few more lovely features :) ).
(Believe me ive tried a few times so far)

While upgrading umbraco is maybe a one - four hours job if its a complex solution(and here im not talking going from 6-7 thats a whole other story hehe ;) )

But no mistake im still really really happy that your helping us out, its just hard to put to numbers what they will recieve for the money/time put in even if I take a cut because i wanna upgrade them.

BTW we are building the post DK integration thing for TC, and it will be usable for tc 2 aswell, remember talking to you about it :)

is working on a reply...