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

CP Blueprint fieldtype(s) & content not being removed from published pages #4566

Closed
archoda opened this issue Oct 24, 2021 · 1 comment
Closed

Comments

@archoda
Copy link

archoda commented Oct 24, 2021

Bug description

When you edit a blueprint and add a content field type. You can go to a page, add and publish content. It works fine. But, when you remove that field from the blueprint, then republish that corresponding page it doesn't remove the old blueprint field and data in the YAML.

How to reproduce

  1. Go to Blueprints -> Pages.
  2. Add a simple Text FieldType, call it 'simple' save
  3. Navigate to Collections -> Pages -> [Any Page] and ADD content to the 'simple' field and publish
  4. Find the file 'content/collections/pages[pagename].md' to ensure it added and published the content
  5. Navigate to Collections -> Pages -> [Any Page] and REMOVE content to the 'simple' field and re-publish
  6. Find the file 'content/collections/pages[pagename].md' and see it keeps the 'simple' field and content

Screen Shot 2021-10-24 at 12 55 32 PM

Logs

No response

Versions

Statamic 3.2.17 Solo
Laravel 8.67.0
PHP 7.3.24-(to be removed in future macOS)
No addons installed

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

@jasonvarga
Copy link
Member

You're allowed to have any arbitrary data in your entries. They don't all have to be part of the blueprint. We don't remove any content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants