There is a small bug in the build-images-locally.ps1 file, at least for Angular:
Write-Host "********* BUILDING Angular Application *********" -ForegroundColor Green $angularAppFolder = Join-Path $slnFolder "../angular"
This should be ./angular with only one dot as above it, you already have the lines
$currentFolder = $PSScriptRoot $slnFolder = Join-Path $currentFolder "../../"
Or the script wont find the folder (at least assuming you follow the instructions "Navigate to etc/docker-compose folder and run the build-images-locally.ps1 ").
As the previous thread was closed, I create a new one regarding the now re-added Docker (Docker compose) support in ABP Commercial to follow up on improvements and possible problems. Probably a good idea to keep it all in one place rather than creating different tickets for everything (hopefully it won't be much but you never know). Please refund this ticket as the previous one was closed and can not be reopened it seems.
https://abp.io/support/questions/8082/What-is-the-support-for-Docker-in-ABP-Commercial-today
Reopened once again.....
It seems when using the Angular UI and creating Navigation properties, ABP Suite tries to invent the type "Guid" in Angular/Typescript even though that does not exist (at least not by default). If you change it to string it will work both development time and run time it seems.
Is any action being taken on this? It seems like we rarely get feedback on bugs etc reported in this thread compared with when creating new ones, but then general threads like this seems kind of pointless. Thanks.
Hello,
Which version does your app use? Also on which page did you test this? When I test it on the Tenants page, I get a result like below:
Using latest version of ABP Suite to generate Angular components/pages and they all have this problem still.
The problem here
https://abp.io/support/questions/7455/Action-menu-is-displayed-even-if-there-are-no-actions-in-in
was supposed to be fixed in the next release (7 months ago) but is still there, at least in Angular but would imagine in all UI:s since it is probably permission related rather than UI related.
BTW, the name of this thread should probably change now in 2025.
In ABP Suite when creating properties for Entities, it would be nice if you besides "Name" could enter an optional "UI name" or something like that, that would be used in the generated UI instead of Name.
For example, if you create a property "HomepageUrl" for a Company entity, you would probably want that to show up as "Homepage:" rather than "HomepageUrl:" in UI.
We do not typically close tickets unless they are fully resolved or inactive for some time. We understand the issue you are facing and are actively working on a fix to prevent this from happening again. Thanks for your patience.
The problem seems to be an overzealous bot with really poor patience that decides to close even unresolved ticket way too early.
