MaximumUserCount Feature #12633

4 Answer(s)

• 

  0

  oguzhanagir created 7 months ago

  Support Team

  Hi @gerryp

  The "Maximum User Count" feature uses a numeric input type, not a checkbox type. The disabled checkbox you see is just how tree component renders non selectable nodes, it's cosmetic and expected.

  You should see a number input field to the right of the "Maximum User Count" label. Type the desired value there (e.g., 10 for 10 users, or 0 for unlimited). The value is controlled by the text input, not the checkbox.

  If you don't see the number input at all, it could be a CSS/rendering issue. Try inspecting the element in your browser's developer tools to see if the <input type="number"> is present but possibly hidden.

  The backend definition in AppFeatureProvider.cs is:

  context.Create(
      AppFeatures.MaxUserCount,
      defaultValue: "0", // 0 = unlimited
      displayName: L("MaximumUserCount"),
      description: L("MaximumUserCount_Description"),
      inputType: new SingleLineStringInputType(new NumericValueValidator(0, int.MaxValue))
  );
  

  If you require further information, please do not hesitate to contact us.

  Thank you

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  gerryp created 7 months ago

  I've looked at the generated HTML using the developer tools. There is no <input type="number"/>. In fact, there is no input at all. I think there may have been some kind of regression. This is asp.net zero version v14.2.

  Thanks.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  oguzhanagir created 7 months ago

  Support Team

  Hi @gerryp

  Thank you for the clarification.

  If there is no input element rendered at all in the DOM, then this is not expected behavior. For MaxUserCount, ASP.NET Zero defines this feature as a numeric text input, so the UI should render an editable field rather than only a checkbox placeholder.

  Since you mentioned you are using v14.2, this may be related to a UI regression or a customization issue in the tenant feature modal.

  Could you please check the following points:

  1. Open the tenant Features modal and inspect whether there are any JavaScript errors in the browser console.
  2. Verify whether this issue also occurs in a fresh, unmodified ASP.NET Zero v14.2 installation.
  3. Check whether there are any customizations in the feature management component/page that may affect rendering.

  For reference, the feature is defined in AppFeatureProvider.cs like this:

  context.Create(
      AppFeatures.MaxUserCount,
      defaultValue: "0",
      displayName: L("MaximumUserCount"),
      description: L("MaximumUserCount_Description"),
      inputType: new SingleLineStringInputType(new NumericValueValidator(0, int.MaxValue))
  );
  

  So an input should definitely be generated for this feature.

  If possible, please send us:

  • a screenshot of the Features modal,
  • the browser console output,
  • whether your project is customized or a clean installation,
  • and if you could also tell us which UI you're using, we can conduct a more accurate investigation.

  This will help determine whether the issue is caused by a regression in v14.2 or by a project specific customization.

  You can send your project to [email protected] if you wish. We can examine this in more detail and offer you a specific solution to your problem.

  Thank you.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel
• 

  0

  gerryp created 7 months ago

  I found the issue. It's not asp.net zero at all. There is a known bug in primeng's tree control with how templates are used.

  First, if you're using standalone components with Angular 20, PrimeTemplate must be explicitly imported in your component for the [pTemplate] directive to be recognized. You need to import SharedModule like this:

  import { SharedModule } from 'primeng/api';

  and include it in the list of imported modules.

  Next, I changed the template definition in feature-tree.component.ts from: <ng-template let-node #default>

  to:

  <ng-template let-node pTemplate='default'>

  And then the editor appeared.

  This may be affecting other p-tree controls used in the asp.net zero UI.

  Markdown is supported

  Copy & paste or drag & drop images (max 30 MB per image)

  Save Cancel