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

Content Type set to Binary by default #9026

Closed
garryn opened this issue Oct 25, 2012 · 0 comments
Closed

Content Type set to Binary by default #9026

garryn opened this issue Oct 25, 2012 · 0 comments
Labels
area-core bug The issue in the code or project, which should be addressed.

Comments

@garryn
Copy link
Member

garryn commented Oct 25, 2012

garryn created Redmine issue ID 9026

When adding a content type, the Binary dropdown says 'No' but, by default, the content type is added with the Binary option set.

enigmatic-user pushed a commit to enigmatic-user/revolution that referenced this issue Feb 13, 2014
enigmatic-user pushed a commit to enigmatic-user/revolution that referenced this issue Feb 13, 2014
Merge remote-tracking branch 'garryn/bug-9026' into bug-9026

* garryn/bug-9026:
  [modxcms#9026] Fix issue where a new Content Type was always added with Binary set to true
danyaPostfactum pushed a commit to danyaPostfactum/revolution that referenced this issue Mar 26, 2014
* release-2.2:
  [modxcms#8928] Error saving Resource with access-restricted TemplateVars
  [modxcms#8978] Fix issue where change template was not fired due to onsave check overriding listener
  [modxcms#9026] Fix issue where a new Content Type was always added with Binary set to true

Conflicts:
	core/docs/changelog.txt
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-core bug The issue in the code or project, which should be addressed.
Projects
None yet
Development

No branches or pull requests

1 participant