So we have two machines, both running the same code, and they uses the same database(s) and they both point to the same appdata folder.
On one machine (my own computer), the Catalog in CMS works fine, but on our test machine, we get a script error when starting it, so it will not work at all, this happens on the URL '/episerver/Commerce/Catalog' line 67, where the function parser.parse() is called. What can possibly be wrong here cause I am sure there is some error somewhere on the server or related, but there is nothing apart from this crypptic dojo error. So everything else works perfectly fine, even using catalog items (ex. products) as blocks and editing them after they have been placed, tis just the "Catalog" (that has the link above) that throws this error.
Forgot version numbers, everything installed from the latest version available in nuget feed, there are no updates available for any of the relevant addons either:
<package id="EPiServer.CMS.Core" version="7.5.1002.0" targetFramework="net45" /> <package id="EPiServer.CMS.UI" version="7.5.446.0" targetFramework="net45" /> <package id="EPiServer.Commerce" version="7.5.1000.0" targetFramework="net45" /> <package id="EPiServer.CommonFramework" version="7.5.446.1" targetFramework="net45" /> <package id="EPiServer.Framework" version="7.5.1002.0" targetFramework="net45" /> <package id="EPiServer.Search" version="7.5.446.0" targetFramework="net45" />
I'm experiencing the exact same thing here on one of our development machines :(
I manged to solve it (sort of), by completely wiping the site root of the dev machine and deploying everything again. Only thing I can think of is that there was a wrong version of a dll in the "modulesbin" folder, but I am not 100% sure what exactly solved the problem (or what the problem even was in the first place).
We saw the same issue on a developer machine that did not have EPiServer installed in "C:\Program Files\..."
Hmm, that might be related. The machine did indeed lack the Episerver commerce module installation in program files at one point (it had episerver installed). Though it still showed the same error after installing the commerce module installer, might have been a combination of issues.