If you already switched to the latest ABP version 5.3.1 and see an issue, please report it under this topic. let's report only 5.3.1 problems not the old versions
11 Answer(s)
-
0
We are stuck because of this one here https://support.abp.io/QA/Questions/3301/qgApoZ2OmDdJqiAoXp5L4ObZ82mStp54vqoB0A-is-not-a-valid-page-error . We got contractors to work with us for one week so there are like 3 man-weeks worth of changes that we can’t ship so super important to get this fixed (almost 1.5 weeks since discovered!!)
-
0
I have been updating my app which was created using ABP suite since version 3.x There may be legacy code relating to CMS that needs to be updated in my project???
The current app does not run when deployed, but runs in debug mode.
To get the app to deploy, I need to disable CMS, probably just the Volo.CmsKit.Pro.Admin.Web which I have done as below.
The only way that I can deploy, is remove reference to the Volo.CmsKit.Pro.Admin.Web.dll in the solutions .web project
- remove package .Web.csproj
- In the MenuContributor, remobe 2 lines of code using Volo.CmsKit.Pro.Admin.Web.Menus; context.Menu.SetSubItemOrder(CmsKitProAdminMenus.GroupName, 4);
- In the WebModule, remove 2 lines of code using Volo.CmsKit.Pro.Admin.Web; typeof(CmsKitProAdminWebModule),
I am fortunate that I am not currently using the CMS, but now I can deploy.
-
0
We are stuck because of this one here https://support.abp.io/QA/Questions/3301/qgApoZ2OmDdJqiAoXp5L4ObZ82mStp54vqoB0A-is-not-a-valid-page-error . We got contractors to work with us for one week so there are like 3 man-weeks worth of changes that we can’t ship so super important to get this fixed (almost 1.5 weeks since discovered!!)
this problem has been addressed and we have fixed it. it's related to aspnet core razor pages base class change. we're testing the result to be sure it's working in 5.3.2. Therefore you'll get this fix with 5.3.2. And the planned date for 5.3.2 is July 5th, Tuesday 2022.
-
0
We are stuck because of this one here https://support.abp.io/QA/Questions/3301/qgApoZ2OmDdJqiAoXp5L4ObZ82mStp54vqoB0A-is-not-a-valid-page-error . We got contractors to work with us for one week so there are like 3 man-weeks worth of changes that we can’t ship so super important to get this fixed (almost 1.5 weeks since discovered!!)
this problem has been addressed and we have fixed it. it's related to aspnet core razor pages base class change. we're testing the result to be sure it's working in 5.3.2. Therefore you'll get this fix with 5.3.2. And the planned date for 5.3.2 is July 5th, Tuesday 2022.
is version 5.3.2 released ??
-
0
not yet because we have detected an issue and trying to fix it. 5.3.2 will be released this week (until Friday).
-
0
We are stuck because of this one here https://support.abp.io/QA/Questions/3301/qgApoZ2OmDdJqiAoXp5L4ObZ82mStp54vqoB0A-is-not-a-valid-page-error . We got contractors to work with us for one week so there are like 3 man-weeks worth of changes that we can’t ship so super important to get this fixed (almost 1.5 weeks since discovered!!)
ABP v5.3.2 has just been released and this issue has been fixed.
-
0
An error occurred when the Organization Top-Level Move button was clicked
v5.3.0 or v5.3.2
-
0
Mmm, I don't have move, my styling is different too.
-
0
Mmm, I don't have move, my styling is different too.
UI is used BlazorServer,the same error occurs with the new project
-
0
An error occurred when the Organization Top-Level Move button was clicked
v5.3.0 or v5.3.2
Hi,
We created an internal issue and will fix it.
-
0
We are stuck because of this one here https://support.abp.io/QA/Questions/3301/qgApoZ2OmDdJqiAoXp5L4ObZ82mStp54vqoB0A-is-not-a-valid-page-error . We got contractors to work with us for one week so there are like 3 man-weeks worth of changes that we can’t ship so super important to get this fixed (almost 1.5 weeks since discovered!!)
ABP v5.3.2 has just been released and this issue has been fixed.
This is still an issue.. nothing has been fixed. This is starting to be ridicules..
