Every SaaS system I have ever used has required an email, this is industry standard. Faceboook, Google+, Discord, Slack, Mint.com, Turbotax... I literally cannot think of a single service that DOESN'T require a valid email.
Without email verification, how will you prevent a bot service from launching an attack on your site and flooding it with fake accounts? And Don't say reCaptcha (See this whitepaper: here.)
Also, what happens when a user forgets his password? How are you going to allow them to reset if you have no user information to otherwise identify him/her?
Moreover, without the ability to contact your users, how are you going to send them information and updates about your platform?
Which SMTP provider are you using? Are they configured to use TLS or SSL? Do they require Authentication? Did you provide the correct authentication credentials if so?
Pretty sure the Localization cookie is how the front end knows what language to localize in javascript.
I don't think external links are supported. I have a separate issue due to the current constraints of the menu system, see here:
Perhaps it would be of use to request enhancements to the constricting menu system on github?
Hey Guys,
We're implementing our own page 'transitioner' in between server calls. I've looked for the current circle icon transitioner when a user authenticates and is routed to the dashboard but can't seem to find it. Any idea where this lives and what its called?
Thanks.
Part of the answer is "Them's the requirements." Stakeholders and such.
Part of the answer is, some of the forms take up multiple pages, and modals are very poorly suited for displaying the content, so the navigation must direct to full pages.
We can manually create the menu on each page, but that is less than ideal, for obvious reasons.
My current thinking is to add an additional params string[] parameter to the view component itself, and in the menu definition use a string format pattern. Then I can add an string[] to the MenuItemViewModel, and update the CalculateUrl extension to accept the params as well.
But this only works if every menu item requires the same params, which may or may not be the case for some applications.
Imagine you have the standard top menu for the application, you navigate from the tenant page to a tenant details view.
There is a left nav built using the navigation provider, that has an edit and delete link to pages instead of modals.
Those edit and delete links reference actions that have a parameter, but the navigation provider does not appear to support actions with parameters.
(This is not our exact scenario, and is only presented as an example.)
We are trying to determine the best approach to fit our needs, because we will have a lot of menus like this, and we don't want to make extensive customizations to the NavigationProvider class in the event it gets updated in the future, unless we absolutely have to.
I would just like to chime in that I think this would be very useful.
Especially topics like hosting, deployments, CI, etc.
I know this isn't necessarily Volosoft's responsibility, but there are some unique challenges due to the framework. For instance, the nature of the application means that our TeamCity build process has some extra steps, and must create two separate packages for Octopus, one for the migration project, and one for the web app, because we are deploying the application to an Azure Web App.
Also, it seems like a lot of the customers are choosing this product because they don't have the resources to develop the framework on their own, so it stands to reason that they may not have dedicated senior DevOps to guide them.
For our team, it definitely took us a while to realize that we needed to go back to the ABP documentation and really dig into it before we could understand how to work with Zero. In the beginning it was very unclear for us where ABP ended and Zero began (the truth of the matter is, ABP is really all that matters. Everything in Zero is just customization / extensions to ABP.)
But from a business perspective, their team is small, and they actually have better documentation that most frameworks I've worked with outside of monolithic frameworks like Angular. I think, as consumers, we could contribute a lot to the community by sharing our solutions, and Volosoft could contribute by compiling them into an easy to consume platform (a Wiki or something) that would allow us to find these solutions in a better format than the forums.
Just my two cents :D
Hello,
We are wanting to create a reusable sub-nav / menu for a series of pages that belong to an entity.
For example, the main navigation provider has a link to 'Companies'. Clicking this navigates the user to a list view of companies where the user can then click the Action drop down to then navigate to the 'Details' view of a company.
The 'Details' view of a particular company is where we want to create a reusable navigation provider for a left navigation which will have other pages that are associates of a Company Entity such as Company Documents, Contacts, Addresses etc.
What is the best approach to appending the Company Id to these links if we are using a custom menu that extends the NavigationProvider class? Thanks.
I tried both ReSharper and VS test runner.
It turned out to be an issue with shadow copying, and even with ReSharper set to not shadow copy, it still would.
I ended up having to create an xunit.runner.json in the test project and set shadowCopy: false, per this:
<a class="postlink" href="https://xunit.github.io/docs/configuring-with-json.html">https://xunit.github.io/docs/configuring-with-json.html</a>
