-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Draft feature added to the pages. #24053
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
MansurBesleney
wants to merge
10
commits into
dev
Choose a base branch
from
issue-#23616
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduces the PageStatus enum and adds a Status property to Page and PageCacheItem. Updates PageManager, IPageRepository, EfCorePageRepository, and MongoPageRepository to support filtering and managing pages by status. This enables handling draft and published states for pages.
Introduces the PageStatus property to page-related DTOs, allowing filtering and setting of page status in admin APIs. Updates service methods and repository calls to handle the new status parameter, and enforces the status field as required in the EF Core model configuration.
Introduces a 'Status' field to both the page creation and update forms in the admin web module, allowing users to set or modify the status of a page. Updates the view models and UI to support this new property.
Introduces a PageStatus property to PageDto and updates PagePublicAppService to only return pages with a published status. This ensures that only published pages are accessible via public endpoints.
Introduced a new 'Status' field to the Pages entity via EF Core migration. Added migration files and updated the model snapshot to reflect the schema change. Also removed the solution file 'cms-kit.sln'.
Replaces the single submit button with separate 'Save as Draft' and 'Publish' buttons on both Create and Update page forms. Updates the status field handling and form submission logic in the corresponding JavaScript files. Marks the Status property as hidden input in the page models to support the new workflow.
Introduced a new 'Status' column in the CMS pages admin table, displaying localized page status values. Added corresponding English localization entries for page status enums.
maliming
approved these changes
Oct 30, 2025
gizemmutukurt
requested changes
Oct 30, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
Resolves #23616
Checklist