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

Allow copying contents when they're not in the elements.yml #2068

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

mamhoff
Copy link
Contributor

@mamhoff mamhoff commented Apr 15, 2021

What is this pull request for?

When changing the elements.yml, we will often still have contents from
previous iterations of that file in the database. Copying must still
work.

Checklist

  • I have followed Pull Request guidelines
  • I have added a detailed description into each commit message
  • I have added tests to cover this change

When changing the elements.yml, we will often still have contents from
previous iterations of that file in the database. Copying must still
work.
@tvdeyen tvdeyen added this to the 6.0 milestone Apr 15, 2021
Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks

@mamhoff mamhoff merged commit 9eb591e into AlchemyCMS:main Apr 15, 2021
@mamhoff mamhoff deleted the allow-publishing-legacy-contents branch April 15, 2021 17:07
robinboening pushed a commit to robinboening/alchemy_cms that referenced this pull request Jul 2, 2021
…MS#2068)

When changing the elements.yml, we will often still have contents from
previous iterations of that file in the database. Copying must still
work.
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

Successfully merging this pull request may close these issues.

2 participants