@maliming he's using the MVC template and as he says; the app renders as authorized, but he's not.
Sorry for the late response @mahmut is on it.
when you navigate to the URL, what happens?
I generally agree with you @chauey, but Suite is designed to create pages with the collection tab on the master entity not the child entity. if you want to have both child entity collection, you need to write code for the second page. for instance, you'll first generate a Category entity then a Tag entity (with a Category relationship), and after that add a Tags tab to your Category page. On the other hand, I see that there's a design problem with your solution. I would go with Enum type instead of a Tag entity. Anyway, without knowing all the requirements of your business logic, it's hard to determine the best practice. So you can follow my suggestion above to achieve this problem.
Your feature request thread was auto closed btw.
thanks. I reactivated it.
re-activated
thanks for the feedback
All your feedback is being evaluated. Don't hesitate to declare your suggestions, issues and ideas.
if he doesn't make debugging then there's no need for him to allocate your developer seat. he can run the application with "dotnet run" and no need a license for him.
This package exists on nuget.abp.io, and I can successfully download it.
Replace the {YOUR_API_KEY} with your own NuGet API key and test this file:
https://nuget.abp.io/{YOUR_API_KEY}/v3/package/Volo.Abp.AuditLogging.Application/6.0.3/Volo.Abp.AuditLogging.Application.6.0.3.nupkg
On the other hand, please ignore this message HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.auditlogging.application/index.json with an error: 404-Not Found. ... because package restore system tries to find the required package in all NuGet sources because it doesn't know where it's located. therefore these errors are actually informational logs.
