Would that also inadvertently kill all page notifications, or is it only the chat-notifications that it gets rid of?
There was a post that asked about SignalR (https://support.aspnetzero.com/QA/Questions/8300) So, it seems we'd lose 'Real-Time' notification and I wanted to make sure that I understood that 'Chat notifications' and 'Real-time notifications' were synonymous and there was nothing else using real time notifications
aaron, is there a way to easily supress the amount of network/API log spam that SignalR produces?
I have noticed this often
It mainly happens with new browsers with no cached info and it hangs up on /AbpUserConfiguration/GetAll?d=1578436192228
Is there any update on this?
@maliming - the first link you mentioned gives the direction: "you can remove it's codes from your project." Is there more information on how to remove chat all together other than "Just remove it"
Is @tinytownsoftware's answer the easiest way to do that and is that the extent of the changes in order to remove Chat as a whole?
I've found a number of issues come up if you are not running ASPNETCORE_ENVIRONMENT = Production when hosting
One of which being the Emails will NOT get sent if in Development, theres code that catches email credentials and fakes sending it
there were a few changes to page but nothing significant When I compared the files it looks like there was a reordered div
updating code with div in what I think is the original location and seeing if that fixes the issue
Edit: Confirmed. That reorder had indeed killed the UI and now it seems to be working as expected
They're going to ask Which product? and then probably tell you to check the log - which should be located at \App_Data\Logs\Logs.txt
The issue you might run into trying to find that file is if you're using an App service you need to find a way to FTP to the location in order to reach the log file blob and download it locally
Heres the angular content which might help you figure out what to add there https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Overview-Angular#basic-configuration
In the development time...
Ok, but I am attempting to push to production. All the options and settings that I've seen for build have been specific for a Production environment. Where exactly am I supposed to switch something to tell the application that this is production - since all the places that I saw should have told the application this is Production yet the option is still showing up.
Is there a setting that would delete that from being on the login page or is this a manual edit that must be made on the application when we are ready for production?
I noticed that if I setup a new tenant/user, when validating the user it emails a link for verification. The link sends you to a Tenant.mywebsite.com. What I'm having an issue understanding is the tenant option is already selected when I use that link and it does indeed sign me into that tenant
When I use a new browser to go directly to tenant.mywebsite.com, it only ever sends me to the host tenant
Based on your description of how tenant routing works, it seems to not be able to recognize the tenant in the browser and always sends me to host.
There are no errors in the log and the network logs do indeed show that tenant.mysite.com was hit Where in the application does it identify which tenant it should be routing to?
If log is telling me that I’m hitting the right tenant and browser always sends me to host - is this a bug with the application or if not, can you direct me to identify where it might be failing?
2020-01-07 edit: It looks like there was an additional issue that was causing my confusion. The account.component.html was modified by dev and due to that error it caused the issues mentioned
There is documentation that talks about tenancy and how to implement in general but I am not sure what a client solution looks like
I have not come across documentation saying to updating those files but I'm running into other issues and I wanted to ask if launchsettings.json files should be updated prior to build - or does routing and variable updating happen off of the appsettings.Production.json