December 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13439) Photoalbum - update help section

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13439?page=com.atlassian.jira.plugin.s... ] Michal Petrov updated RF-13439: ------------------------------- Fix Version/s: 4.3.5 > Photoalbum - update help section > -------------------------------- > > Key: RF-13439 > URL: https://issues.jboss.org/browse/RF-13439 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.5 > > > * The help stylesheets link to docbook resources that were removed from RF. > * The help popups need updating > ** The code and the pictures may not display the current state of the app > ** New popups for the social integration should probably be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13257) PhotoAlbum bugs

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13257?page=com.atlassian.jira.plugin.s... ] Michal Petrov resolved RF-13257. -------------------------------- Resolution: Done > PhotoAlbum bugs > --------------- > > Key: RF-13257 > URL: https://issues.jboss.org/browse/RF-13257 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Jiří Štefek > Assignee: Michal Petrov > Fix For: 4.3.5 > > > PhotoAlbum 4.3.x known bugs: > * uploading file to album (image isn't saved to DB) > * deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13317: ------------------------------------ [~lfryc] have you yet pushed your changes to github? Can you link to the branch here? I see this branch: > https://github.com/richfaces/richfaces/tree/RF-13317-jsf22-view-state-update However the last commit there is for the PoC workaround with the com.sun class. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Lukáš Fryč > Priority: Critical > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/no...] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13438) Update jboss-parent

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13438?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13438: ------------------------------- Sprint: 5.0.0.Alpha3 - Sprint 1 > Update jboss-parent > ------------------- > > Key: RF-13438 > URL: https://issues.jboss.org/browse/RF-13438 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13438) Update jboss-parent

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13438?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13438. -------------------------------- Resolution: Done > Update jboss-parent > ------------------- > > Key: RF-13438 > URL: https://issues.jboss.org/browse/RF-13438 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13438) Update jboss-parent

by Brian Leathem (JIRA)

Brian Leathem created RF-13438: ---------------------------------- Summary: Update jboss-parent Key: RF-13438 URL: https://issues.jboss.org/browse/RF-13438 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: build/distribution Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 5.0.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-9557) TabPanel: scrolling of tabs and popup list for choosing implementation

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-9557?page=com.atlassian.jira.plugin.sy... ] Brian Leathem resolved RF-9557. ------------------------------- Fix Version/s: (was: 5-Future) Resolution: Incomplete Description > TabPanel: scrolling of tabs and popup list for choosing implementation > ---------------------------------------------------------------------- > > Key: RF-9557 > URL: https://issues.jboss.org/browse/RF-9557 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Reporter: Ilya Shaikovsky > > not implemented in M4. feature moved to next iterations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13433) extendeddatatable: Column resizing and column reordering not working for RTL languages

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13433?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13433: ------------------------------- Fix Version/s: 5-Tracking > extendeddatatable: Column resizing and column reordering not working for RTL languages > -------------------------------------------------------------------------------------- > > Key: RF-13433 > URL: https://issues.jboss.org/browse/RF-13433 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.4 > Environment: ALL > Reporter: Holger Walter > Labels: richfaces > Fix For: 5-Tracking > > > For the extendeddatatable column resizing and column reordering are not working correctly for RTL (right-to-left) languages. > a) Column resizing > In case you try to increase the width of one column, RF does in fact decrease the width of the left side neighbor column. In case of decreasing the width, RF increases the width of the neighbor. > b) Column reordering > When dragging a column to a new position an arrow is shown at the place where it is intended to be inserted. However, after releasing the mouse, the columns is inserted at another place. > In case you cannot fix these issues soon, please provide at least the > possibility to disable columns reordering. > Column resizing can be disabled by CSS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13226) Restoring table sorting on extendedDataTable does not work when a dataScroller is present

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13226?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13226: ------------------------------- Summary: Restoring table sorting on extendedDataTable does not work when a dataScroller is present (was: Restoring table sorting on extendedDataTable does not work) > Restoring table sorting on extendedDataTable does not work when a dataScroller is present > ----------------------------------------------------------------------------------------- > > Key: RF-13226 > URL: https://issues.jboss.org/browse/RF-13226 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Labels: extendedDataTable > Fix For: 5-Tracking > > > If you persist the table state of a rich:extendedDataTable the sorting order is not restored when you reload the page if the extendedDataTable has a rich:dataScroller. > However when you use the dataScroller to go to the 2nd page and then back to the 1st page the sorting is correct again. > > This causes a second problem (which I haven't managed to isolate yet) that actions in the table (e.g. calling an action method and passing in the column var) does not work. Please note this does work in the example code below, but not in our real live table. If I go to the 2nd page all links in that table work. > See https://community.jboss.org/thread/232647 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13230: ------------------------------- Fix Version/s: 5-Tracking (was: 4.3.5) > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Matej Novotny > Fix For: 5-Tracking > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2013