menu
Logo
  • Why azing?
  • Blog
  • Help
ENarrow_drop_down
  • DE
  • EN
Suche in Checklisten
search
azing Logo ENarrow_drop_down
  • DE
  • EN
  • Why azing?
  • Help
2sxc
drive_folder_upload
  • homeChecklist Templates
  • south
  • fiber_manual_recordZ: Internal Stuff for the 2sxc-Dev Team
  • south

folder_sharedFeatures Management

  • homeChecklist Templates
  • south
  • fiber_manual_recordZ: Internal Stuff for the 2sxc-Dev Team
  • south

folder_sharedFeatures Management

Folders and checklists

  • check_circleFeature - Create new registered feature
  • check_circleFeature - Program a feature activation and warning in C#
  • check_circleFeature - Register new Feature Guid in Web-Catalog and Code-Catalog
  • infoFeature - Understanding UI and Public

Parts (0) expand_more

These are small document-parts which are used in other documents. They are not a starting point for any real activity. Because of this, they will be listed further down and the search will not list them unless requested. 

Every feature that the server code knows about can be UI-Relevant or Public. You'll see this in code like:

public static FeatureList Catalog = new FeatureList(new List<Feature>
{
// released features
new Feature(FeatureIds.PublicForms, true, false),
new Feature(FeatureIds.PublicUpload, true, false),

...

Here's what it means:

  • UI means that this information is needed by the normal edit-ui, because this feature status will be needed in JavaScript. Setting it to true means that it will be provided in the features webapi for lookup.
  • Public means that this information will also be given to JavaScript in cases where the user is not logged in. So some UI features may be important, but we don't want to have public users know that it's activated or not, so we won't let them know this.
Logo
Legal | Content Copyright CC-BY 4.0
bug_reportReport Bug
  • info
  • Links
  • Permissions
code Share
code
URL copied to clipboard.
Embed Checklist close
Copy Copy
Content Copyright

CC-BY 4.0

Translations

None

2sxc - Content Management for DNN & Oqtane Logo

2sxc - Content Management for DNN & Oqtane

QR-Code
azing.org/2sxc/r/o88slPcp
View & Use

Public (can be used by everybody)

Edit & Admin

Default (all members can edit)

This catalog has a simple permission model, where all members have the same permissions. For advanced permissions, upgrade to Enterprise.

Here you can see how this document is used and linked by other documents

Used in (1)

Others referencing this

  1. Feature - Register new Feature Guid in Web-Catalog and Code-Catalog
Uses these (0)

Documents linked from this document

How it Behaves

How this document is categorized changes how it behaves.

This is a main document, it is listed normally and appears in search result.

Type

This is an Information. Lists are treated as information and not as checkboxes'

Get something to say?

Comment to start a discussion or make a note
send

please log on to chat

close

Durchsuche ganz Azing