This is happening anytime you see a <br /> element in the code. It's happening to me with IE11 on windows 10. I think this is an issue with Open Sans font.
I download the latest version from GitHub just yesterday and ran it today in IE11 and I get the little square anytime you put a <br /> in your code. I took a screenshot on the one that is on the dashboard.
If you inspect that element, nothing stands out but if you go down and take Open Sans out of the font family, it no longer shows up wrong. So after that, I went out to the metronic theme and saw how they were including the google font
<link href="http://fonts.googleapis.com/css?family=Open+Sans:400,300,600,700&subset=all" rel="stylesheet" type="text/css" />
I replaced the link to the local open sans font and it is also working. Not sure how you download the font but there could be something wrong with the local Open Sans files.
I laughed out loud when i saw that. That fixed it. Very much appreciated!
I followed that viewtopic but it's not working for me. I added this code to the User class:
[MaxLength(AbpUserBase.MaxEmailAddressLength)]
public override string UserName { get; set; }
EF recognized the change and added the migration, but when I try and save the entity, it fails validation. Any ideas?
Yes, I already started to do something like that. I think I will add a feature request on GitHub. It would be nice if this was part of the IUserNotificationManager. It's just cleaner if I don't have to implement my own NotificationManager since that is part of the ABP framework and not part of the template.
We could either create an overload for GetUserNotificationsAsync on IUserNotificatioManager or create an alternate method to pass the additional entity information. Maybe GetUserEntityNotificationsAsync.
Once I am done with what I do, I will post the request.
Thanks!
I see where we can publish a notification by Entity (using EntityIdentifier), but I don't see a built in way to query by that. Like the list of Notifications built into the app, I need to create a list to see the all notifications for a particular Entity.
Is there a way to do this that I am just missing? It's probably wishful thinking but I thought I would ask.
Thanks for the prompt reply!
I am on v0.9.6 of the framework:
I am running this code and when I run it, the IMustHaveTenant filter is not getting reset properly on exit of the Using.
using (UnitOfWorkManager.Current.SetTenantId(null))
{
result = _tenantRepository.Get(tenantId.Value);
}
UnitOfWorkManager.Current.SetTenantId(tenantId.Value);
Before I execute the using, there is one FilterParameters in the MustHaveTenant data filter with tenantId = 7. Upon calling SetTenantId(Null), the filter parameter value tenantId turns to 0 as expected. Immediately after the using block, the MustHaveTenant FilterParameters is removed, there is no parameters in the data filter. I expect this to turn back to the way it was before I called SetTenantId(null). This is causing my next get from a MustHaveTenant table to fail because it passes Zero as the parameter value to Sql.
Right now, I am working around the issue by calling the SetTenantId(tenantId.value). This sets the parameters back to the way it was. But, I shouldn't need to call that. This is actually causing me several issues throughout the application.
I looked through the current code on GitHub and I don't see anything that jumps out at me as though it has changed in the latest version of the BaseUnitOfWork.
Here is a video of what is happening:
[https://1drv.ms/v/s!Am91meCOztkro7p10v62y081S_XS_w])
Thanks!
You are correct. I was thinking Host setting not tenant setting.
In a multi-tenant environment, it would be nice to have a setting at the tenant level that was the "host" url.
host.somecompany.com.
As you parse the URL for the tenant name, if it was that setting value, then it would use the Host as the tenant. Right now, I have this out on Azure so I can go to the root website URL to get into the Host, but I would like to give my admin users a proper URL to get to the host.
If there is another way to do this let me know.
Thanks for the quick reply.
Yes, I tossed around keeping it one Context to simplify but I just liked the clean separation. I know it's a bit more complicated, but I just felt like I wanted the system to fail if I try and Add an Edition record to a Tenant DB. But I do respect keeping it one for simplification. I definitely did not want to use separate contexts with similar schemas.
I will make these changes and share them here in case anyone else wants to be brave like me :)
Before I start my next step, making all this work in Azure, have you all tried this yet? I am not 100% sure, but I have a feeling the Create tenant database process when adding a tenant won't work (not sure you can create DB's like that and not sure DTC works in Azure). Just wondering if you all may have worked through any of this.
Thanks again!