[JIRA] Commented: (NXS-872) Add a feature to completely override a document type
[
https://jira.nuxeo.com/browse/NXS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=109679#comment-109679
]
Pivotal Integration commented on NXS-872:
-
Delphine Renevey deleted the linked story in Pivotal Tracker
Add a feature to completely override a document type
-
Key: NXS-872
URL: https://jira.nuxeo.com/browse/NXS-872
Project: Nuxeo Studio
Issue Type: Improvement
Components: Schemas
Affects Versions: 2.4.3
Reporter: Thierry Martins
Priority: Major
Fix For: 2.6, Short term backlog
Sometimes, a user needs to override the previous definition of a document
type defined in Nuxeo, like Workspace or Folder: for instance, he will need
to redefine the accepted document types.
But because of the default definition and the merge policy of the extension
point, you can only add accepted document types.
It would be interesting to add a checkbox to force the overriding and
generate a contribution like
{code:xml}
type id=Workspace remove=true /
{code}
before the contribution corresponding to what was defined in Studio UI.
Otherwise, we can think about implementing the deniedSubTypes attribute, but
it won't solve all issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
[JIRA] Commented: (NXS-872) Add a feature to completely override a document type
[
https://jira.nuxeo.com/browse/NXS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=109531#comment-109531
]
Pivotal Integration commented on NXS-872:
-
A Pivotal Tracker story has been created for this Issue:
http://www.pivotaltracker.com/story/show/23405643
Add a feature to completely override a document type
-
Key: NXS-872
URL: https://jira.nuxeo.com/browse/NXS-872
Project: Nuxeo Studio
Issue Type: Improvement
Components: Schemas
Affects Versions: 2.4.3
Reporter: Thierry Martins
Priority: Major
Fix For: 2.6, Short term backlog
Sometimes, a user needs to override the previous definition of a document
type defined in Nuxeo, like Workspace or Folder: for instance, he will need
to redefine the accepted document types.
But because of the default definition and the merge policy of the extension
point, you can only add accepted document types.
It would be interesting to add a checkbox to force the overriding and
generate a contribution like
{code:xml}
type id=Workspace remove=true /
{code}
before the contribution corresponding to what was defined in Studio UI.
Otherwise, we can think about implementing the deniedSubTypes attribute, but
it won't solve all issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
[JIRA] Commented: (NXS-872) Add a feature to completely override a document type
[
https://jira.nuxeo.com/browse/NXS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=109035#comment-109035
]
Alain Escaffre commented on NXS-872:
Studio features are not designed to do merge with existing contributions, it
is not the philosophy. So why don't we add the remove=true systematically ?
Indeed the overriding vs merging stuff is to complex for many of the Studio
users, I think.
Furthermore, so far the remove instruction is probably not on all the
extension descriptors. At least, the frequent usecases for overriding would be
for (those who would need this instruction):
- document types
- layouts
- result layouts
- lifecycle
- content template (Structure template)
- mail notification
Add a feature to completely override a document type
-
Key: NXS-872
URL: https://jira.nuxeo.com/browse/NXS-872
Project: Nuxeo Studio
Issue Type: Improvement
Components: Schemas
Affects Versions: 2.4.3
Reporter: Thierry Martins
Priority: Major
Sometimes, a user needs to override the previous definition of a document
type defined in Nuxeo, like Workspace or Folder: for instance, he will need
to redefine the accepted document types.
But because of the default definition and the merge policy of the extension
point, you can only add accepted document types.
It would be interesting to add a checkbox to force the overriding and
generate a contribution like
{code:xml}
type id=Workspace remove=true /
{code}
before the contribution corresponding to what was defined in Studio UI.
Otherwise, we can think about implementing the deniedSubTypes attribute, but
it won't solve all issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
[JIRA] Commented: (NXS-872) Add a feature to completely override a document type
[
https://jira.nuxeo.com/browse/NXS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108164#comment-108164
]
Anahide Tchertchian commented on NXS-872:
-
this should be addressed as a whole for all features, not only documents (as
well as possibility to disable the feature for instance)
Add a feature to completely override a document type
-
Key: NXS-872
URL: https://jira.nuxeo.com/browse/NXS-872
Project: Nuxeo Studio
Issue Type: Improvement
Components: Schemas
Affects Versions: 2.4.3
Reporter: Thierry Martins
Priority: Major
Sometimes, a user needs to override the previous definition of a document
type defined in Nuxeo, like Workspace or Folder: for instance, he will need
to redefine the accepted document types.
But because of the default definition and the merge policy of the extension
point, you can only add accepted document types.
It would be interesting to add a checkbox to force the overriding and
generate a contribution like
{code:xml}
type id=Workspace remove=true /
{code}
before the contribution corresponding to what was defined in Studio UI.
Otherwise, we can think about implementing the deniedSubTypes attribute, but
it won't solve all issues.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
