Version 7.19.2 and 8.7.1
in the new Commerce UI, i get a 404 in "on-page editing" mode in UI. the url is
if i try to remove the comas ",," (http://mygod.com:80/EPiServer/CMS/Content/en/5470/Products/Inspiration/Sales-Tools/Digital-print-folder-Trifold,,969__CatalogContent/?epieditmode=True)
it do work. where is the problem? what does the commas mean?
I think this did work in version 7.15 and 8.2
try this, http://world.episerver.com/blogs/K-Khan-/Dates/2015/2/fix-for-a-catalog-ui-issue-in-episerver-commerce-8.7.1/if doesnot work, Is there any excetion in log files?
Talking from experience, something tells me to never update to the newest version. Version CMS 7.19.2 is a headache! beeing not compatible with Commerce 8.7.1. Also when updating to the latest version you can be sure to be first with the problems to solve them yourself.... so upgrading to CMS 8 is not an option. Maybe i should downgrade to 7.19.1?
Is Commerce 8.8 compatible with cms 7.19.2?
I always upgrade to Latest Commerce version as those comes with compatible testngs and gurantees dependent assemblies will work fine.But if we upgrade CMS first and then upgrade Commerce on top of that, There are chances that CMS is a version ahead already.
So what you're saying is that Commerce 8.8 is compatible with cms 7.19.2?
Commerce 8.8 is supposed to compatible with CMS 8.x only. CMS 8.0 had breaking changes so Commerce 8.8 was updated to work with that.
Is CMS 7.19.2 a must have for you?
No, 7.19.2 is not important for us. Is just that its always time consuming between the upgrades, as it was between 7.15 and 7.19. I don't want to go from one bug to another new one. Remember im in the process to upgrade from 6r2 to 7.19. Many steps.
Now to my question: is this bug with commas ",," something i can do anything about? even one comma is working, but not two.
Honestly I'm not sure what is wrong, but the default url of catalog UI should looks like this:
So I guess your site has issues with Path and routing. Do you have any custom routing registered?
The main url looks like that (in your example). But my problem is in the "frame" when clicking "on page editing" on one specific product in the new Catalog UI. Editing properties works. Understood?
No custom routing.
Have you gone through data migration process after upgrade?http://mygod.com:80/EPiServer/Commerce/MigrateRegards/K
The data migration steps are mandatory and you must/should go through it before doing any other tasks.
@Lucster: Can you post and screenshot with HTTP requests?
PS: Yes, there's trick to skip migration steps but we recommend to migrate your data :).
It did work in version 7.15. How does the address look for you guys, if you use that same version or later?
Screenshot is comming up soon
Here come a screenshot:
Can you confirm that these enviornments are not behind some firewalls like Barracuda? I had a case for my Commerec Manager when page was 404 and blocked by he firewall.Rgards/K
@khan No, we are working localy. but same problem on dev, test and prodserver.
From the screen shot I just Noticed wildcard looks missing for ManagedPipelineHandler, Can you check all the required modules are installed on IIS7.Confirm another thing "Where your handlers are defined in the web.config, add a <clear /> before the first item in the list"
Clear is there...
Regarding Wildcard and ManagedPipelineHandler I'm not really sure about this, any idea if i missing anything?
<httpRuntime maxRequestLength="1000000" requestValidationMode="2.0" />
<pages enableEventValidation="true" enableViewState="true" enableSessionState="true" enableViewStateMac="true">
<add tagPrefix="EPiServerUI" namespace="EPiServer.UI.WebControls" assembly="EPiServer.UI" />
<add tagPrefix="EPiServerScript" namespace="EPiServer.ClientScript.WebControls" assembly="EPiServer" />
<add tagPrefix="EPiServerScript" namespace="EPiServer.UI.ClientScript.WebControls" assembly="EPiServer.UI" />
<globalization requestEncoding="utf-8" responseEncoding="utf-8" />
<allow roles="WebEditors, WebAdmins, Administrators" />
<deny users="*" />
<add name="AssemblyResourceLoader-Integrated-4.0" path="WebResource.axd" verb="GET,DEBUG" type="System.Web.Handlers.AssemblyResourceLoader" preCondition="integratedMode,runtimeVersionv4.0" />
<add name="PageHandlerFactory-Integrated-4.0" path="*.aspx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.PageHandlerFactory" preCondition="integratedMode,runtimeVersionv4.0" />
<add name="SimpleHandlerFactory-Integrated-4.0" path="*.ashx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.SimpleHandlerFactory" preCondition="integratedMode,runtimeVersionv4.0" />
<add name="WebServiceHandlerFactory-Integrated-4.0" path="*.asmx" verb="GET,HEAD,POST,DEBUG" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode,runtimeVersionv4.0" />
<add name="svc-Integrated-4.0" path="*.svc" verb="*" type="System.ServiceModel.Activation.ServiceHttpHandlerFactory, System.ServiceModel.Activation, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode,runtimeVersionv4.0" />
<add name="wildcard" path="*" verb="*" type="EPiServer.Web.StaticFileHandler, EPiServer.Framework" />
<add name="StaticFileHandler" path="*" verb="*" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" resourceType="Either" requireAccess="Read" />
The only thing I found different was the last handler
I think I can replicate your problem, but I'm not sure the root cause is the same.
Can you confirm the Content with id = 5470 is your start page?
yes, it is the startpage of that domain (we have multisite)
Then it should be
Where Iggesund is the catalog
Don't know why it's missing.
You said no custom route, so only CatalogRouteHelper.MapDefaultHierarchialRouter(RouteCollection routes, bool enableOutgoingSeoUri)?
I found the problem: RouteTable.Routes.RegisterPartialRouter(this); on a CustomContentProviderInitialitiation is causing it not to work. When I deactivate initialization of this provider it works. And that is another thread and problem of mine: http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=117993&epslanguage=en
So i guess this is a none issue as long as we havent solved the other thread. Thanks for your help. Much appreciated.
Regarding url: You have a point. But No, that didnt make the trick. Under another catalog, the url is with "Iggesund". When i change manually this url works "mydomain.com/EPiServer/CMS/Content/en/,,,,,,135__CatalogContent/?epieditmode=True" without the 5470/ segments