In the Angular + Core version pinning does not work properly. The application blocks and you can't really open the chat to solve it. With every click somewhere on the page it flickers.
I also tested with a whole new unchanged project.
We use the Angular + Core version. I tried to switch to version 7 today.
When running the application I get the following errors. What did I forget during the update?
Is there a way to restrict the chat to user groups? For example, only users in an organization unit.
We don't want every user to be able to chat with everyone and certainly not with other tenants.
What's the best way to do that? It would still be best with the Organization Units. The user can only chat with users from the same unit or under it.
We need such a delimitation in any case.
Can you please make the deltas available with your updates?
This would greatly improve the update process.
In the download area you could provide a selection of deltas from version XXX or download the whole project.
If you don't want to change your download area it would be possible to put the deltas of the previous version into one folder and put the whole project into another folder and then into the ZIP file. I don't think anyone would be bothered if they had to download some more files.
If you don't want to provide deltas please explain why not.
We use the Angular + Code version (6.9.1)
When we create a page with the PowerTool there are errors with the modals. The main problem is that you display the modal only with "show" and "hide" and replace the data.
The modal should always be completely reloaded when editing an entry.
Examples of errors:
I have an error message when validating a field. I close the modal without saving and open another entry. All error messages are immediately visible although I haven't changed anything in the new entry yet.
I have readonly fields depending on the settings for some entries. If I edit an entry and the fields become readonly then they remain readonly for every entry I open afterwards.
We've changed that for us, but you might want to change it for you too to make it effective for everyone?
When you create pages through the PowerTools everywhere is an autofocus contained but not in the modals. It would be nice if you open a modal that automatically the first active field becomes an autofocus.
Is there a way to disable visual settings for all users? I would like to activate a template and this should be valid for all users without the possibility to change it.
After upgrading to the new version 6.9.1 Anguar+Core I get an error message for the file app-navigation.servie.ts.
ignoreFeatureCheckForHostUsers does not exist.
Here is the code excerpt:
if (this._appSessionService.tenant || !abp.multiTenancy.ignoreFeatureCheckForHostUsers) { if (menuItem.hasFeatureDependency() && !menuItem.featureDependencySatisfied()) { hideMenuItem = true; } }
After updating to the new version 6.8 of the Angular + Core edition there are bugs in the files "Application\Install\InstallAppService.cs", "Application\Install\Dto\InstallDto.cs" "Application\Configuration\Host\HostSettingsAppService.cs"
The error is that there is an equivocality because the same class is present in "Application.Shared\Configuration\Host\Dto\EmailSettingsEditDto.cs" and "Application.Shared\Configuration\Dto\EmailSettingsEditDto.cs" and there is a using for both.
The selection of entries per page is not displayed correctly in the edge browser. It looks good in Chrome.
Version 6.7.0 Core + Angular.
