A new Flexera Community experience is coming on November 25th. Click here for more information.
I just upgraded 2021 R2 over a 2019 R1 database. Everything seems to be working except for the categories. When on the Browse Catalog tab none of the categories are not showing. The user.log has no errors, AD logs have no errors, I've deleted cache, reset IIS and stopped/started the ESD service.
I'm not sure what else to check for this.
‎Oct 11, 2022 12:49 PM
Thanks for the screen capture.. I'm still seeing a reference to https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js, which should not have been the case. I looked at the file I sent to you, and found that it was not the correct version of the file (at least the KB was internal :)). Anyways, try the attached file instead. I confirmed that this should be correct.
‎Oct 12, 2022 01:49 PM
Teri,
This sounds like a known issue. Can you try applying the new _Layout.cshtm, which can be found in the following KB, to see if this resolves your issue?
‎Oct 11, 2022 12:55 PM
the URL to the KB has "internal" in it, so if you can't access it, I've attached the file to this post.
To apply, do the following:
1. In the directory <install Dir>\Web\Views\Shared rename the file _Layout.cshtml to _Layout.cshtml.bak.
2. Copy the attached file into <install Dir>\Web\Views\Shared.
3. Perform an iisreset
‎Oct 11, 2022 12:58 PM
Shoot - I was hoping that would fix it but the categories are still not showing
‎Oct 11, 2022 01:13 PM
I can't really think of anything else that would cause this.. If you open developer tools (F12) do you see any errors under the console tab? Just to confirm, you are seeing the browse catalog tab, but are simply not seeing the categories, correct? Same for all user accounts? Do you have category security defined on your categories?
‎Oct 12, 2022 11:26 AM
Thanks for the screen capture.. I'm still seeing a reference to https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js, which should not have been the case. I looked at the file I sent to you, and found that it was not the correct version of the file (at least the KB was internal :)). Anyways, try the attached file instead. I confirmed that this should be correct.
‎Oct 12, 2022 01:49 PM
The new file fixed it. Thanks Charles!
‎Oct 12, 2022 03:28 PM