CyberStoreBaseControl
CyberStoreBaseControl is the shared base control for front-end CyberStore controls. Its configurable properties establish common visibility and access conditions. A derived control can provide additional properties for its own behavior.
Visibility and access
Use these properties on a control configuration when the supported control behavior needs a shared condition.
| Property | Default | Valid values or format | Effect |
|---|---|---|---|
IgnoreControlNot specified | Not specified | When true, CyberStore skips control processing and does not render the control. | |
RequireAnonymousNot specified | Not specified | Applies the control’s anonymous-shopper loading condition. | |
RequireLoginNot specified | Not specified | Applies the control’s signed-in-shopper loading condition. | |
AttributesBagNot specified | Not specified | Gets or sets the attributes bag. | |
IsItemPageNot specified | Not specified | Gets a value indicating whether this object is item page. |
SitePages.config example
The following example loads CyberStoreBaseControl.ascx and applies the documented literal defaults. The following properties are omitted because they do not have documented literal defaults: IgnoreControl, RequireAnonymous, RequireLogin, AttributesBag, IsItemPage.
<Control src="CyberStoreBaseControl.ascx" />
Add this <Control> element to the appropriate page placeholder as described in The SitePages.config File.
This reference does not document defaults, supported combinations, or precedence for these properties. Validate the selected condition in the target storefront before publishing it.
Inheritance
Controls derived from CyberStoreBaseControl can use these shared conditions and can define their own configurable behavior. Do not repeat inherited options on a derived-control configuration unless that control explicitly changes their behavior.
ItemControl is a direct CyberStore base derived from this control. See ItemControl for its item-type visibility conditions.
Implementation boundary
The legacy reference also exposes control context, configuration, shopper, and site values used internally during processing. Those values are not a supported public configuration surface and are intentionally omitted from this guide.
Validate the control
- Add the target control through
SitePages.config. - Set one shared visibility or access condition.
- Test the condition with the applicable shopper state or control configuration.
- Confirm that the control renders or does not render as expected without affecting unrelated controls on the page.