[JIRA] Created: (LIVED-215) No action clik on live edit icon.
No action clik on live edit icon. - Key: LIVED-215 URL: https://jira.nuxeo.com/browse/LIVED-215 Project: Nuxeo Live Desktop Issue Type: Bug Components: NLE MSO, Protocol Handler plugin Affects Versions: Protocol Handler 0.5.0, NLE 2.3.0 Environment: nuxeo in ubuntu server 10.04 ; navigate unde windows 7 with Firefox 4+ Reporter: etienne vallier Assignee: Arnaud Kervern Priority: Major in nuxeo interface live edit icon doesn't work. no action when click on. I have this issue since upgrade in protocol handler 0.5 I upgrade last live edit I test in all firefox since 4 to 9 the same issue. I can't test live edit alone, i use IE9 and it's not compatible plugin's thanks for look at this. -- 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: (LIVED-215) No action clik on live edit icon.
[ https://jira.nuxeo.com/browse/LIVED-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108369#comment-108369 ] Arnaud Kervern commented on LIVED-215: -- You could test LiveEdit with IE9 using the compatibility modes in the developer toolbar (IE9 compatibility mode is enough). Be sure to enable it before login. No action clik on live edit icon. - Key: LIVED-215 URL: https://jira.nuxeo.com/browse/LIVED-215 Project: Nuxeo Live Desktop Issue Type: Bug Components: NLE MSO, Protocol Handler plugin Affects Versions: NLE 2.3.0, Protocol Handler 0.5.0 Environment: nuxeo in ubuntu server 10.04 ; navigate unde windows 7 with Firefox 4+ Reporter: etienne vallier Assignee: Arnaud Kervern Priority: Major in nuxeo interface live edit icon doesn't work. no action when click on. I have this issue since upgrade in protocol handler 0.5 I upgrade last live edit I test in all firefox since 4 to 9 the same issue. I can't test live edit alone, i use IE9 and it's not compatible plugin's thanks for look at this. -- 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] Created: (NXP-8200) User suggest box style changes when DAM is installed
User suggest box style changes when DAM is installed Key: NXP-8200 URL: https://jira.nuxeo.com/browse/NXP-8200 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Web UI Affects Versions: 5.5 Reporter: Solen Guitter Priority: Detail Fix For: 5.5.x When user installs CAP, DM, Social Collab, the user suggest box (used in Access Rights tab for instance) has a white background. As soon as user installs DAM, the box gets the old light blue background everywhere. -- 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] Updated: (NXP-8200) User suggest box style changes when DAM is installed
[ https://jira.nuxeo.com/browse/NXP-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solen Guitter updated NXP-8200: --- Attachment: Screen Shot 2011-12-21 at 11.13.49.png Screen Shot 2011-12-21 at 11.21.29.png User suggest box style changes when DAM is installed Key: NXP-8200 URL: https://jira.nuxeo.com/browse/NXP-8200 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Web UI Affects Versions: 5.5 Reporter: Solen Guitter Priority: Detail Fix For: 5.5.x Attachments: Screen Shot 2011-12-21 at 11.13.49.png, Screen Shot 2011-12-21 at 11.21.29.png When user installs CAP, DM, Social Collab, the user suggest box (used in Access Rights tab for instance) has a white background. As soon as user installs DAM, the box gets the old light blue background everywhere. -- 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] Created: (NXP-8201) Add support for document rendition via Office Templating
Add support for document rendition via Office Templating
Key: NXP-8201
URL: https://jira.nuxeo.com/browse/NXP-8201
Project: Nuxeo Enterprise Platform
Issue Type: User story
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
h2. Use cases
There are several cases where it makes sens to generate a rendition of a Nuxeo
Document.
Typically :
- you store product related information in Nuxeo
= you want to generate a Product description file in .doc or .pdf
(with most important meta-data + version and history info + picture)
- you manage mails in Nuxeo
= you want to generate the response letter
(with logo, custom header ...)
- you store Specifications / Code audit / Benchmark results in Nuxeo
= you want to generate the delivrable report
(with Cover page, Index, and data aggregated from several documents ...)
We already have several features like this in Nuxeo Platform :
- generate PDF / Excel view via JSF / Seam / iText
= but template is not easy to update for users
= page layout must remain simple
- generate BIRT reports
= creating a BIRT report design can be complicated
= the goal of BIRT is more data aggregation and BI than rendering
h2. Constraints
h3. Easy templating
The main constraints has to be the template model.
In a lot of cases, users need to be able to modify the template, but :
- contributing XML / Layouts is either :
- not flexible enough
- not powerful enough
- writting complete JSF / Freemarker template seen complicated
Truth is that most people want to use Office tools (like MSO or OpenOffice) to
do that.
h3. Standard based
As much as possible we need to rely on standard like {{OpenDocument}} and
{{DocX}}.
It's easier to use XML based generation and it avoids relying on a running
OpenOffice server.
h2. Approach
We have already done some successful tests with {{DocX}} and {{JODReport}}.
The approach of {{JODReport}}, using Freemarker to generate OpenDocument seems
like the right one.
h2. High level User Story
# Template file creation
#* create an office document via OpenOffice or MSOffice
#* From within the editor program I mark some fields or section to be
merge/replaced
(basically I tag the Document)
# Create the Template document in Nuxeo
#* Inside Nuxeo I create a new Template Document and upload my template file
#* Nuxeo extract the structure from the template file and gives me a listing of
the fields
#** I can define types and binding for each fields ( direct value, or XPath to
document properties)
#** I can add fields if needed
# Create a Template Based document in Nuxeo
#* For selected Document types when I create them I can select the associated
template
#* If some parameters are still unset at template level the user will be
prompted to enter them
--
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] Created: (NXP-8202) Initial prototype
Initial prototype
--
Key: NXP-8202
URL: https://jira.nuxeo.com/browse/NXP-8202
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Create an initial prototype based on the existing work :
- {{nuxeo-platform-docx-templates}}
http://hg.nuxeo.org/sandbox/nuxeo-platform-docx-templates/
- tests done via {{Automation}} and {{JODReport}}
--
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] Resolved: (NXP-8202) Initial prototype
[
https://jira.nuxeo.com/browse/NXP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat resolved NXP-8202.
--
Resolution: Fixed
Prototype available on GitHub :
https://github.com/tiry/nuxeo-platform-rendering-templates
Initial prototype
--
Key: NXP-8202
URL: https://jira.nuxeo.com/browse/NXP-8202
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 3 weeks
Remaining Estimate: 3 weeks
Create an initial prototype based on the existing work :
- {{nuxeo-platform-docx-templates}}
http://hg.nuxeo.org/sandbox/nuxeo-platform-docx-templates/
- tests done via {{Automation}} and {{JODReport}}
--
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] Updated: (NXP-8202) Initial prototype
[
https://jira.nuxeo.com/browse/NXP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8202:
-
Status: Open (was: Triage)
Initial prototype
--
Key: NXP-8202
URL: https://jira.nuxeo.com/browse/NXP-8202
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 3 weeks
Remaining Estimate: 3 weeks
Create an initial prototype based on the existing work :
- {{nuxeo-platform-docx-templates}}
http://hg.nuxeo.org/sandbox/nuxeo-platform-docx-templates/
- tests done via {{Automation}} and {{JODReport}}
--
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] Created: (NXP-8203) Migrate from Custom DocX+{{JODReport}} to {{XDocReport}}
Migrate from Custom DocX+{{JODReport}} to {{XDocReport}}
Key: NXP-8203
URL: https://jira.nuxeo.com/browse/NXP-8203
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
--
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] Updated: (NXP-8203) Migrate from Custom DocX+JODReport to XDocReport
[
https://jira.nuxeo.com/browse/NXP-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8203:
-
Description:
{{JODReports}} suffers from several limitations
- does only support ODT
- no built-in support for embeddding images
- no formatting features
- no doc
Our current implementation of DocX feature is very custom and very poor.
{{XDocreport}} (http://code.google.com/p/xdocreport/) represents a good
alternative :
- supports OpenDocument and MSOffice XML format
- support XL and PPT too
- experimental support for formating
- code is clean, modular and allows for extensions (we will need that)
- documentation
- support for simple conversions via XSLT
For us this project provides the abstraction API around OpenDocument and DocX
Formats + a set of pluggable tools.
= this looks like a very good fit for a provider for our Document templating
system
Summary: Migrate from Custom DocX+JODReport to XDocReport (was:
Migrate from Custom DocX+{{JODReport}} to {{XDocReport}})
Migrate from Custom DocX+JODReport to XDocReport
Key: NXP-8203
URL: https://jira.nuxeo.com/browse/NXP-8203
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Original Estimate: 2 days
Remaining Estimate: 2 days
{{JODReports}} suffers from several limitations
- does only support ODT
- no built-in support for embeddding images
- no formatting features
- no doc
Our current implementation of DocX feature is very custom and very poor.
{{XDocreport}} (http://code.google.com/p/xdocreport/) represents a good
alternative :
- supports OpenDocument and MSOffice XML format
- support XL and PPT too
- experimental support for formating
- code is clean, modular and allows for extensions (we will need that)
- documentation
- support for simple conversions via XSLT
For us this project provides the abstraction API around OpenDocument and DocX
Formats + a set of pluggable tools.
= this looks like a very good fit for a provider for our Document templating
system
--
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] Created: (NXP-8204) Add support for Document Composition
Add support for Document Composition Key: NXP-8204 URL: https://jira.nuxeo.com/browse/NXP-8204 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8205) Bind Audit inside rendering context
Bind Audit inside rendering context --- Key: NXP-8205 URL: https://jira.nuxeo.com/browse/NXP-8205 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8206) Plug output converters
Plug output converters -- Key: NXP-8206 URL: https://jira.nuxeo.com/browse/NXP-8206 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8207) Plug preview system
Plug preview system --- Key: NXP-8207 URL: https://jira.nuxeo.com/browse/NXP-8207 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8208) Make a set of nice template examples
Make a set of nice template examples Key: NXP-8208 URL: https://jira.nuxeo.com/browse/NXP-8208 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8209) Misc UI work
Misc UI work - Key: NXP-8209 URL: https://jira.nuxeo.com/browse/NXP-8209 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8211) Marketplace package
Marketplace package --- Key: NXP-8211 URL: https://jira.nuxeo.com/browse/NXP-8211 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8212) Documentation
Documentation - Key: NXP-8212 URL: https://jira.nuxeo.com/browse/NXP-8212 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Created: (NXP-8210) Polish / Cleanup API
Polish / Cleanup API Key: NXP-8210 URL: https://jira.nuxeo.com/browse/NXP-8210 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat -- 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] Updated: (NXP-8203) Migrate from Custom DocX+JODReport to XDocReport
[
https://jira.nuxeo.com/browse/NXP-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8203:
-
Description:
{{JODReports}} suffers from several limitations
- does only support ODT
- no built-in support for embeddding images
- no formatting features
- no doc
Our current implementation of DocX feature is very custom and very poor.
{{XDocreport}} (http://code.google.com/p/xdocreport/) represents a good
alternative :
- supports OpenDocument and MSOffice XML format
- support XL and PPT too
- experimental support for formating
- code is clean, modular and allows for extensions (we will need that)
- documentation
- support for simple conversions via XSLT
For us this project provides the abstraction API around OpenDocument and DocX
Formats + a set of pluggable tools.
= this looks like a very good fit for a provider for our Document templating
system
was:
{{JODReports}} suffers from several limitations
- does only support ODT
- no built-in support for embeddding images
- no formatting features
- no doc
Our current implementation of DocX feature is very custom and very poor.
{{XDocreport}} (http://code.google.com/p/xdocreport/) represents a good
alternative :
- supports OpenDocument and MSOffice XML format
- support XL and PPT too
- experimental support for formating
- code is clean, modular and allows for extensions (we will need that)
- documentation
- support for simple conversions via XSLT
For us this project provides the abstraction API around OpenDocument and DocX
Formats + a set of pluggable tools.
= this looks like a very good fit for a provider for our Document templating
system
Fix Version/s: 5.6
Migrate from Custom DocX+JODReport to XDocReport
Key: NXP-8203
URL: https://jira.nuxeo.com/browse/NXP-8203
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 2 days
Remaining Estimate: 2 days
{{JODReports}} suffers from several limitations
- does only support ODT
- no built-in support for embeddding images
- no formatting features
- no doc
Our current implementation of DocX feature is very custom and very poor.
{{XDocreport}} (http://code.google.com/p/xdocreport/) represents a good
alternative :
- supports OpenDocument and MSOffice XML format
- support XL and PPT too
- experimental support for formating
- code is clean, modular and allows for extensions (we will need that)
- documentation
- support for simple conversions via XSLT
For us this project provides the abstraction API around OpenDocument and DocX
Formats + a set of pluggable tools.
= this looks like a very good fit for a provider for our Document templating
system
--
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] Updated: (NXP-8203) Migrate from Custom DocX+JODReport to XDocReport
[
https://jira.nuxeo.com/browse/NXP-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8203:
-
Status: Open (was: Triage)
Migrate from Custom DocX+JODReport to XDocReport
Key: NXP-8203
URL: https://jira.nuxeo.com/browse/NXP-8203
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 2 days
Remaining Estimate: 2 days
{{JODReports}} suffers from several limitations
- does only support ODT
- no built-in support for embeddding images
- no formatting features
- no doc
Our current implementation of DocX feature is very custom and very poor.
{{XDocreport}} (http://code.google.com/p/xdocreport/) represents a good
alternative :
- supports OpenDocument and MSOffice XML format
- support XL and PPT too
- experimental support for formating
- code is clean, modular and allows for extensions (we will need that)
- documentation
- support for simple conversions via XSLT
For us this project provides the abstraction API around OpenDocument and DocX
Formats + a set of pluggable tools.
= this looks like a very good fit for a provider for our Document templating
system
--
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] Updated: (NXP-8204) Add support for Document Composition
[ https://jira.nuxeo.com/browse/NXP-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thierry Delprat updated NXP-8204: - Description: Having a simple merge of fields is interesting, but for some use cases we need to go further. Typically, if the Document I want to render is a Note I would like to keep the formating of the Note contents inside the rendered Document. In such a case we have : * the template that manages ** cover page with logo ** history of the document ** index * the Nuxeo Note Document that provides ** Fields data (Title, author, creation date, history info ...) ** Blobs (pictures) ** the formatted text content Fix Version/s: 5.6 Add support for Document Composition Key: NXP-8204 URL: https://jira.nuxeo.com/browse/NXP-8204 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat Fix For: 5.6 Original Estimate: 3 days Remaining Estimate: 3 days Having a simple merge of fields is interesting, but for some use cases we need to go further. Typically, if the Document I want to render is a Note I would like to keep the formating of the Note contents inside the rendered Document. In such a case we have : * the template that manages ** cover page with logo ** history of the document ** index * the Nuxeo Note Document that provides ** Fields data (Title, author, creation date, history info ...) ** Blobs (pictures) ** the formatted text content -- 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: (LIVED-215) No action clik on live edit icon.
[ https://jira.nuxeo.com/browse/LIVED-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108381#comment-108381 ] etienne vallier commented on LIVED-215: --- Thank, your are right. in IE9 (32bit) in compatibility mode live edit (2.3.0) work. So, is it a protocol Handler issue ? nota :chrome work fine with HTML drag and drop, have you a planning to integrate live edit plugin ? No action clik on live edit icon. - Key: LIVED-215 URL: https://jira.nuxeo.com/browse/LIVED-215 Project: Nuxeo Live Desktop Issue Type: Bug Components: NLE MSO, Protocol Handler plugin Affects Versions: NLE 2.3.0, Protocol Handler 0.5.0 Environment: nuxeo in ubuntu server 10.04 ; navigate unde windows 7 with Firefox 4+ Reporter: etienne vallier Assignee: Arnaud Kervern Priority: Major in nuxeo interface live edit icon doesn't work. no action when click on. I have this issue since upgrade in protocol handler 0.5 I upgrade last live edit I test in all firefox since 4 to 9 the same issue. I can't test live edit alone, i use IE9 and it's not compatible plugin's thanks for look at this. -- 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] Updated: (NXP-8204) Add support for Document Composition
[
https://jira.nuxeo.com/browse/NXP-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8204:
-
Description:
Having a simple merge of fields is interesting, but for some use cases we need
to go further.
Typically, if the Document I want to render is a Note I would like to keep the
formating of the Note contents inside the rendered Document.
In such a case we have :
* the template that manages
** cover page with logo
** history of the document
** index
* the Nuxeo Note Document that provides
** Fields data (Title, author, creation date, history info ...)
** Blobs (pictures)
** the formatted text content
{{XDocReport}} provides some experimental support for text styling that allow
to integrate HTML and Wiki markup inside ODT and DocX files.
We will probably need to extend this, but since the system is pluggable this
should not be a real issue and anyway it's far more simple that really merging
2 documents with their style (tested this in the prototype :( )
was:
Having a simple merge of fields is interesting, but for some use cases we need
to go further.
Typically, if the Document I want to render is a Note I would like to keep the
formating of the Note contents inside the rendered Document.
In such a case we have :
* the template that manages
** cover page with logo
** history of the document
** index
* the Nuxeo Note Document that provides
** Fields data (Title, author, creation date, history info ...)
** Blobs (pictures)
** the formatted text content
Add support for Document Composition
Key: NXP-8204
URL: https://jira.nuxeo.com/browse/NXP-8204
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 3 days
Remaining Estimate: 3 days
Having a simple merge of fields is interesting, but for some use cases we
need to go further.
Typically, if the Document I want to render is a Note I would like to keep
the formating of the Note contents inside the rendered Document.
In such a case we have :
* the template that manages
** cover page with logo
** history of the document
** index
* the Nuxeo Note Document that provides
** Fields data (Title, author, creation date, history info ...)
** Blobs (pictures)
** the formatted text content
{{XDocReport}} provides some experimental support for text styling that allow
to integrate HTML and Wiki markup inside ODT and DocX files.
We will probably need to extend this, but since the system is pluggable this
should not be a real issue and anyway it's far more simple that really
merging 2 documents with their style (tested this in the prototype :( )
--
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] Updated: (NXP-8205) Bind Audit inside rendering context
[ https://jira.nuxeo.com/browse/NXP-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thierry Delprat updated NXP-8205: - Description: Audit entries should be part of the rendering context. = this will allow to automatically fill the history section of the template Fix Version/s: 5.6 Bind Audit inside rendering context --- Key: NXP-8205 URL: https://jira.nuxeo.com/browse/NXP-8205 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat Fix For: 5.6 Original Estimate: 4 hours Remaining Estimate: 4 hours Audit entries should be part of the rendering context. = this will allow to automatically fill the history section of the template -- 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] Updated: (NXP-8206) Plug output converters
[
https://jira.nuxeo.com/browse/NXP-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8206:
-
Description:
We will mainly use ODT and DocX based templates.
But in somes cases, the output of the rendering should be converted :
- to PDF
- to Word OLE format
So the idea would be to associate a template with a converter.
We can of course use existing Converters, but for PDF we can test the XSLT/FOP
based converters included in {{XDocReport}} (would avoid to go through
openoffice server).
Fix Version/s: 5.6
Plug output converters
--
Key: NXP-8206
URL: https://jira.nuxeo.com/browse/NXP-8206
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 1 day
Remaining Estimate: 1 day
We will mainly use ODT and DocX based templates.
But in somes cases, the output of the rendering should be converted :
- to PDF
- to Word OLE format
So the idea would be to associate a template with a converter.
We can of course use existing Converters, but for PDF we can test the
XSLT/FOP based converters included in {{XDocReport}} (would avoid to go
through openoffice server).
--
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] Updated: (NXP-8202) Initial prototype
[
https://jira.nuxeo.com/browse/NXP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8202:
-
Remaining Estimate: 2 days (was: 3 weeks)
Original Estimate: 2 days (was: 3 weeks)
Initial prototype
--
Key: NXP-8202
URL: https://jira.nuxeo.com/browse/NXP-8202
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 2 days
Remaining Estimate: 2 days
Create an initial prototype based on the existing work :
- {{nuxeo-platform-docx-templates}}
http://hg.nuxeo.org/sandbox/nuxeo-platform-docx-templates/
- tests done via {{Automation}} and {{JODReport}}
--
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] Updated: (NXP-8208) Make a set of nice template examples
[ https://jira.nuxeo.com/browse/NXP-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thierry Delprat updated NXP-8208: - Description: We must provide 1 or 2 nice looking examples for both ODT and DocX. Fix Version/s: 5.6 Make a set of nice template examples Key: NXP-8208 URL: https://jira.nuxeo.com/browse/NXP-8208 Project: Nuxeo Enterprise Platform Issue Type: Sub-task Reporter: Thierry Delprat Assignee: Thierry Delprat Fix For: 5.6 Original Estimate: 1 day Remaining Estimate: 1 day We must provide 1 or 2 nice looking examples for both ODT and DocX. -- 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] Updated: (NXP-8207) Plug preview system
[
https://jira.nuxeo.com/browse/NXP-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8207:
-
Description:
For the Template based Documents we probably want the preview to take into
account the rendering.
This should be easy to do.
For the Template themself, this would be great to also have a preview of the
file.
Ideally the preview should show the merge fields.
We could do that by doing a custom rendering of the template, but this would
require the template to be fail safe!
May be we should look at how {{XDocReport}} generate it's layout preview on
http://xdocreport.opensagres.cloudbees.net/processReport.
Fix Version/s: 5.6
Plug preview system
---
Key: NXP-8207
URL: https://jira.nuxeo.com/browse/NXP-8207
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 2 days
Remaining Estimate: 2 days
For the Template based Documents we probably want the preview to take into
account the rendering.
This should be easy to do.
For the Template themself, this would be great to also have a preview of the
file.
Ideally the preview should show the merge fields.
We could do that by doing a custom rendering of the template, but this would
require the template to be fail safe!
May be we should look at how {{XDocReport}} generate it's layout preview on
http://xdocreport.opensagres.cloudbees.net/processReport.
--
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] Updated: (NXP-8209) Misc UI work
[
https://jira.nuxeo.com/browse/NXP-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8209:
-
Description:
The existing prototype show that some UI work is needed :
- how to manage manual update of the rendition ?
- how to dynamically add the {{TemplateBased}} facet to a document ?
Fix Version/s: 5.6
Misc UI work
-
Key: NXP-8209
URL: https://jira.nuxeo.com/browse/NXP-8209
Project: Nuxeo Enterprise Platform
Issue Type: Sub-task
Reporter: Thierry Delprat
Assignee: Thierry Delprat
Fix For: 5.6
Original Estimate: 2 days
Remaining Estimate: 2 days
The existing prototype show that some UI work is needed :
- how to manage manual update of the rendition ?
- how to dynamically add the {{TemplateBased}} facet to a document ?
--
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] Updated: (NXP-8201) Add support for document rendition via Office Templating
[
https://jira.nuxeo.com/browse/NXP-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8201:
-
Description:
h2. Use cases
There are several cases where it makes sens to generate a rendition of a Nuxeo
Document.
Typically :
- you store product related information in Nuxeo
= you want to generate a Product description file in .doc or .pdf
(with most important meta-data + version and history info + picture)
- you manage mails in Nuxeo
= you want to generate the response letter
(with logo, custom header ...)
- you store Specifications / Code audit / Benchmark results in Nuxeo
= you want to generate the delivrable report
(with Cover page, Index, and data aggregated from several documents ...)
We already have several features like this in Nuxeo Platform :
- generate PDF / Excel view via JSF / Seam / iText
= but template is not easy to update for users
= page layout must remain simple
- generate BIRT reports
= creating a BIRT report design can be complicated
= the goal of BIRT is more data aggregation and BI than rendering
h2. Constraints
h3. Easy templating
The main constraints has to be the template model.
In a lot of cases, users need to be able to modify the template, but :
- contributing XML / Layouts is either :
- not flexible enough
- not powerful enough
- writting complete JSF / Freemarker template seen complicated
Truth is that most people want to use Office tools (like MSO or OpenOffice) to
do that.
h3. Standard based
As much as possible we need to rely on standard like {{OpenDocument}} and
{{DocX}}.
It's easier to use XML based generation and it avoids relying on a running
OpenOffice server.
h2. Approach
We have already done some successful tests with {{DocX}} and {{JODReport}}.
The approach of {{JODReport}}, using Freemarker to generate OpenDocument seems
like the right one.
On the Nuxeo level we have :
- a TemplateDocument : this documents holds the template file as well as some
default parameters
- a TemplateBasedDocument : this is a standard Nuxeo Document that is
associated with a Template and can then support rendition
In the prototype the logic is bound to {{Facets}} so that you can create a
rendition from potentially any kind of Document (this may require to store the
resulting rendering in a field associated to the facet wich is not the case for
now).
h2. High level User Story
# Template file creation
#* create an office document via OpenOffice or MSOffice
#* From within the editor program I mark some fields or section to be
merge/replaced
(basically I tag the Document)
# Create the Template document in Nuxeo
#* Inside Nuxeo I create a new Template Document and upload my template file
#* Nuxeo extract the structure from the template file and gives me a listing of
the fields
#** I can define types and binding for each fields ( direct value, or XPath to
document properties)
#** I can add fields if needed
# Create a Template Based document in Nuxeo
#* For selected Document types when I create them I can select the associated
template
#* If some parameters are still unset at template level the user will be
prompted to enter them
was:
h2. Use cases
There are several cases where it makes sens to generate a rendition of a Nuxeo
Document.
Typically :
- you store product related information in Nuxeo
= you want to generate a Product description file in .doc or .pdf
(with most important meta-data + version and history info + picture)
- you manage mails in Nuxeo
= you want to generate the response letter
(with logo, custom header ...)
- you store Specifications / Code audit / Benchmark results in Nuxeo
= you want to generate the delivrable report
(with Cover page, Index, and data aggregated from several documents ...)
We already have several features like this in Nuxeo Platform :
- generate PDF / Excel view via JSF / Seam / iText
= but template is not easy to update for users
= page layout must remain simple
- generate BIRT reports
= creating a BIRT report design can be complicated
= the goal of BIRT is more data aggregation and BI than rendering
h2. Constraints
h3. Easy templating
The main constraints has to be the template model.
In a lot of cases, users need to be able to modify the template, but :
- contributing XML / Layouts is either :
- not flexible enough
- not powerful enough
- writting complete JSF / Freemarker template seen complicated
Truth is that most people want to use Office tools (like MSO or OpenOffice) to
do that.
h3. Standard based
As much as possible we need to rely on standard like {{OpenDocument}} and
{{DocX}}.
It's easier to use XML based generation and it avoids relying on a running
OpenOffice server.
h2. Approach
We have already done some successful tests with {{DocX}} and {{JODReport}}.
The approach of
[JIRA] Created: (NXP-8213) optimize publication status retrieve on documents
optimize publication status retrieve on documents
-
Key: NXP-8213
URL: https://jira.nuxeo.com/browse/NXP-8213
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Fix For: 5.6
In
{{org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory#isPublished}}
we're scanning for tasks but in the other hand, in
{{org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory.isPublishedDocWaitingForPublication}}
we're checking for the {{ACL}} existence.
We should use the same logic in both methods. It seem that the {{ACL}} check is
better optimized.
A special thank for {{Marc Berhaut}} from {{AC rennes}} for reporting this
problem.
--
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] Assigned: (NXP-8213) optimize publication status retrieve on documents
[
https://jira.nuxeo.com/browse/NXP-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphane Lacoin reassigned NXP-8213:
Assignee: Stéphane Lacoin
optimize publication status retrieve on documents
-
Key: NXP-8213
URL: https://jira.nuxeo.com/browse/NXP-8213
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Components: Publishing
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Stéphane Lacoin
Fix For: 5.6
In
{{org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory#isPublished}}
we're scanning for tasks but in the other hand, in
{{org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory.isPublishedDocWaitingForPublication}}
we're checking for the {{ACL}} existence.
We should use the same logic in both methods. It seem that the {{ACL}} check
is better optimized.
A special thank for {{Marc Berhaut}} from {{AC rennes}} for reporting this
problem.
--
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] Updated: (NXP-8213) optimize publication status retrieve on documents
[
https://jira.nuxeo.com/browse/NXP-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphane Lacoin updated NXP-8213:
-
Component/s: Publishing
optimize publication status retrieve on documents
-
Key: NXP-8213
URL: https://jira.nuxeo.com/browse/NXP-8213
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Components: Publishing
Affects Versions: 5.4.2
Reporter: Stéphane Lacoin
Assignee: Stéphane Lacoin
Fix For: 5.6
In
{{org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory#isPublished}}
we're scanning for tasks but in the other hand, in
{{org.nuxeo.ecm.platform.publisher.task.CoreProxyWithWorkflowFactory.isPublishedDocWaitingForPublication}}
we're checking for the {{ACL}} existence.
We should use the same logic in both methods. It seem that the {{ACL}} check
is better optimized.
A special thank for {{Marc Berhaut}} from {{AC rennes}} for reporting this
problem.
--
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: (LIVED-215) No action clik on live edit icon.
[ https://jira.nuxeo.com/browse/LIVED-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108390#comment-108390 ] Arnaud Kervern commented on LIVED-215: -- It looks to be, but could you check that you still have a temporary folder setted? (in the extension conf) For chrome, you should check this page: http://doc.nuxeo.com/x/X4Ek No action clik on live edit icon. - Key: LIVED-215 URL: https://jira.nuxeo.com/browse/LIVED-215 Project: Nuxeo Live Desktop Issue Type: Bug Components: NLE MSO, Protocol Handler plugin Affects Versions: NLE 2.3.0, Protocol Handler 0.5.0 Environment: nuxeo in ubuntu server 10.04 ; navigate unde windows 7 with Firefox 4+ Reporter: etienne vallier Assignee: Arnaud Kervern Priority: Major in nuxeo interface live edit icon doesn't work. no action when click on. I have this issue since upgrade in protocol handler 0.5 I upgrade last live edit I test in all firefox since 4 to 9 the same issue. I can't test live edit alone, i use IE9 and it's not compatible plugin's thanks for look at this. -- 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: (LIVED-215) No action clik on live edit icon.
[ https://jira.nuxeo.com/browse/LIVED-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108392#comment-108392 ] etienne vallier commented on LIVED-215: --- OK I have a working directory setted ; but it isn't create ! you can close this, report the bug is between the screen and the chair :@ I'm sorry, thanks for your help. No action clik on live edit icon. - Key: LIVED-215 URL: https://jira.nuxeo.com/browse/LIVED-215 Project: Nuxeo Live Desktop Issue Type: Bug Components: NLE MSO, Protocol Handler plugin Affects Versions: NLE 2.3.0, Protocol Handler 0.5.0 Environment: nuxeo in ubuntu server 10.04 ; navigate unde windows 7 with Firefox 4+ Reporter: etienne vallier Assignee: Arnaud Kervern Priority: Major in nuxeo interface live edit icon doesn't work. no action when click on. I have this issue since upgrade in protocol handler 0.5 I upgrade last live edit I test in all firefox since 4 to 9 the same issue. I can't test live edit alone, i use IE9 and it's not compatible plugin's thanks for look at this. -- 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] Work logged: (NXP-8167) Marketplace package for Polls
[
https://jira.nuxeo.com/browse/NXP-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Thomas Roger logged work on NXP-8167:
-
Author: Thomas Roger
Created on: 21/12/11 14:54
Start Date: 21/12/11 14:54
Worklog Time Spent: 3 hours
Issue Time Tracking
---
Worklog Id: (was: 27632)
Time Spent: 1 day, 3 hours (was: 1 day)
Marketplace package for Polls
---
Key: NXP-8167
URL: https://jira.nuxeo.com/browse/NXP-8167
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Packaging
Reporter: Delphine Renevey
Assignee: Thomas Roger
Fix For: 5.5.x
Time Spent: 1 day, 3 hours
Remaining Estimate: 0 minutes
--
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: (NXP-8168) Marketplace package for BIRT
[ https://jira.nuxeo.com/browse/NXP-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108393#comment-108393 ] Thomas Roger commented on NXP-8168: --- http://hg.nuxeo.org/marketplace/birt-reporting/rev/3be902658b70 http://hg.nuxeo.org/marketplace/birt-reporting/rev/ef8ef2347041 Marketplace package for BIRT - Key: NXP-8168 URL: https://jira.nuxeo.com/browse/NXP-8168 Project: Nuxeo Enterprise Platform Issue Type: Task Components: Packaging Reporter: Delphine Renevey Fix For: 5.5.x Time Spent: 4 hours Remaining Estimate: 0 minutes -- 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] Work logged: (NXP-8168) Marketplace package for BIRT
[
https://jira.nuxeo.com/browse/NXP-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]
Thomas Roger logged work on NXP-8168:
-
Author: Thomas Roger
Created on: 21/12/11 14:54
Start Date: 21/12/11 14:54
Worklog Time Spent: 2 hours
Issue Time Tracking
---
Worklog Id: (was: 27633)
Time Spent: 4 hours (was: 2 hours)
Marketplace package for BIRT
-
Key: NXP-8168
URL: https://jira.nuxeo.com/browse/NXP-8168
Project: Nuxeo Enterprise Platform
Issue Type: Task
Components: Packaging
Reporter: Delphine Renevey
Fix For: 5.5.x
Time Spent: 4 hours
Remaining Estimate: 0 minutes
--
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] Updated: (NXP-6681) File system level mapping
[ https://jira.nuxeo.com/browse/NXP-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-6681: --- Description: Mapping a Nuxeo repository to a filesystem is not an easy job because the models do not match correctly: - name vs title+filename+name - file+folder vs folderish doc + multiple attachements Most existing filesystem mapping protocol implementations in Nuxeo have tried to solve this issue: WebDav, WSS and CMIS. There is no ideal solution and we will have to add some constraints on top of the Nuxeo model. Rather that continuing with several mapping logic, it's time to build a generic module that will handle all the work: - Nuxeo Document - Filesystem resource - File System resource - Nuxeo Document (including what is done via FileManager) - Listeners to enforce the limitations of the FS model This new module should be integrated in WebDav, WSS and CMIS. was: We know for quite a long time than mapping Nuxeo repository to a file system is not an easy job because the model do not match correctly : - name vs title + filename + name - file+folder vs folderish doc + multiple attachements Most existing file-system mapping protocol implementations in Nuxeo have tried to solve this issue : WebDav, WSS and CMIS. There is no ideal solution and we will have to add some constraints on the Nuxeo model. Rather that continuing with several mapping logic, it's time to build a generic module that will handle all the work : - Nuxeo Document = File System resource - File System resource = Nuxeo Document (including what is done via FileManager) - Listeners to enforce the limitations of the FS model This new module should be integrated in WebDav, WSS and CMIS. WebDav and CMIS should be based on the newly contributed version from Gagnavarslan that allows FileSystem level mounting via WSS. File system level mapping - Key: NXP-6681 URL: https://jira.nuxeo.com/browse/NXP-6681 Project: Nuxeo Enterprise Platform Issue Type: Improvement Components: Desktop Integration, WSS integration Reporter: Thierry Delprat Assignee: Florent Guillaume Fix For: 6.0 Mapping a Nuxeo repository to a filesystem is not an easy job because the models do not match correctly: - name vs title+filename+name - file+folder vs folderish doc + multiple attachements Most existing filesystem mapping protocol implementations in Nuxeo have tried to solve this issue: WebDav, WSS and CMIS. There is no ideal solution and we will have to add some constraints on top of the Nuxeo model. Rather that continuing with several mapping logic, it's time to build a generic module that will handle all the work: - Nuxeo Document - Filesystem resource - File System resource - Nuxeo Document (including what is done via FileManager) - Listeners to enforce the limitations of the FS model This new module should be integrated in WebDav, WSS and CMIS. -- 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] Updated: (NXP-6681) Filesystem mapping
[ https://jira.nuxeo.com/browse/NXP-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florent Guillaume updated NXP-6681: --- Priority: Major (was: Minor) Summary: Filesystem mapping (was: File system level mapping) Filesystem mapping -- Key: NXP-6681 URL: https://jira.nuxeo.com/browse/NXP-6681 Project: Nuxeo Enterprise Platform Issue Type: Improvement Components: Desktop Integration, WSS integration Reporter: Thierry Delprat Assignee: Florent Guillaume Priority: Major Fix For: 6.0 Mapping a Nuxeo repository to a filesystem is not an easy job because the models do not match correctly: - name vs title+filename+name - file+folder vs folderish doc + multiple attachements Most existing filesystem mapping protocol implementations in Nuxeo have tried to solve this issue: WebDav, WSS and CMIS. There is no ideal solution and we will have to add some constraints on top of the Nuxeo model. Rather that continuing with several mapping logic, it's time to build a generic module that will handle all the work: - Nuxeo Document - Filesystem resource - File System resource - Nuxeo Document (including what is done via FileManager) - Listeners to enforce the limitations of the FS model This new module should be integrated in WebDav, WSS and CMIS. -- 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] Resolved: (LIVED-215) No action clik on live edit icon.
[ https://jira.nuxeo.com/browse/LIVED-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Kervern resolved LIVED-215. -- Resolution: Not A Bug No action clik on live edit icon. - Key: LIVED-215 URL: https://jira.nuxeo.com/browse/LIVED-215 Project: Nuxeo Live Desktop Issue Type: Bug Components: NLE MSO, Protocol Handler plugin Affects Versions: NLE 2.3.0, Protocol Handler 0.5.0 Environment: nuxeo in ubuntu server 10.04 ; navigate unde windows 7 with Firefox 4+ Reporter: etienne vallier Assignee: Arnaud Kervern Priority: Major in nuxeo interface live edit icon doesn't work. no action when click on. I have this issue since upgrade in protocol handler 0.5 I upgrade last live edit I test in all firefox since 4 to 9 the same issue. I can't test live edit alone, i use IE9 and it's not compatible plugin's thanks for look at this. -- 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] Created: (NXP-8215) clone.py must ignore optional addons by default
clone.py must ignore optional addons by default --- Key: NXP-8215 URL: https://jira.nuxeo.com/browse/NXP-8215 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Installers / Admin tools Reporter: Julien Carsique Assignee: Julien Carsique Fix For: 5.5.x, 5.6 Some addons, called optionals, are not released by default, thus they are not deprecated and currently are automatically cloned by clone.py clone.py must not clone them by default. -- 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] Created: (NXP-8214) Add optional state to require attribute in OSGI component - Add enable/disable state to components
Add optional state to require attribute in OSGI component - Add enable/disable state to components Key: NXP-8214 URL: https://jira.nuxeo.com/browse/NXP-8214 Project: Nuxeo Enterprise Platform Issue Type: Improvement Components: Core Affects Versions: 5.5 Reporter: Vladimir Pasquier Assignee: Bogdan Stefanescu Fix For: 5.5.x Use case: An addon component (faceted search) is overridden in CMF distribution. But its possible to run CMF without faceted search addon. So, we need an optional registration of components that overridden optional addon components (require included) -- 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] Created: (NXCM-510) Faceted search contrib is not registered due to new 5.5 packaging
Faceted search contrib is not registered due to new 5.5 packaging - Key: NXCM-510 URL: https://jira.nuxeo.com/browse/NXCM-510 Project: Nuxeo Case Management Issue Type: Bug Affects Versions: 5.5 Reporter: Vladimir Pasquier Assignee: Vladimir Pasquier The addon faceted search contrib is not registered since we packaged cmf (5.5) as an addon. We need to remove this contribution waiting for NXP-8214 and then re-add it. -- 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] Resolved: (NXP-8215) clone.py must ignore optional addons by default
[ https://jira.nuxeo.com/browse/NXP-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Carsique resolved NXP-8215. -- Resolution: Fixed clone.py must ignore optional addons by default --- Key: NXP-8215 URL: https://jira.nuxeo.com/browse/NXP-8215 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Installers / Admin tools Reporter: Julien Carsique Assignee: Julien Carsique Fix For: 5.5.x, 5.6 Some addons, called optionals, are not released by default, thus they are not deprecated and currently are automatically cloned by clone.py clone.py must not clone them by default. -- 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] Updated: (NXP-8215) clone.py must ignore optional addons by default
[ https://jira.nuxeo.com/browse/NXP-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Carsique updated NXP-8215: - Status: Open (was: Triage) clone.py must ignore optional addons by default --- Key: NXP-8215 URL: https://jira.nuxeo.com/browse/NXP-8215 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Installers / Admin tools Reporter: Julien Carsique Assignee: Julien Carsique Fix For: 5.5.x, 5.6 Some addons, called optionals, are not released by default, thus they are not deprecated and currently are automatically cloned by clone.py clone.py must not clone them by default. -- 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] Resolved: (NXP-8190) Migration to GitHub
[ https://jira.nuxeo.com/browse/NXP-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Carsique resolved NXP-8190. -- Resolution: Fixed Migration to GitHub --- Key: NXP-8190 URL: https://jira.nuxeo.com/browse/NXP-8190 Project: Nuxeo Enterprise Platform Issue Type: Task Reporter: Julien Carsique Assignee: Julien Carsique Fix For: 5.6 Everything moved to https://github.com/nuxeo but old main repositories (nuxeo-platform and nuxeo-gwt) and old/not-up-to-date addons (nuxeo-activity nuxeo-features-page-layout nuxeo-gsa-connector nuxeo-platform-annotations nuxeo-platform-archive nuxeo-platform-archive-importer nuxeo-platform-documentLink nuxeo-platform-dynsearch nuxeo-platform-exalead-connector nuxeo-platform-filemanager-io-plugin nuxeo-platform-flex nuxeo-platform-gwt nuxeo-platform-high-availability nuxeo-platform-imaging nuxeo-platform-imaging-tiling nuxeo-platform-indexing-gateway nuxeo-platform-intuition nuxeo-platform-mail nuxeo-platform-mail-dispatcher nuxeo-platform-metadata-injector nuxeo-platform-metadataext nuxeo-platform-orderedfolder-web nuxeo-platform-preview nuxeo-platform-restpack nuxeo-platform-seam-pdf nuxeo-platform-signature nuxeo-platform-spellchecker nuxeo-platform-transform-plugins nuxeo-platform-userdata nuxeo-platform-userdata-core-contrib nuxeo-platform-userworkspace nuxeo-platform-virtualnavigation nuxeo-platform-webdav-server nuxeo-platform-webwidgets-providers nuxeo-platform-xmlrpc-connector nuxeo-platform-zip2text-extractor nuxeo-portlets nuxeo-samples nuxeo-shell-scripts). TODO: - update clone.py - add a release script - document - cleanup - add DEPRECATED.txt files on Mercurial deprecated branches - add README.md files to all git repositories -- 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] Updated: (NXP-8176) PostgreSQL nx_vacuum_read_acls takes too long on large database
[
https://jira.nuxeo.com/browse/NXP-8176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thierry Delprat updated NXP-8176:
-
Status: Open (was: Triage)
PostgreSQL nx_vacuum_read_acls takes too long on large database
---
Key: NXP-8176
URL: https://jira.nuxeo.com/browse/NXP-8176
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Components: Core SQL Storage
Affects Versions: 5.5
Environment: PostgreSQL 8.3 may be 8.4
Reporter: Benoit Delbosc
The nx_vacuum_read_acls function is called at startup to remove unused acl
read on the aclr table.
The left join on huge table generate a poor query plan at least on PostgreSQL
8.3.
{code}
DELETE FROM aclr WHERE acl_id IN (SELECT r.acl_id FROM aclr AS r
LEFT JOIN hierarchy_read_acl AS h ON r.acl_id=h.acl_id
WHERE h.acl_id IS NULL);
---
Nested Loop IN Join (cost=0.00..3509.08 rows=166 width=6)
Join Filter: ((r.acl_id)::text = (aclr.acl_id)::text)
- Seq Scan on aclr (cost=0.00..5.66 rows=166 width=39)
- Merge Left Join (cost=0.00..106473.28 rows=928778 width=33)
Merge Cond: ((r.acl_id)::text = (h.acl_id)::text)
Filter: (h.acl_id IS NULL)
- Index Scan using aclr_acl_id_idx on aclr r (cost=0.00..18.74
rows=166 width=33)
- Index Scan using hierarchy_read_acl_acl_id_idx on
hierarchy_read_acl h (cost=0.00..83234.66 rows=1857557 width=33)
{code}
This should be rewriten to something like this:
{code}
EXPLAIN ANALYZE SELECT acl_id FROM aclr WHERE NOT EXISTS (SELECT 1 FROM
hierarchy_read_acl h WHERE h.acl_id = aclr.acl_id LIMIT 1);
---
Seq Scan on aclr (cost=0.00..23.84 rows=83 width=33) (actual
time=3.535..3.535 rows=0 loops=1)
Filter: (NOT (subplan))
SubPlan
- Limit (cost=0.00..0.11 rows=1 width=0) (actual time=0.020..0.020
rows=1 loops=167)
- Index Scan using hierarchy_read_acl_acl_id_idx on
hierarchy_read_acl h (cost=0.00..2787.52 rows=25446 width=0) (actual
time=0.019..0.019 rows=1 loops=167)
Index Cond: ((acl_id)::text = ($0)::text)
Total runtime: 3.561 ms
{code}
--
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] Created: (NXP-8216) Social workspace members don't have the Go to News item action
Social workspace members don't have the Go to News item action -- Key: NXP-8216 URL: https://jira.nuxeo.com/browse/NXP-8216 Project: Nuxeo Enterprise Platform Issue Type: Bug Components: Social Collaboration Affects Versions: 5.5 Reporter: Solen Guitter Fix For: 5.5.x In the Actions menu, the members of a social workspace don't have Go to News item to see all the news directly. -- 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] Issue Comment Edited: (NXP-7983) don't synchronize core session once the repository is initialized
[ https://jira.nuxeo.com/browse/NXP-7983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=106804#comment-106804 ] Florent Guillaume edited comment on NXP-7983 at 12/21/11 4:29 PM: -- Moved repository initialization handling from core session to repository manager. Pushed changed into NXP-7983-remove-session-sync for review. Is repository manager refs still needed ? The reference count is deprecated and unused. http://hg.nuxeo.org/nuxeo/nuxeo-core/rev/ab0bf0f270b7 http://hg.nuxeo.org/nuxeo/nuxeo-core/rev/512985caad57 was (Author: slacoin): Moved repository initialization handling from core session to repository manager. Pushed changed into NXP-7983-remove-session-sync for review. Is repository manager refs still needed ? The reference count is deprecated and unused. http://hg.nuxeo.org/nuxeo/nuxeo-core/rev/ab0bf0f270b7 don't synchronize core session once the repository is initialized - Key: NXP-7983 URL: https://jira.nuxeo.com/browse/NXP-7983 Project: Nuxeo Enterprise Platform Issue Type: Improvement Affects Versions: 5.5.x Reporter: Stéphane Lacoin Assignee: Stéphane Lacoin Priority: Major Fix For: 5.5.x In the core session, we're synchronizing the opening of the repository for initializing the repository. By registering the processing state in the repository service, we can avoid that synchronization section. -- 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] Created: (NXS-882) Improve the document type generated layout
Improve the document type generated layout -- Key: NXS-882 URL: https://jira.nuxeo.com/browse/NXS-882 Project: Nuxeo Studio Issue Type: Task Components: User Experience Affects Versions: 2.4.3 Reporter: Lise Kemen Assignee: Lise Kemen Fix For: 2.4.4 One of the first thing you can do with Studio is to create a custom document type, with your fields of data. But the layout generation is really messy. See screenshots. - Products side: provide a classes system to have a flexible layout - Studio side: make studio generate the right classes depending of user's layout choice -- 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] Updated: (NXS-882) Improve the document type generated layout
[ https://jira.nuxeo.com/browse/NXS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lise Kemen updated NXS-882: --- Attachment: Screen Shot 2011-12-21 at 17.03.21.png Screen Shot 2011-12-21 at 17.03.33.png Improve the document type generated layout -- Key: NXS-882 URL: https://jira.nuxeo.com/browse/NXS-882 Project: Nuxeo Studio Issue Type: Task Components: User Experience Affects Versions: 2.4.3 Reporter: Lise Kemen Assignee: Lise Kemen Fix For: 2.4.4 Attachments: Screen Shot 2011-12-21 at 17.03.21.png, Screen Shot 2011-12-21 at 17.03.33.png One of the first thing you can do with Studio is to create a custom document type, with your fields of data. But the layout generation is really messy. See screenshots. - Products side: provide a classes system to have a flexible layout - Studio side: make studio generate the right classes depending of user's layout choice -- 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-882) Improve the document type generated layout
[ https://jira.nuxeo.com/browse/NXS-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108414#comment-108414 ] Lise Kemen commented on NXS-882: The orange tips have to be improved to. We need to find another way to add tips for Studio users. Improve the document type generated layout -- Key: NXS-882 URL: https://jira.nuxeo.com/browse/NXS-882 Project: Nuxeo Studio Issue Type: Task Components: User Experience Affects Versions: 2.4.3 Reporter: Lise Kemen Assignee: Lise Kemen Fix For: 2.4.4 Attachments: Screen Shot 2011-12-21 at 17.03.21.png, Screen Shot 2011-12-21 at 17.03.33.png One of the first thing you can do with Studio is to create a custom document type, with your fields of data. But the layout generation is really messy. See screenshots. - Products side: provide a classes system to have a flexible layout - Studio side: make studio generate the right classes depending of user's layout choice -- 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] Created: (NXP-8217) Marketplace package for Email suggestion
Marketplace package for Email suggestion Key: NXP-8217 URL: https://jira.nuxeo.com/browse/NXP-8217 Project: Nuxeo Enterprise Platform Issue Type: Task Components: Packaging Reporter: Thomas Roger Assignee: Thomas Roger Fix For: 5.5.x -- 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] Updated: (CMIS-69) Implement getCheckedOutDocs
[
https://jira.nuxeo.com/browse/CMIS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume updated CMIS-69:
--
Fix Version/s: nuxeo-5.5
Implement getCheckedOutDocs
---
Key: CMIS-69
URL: https://jira.nuxeo.com/browse/CMIS-69
Project: Nuxeo Chemistry
Issue Type: Sub-task
Reporter: Florent Guillaume
Assignee: Florent Guillaume
Fix For: nuxeo-5.5
Implement {{session.getCheckedOutDocs}}.
--
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] Resolved: (NXS-881) error when going on the results tab of an existing content view
[ https://jira.nuxeo.com/browse/NXS-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anahide Tchertchian resolved NXS-881. - Resolution: Fixed https://hgpriv.nuxeo.org/nuxeo-studio/rev/8e054b66e63c another NPE appears, NXS-633 has been reopened for it error when going on the results tab of an existing content view --- Key: NXS-881 URL: https://jira.nuxeo.com/browse/NXS-881 Project: Nuxeo Studio Issue Type: Bug Affects Versions: 2.5 Reporter: Alain Escaffre Priority: Blocker Fix For: 2.5 Attachments: Capture d’écran 2011-12-21 à 08.10.30.png On test platform, if I click on the Result tab of a content view already defined I have an error (see screenshot in attachment and link in comment) : ncaught exception: com.google.gwt.event.shared.UmbrellaException: One or more exceptions caught, see full set in UmbrellaException#getCauses at Unknown.re(Unknown Source) at Unknown.lj(Unknown Source) at Unknown.rz(Unknown Source) at Unknown.uz(Unknown Source) at Unknown.Qy(Unknown Source) at Unknown.Ktb(Unknown Source) at Unknown.Ttb(Unknown Source) Caused by: com.google.gwt.event.shared.UmbrellaException: One or more exceptions caught, see full set in UmbrellaException#getCauses at Unknown.re(Unknown Source) at Unknown.lj(Unknown Source) at Unknown.rz(Unknown Source) at Unknown.uz(Unknown Source) at Unknown.Qy(Unknown Source) at Unknown.Ktb(Unknown Source) at Unknown.Ttb(Unknown Source) Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError): Cannot read property 'bb' of null at Unknown.Tvb(Unknown Source) at Unknown.$Tc(Unknown Source) at Unknown.dUc(Unknown Source) at Unknown.fUc(Unknown Source) at Unknown.TIc(Unknown Source) at Unknown.kJc(Unknown Source) at Unknown.Vx(Unknown Source) at Unknown.bz(Unknown Source) at Unknown.Qy(Unknown Source) at Unknown.Ktb(Unknown Source) -- 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] Updated: (NXS-881) error when going on the results tab of an existing content view
[ https://jira.nuxeo.com/browse/NXS-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anahide Tchertchian updated NXS-881: Status: Open (was: Triage) error when going on the results tab of an existing content view --- Key: NXS-881 URL: https://jira.nuxeo.com/browse/NXS-881 Project: Nuxeo Studio Issue Type: Bug Affects Versions: 2.5 Reporter: Alain Escaffre Priority: Blocker Fix For: 2.5 Attachments: Capture d’écran 2011-12-21 à 08.10.30.png On test platform, if I click on the Result tab of a content view already defined I have an error (see screenshot in attachment and link in comment) : ncaught exception: com.google.gwt.event.shared.UmbrellaException: One or more exceptions caught, see full set in UmbrellaException#getCauses at Unknown.re(Unknown Source) at Unknown.lj(Unknown Source) at Unknown.rz(Unknown Source) at Unknown.uz(Unknown Source) at Unknown.Qy(Unknown Source) at Unknown.Ktb(Unknown Source) at Unknown.Ttb(Unknown Source) Caused by: com.google.gwt.event.shared.UmbrellaException: One or more exceptions caught, see full set in UmbrellaException#getCauses at Unknown.re(Unknown Source) at Unknown.lj(Unknown Source) at Unknown.rz(Unknown Source) at Unknown.uz(Unknown Source) at Unknown.Qy(Unknown Source) at Unknown.Ktb(Unknown Source) at Unknown.Ttb(Unknown Source) Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError): Cannot read property 'bb' of null at Unknown.Tvb(Unknown Source) at Unknown.$Tc(Unknown Source) at Unknown.dUc(Unknown Source) at Unknown.fUc(Unknown Source) at Unknown.TIc(Unknown Source) at Unknown.kJc(Unknown Source) at Unknown.Vx(Unknown Source) at Unknown.bz(Unknown Source) at Unknown.Qy(Unknown Source) at Unknown.Ktb(Unknown Source) -- 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-633) Add layout registries
[ https://jira.nuxeo.com/browse/NXS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=108423#comment-108423 ] Anahide Tchertchian commented on NXS-633: - fix layout reference on documents for target 5.5 + remove result layout configuration before 5.4.0 since they can only be referenced by content views (available since 5.4.0 too) + add tests: https://hgpriv.nuxeo.org/nuxeo-studio/rev/201af16a388d https://hgpriv.nuxeo.org/nuxeo-studio/rev/50a485306b75 Add layout registries - Key: NXS-633 URL: https://jira.nuxeo.com/browse/NXS-633 Project: Nuxeo Studio Issue Type: New Feature Components: Layouts Affects Versions: 2.1 Reporter: Alain Escaffre Assignee: Anahide Tchertchian Priority: Major Fix For: 2.5, Short term backlog Attachments: Capture d’écran 2011-12-20 à 01.39.49.png Once a new entry is added into the new layout registry where user can reference layout they have contributed by other means (like an eclipse based project), it is possible to use this layout in a new document tab (new coming feature, see related ticket). Furthermore, it is possible to declare new layouts in a new Layout feature. When a user add an entry to the new result layout registry, in Studio, it is possible to reference it from the content view editor, on the result tab: the user doesn't have to configure the same result set when only the query changes. Furthermore, there is a new Result layout feature, that enables to declare new result layouts that will be available from the content view editor (new feature + registry). -- 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] Updated: (NXP-5707) Validate setup in admin center and wizard
[ https://jira.nuxeo.com/browse/NXP-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Carsique updated NXP-5707: - Description: Add a database global validation (driver, connection, ...) Add simple values validation on other fields (see http://blogs.nuxeo.com/dev/2009/03/cross-validation-with-jsf.html) was: Add simple values validation on fields Add a database global validation (see http://blogs.nuxeo.com/dev/2009/03/cross-validation-with-jsf.html) Summary: Validate setup in admin center and wizard (was: Validate setup wizard in admin center) Validate setup in admin center and wizard - Key: NXP-5707 URL: https://jira.nuxeo.com/browse/NXP-5707 Project: Nuxeo Enterprise Platform Issue Type: Improvement Components: Admin Center Reporter: Julien Carsique Assignee: Julien Carsique Fix For: 5.5.x Add a database global validation (driver, connection, ...) Add simple values validation on other fields (see http://blogs.nuxeo.com/dev/2009/03/cross-validation-with-jsf.html) -- 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
