Re: Discussion: Flat Grey Visual Theme
IIRW, it's the only really RTL capable. So a big YES to keep it, of course. I have no ideas though :/ Jacques From: Adrian Crum adrian.c...@yahoo.com The Flat Grey visual theme is getting old. The current version of the theme is based on the original look and feel of OFBiz when I first joined the community - back in 2004. Around the Spring of 2007 I added some gradient gifs to make the original style a little more interesting. After that, the visual theme was converted to a floating flexible layout (to fit any size screen), it was made sight-impaired accessible (font size can be changed), and it added support for bi-directional layout (for rtl languages). Those design decisions were made by the OFBiz community and, in my opinion, continue to make the Flat Grey theme the fallback theme when all else fails. It just works. Despite its advantages, it looks dated. I would like to update it to make it more modern, but maintain its advantages over the other themes. I'm thinking it only needs css and gif file updates. The current templates and javascripts would be maintained. If anyone is interested, they are welcome to help out. I would also appreciate any suggestions or comments. Let me know what you think. -Adrian
[jira] Created: (OFBIZ-4080) Implement a Column Widget
Implement a Column Widget - Key: OFBIZ-4080 URL: https://issues.apache.org/jira/browse/OFBIZ-4080 Project: OFBiz Issue Type: Wish Components: framework Reporter: Bruno Busco Priority: Minor Some time ago there was a discussion on the dev mailing list about how to implement something to display contents in columns on screens. I cut and past an Adrian's idea that is something we should consider to implement. -- From the screen widget XML perspective, it could look like this: column-container column name=first-column !-- column contents -- /column column name=second-column !-- column contents -- /column ... /column-container The column elements can contain additional column-container elements. The column element can have an attribute to specify its width as a percentage of the column-container width. Pixel widths should be avoided since the screen widgets are supposed to be rendering device agnostic. The column-container and column elements will support the common screen widget attributes like name, style, id, etc. The column-container could support a type attribute that controls how the contained columns behave. For example, type=splitter will render the contained columns as a splitter window. From the widget model perspective, the column-container manages resizing columns when one of them is collapsed or its width changes. Column size information needs to be kept in the rendering context. The information would start off with some default values that are overridden by user preferences. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4081) Form widget improvements
Form widget improvements Key: OFBIZ-4081 URL: https://issues.apache.org/jira/browse/OFBIZ-4081 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Bruno Busco Priority: Minor I have a list of ideas about improvements that could be done on the frame widget. I think that creating jiras for these could be a good starting point to discuss, and eventually design and implement them. This issue is an umbrella task for them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4076) When audit log is enabled it creates log transacations even when there's no change
[ https://issues.apache.org/jira/browse/OFBIZ-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen van der Wal updated OFBIZ-4076: -- Attachment: OFBIZ-4076-v2.patch Here's a patch based on revision 1053569 of Ofbiz trunk. After applying this patch the overhead of the AuditEntityLog is recuded from 32% to 25%. There's even more room for performance increase: a findOne serach for the previous entity is done for every field that's enabled. When audit log is enabled it creates log transacations even when there's no change -- Key: OFBIZ-4076 URL: https://issues.apache.org/jira/browse/OFBIZ-4076 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Reporter: Jeroen van der Wal Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-4076-v2.patch, OFBIZ-4076.patch The createEntittyAuditLogSingle function creates a record in the AuditLog entity even when there's no change. This patch only logs new, changed and deleted values. Also, all changes in the same transaction will get the same change date. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4082) Adding a Print this form icon to the top frame bar
Adding a Print this form icon to the top frame bar Key: OFBIZ-4082 URL: https://issues.apache.org/jira/browse/OFBIZ-4082 Project: OFBiz Issue Type: Improvement Reporter: Bruno Busco There should be a new frame tag attribute that would specify that a Print this form icon should be displayed in the top frame bar. This icon should allow the user to print the actual frame in a consistent way (all frame will have the same icon). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4083) Adding a Go to next record and a Go to previous record icons in the frame top bar
Adding a Go to next record and a Go to previous record icons in the frame top bar - Key: OFBIZ-4083 URL: https://issues.apache.org/jira/browse/OFBIZ-4083 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Bruno Busco Priority: Minor These icons should allow to navigate through all the records of a list. These should only be available for single type forms. The list to navigate should be for example the list of records that has been selected by a previous find operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4084) Adding a Return to search icon in the single frame top bar
Adding a Return to search icon in the single frame top bar Key: OFBIZ-4084 URL: https://issues.apache.org/jira/browse/OFBIZ-4084 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Bruno Busco Priority: Minor If the single frame being displyied comes from a previous search this button icon should allow to go back to the previous search query. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4085) Adding a View attachments button icon to the single form's top bar
Adding a View attachments button icon to the single form's top bar Key: OFBIZ-4085 URL: https://issues.apache.org/jira/browse/OFBIZ-4085 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Bruno Busco Priority: Minor There should be a standard way to allow the display of a list of attachments to a single record. The Attachments icon button with the relative attachments list screen should be a standard feature that should be easily implemented on any single frame record. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4080) Implement a Column Widget
[ https://issues.apache.org/jira/browse/OFBIZ-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-4080: --- Issue Type: Sub-task (was: Wish) Parent: OFBIZ-4081 Implement a Column Widget - Key: OFBIZ-4080 URL: https://issues.apache.org/jira/browse/OFBIZ-4080 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Bruno Busco Priority: Minor Some time ago there was a discussion on the dev mailing list about how to implement something to display contents in columns on screens. I cut and past an Adrian's idea that is something we should consider to implement. -- From the screen widget XML perspective, it could look like this: column-container column name=first-column !-- column contents -- /column column name=second-column !-- column contents -- /column ... /column-container The column elements can contain additional column-container elements. The column element can have an attribute to specify its width as a percentage of the column-container width. Pixel widths should be avoided since the screen widgets are supposed to be rendering device agnostic. The column-container and column elements will support the common screen widget attributes like name, style, id, etc. The column-container could support a type attribute that controls how the contained columns behave. For example, type=splitter will render the contained columns as a splitter window. From the widget model perspective, the column-container manages resizing columns when one of them is collapsed or its width changes. Column size information needs to be kept in the rendering context. The information would start off with some default values that are overridden by user preferences. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4083) Adding a Go to next record and a Go to previous record icons in the frame top bar
[ https://issues.apache.org/jira/browse/OFBIZ-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-4083: --- Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-4081 Adding a Go to next record and a Go to previous record icons in the frame top bar - Key: OFBIZ-4083 URL: https://issues.apache.org/jira/browse/OFBIZ-4083 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Bruno Busco Priority: Minor These icons should allow to navigate through all the records of a list. These should only be available for single type forms. The list to navigate should be for example the list of records that has been selected by a previous find operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4084) Adding a Return to search icon in the single frame top bar
[ https://issues.apache.org/jira/browse/OFBIZ-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-4084: --- Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-4081 Adding a Return to search icon in the single frame top bar Key: OFBIZ-4084 URL: https://issues.apache.org/jira/browse/OFBIZ-4084 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Bruno Busco Priority: Minor If the single frame being displyied comes from a previous search this button icon should allow to go back to the previous search query. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4085) Adding a View attachments button icon to the single form's top bar
[ https://issues.apache.org/jira/browse/OFBIZ-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-4085: --- Issue Type: Sub-task (was: Improvement) Parent: OFBIZ-4081 Adding a View attachments button icon to the single form's top bar Key: OFBIZ-4085 URL: https://issues.apache.org/jira/browse/OFBIZ-4085 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Bruno Busco Priority: Minor There should be a standard way to allow the display of a list of attachments to a single record. The Attachments icon button with the relative attachments list screen should be a standard feature that should be easily implemented on any single frame record. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4021) Adding columns filtering fields in form widget
[ https://issues.apache.org/jira/browse/OFBIZ-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-4021: --- Issue Type: Sub-task (was: New Feature) Parent: OFBIZ-4081 Adding columns filtering fields in form widget -- Key: OFBIZ-4021 URL: https://issues.apache.org/jira/browse/OFBIZ-4021 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Bruno Busco Priority: Minor Attachments: column_filter_disabled.JPG, column_filter_enabled.JPG, content_list.JPG, FilterForm.patch, FilterForm.patch, img_for_tomahawk.zip This patch includes an initial implementation of a list-form column filtering feature. The aim is to add the possibility to configure a list form to show, in its header, some fields that could be used to filter the rows displayed in the form. This is a feature quite standard in many systems and could be seen into OFBiz as a quick search; the standard way of searching using a complete single-type form could be seen as an advanced search. Please find attached to this JIRA two screenshots that show you how the filtering option appears on the screen. *How the user uses this feature* The part of the screen that is normally used for the pagination controls (only the upper one) has been extended so that two icons are shown on the left. The first one (a funnel) is used to show or hide the filtering fields. The second one (a magnifing glass) is used to run the search with the filter content. *How the developer uses this feature* The filtering feature can be enabled on any list-type form specifying the filter-form-name attribute. This must be the name of a form that contains the details about how the filtering fields should be rendered. When a list form with the filter-form-name option set is rendered, any column field is searched for in the filter-form. If a field with the same name is found, its field rendering options are used to render the filter field. A new field attribute filter-field has also been added. This defaults to true but if it is set to false the filter field is not rendered for this column, even if a field with the same name is present in the filter-form. This feature allows to use as filter-form an already existent form such as a regular FindXXX form. In the patch the ListExample form has been changed to use this feature. You can check it there. Unfortunately the patch does not work yet 100% but I hope that if someone finds it interesting could help me. *What is there still to do* 1) There is a FIXME in MacroFormRenderer.java file. I cannot make it work. If I enable the code that is commented there I get an error when a search is run. 2) I cannot make the filtering fields show the actual content after a search is run. They are always rendered as empty. 3) The filter row hide/show status should be saved so that it is maintained after a pagination. I submit this patch as it is becouse I cannot easily improve it further but I hope someone could help. The img_for_tamahawk.zip file includes imgs that should be added in the tomahawk images folder to make the patch work. Thank you for any help! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4086) Adding a download CSV file button icon for list forms
Adding a download CSV file button icon for list forms - Key: OFBIZ-4086 URL: https://issues.apache.org/jira/browse/OFBIZ-4086 Project: OFBiz Issue Type: Sub-task Reporter: Bruno Busco -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4086) Adding a download CSV file button icon for list forms
[ https://issues.apache.org/jira/browse/OFBIZ-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12975775#action_12975775 ] Bruno Busco commented on OFBIZ-4086: From the DEV ML Hi Jacopo, thank you for your proposal. In my mind there was only something like your #1. This would allow to embed an export link in the form (I would like to include a standard download icon in the list form pagination bar) whose target is automatically derived from the form's target. This link could be rendered if the cvs-export=true is added to the frame attributes. #2 will for sure add more generality and would allow the export to any screen even not just a form. This would be great. #3 Yes, but I would prefer to have specific icons i the top bars (i.e. the form pagination or the screenlet title bar) The export link should perform a request with the same search parameters as the last one. Thank you very much for discussing on this. -Bruno 2010/12/4 Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com Hi Bruno, this is not exactly the same topic but I would like to share some of my ideas for enhancements for the macro screen widget. Currently, in order to get an html and a csv version of a screen we have to create the two screen definitions (with different decorators) and setup entries in the controller like: view-map name=InventoryItemTotals type=screen page=component://product/widget/facility/FacilityScreens.xml#InventoryItemTotals/ view-map name=InventoryItemTotalsExport type=screencsv page=component://product/widget/facility/FacilityScreens.xml#InventoryItemTotalsExport content-type=text/csv encoding=none/ The following improvements will make the rendering in different formats more dynamic: 1) in the controller, the two view-maps could be grouped into one where the content-type is dynamically retrieved from the request (then the view handler will use screen or screencsv etc based on the content type) 2) enhance the global decorator to render properly on different formats; if the decorator contains screens/forms widgets then the widget should render themselves in the proper format; if the decorator contains ftl templates, we will have to provide alternative ones like: platform-specific htmlhtml-template location=component://common/webcommon/includes/simple.ftl//html xsl-fohtml-template location=component://common/webcommon/includes/simple.fo.ftl//xsl-fo xmlhtml-template location=component://common/webcommon/includes/minimal-decorator.ftl//xml /platform-specific 3) in the search form we could add a drop down for the selection of the content-type At this point we may be able to export in different formats virtually any screen in OFBiz simply by adding a drop down box for the output format at the top of the screen (in a decorator): export to PDF, export to xml. Jacopo On Dec 4, 2010, at 12:22 AM, Bruno Busco wrote: Hi, I was thinking that having a CSV export feature embedded in the list form widget could be nice. I mean a feature that, simply adding something like a csv-export=true attribute in the form widget, would show a link or an icon in the top form pagination bar that would export the actual data listed in the form. Does this make sense? Any idea on how to implement this? Many thanks to everybody wants to share ideas on this. -Bruno Adding a download CSV file button icon for list forms - Key: OFBIZ-4086 URL: https://issues.apache.org/jira/browse/OFBIZ-4086 Project: OFBiz Issue Type: Sub-task Reporter: Bruno Busco -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4011) Implement saved searches and other persisted requests
[ https://issues.apache.org/jira/browse/OFBIZ-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Busco updated OFBIZ-4011: --- Issue Type: Sub-task (was: New Feature) Parent: OFBIZ-4081 Implement saved searches and other persisted requests - Key: OFBIZ-4011 URL: https://issues.apache.org/jira/browse/OFBIZ-4011 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Scott Gray Priority: Minor Attachments: saved-search.patch https://cwiki.apache.org/confluence/display/OFBIZ/Saved+Searches -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4080) Implement a Column Widget
[ https://issues.apache.org/jira/browse/OFBIZ-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12975777#action_12975777 ] Bruno Busco commented on OFBIZ-4080: This is not strictly related to the frame widget but to the screen one. In any case it could be useful to have it in the frame widget also to replace the actual position attribute for fields. Implement a Column Widget - Key: OFBIZ-4080 URL: https://issues.apache.org/jira/browse/OFBIZ-4080 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Bruno Busco Priority: Minor Some time ago there was a discussion on the dev mailing list about how to implement something to display contents in columns on screens. I cut and past an Adrian's idea that is something we should consider to implement. -- From the screen widget XML perspective, it could look like this: column-container column name=first-column !-- column contents -- /column column name=second-column !-- column contents -- /column ... /column-container The column elements can contain additional column-container elements. The column element can have an attribute to specify its width as a percentage of the column-container width. Pixel widths should be avoided since the screen widgets are supposed to be rendering device agnostic. The column-container and column elements will support the common screen widget attributes like name, style, id, etc. The column-container could support a type attribute that controls how the contained columns behave. For example, type=splitter will render the contained columns as a splitter window. From the widget model perspective, the column-container manages resizing columns when one of them is collapsed or its width changes. Column size information needs to be kept in the rendering context. The information would start off with some default values that are overridden by user preferences. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4080) Implement a Column Widget
[
https://issues.apache.org/jira/browse/OFBIZ-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12975784#action_12975784
]
Adrian Crum commented on OFBIZ-4080:
Some additional thoughts on this:
1. The column-container element should accept only column sub-elements. If
other widget elements were allowed, then it would be difficult to determine
where they would appear in a multi-column layout.
2. An improved XML example:
{code}
column-container
column name=this-column
!-- column contents --
/column
column name=that-column
!-- column contents --
/column
...
/column-container
{code}
...because the first-column and second-column names imply position, and it
is important to keep in mind that column placement could be under the user's
control.
3. I like the idea of including the new elements in form widgets.
Implement a Column Widget
-
Key: OFBIZ-4080
URL: https://issues.apache.org/jira/browse/OFBIZ-4080
Project: OFBiz
Issue Type: Sub-task
Components: framework
Reporter: Bruno Busco
Priority: Minor
Some time ago there was a discussion on the dev mailing list about how to
implement something to display contents in columns on screens.
I cut and past an Adrian's idea that is something we should consider to
implement.
--
From the screen widget XML perspective, it could look like this:
column-container
column name=first-column
!-- column contents --
/column
column name=second-column
!-- column contents --
/column
...
/column-container
The column elements can contain additional column-container elements.
The column element can have an attribute to specify its width as a percentage
of the column-container width. Pixel widths should be avoided since the
screen widgets are supposed to be rendering device agnostic.
The column-container and column elements will support the common screen
widget attributes like name, style, id, etc.
The column-container could support a type attribute that controls how the
contained columns behave. For example, type=splitter will render the
contained columns as a splitter window.
From the widget model perspective, the column-container manages resizing
columns when one of them is collapsed or its width changes. Column size
information needs to be kept in the rendering context. The information would
start off with some default values that are overridden by user preferences.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r1053198 - /ofbiz/trunk/framework/images/webapp/images/getDependentDropdownValues.js
Added in https://cwiki.apache.org/confluence/display/OFBADMIN/Coding+Conventions (updated and amended) Jacques From: Jacques Le Roux jacques.le.r...@les7arts.com Hi, Following this, I'd like to suggest to use, if possible, Eclipse/Aptana for editing Javascript files and notably to format them correctly. I suggest also to not use tabs in *our* javascript files but 4 spaces (like in Java) I have put the Aptana formatting template as an attachment of OFBiz Contributors Best Practices Thanks to share your opinion Jacques From: jler...@apache.org URL: http://svn.apache.org/viewvc?rev=1053198view=rev Log: Use the power of Aptana to format correctly this file. I have adapted the default format setting to be more near our best practices. If you are interested I can share the formatting template. Anyway I think I will discuss that on dev ML latter. We could have it posted in the wiki, when agreed upon its content, and use it as part of our best practices...
[jira] Updated: (OFBIZ-4079) Adding content in CMS using add long text (right mouse click) doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-4079: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-3814 Adding content in CMS using add long text (right mouse click) doesn't work -- Key: OFBIZ-4079 URL: https://issues.apache.org/jira/browse/OFBIZ-4079 Project: OFBiz Issue Type: Sub-task Components: content Affects Versions: SVN trunk Reporter: Willem Janssen Attachments: 2010-12-28_2329.png When using the add long text function in the menu that shows when using the right mouse click the existing content is shown, not an empty form. Now it's not possible to add content in the CMS because only existing content is shown in the forms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4079) Adding content in CMS using add long text (right mouse click) doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12975905#action_12975905 ] Jacques Le Roux commented on OFBIZ-4079: Always easier with an URL https://localhost:8443/content/control/WebSiteCms?webSiteId=CmsSite Adding content in CMS using add long text (right mouse click) doesn't work -- Key: OFBIZ-4079 URL: https://issues.apache.org/jira/browse/OFBIZ-4079 Project: OFBiz Issue Type: Sub-task Components: content Affects Versions: SVN trunk Reporter: Willem Janssen Attachments: 2010-12-28_2329.png When using the add long text function in the menu that shows when using the right mouse click the existing content is shown, not an empty form. Now it's not possible to add content in the CMS because only existing content is shown in the forms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4079) Adding content in CMS using add long text (right mouse click) doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12975923#action_12975923 ] Jacques Le Roux commented on OFBIZ-4079: It's not the only issue: The top menus (links) * Quick Sub-Content * Path Alias * Meta Tags don't work either. It seems related to js callDocument() function and its Ajax request (see editorUrl var, aliasUrl and metaUrl are not implemented at all) var editorUrl = '/content/control/views/WebSiteCMSContent'; var aliasUrl = '/content/control/views/WebSiteCMSPathAlias'; var metaUrl = '/content/control/views/WebSiteCMSMetaInfo'; I have no time to look at it now... Adding content in CMS using add long text (right mouse click) doesn't work -- Key: OFBIZ-4079 URL: https://issues.apache.org/jira/browse/OFBIZ-4079 Project: OFBiz Issue Type: Sub-task Components: content Affects Versions: SVN trunk Reporter: Willem Janssen Attachments: 2010-12-28_2329.png When using the add long text function in the menu that shows when using the right mouse click the existing content is shown, not an empty form. Now it's not possible to add content in the CMS because only existing content is shown in the forms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-4079) Adding content in CMS using add long text (right mouse click) doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4079: -- Assignee: Jacques Le Roux Adding content in CMS using add long text (right mouse click) doesn't work -- Key: OFBIZ-4079 URL: https://issues.apache.org/jira/browse/OFBIZ-4079 Project: OFBiz Issue Type: Sub-task Components: content Affects Versions: SVN trunk Reporter: Willem Janssen Assignee: Jacques Le Roux Attachments: 2010-12-28_2329.png When using the add long text function in the menu that shows when using the right mouse click the existing content is shown, not an empty form. Now it's not possible to add content in the CMS because only existing content is shown in the forms. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
