This article explains the fixed permissions and field structure for the following Wix Forum collections:
Note: These collections are system collections, so you can't change their permissions in the CMS.
Tip: Before continuing, make sure you've read Working with Wix App Collections.
This section explains the permissions and fields available in the Categories collection.
To use the Categories collection in code, refer to it as Forum/Categories.
The Categories collection has the following permissions:
read: ANYONEcreate: Noneupdate: Noneremove: NoneThis section describes each field in this collection and its properties.
Note: This app collection contains read-only fields that cannot be managed from the collection. You can update the fields from the relevant app in your site’s dashboard.
Each field heading shows the field name followed by the field ID in parentheses, in the format "fieldName (fieldId)".
The fields are listed in the same order as the collection's default order in the CMS.
_id)Description: The category ID.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne, hasSome
Read-only: Yes
parentId)Description: ID of the parent category (for subcategories).
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
name)Description: Category name.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: Yes
Sortable: No
Filter Support: eq, ne, contains, startsWith, hasSome
Read-only: Yes
headerTitle)Description: Title in the category header.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: Yes
Sortable: No
Filter Support: eq, ne, contains, startsWith, hasSome
Read-only: Yes
description)Description: Description in the category header.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: contains, startsWith, hasAll
Read-only: Yes
headerType)Description: Type of category header.
Type: String
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
Note: The headerType field has one of the following values:
ABANDONEDRECOVEREDheaderImage)Description: Header Image.
Type: Image
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
headerImageOverlayColor)Description: Header image overlay color.
Type: Text
Can connect to data: No
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
headerBackgroundColor)Description: Header background color.
Type: Text
Can connect to data: No
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
headerTextColor)Description: Header text color.
Type: No
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
rank)Description: Category order, where 0 indicates the first category.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
postCount)Description: Number of posts in the category.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
postViewCount)Description: Number of times the posts in the category have been viewed.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
Description:
Type: Boolean
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
pageUrl)Description: URL of the category page.
Type: URL
Can connect to data: Yes, can connect as a button click action.
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
slug)Description: The category's slug, which is its URL-friendly name that is unique across the forum.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: Yes
Sortable: No
Filter Support: Yes
Read-only: Yes
This section explains the permissions and fields available in the Comments collection.
To use the Comments collection in code, refer to it as Forum/Comments.
The Comments collection has the following permissions:
read: ANYONEcreate: Noneupdate: Noneremove: NoneThis section describes each field in this collection and its properties.
Note: This app collection contains read-only fields that cannot be managed from the collection. You can update the fields from the relevant app in your site’s dashboard.
Each field heading shows the field name followed by the field ID in parentheses, in the format "fieldName (fieldId)".
The fields are listed in the same order as the collection's default order in the CMS.
_id)Description: The comment ID.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne, hasSome, contains
Read-only: Yes
parentId)Description: ID of the parent comment (for replies).
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
postId)Description: ID of the post that the comment is commenting on.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
ownerId)Description: ID of the comment owner.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: Yes
Read-only: Yes
plainContent)Description: Plain content of the comment.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
replyCount)Description: Number of replies to the comment.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
likeCount)Description: Number of likes on the comment.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
_createdDate)Description: Date and time the comment was created.
Type: Date and Time
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
_editedDate)Description: Date and time the comment was last edited.
Type: Date and Time
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
lastActivityDate)Description: Date and time of the last activity on the comment.
Type: Date and Time
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
pageUrl)Description: URL of the comment page.
Type: URL
Can connect to data: Yes, can connect as a button click action.
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
upvoteCount)Description: Number of upvotes on the comment.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
downvoteCount)Description: Number of downvotes on the comment.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
score)Description: Number of upvotes minus the number of downvotes.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
This section explains the permissions and fields available in the Posts collection.
To use the Posts collection in code, refer to it as Forum/Posts.
The Posts collection has the following permissions:
read: ANYONEcreate: Noneupdate: Noneremove: NoneThis section describes each field in this collection and its properties.
Note: This app collection contains read-only fields that cannot be managed from the collection. You can update the fields from the relevant app in your site’s dashboard.
Each field heading shows the field name followed by the field ID in parentheses, in the format "fieldName (fieldId)".
The fields are listed in the same order as the collection's default order in the CMS.
_id)Description: The post ID.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne, hasSome
Read-only: Yes
categoryId)Description: Post category ID.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
ownerId)Description: Post owner's ID.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
title)Description: Post title.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: Yes
Sortable: No
Filter Support: eq, ne, contains, startsWith, hasSome
Read-only: Yes
plainContent)Description: Plain content of the forum post.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: contains, startsWith, hasAll
Read-only: Yes
bestAnswerCommentId)Description: ID of the comment marked as the best answer.
Type: String
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
pinned)Description: Whether the post is pinned.
Type: Boolean
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne
Read-only: Yes
commentingDisabled)Description: Whether comments are disabled for the post.
Type: Boolean
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
commentCount)Description: Number of comments on the post.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
likeCount)Description: Number of likes on the post.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
viewCount)Description: Number of times the post has been viewed.
Type: Number
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
_createdDate)Description: Date and time the post was created.
Type: Date and Time
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
_editedDate)Description: Date and time the post was last edited.
Type: Date and Time
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
lastActivityDate)Description: Date and time of the last activity performed on the post.
Type: Date and Time
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: Yes
Filter Support: eq, ne, lt, lte, gt, gte
Read-only: Yes
pageUrl)Description: URL of the post page.
Type: URL
Can connect to data: Yes, can connect as a button click action.
Can use in dynamic page URL: No
Sortable: No
Filter Support: No
Read-only: Yes
slug)Description: The post's slug, which is its URL-friendly name that is unique across the forum.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: Yes
Sortable: No
Filter Support: Yes
Read-only: Yes
postType)Description: Type of post.
Type: Text
Can connect to data: Yes
Can use in dynamic page URL: No
Sortable: No
Filter Support: eq, ne
Read-only: Yes
Note: The postType field has one of the following values:
DISCUSSIONQUESTION