Are there some extra steps required when upgrading uCommerce or I just have to install the new package and that's it? I did this upgrade (1.0.5.2->1.1.0.1) because I wanted to have the DIBS integration and it looks like it's there, but I noticed one issue: when choosing price groups for for DIBS service, I can choose price groups that I have been deleted some while ago and which are not showing up under the PriceGroups section. Or is this just a small bug?
If you've registered custom pipeline tasks you might want to replace the new pipeline configs with your previous one (there's a backup sitting next to it in the /umbraco/ucommerce/pipelines folder).
The deleted price groups should not be displayed. I'll make sure and fix that.
You just install uCommerce on top of what you've got already. uCommerce will pick up that you're doing an update and will only update the areas necessary. Any files modified will be backed up.
If you've registered custom pipeline tasks you'll need to register them.
Andrei, thanks for reporting this. The issue here is that Umbraco uses a very simple mechanism to determine which right-click menu items should be executed (a letter as identifier essentially) and we've apparently selected a letter which is already being used. I'll go ahead and change this in the release I'm rolling out tomorrow.
We have upgraded ucommerce from 1.0.4.1 to 1.2.0.0 and following error started displaying on the site. Moreover when we upgraded both the package instances can be seen in umbraco installed packages section. Does this make any difference?
1.Xslt parsing error is coming becuase of this type of error found in most of xslts while saving: System.InvalidOperationException: No product catalog group supporting the url "http://dev-lwpu1.seventechnology.com:80/umbraco/webservices/codeEditorSave.asmx/SaveXslt" found. at UCommerce.Runtime.CatalogContext.FindProductCatalogGroupForDomain() at UCommerce.Runtime.CatalogContext.get_CurrentCatalogSet() at UCommerce.Xslt.ClientContext.get_CurrentGroup() at UCommerce.Xslt.XsltLibrary.get_InProductCatalogGroupContext() at UCommerce.Xslt.CatalogLibrary.GetAllCatalogs() at UCommerce.Xslt.Library.b__0() at UCommerce.Xslt.Library.HandledCall[T](Func`1 method) at UCommerce.Xslt.Library.GetAllCatalogs()
The following xslts are giving above error: 1.1. AllCatalogs[XSLT].xslt 1.2. AllCategory[XSLT].xslt 1.3. Category[XSLT].xslt 1.4. FeaturedProducts.xslt 1.5. LatestOffers.xslt 1.6. PaymentMethods[XSLT].xslt 1.7. productMetaInformation.xslt 1.8. productpricelistXSLT.xslt 1.9. Product[XSLT].xslt 1.10.RootCategories[XSLT].xslt
By default Umbraco will install the updated package as a new one. It doesn't make any difference.
I believe the reason is that you haven't configured a store to run as part of the URL you're doing the editing on. Please check which hostname is assigned to the site you're editing on (in content right click site and click hostname) and which hostname is configured in your store (in uCommerce expand product catalog, click your store, and make sure that the URL is the same as the one you're editing on).
If the site is working without problem you can check "Skip testing" when you save your XSLT and you should be fine.
Do you have a hostname setup with this specific value, "http://dev-lwpu1.seventechnology.com:80"? The issue is that our API is running in the backend context, which doesn't have the same information available as assumed on the frontend.
Also could you provide me with information of what's stored in the table called "umbracoDomains"? uCommerce tries to match up the entries found in there with the current URL. If it doesn't find a match it'll generated the error you're seeing. I'm guessing it's related to the fact that the port number is part of the URL.
You could try to check the "Skip testing" when you save, which will ignore the error altogether.
The specific value, "http://dev-lwpu1.seventechnology.com:80" is setup at backend.Furthermore UmbracoDomain table contains URL:dev-lwpu1.seventechnology.com.Also screen shot is attached below:
Skip testing doesn't solves the problem, I have checked.
If you're running with a single store you could try and remove the domain binding in uCommerce altogether making you're one store the default. If uCommerce doesn't find a specific binding it will use the default.
I have upgraded my two sites to ucommerce 1.3.0.1 version. Now products variable @displayName is not showing anything on sites. Can you please help me in this.
Do you have a culture set for the hostname in Umbraco? Umbraco will set the current culture based on what is specified on the hostname. If no culture is specified Umbraco will use the browser language I believe which might not match with a culture in the system.
Upgrading uCommerce
Hi Søren,
Are there some extra steps required when upgrading uCommerce or I just have to install the new package and that's it? I did this upgrade (1.0.5.2->1.1.0.1) because I wanted to have the DIBS integration and it looks like it's there, but I noticed one issue: when choosing price groups for for DIBS service, I can choose price groups that I have been deleted some while ago and which are not showing up under the PriceGroups section. Or is this just a small bug?
Hi Andrei,
If you've registered custom pipeline tasks you might want to replace the new pipeline configs with your previous one (there's a backup sitting next to it in the /umbraco/ucommerce/pipelines folder).
The deleted price groups should not be displayed. I'll make sure and fix that.
The issue is fixed and will be included in 1.1.1.
Hi Andrei,
The release with your fix is out at www.ucommerce.dk/releases/uCommerce-1.1.0.2.zip
Hi
I have ucommerce 1.0.4.1 installed and want to upgrade to 1.1. How can I upgrade so I don't loose all my styling and customisations in 1.0.4.1?
Or I have to uninstall the previous ucommerce and install the new release from start?
Nauman
Hi Nauman,
You just install uCommerce on top of what you've got already. uCommerce will pick up that you're doing an update and will only update the areas necessary. Any files modified will be backed up.
If you've registered custom pipeline tasks you'll need to register them.
Hi Soren,
I think there is a problem with the new version of uCommerce from your last link. It seems now I can't view or change data types:
Andrei, thanks for reporting this. The issue here is that Umbraco uses a very simple mechanism to determine which right-click menu items should be executed (a letter as identifier essentially) and we've apparently selected a letter which is already being used. I'll go ahead and change this in the release I'm rolling out tomorrow.
Soren
We have upgraded ucommerce from 1.0.4.1 to 1.2.0.0 and following error started displaying on the site. Moreover when we upgraded both the package instances can be seen in umbraco installed packages section. Does this make any difference?
1.Xslt parsing error is coming becuase of this type of error found in most of xslts while saving:
System.InvalidOperationException: No product catalog group supporting the url "http://dev-lwpu1.seventechnology.com:80/umbraco/webservices/codeEditorSave.asmx/SaveXslt" found.
at UCommerce.Runtime.CatalogContext.FindProductCatalogGroupForDomain()
at UCommerce.Runtime.CatalogContext.get_CurrentCatalogSet()
at UCommerce.Xslt.ClientContext.get_CurrentGroup()
at UCommerce.Xslt.XsltLibrary.get_InProductCatalogGroupContext()
at UCommerce.Xslt.CatalogLibrary.GetAllCatalogs()
at UCommerce.Xslt.Library.b__0()
at UCommerce.Xslt.Library.HandledCall[T](Func`1 method)
at UCommerce.Xslt.Library.GetAllCatalogs()
The following xslts are giving above error:
1.1. AllCatalogs[XSLT].xslt
1.2. AllCategory[XSLT].xslt
1.3. Category[XSLT].xslt
1.4. FeaturedProducts.xslt
1.5. LatestOffers.xslt
1.6. PaymentMethods[XSLT].xslt
1.7. productMetaInformation.xslt
1.8. productpricelistXSLT.xslt
1.9. Product[XSLT].xslt
1.10.RootCategories[XSLT].xslt
Regards
Nauman
Hi Naumann,
By default Umbraco will install the updated package as a new one. It doesn't make any difference.
I believe the reason is that you haven't configured a store to run as part of the URL you're doing the editing on. Please check which hostname is assigned to the site you're editing on (in content right click site and click hostname) and which hostname is configured in your store (in uCommerce expand product catalog, click your store, and make sure that the URL is the same as the one you're editing on).
If the site is working without problem you can check "Skip testing" when you save your XSLT and you should be fine.
Hi Sooren,
I have checked the host name, it is working fine....but no solution yet with this procedure.
Thanks,
Usman
Do you have a hostname setup with this specific value, "http://dev-lwpu1.seventechnology.com:80"? The issue is that our API is running in the backend context, which doesn't have the same information available as assumed on the frontend.
Also could you provide me with information of what's stored in the table called "umbracoDomains"? uCommerce tries to match up the entries found in there with the current URL. If it doesn't find a match it'll generated the error you're seeing. I'm guessing it's related to the fact that the port number is part of the URL.
You could try to check the "Skip testing" when you save, which will ignore the error altogether.
Hi Soren,
The specific value, "http://dev-lwpu1.seventechnology.com:80" is setup at backend.Furthermore UmbracoDomain table contains URL:dev-lwpu1.seventechnology.com.Also screen shot is attached below:
Skip testing doesn't solves the problem, I have checked.
Thanks,
Usman
If you're running with a single store you could try and remove the domain binding in uCommerce altogether making you're one store the default. If uCommerce doesn't find a specific binding it will use the default.
soren,
The Hostname sol has finaaly solved the problem.
Thanks,
Usman
Hi Soren,
I have upgraded my two sites to ucommerce 1.3.0.1 version. Now products variable @displayName is not showing anything on sites. Can you please help me in this.
Thanks,
Usman
Do you have a culture set for the hostname in Umbraco? Umbraco will set the current culture based on what is specified on the hostname. If no culture is specified Umbraco will use the browser language I believe which might not match with a culture in the system.
Hi soren,
Thanks for all the help. Issue Resolved
Thanks,
Usman
is working on a reply...