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

Quick Create does not respect setting for default template #5078

Closed
modxbot opened this issue Jun 20, 2011 · 4 comments
Closed

Quick Create does not respect setting for default template #5078

modxbot opened this issue Jun 20, 2011 · 4 comments
Labels
bug The issue in the code or project, which should be addressed. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.

Comments

@modxbot
Copy link
Contributor

modxbot commented Jun 20, 2011

fveaux created Redmine issue ID 5078

When a resource or symlink is created using Quick Create, the Template always defaults to template #1, regardless of the setting for the default template in System Settings.

@splittingred
Copy link

splittingred submitted:

I can't replicate this at all; mine works fine. Can you provide more information?

@modxbot
Copy link
Contributor Author

modxbot commented Jul 1, 2011

fveaux submitted:

I've done some more testing, and it appears to happen only in a context other than the default Web context. Steps to reproduce:

  1. Create anew context.
  2. In the context settings, create a new key default_template and assign it a value other than 1.
  3. Right-click the context and choose Create -> Create a Document Here. The setting for the default template is respected.
  4. Right-click the context and choose Quick Create -> Document or Quick Create -> Symlink. The setting for the default template is not respected.

@opengeek
Copy link
Member

opengeek submitted:

I can confirm this behavior on 2.1.3-pl and latest develop when using Quick Create on the context node that has a different default_template.

@splittingred
Copy link

splittingred submitted:

Whew, that was a tricky one. Fixed: 1dc224b

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue in the code or project, which should be addressed. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.
Projects
None yet
Development

No branches or pull requests

3 participants