Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
So the site was showing all the Variant data fine in the back office this morning.
Then this afternoon, the Variants tab won't show any variants?
On the front end of the site, there are no variants in the drop-downs either.
I see this on the back end though when I open the Variants tab.
Variants not being populated:
Do you have any errors in your error log?
I can see:
System.NullReferenceException: The property editor with alias TeaCommerce.VariantEditor does not exist
When I go to DataTypes and select the Variant Editor I get:
Server error: Contact administrator, see log for full details.
Failed to retrieve data for data type id 9325
Hmm, so then it sounds like Umbraco is failing to locate the Varaint property editor for some reason.
Have your tried an app pool recycle to see if that brings it back? If it does, then it sounds as if it's being lost in memory. If it's not found after recycle, then is it possible the DLLs have reverted at all?
Trying a restart now.
That bloody PaymentProvider.Stripe I can see back in there, just deleted it out again.
I'll check the DLLs are 3.1.4 again.
Nah, no change Matt.
Rebooted, made sure those DLLs are correct.
Still the Variants not showing :(
Are there any other references to TC in your log file? Strange that it was able to find it and then it's not 🤔
Umbraco.Core.Models.DataTypeDefinition ---> System.InvalidOperationException: Could not find property editor with alias TeaCommerce.VariantEditor
at Umbraco.Web.Models.Mapping.PreValueDisplayResolver.Convert(IDataTypeDefinition source)
at Umbraco.Web.Models.Mapping.PreValueDisplayResolver.ResolveCore(IDataTypeDefinition source)
at AutoMapper.ValueResolver`2.Resolve(ResolutionResult source) in c:\dev\AutoMapper\src\AutoMapper\ValueResolver.cs:line 17
at AutoMapper.PropertyMap.<ResolveValue>b__6(ResolutionResult current, IValueResolver resolver) in c:\dev\AutoMapper\src\AutoMapper\PropertyMap.cs:line 127
at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func)
at AutoMapper.PropertyMap.ResolveValue(ResolutionContext context) in c:\dev\AutoMapper\src\AutoMapper\PropertyMap.cs:line 127
at AutoMapper.Mappers.TypeMapObjectMapperRegistry.PropertyMapMappingStrategy.MapPropertyValue(ResolutionContext context, IMappingEngineRunner mapper, Object mappedObject, PropertyMap propertyMap) in c:\dev\AutoMapper\src\AutoMapper\Mappers\TypeMapObjectMapperRegistry.cs:line 119
--- End of inner exception stack trace ---
Is there anything to do with Umbraco's TypeFinder not being able to load the dll?
Even going to create a New DataType it's missing in the drop-down to create a new one?
Yea, it will be. Ultimately Umbraco isn't finding the provider at all so it's not going to be available anywhere until this is resolved.
Maybe check file permissions on the TeaCommerce.Umbraco.Configuration.dll too as this is where the property editor lives and should be found by Umbracos type finder.
Can I check file permissions on a DLL in Azure? Not even sure how to?
And what file permissions should be set?
yea, I'm not sure either. Not sure why it would be blocked, but sometimes they can be on regular file systems, I'd assume they can be in Azure too 🤷♂️
It seems to be doing the same locally.
My local version is connected to the Live DB on Azure.
Do you think it could be the DLLs? Can I download the starter Kit, upgrade to the latest version and copy over the DLLs in Azure?
Clutching at straws here, no idea why it would just stop working?
What version of Umbraco are you using? It can sometimes fail to load a DLL if the DLL it's trying to load was compiled against a newer version of .NET, I don't think that would be the case though here as we never compile against a newer version.
In your local setup, if you right click on the TeaCommerce.Umbraco.Configuration.dll dll and go to properties to see if the DLL is saying it's blocked?
Umbraco version 7.15.3 assembly: 1.0.7180.24662
Right clicked the DLL, can't see anything saying Blocked, I can see checkboxes for Hidden and Read-Only, both not selected.
And what version number is the TeaCommerce.Umbraco.Configuration.dll reporting?
Also, can you check in App_Plugins/TeaCommerce/package.minifest so see if there is a property editor defintion for TeaCommerce.VariantEditor? If there is, there shouldn't be, so remove it. Just wondering if there is a conflict between the package manifest and the definition that is in the DLL.
File Version: 3.3.7207.28303
Product Version: 3.3.3
name: 'Tea Commerce: Store picker',
name: 'Tea Commerce: VAT group picker',
name: 'Tea Commerce: Stock management',
Ok, your manifest is fine, but your DLL version isn't.
The DLL version in the 3.4.1 distro that we upgraded to yesterday has a TeaCommerce.Umbraco.Configuration.dll version number of 3.4.1, so I think your DLLs have gotten out of sync. Something is resetting your DLLs.
You can reinstall TC on your local to see if that fixes it locally. If it does, then you know it's because your DLLs are out of whack. Then you need to chase down why.
Ok great, how can I re-install TC? When I try to install from the local package it says - Package already installed
Is there another way to install it?
Can I un-install and then re-install? Hopefully, that won't break anything doing it that way?
Hmm, I think you can modify the App_Data\packages\installed\installedPackages.config file, locating the entry for TC and changing it's version attribute to be like 3.3.9 for Umbraco 7. I think that should allow it to be reinstalled.
3.3.9 for Umbraco 7
If you have your code + bin folder in source control, it might be worth committing it at that point and then you'll be able to know if something else trys to reset the DLLs later as it'll say they have changed.
Matt you are a STAR!!
I think I'm going to retire after this site, I feel thick as mince!
That sorted it, DLLs out of sync.
On local publishing to Azure somehow loads the old DLLs?
Not sure why, even after upgrading locally, hitting publish seems to still somehow send the old DLLs up to Azure.
Ive had to FTP them up and not Publish from VS.
Hmm, I’d double check you don’t have a reference to the dlls in a lib folder as that could override them. I’d also maybe clear out your publish folder I think is in the obj folder in case it’s not getting copied to that to deploy.
Anyways. Glad we were able to figure it out 👍🏻
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted