ZOVANTA SOFTWARE / KNOWLEDGEBASE

Groups 1.3.0 • inspected package; hosting/live validation not claimed

Groups — current settings and requirements

Inspected build

Groups 1.3.0, package key forovanta-groups. Declared core requirement: >=1.0.0. This is source documentation, not a fresh live-install certification. Preserve the package/data and read its update plan.

Settings

The following labels/defaults come from the inspected manifest. The runtime may group or replace these controls with a dedicated screen; save through that screen.

Control Initial value Meaning
Groups per page 12 How many group cards one page of the directory shows.
Discussions per page 20 How many discussions one page of a group's feed lists.
Group categories true Let a group be filed under a category, and show the category panel beside the directory. A board that keeps one flat list of clubs can turn this off.
Members can create groups true Turn this off to keep the directory staff-only. Members can still join the groups that exist.
Review new groups false A group a member creates stays hidden until a moderator approves it. Groups staff create are never held.
New groups are "open" What a new group starts as. A group can change its own privacy afterwards, and a closed group's discussions are its members' business. Choices: Open — anyone may join, the group page is public, Closed — anyone may ask, the group page is public, Private — invited members only, nothing is public.
Groups one member may own 3 0 means no limit. It is what keeps a directory from becoming one person's project.
Group discussions true Each group gets a feed of its own. Turning this off leaves the group page, its members and its description.
Members per page 30 How many members one page of a group's member list shows, with the group's owner and moderators first.
Posts per discussion page 20 Follow the package screen and preserve the current value when updating.

Install or update

Use the addon ZIP itself in Admin → Add-ons → Upload → Review → Install/Upgrade; addon.json belongs at its root. Do not upload the complete source/recovery bundle to core Package Manager. Back up database and private files, preserve existing settings/license/enabled state, and do not uninstall as an update step. After upgrading, test the actual member and staff operations, not just the new version label.

Current operating workflow · Shared addon installation

We suggest Panelica for managing your hosting environment.