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

Generated config prevents CloudCannon's handling of Jekyll tags #1

Open
rycoll opened this issue Jan 20, 2023 · 0 comments
Open

Generated config prevents CloudCannon's handling of Jekyll tags #1

rycoll opened this issue Jan 20, 2023 · 0 comments

Comments

@rycoll
Copy link

rycoll commented Jan 20, 2023

I ran the migrator over a Jekyll site, and it produced the following config:

collections_config:
  posts:
    schemas:
      default:
        _inputs:
	  $.tags:
	    type: multiselect
	    options:
	      values: [] # I assume this line is the problem
	      allow_create: true
	      allow_empty: true

This worked great!

... except that when I clicked the tags multiselect for posts in the Content Editor, I didn't get a dropdown showing all the existing tags on the site, which is normally what CloudCannon does for tags on a Jekyll post. Commenting out the _inputs.$.tags config allowed this behaviour to start working again.

Perhaps the migrator could avoid overwriting the default behaviour for tags on a Jekyll site?

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

1 participant