Skip to content
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

Need a provision where the first created version is the published one always. #146

Open
akshyabhargava opened this issue Nov 7, 2023 · 1 comment
Labels
issue: feature request Issue suggesting a new feature severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve

Comments

@akshyabhargava
Copy link

Hi Team

I am inquiring about the possibility of establishing a system where the initially created page or post type always retains its status as the published version, even if we subsequently create new versions and publish them. In other words, when transitioning to a different version, it should automatically publish that particular version while preserving the original ID of the initially created page.

I am requesting this feature because we require consistent references to effectively manage our data.

Looking for a quick help here.

Regards,
Akshya B.

@omikulcik
Copy link
Collaborator

Hi, @akshyabhargava thank you for submiting your feature request. To me it seems like a really edge case feature and thus we will probably not ship it in the foreseeable future if it is not requested by multiple users. However you can always fork this repo and build it yourself.

I will leave this open for a while to see whether more people would like to have this feature.

@omikulcik omikulcik added issue: feature request Issue suggesting a new feature severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve labels Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: feature request Issue suggesting a new feature severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve
Projects
None yet
Development

No branches or pull requests

2 participants