PageVersions Model
Overview
The pageversions table is used to store the versioning details of pages. It allows tracking of different versions of the same page, storing the version name, associated template, package details, and the content of each version.
Fields
| Field | Type | Description | Required |
|---|---|---|---|
| id | string | A unique identifier for the page version | ❌ |
| page_id | string | ID of the page that this version belongs to. Links this version to a specific page in the system. | ✅ |
| pagename | string | The name of the page. | ✅ |
| version | string | The version of the page (e.g., 1.0, 1.1, 2.0). Helps in managing different versions of the same page. | ❌ |
| packageId | string | The package ID that the page version belongs to, if applicable. This could link the page version to a specific set of content or module. | ❌ |
| template_id | string | The identifier of the template associated with the page version.This might refer to a page layout or style template. | ❌ |
| created_at | date | The timestamp when the page version was created. | ❌ |
| modified_at | date | The timestamp when the page version was last updated. | ❌ |
| pagedetails | object | Detailed information about the page version. This could include HTML, JSON, or other serialized content that defines the page’s structure and data. | ❌ |
Sample JSON
{
"id": "example_value",
"page_id": "example_value",
"pagename": "example_value",
"version": "example_value",
"packageId": "example_value",
"template_id": "example_value",
"created_at": "example_value",
"modified_at": "example_value",
"pagedetails": "example_value"
}