Hi,
Thanks for the reply.
We found another sub-application/pathbase issue, this time on the Error page in the LeptonX MVC theme.
Problem:
When the application is hosted as an IIS sub-application under /server, the Error page button "Go to the homepage" redirects to root / instead of /server/.
It's probably coming from the installed theme package:
Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX 5.0.2The homepage link is most probably hardcoded.
So this appears to be another pathbase/sub-application bug in the ABP commercial UI/theme layer.
Could you please confirm:
Thanks.
Thanks for the workaround suggestion.
In our case, this workaround is problematic because the affected Manage/Profile Picture UI is inside the ABP Pro package and we donโt have practical source-level access to patch that page directly in a maintainable way.
For this reason, we would strongly prefer an official bug fix in the module instead of a local workaround.
Could you please confirm this as a product bug in Volo.Abp.Account.Pro.Public.Web.
Hello ABP team,
I checked the docs/samples/search before opening this request.
We are using ABP Commercial and hosting the server as an IIS sub-application under /server (not at site root). We found that the Account Manage/Profile Picture UI generates an image URL without the app pathbase, which breaks under sub-application hosting.
We validated this on package version Volo.Abp.Account.Pro.Public.Web 10.1.1 (same behavior as 10.0.2).
https://<host>/server/https://<host>/web/No server exception is thrown. This is a client-side URL generation issue resulting in 404 for profile picture image requests under https://<host>/server/Account/Manage (please note this is not web but server side app)
https://<host>/server/Account/Manage).https://<host>/api/account/profile-picture-file/{id} (missing /server)https://<host>/server/api/account/profile-picture-file/{id}<img id="CurrentProfilePicture" ...> points to root-relative /api/account/profile-picture-file/{id}.~/api/... / pathbase-aware URL generation.abp.appPath and <base href> are correctly set to /server/.Please advise whether this is a known issue and if there is an official fix/workaround planned.

