StoreServer administrators can move Store components through active, maintenance, deprecated and retired lifecycle states; unpublish or remove them from the Store; or permanently delete components/releases. Before destructive actions, DivisionDesk reports clients using the component/version and publishe…
Read full article →
StoreDefine organization types, then mark Store components required, recommended, optional, unavailable or incompatible. Child organization types inherit parent rules unless overridden. Client update resolution also checks Core, PHP and dependencies/conflicts.
Read full article →
StorePublished package downloads are delivered through a DivisionDesk PHP endpoint rather than directly through static ZIP URLs. The compatibility endpoint checks publication/lifecycle state, Core-version compatibility, release-tree containment and SHA-256 integrity. When a client identity or license co…
Read full article →
StoreStore packages can be Free, Included, Paid, Trial-enabled, Private/Assigned or Not for Sale. Paid packages may offer monthly, annual and lifetime terms. Access is enforced by license entitlements rather than by hiding buttons. Restricted package files are delivered only after signed client authoriz…
Read full article →
StoreModules add major capabilities. Widgets add reusable page output. Themes change design. Site Templates are complete editable websites. Page Layouts provide individual reusable pages. Required dependencies install automatically.
Read full article →