There seem to be problems/confusion regarding how to translate ABP so I create a ticket here as well, also because there might be differences between ABP Free and Commercial. Also considering that you may or may not have access to the source code needed for things outside of the ABP open source framework.
https://github.com/abpframework/abp/issues/21473
Please provide updated instructions on how we can translate ABP Commercial to Swedish (or any other language for that matter) in a way that works properly with latest ABP version. We don't mind doing a lot of the required leg work and sharing the result as long as we get clear instructions/documentation on how to do it.
Thanks.
It used to be that at least ABP Commercial came with full (or at least good) support for Docker, including multi stage Dockerfiles with support for Docker Compose etc. But this does not seem to be the case anymore, the included Dockerfiles are very minimal and isn't even recognized by Visual Studio as Dockerfiles it seems. They also does not seem to work so you can publish to Docker Hub etc. (as Visual Studio claim there is no Dockerfile)
Even finding Docker in the current documentation is hard, we've only been able to find it mentioned in the 8.1 documentation and that seems to be outdated now, for example the build-images-locally.ps1 mentioned there does not seem to exist anymore
https://abp.io/docs/commercial/8.1/startup-templates/application/deployment-docker-compose?UI=BlazorServer&DB=EF&Tiered=Yes
Have tried to find information about this change including updated documentation for the changes that have been made but not found it so:
You can of course build your own Dockerfiles from scratch etc. but my questions here is about what support you get out of the box for Docker in ABP.
Also created an issue on GitHub for this, but the answers might be different between the free and the commercial version of ABP.
https://github.com/abpframework/abp/issues/21057
Thanks.
As it seems a bit uncertain how much attention posts in the "Bugs & Issues v8.3.x" thread gets, and I feel this is an important and kind of urgent question, I post it in a separate ticket. This is especially true if it isn't an intended change as it would most likely mean that solutions created now would not work with future updates of ABP Suite / ABP Studio.
What is the reasoning for the new directory structure of solutions created with ABP Suite / ABP Studio? It used to be that you got a folder for each "application" under the main directory like "MyApplication" = > "aspnet-core", "angular", "react-native" etc but now it seems to be that angular and react-native folders are moved within what used to be the aspnet-core folder. So now you have SLN file and "test" folder for aspnet-core stuff right next to your angular and react-native folders, even though they are stand alone applications (kind of).
Is this even an intended change or some kind of bug? There might be advantages of this as well, like using only one repo for everything etc (which could be both good or bad depending on personal preference).
You can of course change this after creation, but I would imagine that doing that would break code generation etc?
Is there a guide on if we want to tidy this up a bit and still make sure that ABP Suite etc works (and that won't break with updates etc)?
It seems ABP is missing several languages that has been translated, some of them even months back, but they still do not seem to be included in ABP releases. Created an Issue about it over att GitHub but would like to highlight this as several people, including me, have probably spent some time it translating this and it would seem like a quite simple job just to include them as they have already been merged into /dev. Obviously, being able to provide an application in the correct language is kind of a big deal when targeting local audiences/clients. Also, not sure if there are differences here between ABP and ABP Commercial, as the later includes additional modules etc. which we are unsure how to translate as they are probably not in the public repo.
https://github.com/abpframework/abp/issues/20864
Or are we missing something here that we need to do ourselves (besides translating and submitting a PR)?
If it had just been one or maybe a few files we could have done it manually for the time being, but these are quite a lot of files and I am not sure if you can even override translations for commercial modules etc.
Thanks.
ABP Suite incorrectly handles checkboxes, at least when using Angular. It marks the controls as required (*) even though the form can submit regardless of value (selected / not selected) which in correct but it should not be required. It also gets the default value wrong, making it selected for new items even though you have selected the opposite. There are no options in ABP Suite for not required, nullable etc for Boolean values (which renders as checkboxes).
Correct behavior should be that it is not required (at least not unless you can select that in ABP Suite) and also that default value is what you tell it to be in ABP Suite.
When using ABP Suite to add entities / properties, the test cases generated incorrectly tries to add non filterable properties when calling Get methods which will lead to compile errors as those no filterable properties are not parameters of the get method(s).
Extracted from https://abp.io/support/questions/7942/Angular-layered-application-seems-broken-in-83.
It seems like the LeptonX theme breaks for some very certain widths. In our case, it seems to be at 1200 px width in all tested browsers, but make the window only slightly narrower/wider and the problem seem to go away (at least not as obvious). This happens for both Angular and Blazor, but would imagine everywhere as I believe the actual theme is the same.
It used to be that we could only fire up ABP Suite and tell it to create an Angular application it that would be it. Now that option seems to be gone in ABP Suite and ABP Studio only seems to create an Angular application that won't even build due to several missing packages and also quite a lot of deprecated ones. Weirdly enough, creating single layer Angular application does not seem to have this problem, or at least that one you can build even though it also contains numerous packages marked as deprecated. This even if you deselect all additional modules like GDPR, chat etc.
Only using default settings in latest ABP Suite except that we selected Angular as UI and layered application and this is what we got
How are we supposed to create a new working layered Angular application in ABP Commercial 8.3?
Edit: Please note that we don't know exactly why some packages are marked as deprecated and if that is actually true, but still it won't even build when using the layered Angular template due to missing packages.
When trying to build a MAUI Blazor (and probably MAUI Xamarin as well I guess) you will get build errors from OAuthSecureStorage as the AccessTokenKey property is not defined.
using Volo.Abp.Account.Pro.Public.MauiBlazor.OAuth;
using Volo.Abp.DependencyInjection;
namespace ImproWise.Koll.MauiBlazor;
[Volo.Abp.DependencyInjection.Dependency(ReplaceServices = true)]
[ExposeServices(typeof(IOAuthSecureStorage))]
public class OAuthSecureStorage : IOAuthSecureStorage, ITransientDependency
{
public Task SetAsync(string key, string value)
{
#if DEBUG
Preferences.Set(key, value);
return Task.CompletedTask;
#else
return SecureStorage.Default.SetAsync(key, value);
#endif
}
public Task\<string> GetAsync(string key)
{
#if DEBUG
return Task.FromResult(Preferences.Get(key, string.Empty));
#else
** return SecureStorage.Default.GetAsync(AccessTokenKey);**
#endif
}
public Task RemoveAsync(string key)
{
#if DEBUG
Preferences.Remove(key);
#else
** SecureStorage.Default.Remove(AccessTokenKey);**
#endif
return Task.CompletedTask;
}
}\
The only thing close to the documentation we have been able to find about this is:
https://docs.abp.io/en/commercial/latest/getting-started-maui
Which points to:
but I don't see how that could make it work without changing the provided code.
You can make it build by doing something like
string AccessTokenKey = "1234";
but that isn't really a solution to the problem.
Is this a bug or something we should handle ourselves and if so, the documentation probably needs updating.
In a Blazor app (but guessing it might be in all kinds of projects), when a user only has read permission to an entity, the Actions button is still displayed even though the user has no permissions to do anything. When you click it, it appears as nothing happens but in fact there is a very small empty menu that shows up (as the user has no available actions). T
This is quite confusing to the user and the Actions menu should not be displayed when it is empty. Idealy the entire column should be hidden if the current user has not permissions to any actions since it should be the same for all rows as permissions are per entity type.