Hi Rusty,

Can you please confirm that the error i am experiencieng is related and has been fixed?

Do you have an idea when 2.4.0 will be released because sure i need to update it if so.

Thank you in advance.

Cheers.

Is it safe to compile 2.4.0 and replace the dll? This is a real pain.

Same here. This is a show stopper if anything :)

The 2.4.0 release is not packaged but all the code is available in the merchello-dev branch. Im out of town at the moment so can't package a patch release for you -

You can pull the dlls from MyGet

https://www.myget.org/F/merchello/api/v3/index.json

But you will need to merge in the App_Plugins/Merchello files since the have been back office updates. You can grab those from the FastTrack.Ui project in the merchello-dev branch.

It's interesting to that this is occurring frequently in you environment- as it has to do with cookie size. How many cookies are present in you domain? Are you saving info to the customer context data?

Thank You. Will try that.

Just using the default FastTrack as base. Nothing custom (yet).

Hi Rusty,

I cannot understand how I can update through the https://www.myget.org/F/merchello/api/v3/index.json.

Can you please guide me?

Thanks.

I can help. You use Visual Studio? Then use options and select nuget sources. Add this link (all of it). Then you can simply pick this source when updating nuget packages.

Works so far, jippiee, no issues with Backoffice yet. One head ache less.

Thanx Merchello

Works even for me.

Are there any issues you encountered so far?

Not yet but I have some stuff left to implement :). This was particulary nasty since it occured on the testers browser, making it very hard to track down.

I don't know why the cookies became so huge. I just used the default FT as a base.

Is this a new method?

Hi Rusty,

After I Upgraded to 2.4.0 as explained, now I have a controller taking from MerchelloSurfaceController and CurrentCustomer, when I logged in, is being considered as Anonymous.

Any help would be much appreciated.

Hi Marcus,

Can you please check if you have a controller taking from MerhcelloSurfaceController, the CurrentCustomer is always Anonymous even if you're logged in?

Thanks

I will look for that.

Any news Marcus?

Not yet. Working with angular stuff right now but I am soon back to this so I will check more closely.

Any response from Merchello Team?

Not Yet.

Did you find anything in the issues db? Maybe a good case for a new?

Marcus,

Do you actually experiencing the same? Or is it my problem? Always the currentCustomer as Anonymous?

I should add that I do not use the Account feature at all atm. Most purchases are done without logins.

Hi Marcus,

How have you gone through the CustomerContext after the 2.4.0 update?

Thanks

Hi Simon,

I have not had any issues what so ever with the CustomerContext not converting correctly to a know Customer with the membership role change. The customer conversion strategies have also been extended to ensure that values stored in the CustomerContext data are also persisted between customer types and tested ... e.g. everything looks good on my end and I have not been able to replicate the issue since the process of saving the data has changed ...

Would love help tracking this down further if there is still an issue and you have any insight - ATM it appears to be working well from my end.

Hi Simon,

The members are all stored in Umbraco - so in other words, Merchello is not "actually handing the authentication". What happens internally, is Merchello asks Umbraco the status of the member and if it notices that Umbraco says the member is logged in and Merchello is using an IAnonymousCustomer in the context, a conversion process is triggered to create a ICustomer and map the basket and context data to the new class. On log out, a NEW IAnonymousCustomer is created (e.g. does not go back to the original).

Thoughts:

Did you also update the FastTrack dlls?

What version of Umbraco are you using. I've tested back to Umbraco 7.5.2 and was going to upgrade to 7.5.8 before releasing.

The only thing I can think of is that the CustomerContext is not a true per request singleton (something that we are working on revising in v3). So if you are instantiating the context twice within the same scope and using it for different purposes .... maybe?

However, if you are using the property value from the MerchelloSurfaceController consistently, you would never see this.

https://github.com/Merchello/Merchello/blob/merchello-dev/src/Merchello.Web/Mvc/MerchelloSurfaceController.cs#L58