you can remove these files.
I had already done this step to get it working. However, I was concerned about side effects of removing the files. Thank you. That was my main concern.
Hi,
you need to remove the project reference form
.csprojtoo (identityserver, publicweb)
I created a fresh project using abp suite and added the Account and Identity sources. I removed the projects that were not needed. I still get a project publish error. IMPORTANT NOTE* I can successfully build and PUBLISH if I don't add the Account and Identity packages in a non-tiered project. In a tiered project or non-tiered project as soon as I add the Account and Identity sources I get a PUBLISH build failed due to the Account resources having the same relative path. This was not an issue in .NET core 5 or 6. Seems to be related to .NET CORE 7 and later. If I exclude from the project, the _viewstart, etc from one of the dup project issues, I can safely publish. Currently, I just make sure the necessary files (at least one with all taghelpers is included in the build). I exclude from the project the others in the path that are causing errors.
Here are the publish errors and the file contents of _ViewImport and _ViewStart which I included for reference.
Severity Code Description Project File Line Suppression State Tool Details
Error Found multiple publish output files with the same relative path:
D:\abp\myweb2\MyWeb2\modules\Volo.Account.Pro\src\Volo.Abp.Account.Pro.Public.Web.Shared\Pages\Account\_ViewImports.cshtml,
@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bootstrap
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bundling
D:\abp\myweb2\MyWeb2\modules\Volo.Account.Pro\src\Volo.Abp.Account.Pro.Public.Web\Pages\Account\_ViewImports.cshtml,
@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bootstrap
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bundling
@addTagHelper *, Owl.reCAPTCHA
D:\abp\myweb2\MyWeb2\modules\Volo.Account.Pro\src\Volo.Abp.Account.Pro.Admin.Web\Pages\Account\_ViewImports.cshtml,
@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bootstrap
@addTagHelper *, Volo.Abp.AspNetCore.Mvc.UI.Bundling
D:\abp\myweb2\MyWeb2\modules\Volo.Account.Pro\src\Volo.Abp.Account.Pro.Public.Web\Pages\Account\_ViewStart.cshtml,
@using Volo.Abp.AspNetCore.Mvc.UI.Theming
@inject IThemeManager ThemeManager
@{
Layout = ThemeManager.CurrentTheme.GetAccountLayout();
}
D:\abp\myweb2\MyWeb2\modules\Volo.Account.Pro\src\Volo.Abp.Account.Pro.Admin.Web\Pages\Account\_ViewStart.cshtml. MyWeb2.Web 0
@using Volo.Abp.AspNetCore.Mvc.UI.Theming
@inject IThemeManager ThemeManager
@{
Layout = ThemeManager.CurrentTheme.GetAccountLayout();
}
Created a Master/Child project using ABP studio following your orders example from the screen shot produced in the Master entity link. The ABP studio latest version failed to create the detail record form or any part of it. Reverting back to abp suite 8.2.1 and completely uninstalling the latest version of studio ending in .4 and I am able to produce parent child data again. Also, ran into the infinite upgrade loop even after upgrading to latest version as mentioned by @MRBRL
ABP Studio is too painful to use because it breaks everything it touches.
Hi,
you can try to enable SSL to check if it's work
Hi Support; As I mentioned earlier, it works with SSL. It does not work when you attempt to browse the /SettingManagement page via NON-SSL connection. For example: If I browse the new server using the HTTPS url and accept the untrusted self-signed SSL certificate in IIS browser warning, I can connect to /SettingManagement page no problem, even though the browser Chrome/Edge warn that the connection is not private. If I click the advanced button then click the link to the unsecured url, I can navigate successfully.
From there, I can use the /SettingManagement link.
I am perplexed because this link is the only one that fails out of all of the Administration links when it is navigated via non-SSL.
Was hoping you could shed light on why this is an issue for only this one resource link.
Meanwhile, I will use our internal CA server to generate a trusted certificate for this server so that it may continue being used uninterrupted.
Thank you for looking into this matter.
There are no errors. I think Chrome or EDGE is actually passing an XHR POST that is not hitting the generated proxy script.
The main differences: The internal site is not using SSL/TLS - is there a browser reliance on SSL for AJAX for cross site scripting? is there a launchsettings.json that needs to change? Browser shows /MYWEBAPP/_bundles/Pages.SettingManagement.Components.EmailSettingGroup.Default.ACFAD1EB35F39 in the working application.
In the moved application, no references to the PROXY scripts are showing.
headers: Request url: https://mysite.mywebsite/myapp/SettingManagement?handler=RenderView&id=Volo.Abp.EmailSetting show up in the working web site.
In the local site I am not getting this far. Is SSL required for the SettingManagement piece?
Id ApplicationName UserId UserName ExecutionTime ExecutionDuration ClientIpAddress ClientName ClientId CorrelationId BrowserInfo HttpMethod Url Exceptions Comments HttpStatusCode ExtraProperties ConcurrencyStamp
5CC515ED-16B5-395A-C7F7-3A13FC87439C MYWEBAPP.Web 3C4F055A-9E56-8450-4B9A-3A0D47AB47DC admin 2024-07-25 07:45:12.7315718 0 10.22.168.190 NULL NULL 8acdf5632a70446588eb614033bd80ab Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 POST /SettingManagement NULL 400 {} ded99a5c4b7d470091cc7d2eb07aa5e8
45222F8B-D0A5-1A02-A199-3A13FC7954F1 MYWEBAPP.Web 3C4F055A-9E56-8450-4B9A-3A0D47AB47DC admin 2024-07-25 07:29:59.6648106 0 10.22.168.190 NULL NULL b1f057e368344f8ea5eaa1d8f20289b4 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 POST /SettingManagement NULL 400 {} cb2faf4b2fb74941aff4bd14931b661d
6F288DF8-EC60-ADBE-2FE4-3A13FC790C3C MYWEBAPP.Web 3C4F055A-9E56-8450-4B9A-3A0D47AB47DC admin 2024-07-25 07:29:41.0522510 1 10.22.168.190 NULL NULL 0dd3a362bac54001ac70ffc944df70b4 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 POST /SettingManagement NULL 400 {} 35b2dccf6fd041519b6a2479f648696b
3BB8A0CB-BAB7-B59D-9494-3A13FC7901E0 MYWEBAPP.Web 3C4F055A-9E56-8450-4B9A-3A0D47AB47DC admin 2024-07-25 07:29:38.3999505 1 10.22.168.190 NULL NULL 54ffc8c26aee47dbada26c796be409ac Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 POST /SettingManagement NULL 400 {} 6c6c16f438eb4e5aa3ad8c487cae03c4
DB32A4A6-D22B-6F00-90F1-3A13FC78F81B MYWEBAPP.Web 3C4F055A-9E56-8450-4B9A-3A0D47AB47DC admin 2024-07-25 07:29:35.8987819 0 10.22.168.190 NULL NULL 055f04475fd84bc5b7e10d1992e5eb1a Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 POST /SettingManagement NULL 400 {} 18e31554eed640ac882d381c3706049a
95189E19-588F-260A-1A28-3A13FC78EC21 MYWEBAPP.Web 3C4F055A-9E56-8450-4B9A-3A0D47AB47DC admin 2024-07-25 07:29:32.8331461 0 10.22.168.190 NULL NULL b653d3d515094b938c44b75a89892e23 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 POST /SettingManagement NULL 400 {} 180e0c2559ca4a9097a449ceee980b5b
EA656637-95DC-4434-C8FA-3A13FC78E014 MYWEBAPP.Web 3C4F055A-9E56-8450-4B9A-3A0D47AB47DC admin 2024-07-25 07:29:29.7474094 1 10.22.168.190 NULL NULL 84cfebd98201432a9d0eb764ea1dbd22 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 POST /SettingManagement NULL 400 {} 430321663121486cafad781d36508020
HI，
Could you share the error logs?
When you say error logs, do you mean the logs stored in SQL server, or logs stored in the Log folder (none are generated in logs folder)?
Greetings; Thank you for your quick resolution to this issue. I implemented the suggested changes in the web module and removed the reference to identity server. Login is now successful. I consider this particular issue closed. Thank you.
The CSS z-index setting solves the problem. Please do not count against our support allotment. Thank you for your quick response.
the tag <suite-custom-code-block-1>...</suite-custom-code-block-1> is never generated when I choose to generate the page without creating a new entity in the database. This is an existing project upgraded to the 7.4 rc-4. I am trying to get the suite-custom-code-block-# tags to generate in the existing page, which does get regenerated. However, the custom code block tags are not created in the page. If I create a new entity, the suite-custom-code-block-# tag comments are sprinkled throughout the .cshtml page. seems to be ignored when I regenerate code wrapped in this tag in a .cshtml page. I have checked the customizable checkbox in ABP Suite. The .cshtml page is recreated completely, wiping out any change wrapped in the custom code block tags for existing pages that I manually add these tags to, since APB SUITE does not add them when regenerated.
Hi, I have re-checked it again and it seems there is not any problem here. You should have added the code block as follows:
Correct ✅
@*//<suite-custom-code-block-1>*@ <h1>customizated content</h1> @*//</suite-custom-code-block-1>*@Wrong ❌
@*<suite-custom-code-block-1>*@ <h1>Custom Code</h1> @*</suite-custom-code-block-1>*@Our placeholder is
//<suite-custom-code-block-n>, please try with this placeholder and you will see that it's working as expected.
APB Team; The reason I believe this to still be a bug is because: A: The ABP Suite generates the .extended.cs class for existing projects when you check the Customizable Code checkbox. But, it's only half complete. It does not regenerate the pages and javascript files correctly. The .cshtml pages get regenerated but there are no @//<suite-custom-code-block-x>@ @//</suite-custom-code-block-x>@ tags. Why regenerate the main class and create the .extended.cs file if you are going to neglect to regenerate the cshtml and javascript code without the custom code blocks? The same for the javascript files. //<suite-custom-code-block-x> //</suite-custom-code-block-x> blocks are not generated in the freshly regenerated javascript code. It leaves the solution half-baked. Can this issue be fixed? Also, it really shouldn't be counted against my support questions. Thank you for looking into this.
