[LRA-230] Please test the Collaborative dynamic list app Created: 03/Mar/16  Updated: 03/Jun/16

Status: Open
Project: Liferay Apps
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: mcalvo Assignee: mcalvo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Initial and latest version of Liferay 6.2 CE and EE.

Attachments: Text File errors.txt    

 Description   
Please test this app. Documentation of this app is here:
http://wiki.rivetlogic.com/display/LRA/Collaborative+dynamic+list

 Comments   
Comment by Luis Hernandez [X] (Inactive) [ 03/Mar/16 ]
1- [Bug] Some errors are displayed on the tomcat log when the “Spreadsheet View” is configured for a new list

PRIORITY:
====================
Critical

REPRODUCIBILITY LEVEL:
====================
Always

STEPS:
====================
1.Go to any empty page
2.Select and add the next application “Collaborative dynamic list”
3.Click on the “New List” option at the botton of the portlet
4.Create a new List with the following values:
-Name: TesList
-Data Definition: (Select any data definition, if you want, create a new definition with some fields)

5.Click on “Save”
6. Click on the “configuration” icon button of the “Collaborative dynamic list” display portlet, and select the option “Configuration”
7. Check the next options:
-Editable
-Spreadsheet View
8. Click on “Save”
9. Review the log of the tomcat server

CURRENT RESULT:
====================
Some errors are displayed on the tomcat log when the “Spreadsheet View” is configured for a new list. The errors in the log are repeated (seems like a loop).

Watch the next video:
http://screencast.com/t/wrhSpBWlwj9

And, see the attachment file with the log errors of tomcat (errors.txt)

Note: When user refresh the page, the errors in the log stops to appears in the log, and the portlet is displayed fine.

EXPECTED RESULT:
====================
No errors should be present on the log of the server when the application is used or configured.


--Verified as fixed on 04-04-2016--
Comment by Luis Hernandez [X] (Inactive) [ 03/Mar/16 ]
Additionally to the bug above, every time that the page (with the "Dynamic List" portlet) is refreshed the errors are displayed on the log, and in some cases the styles (css) are missing, using other user and accessing the page via other web browser, the other users that are using the page are not displayed in the top of the Spreadsheet.

Please, for the bug above use a totally clean environment with liferay version: liferay-portal-6.2-ee-sp14
Comment by Luis Hernandez [X] (Inactive) [ 04/Mar/16 ]
Currently, I tested the bug above and seems like it was resolved, however, the next error is displayed when i refresh the page(in the first time):

---------------------
17:39:20,885 ERROR [http-bio-8080-exec-10][AtmosphereFramework:113] If you have more than one Connector enabled, make sure they both use the same protocol, e.g NIO/APR or HTTP for all. If not, org.atmosphere.container.BlockingIOCometSupport will be used and cannot be changed.
java.lang.IllegalStateException: Tomcat failed to detect this is a Comet application because context.xml is missing or the Http11NioProtocol Connector is not enabled.You must use the atmosphere-native-runtime dependency in order to use native Comet Support_If that's not the case, you can also remove META-INF/context.xml and WEB-INF/lib/atmosphere-compat-tomcat7.jar [Sanitized]
at org.atmosphere.container.Tomcat7CometSupport.<clinit>(Tomcat7CometSupport.java:56)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.atmosphere.cpr.DefaultAsyncSupportResolver.newCometSupport(DefaultAsyncSupportResolver.java:225)
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolveWebSocket(DefaultAsyncSupportResolver.java:288)
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolve(DefaultAsyncSupportResolver.java:274)
at org.atmosphere.cpr.AtmosphereFramework.autoDetectContainer(AtmosphereFramework.java:1579)
at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:717)
at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:614)
at org.atmosphere.cpr.AtmosphereServlet.configureFramework(AtmosphereServlet.java:91)
at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:80)
at com.liferay.portal.kernel.servlet.PortalDelegateServlet.doPortalInit(PortalDelegateServlet.java:64)
at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:44)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:74)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:58)
at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:54)
at com.liferay.portal.kernel.servlet.SecureServlet.init(SecureServlet.java:76)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1284)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1197)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1087)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5266)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5554)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1263)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1948)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
17:39:20,889 WARN [http-bio-8080-exec-10][AtmosphereFramework:275] Using org.atmosphere.container.Tomcat7BIOSupportWithWebSocket
----------


Tested again on 04-03-2016 afternoon, and the errors are gone--
Comment by mcalvo [ 04/Mar/16 ]
Alejandro please check this.
Comment by Luis Hernandez [X] (Inactive) [ 04/Mar/16 ]
2- [Bug] The rows just added (at the bottom by the owner) are displayed in the top of the sheet for the other users that are in the sheet
 
PRIORITY:
====================
Critical

REPRODUCIBILITY LEVEL:
====================
Always

STEPS:
====================
1.Login to liferay portal with the admin credentials (sheet/site page owner)
2.Go to the page that have the “Collaborative dynamic list” display portlet.
3.Write something in any first row cell
4.In other web browser window, login to liferay portal with other user that is not the sheet owner.
5.Click on any cell of the first row (with the user of the step4)
6. Add one more row at the bottom with the user of the step 1, and review where is the new row in the web browser window of the step 4.

CURRENT RESULT:
====================
The rows just added (at the bottom by the owner) are displayed in the top of the sheet for the other users that are in the sheet

Watch the next video:
http://screencast.com/t/cjeFjjrY9bp

EXPECTED RESULT:
====================
The rows just added always should be added in the bottom of the sheet

--Verified as fixed on 04-04-2016, according with comment below (Alejandro's comment)--
Comment by Luis Hernandez [X] (Inactive) [ 04/Mar/16 ]
3- [Bug] Non-admin users can’t write on the shared spreadSheet
 
PRIORITY:
====================
Critical

REPRODUCIBILITY LEVEL:
====================
Always

STEPS:
====================
1.Login to liferay portal with the admin credentials (sheet/site page owner)
2.Go to the page that have the “Collaborative dynamic list” display portlet.
3.Write something in any first row cell
4.In other web browser window, login to liferay portal with other user that is not the sheet owner.
5.Click on any cell of the first row, and write something on it

CURRENT RESULT:
====================
Non-admin users can’t write on the shared spreadSheet

Watch the next video:
http://screencast.com/t/AEzDcck6

EXPECTED RESULT:
====================
All the user SHOULD be able to write and modify the data on the shared spreadsheet


--Verified as fixed on 04-04-2016, according with comment below (Alejandro's comment)--
Comment by Alejandro Soto [X] (Inactive) [ 04/Mar/16 ]
Hi,
Bugs:
1- Console errors: already send new code push to disable the native comet support lookup, so errors will be gone now
2- Will check with Luis, per screen capture attache, the sort control was set on one of the columns so that's why row is added on top
3- User needs to have update permission over the spreadsheet in order to be able to edit it.
Comment by Luis Hernandez [X] (Inactive) [ 04/Mar/16 ]
4- [Bug] The Data on the cells disappears when other user clicks on the sort actions at the headers of the columns (In the first access to the spreadsheet)

PRIORITY:
====================
Critical

REPRODUCIBILITY LEVEL:
====================
Always

STEPS:
====================
1.Login to liferay portal with the admin credentials (sheet/site page owner)
2.Go to the page that have the “Collaborative dynamic list” display portlet.
3.Write something in any first row cell (repeat this for other cell)
4.In other web browser window, login to liferay portal with other user that is not the sheet owner.
5.Click on the sort action button of any header of columns
6. Notice that the data provided in the step3.

CURRENT RESULT:
====================
The Data on the cells disappears when other user clicks on the sort actions at the headers of the columns

Watch the next video:
http://screencast.com/t/ZRk3kJ53

EXPECTED RESULT:
====================
The data SHOULD not disappear when any user clicks on the sort actions at the headers.

--Verified as fixed on 07-04-2016--
Comment by Alejandro Soto [X] (Inactive) [ 07/Mar/16 ]
Bug number 4 fixed now, please download latest code base, cell field raw value was not being sent properly
Generated at Sat Feb 10 05:49:33 GMT 2024 using Jira 8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6.