[JBoss JIRA] (GTNPORTAL-3014) OrganizationService.getUserHandler().findUsersByGroupId(groupid) not working with H2 database
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3014?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3014:
----------------------------------------------------
Martin Weiler <mweiler(a)redhat.com> made a comment on [bug 915766|https://bugzilla.redhat.com/show_bug.cgi?id=915766]
No, the customer is not using H2 in production. The issue was discovered during testing.
> OrganizationService.getUserHandler().findUsersByGroupId(groupid) not working with H2 database
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3014
> URL: https://issues.jboss.org/browse/GTNPORTAL-3014
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta01
> Reporter: Marek Posolda
> Assignee: Marek Posolda
> Fix For: 3.6.0.Beta02
>
>
> Description of problem:
> Using default setup with H2 database, calling OrganizationService.getUserHandler().findUsersByGroupId(groupid) raises an exception.
> Executing the following code:
> 30 users = organizationService.getUserHandler().findUsersByGroupId("/platform/users");
> 31
> 32 if (users.getSize() > 0)
> 33 {
> results in the following exception:
> 11:01:30,352 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-2) SQL Error: 90068, SQLState: 90068
> 11:01:30,352 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-2) Order by expression "HIBERNATEI2_.NAME" must be in the result list in this case; SQL statement:
> select distinct hibernatei1_.ID as ID4_, hibernatei1_.IDENTITY_TYPE as IDENTITY2_4_, hibernatei1_.NAME as NAME4_, hibernatei1_.REALM as REALM4_ from jbid_io_rel hibernatei0_ inner join jbid_io hibernatei1_ on hibernatei0_.TO_IDENTITY=hibernatei1_.ID cross join jbid_io hibernatei2_ cross join jbid_io hibernatei3_ where hibernatei0_.TO_IDENTITY=hibernatei2_.ID and hibernatei0_.FROM_IDENTITY=hibernatei3_.ID and hibernatei2_.REALM=? and hibernatei3_.REALM=? and (hibernatei2_.NAME like ?) and hibernatei0_.FROM_IDENTITY=? order by hibernatei2_.NAME asc [90068-168]
> 11:01:30,355 ERROR [stderr] (http-/127.0.0.1:8080-2) org.picketlink.idm.api.query.QueryException: Failed to execute query
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.picketlink.idm.impl.api.query.UserQueryExecutorImpl.execute(UserQueryExecutorImpl.java:220)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.picketlink.idm.impl.api.query.UserQueryExecutorImpl.list(UserQueryExecutorImpl.java:245)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.picketlink.idm.impl.api.session.IdentitySessionImpl.list(IdentitySessionImpl.java:364)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.exoplatform.services.organization.idm.IDMUserListAccess.getSize(IDMUserListAccess.java:123)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.exoplatform.demo.portlet.portletOrganization.doView(portletOrganization.java:32)
> The same issue does not show up with other databases, such as MySQL.
--
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, 9 months
[JBoss JIRA] (GTNPORTAL-3014) OrganizationService.getUserHandler().findUsersByGroupId(groupid) not working with H2 database
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3014?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-3014:
----------------------------------------------------
Dominik Pospisil <dpospisi(a)redhat.com> made a comment on [bug 915766|https://bugzilla.redhat.com/show_bug.cgi?id=915766]
Just wondering, the customer is using H2 in production?
> OrganizationService.getUserHandler().findUsersByGroupId(groupid) not working with H2 database
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3014
> URL: https://issues.jboss.org/browse/GTNPORTAL-3014
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration
> Affects Versions: 3.6.0.Beta01
> Reporter: Marek Posolda
> Assignee: Marek Posolda
> Fix For: 3.6.0.Beta02
>
>
> Description of problem:
> Using default setup with H2 database, calling OrganizationService.getUserHandler().findUsersByGroupId(groupid) raises an exception.
> Executing the following code:
> 30 users = organizationService.getUserHandler().findUsersByGroupId("/platform/users");
> 31
> 32 if (users.getSize() > 0)
> 33 {
> results in the following exception:
> 11:01:30,352 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-2) SQL Error: 90068, SQLState: 90068
> 11:01:30,352 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-2) Order by expression "HIBERNATEI2_.NAME" must be in the result list in this case; SQL statement:
> select distinct hibernatei1_.ID as ID4_, hibernatei1_.IDENTITY_TYPE as IDENTITY2_4_, hibernatei1_.NAME as NAME4_, hibernatei1_.REALM as REALM4_ from jbid_io_rel hibernatei0_ inner join jbid_io hibernatei1_ on hibernatei0_.TO_IDENTITY=hibernatei1_.ID cross join jbid_io hibernatei2_ cross join jbid_io hibernatei3_ where hibernatei0_.TO_IDENTITY=hibernatei2_.ID and hibernatei0_.FROM_IDENTITY=hibernatei3_.ID and hibernatei2_.REALM=? and hibernatei3_.REALM=? and (hibernatei2_.NAME like ?) and hibernatei0_.FROM_IDENTITY=? order by hibernatei2_.NAME asc [90068-168]
> 11:01:30,355 ERROR [stderr] (http-/127.0.0.1:8080-2) org.picketlink.idm.api.query.QueryException: Failed to execute query
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.picketlink.idm.impl.api.query.UserQueryExecutorImpl.execute(UserQueryExecutorImpl.java:220)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.picketlink.idm.impl.api.query.UserQueryExecutorImpl.list(UserQueryExecutorImpl.java:245)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.picketlink.idm.impl.api.session.IdentitySessionImpl.list(IdentitySessionImpl.java:364)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.exoplatform.services.organization.idm.IDMUserListAccess.getSize(IDMUserListAccess.java:123)
> 11:01:30,356 ERROR [stderr] (http-/127.0.0.1:8080-2) at org.exoplatform.demo.portlet.portletOrganization.doView(portletOrganization.java:32)
> The same issue does not show up with other databases, such as MySQL.
--
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, 9 months
[JBoss JIRA] (GTNPORTAL-2711) Database/jcr is not initialized before first call
by Tomas Kyjovsky (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2711?page=com.atlassian.jira.pl... ]
Tomas Kyjovsky commented on GTNPORTAL-2711:
-------------------------------------------
Hi! Do any of you guys still have the modified TestGadgetTokenInfoService code? I need it to reproduce this issue (for JPP testing) but the branch on github is already gone: https://github.com/stianst/gatein-portal/tree/GTNPORTAL-2711.
> Database/jcr is not initialized before first call
> -------------------------------------------------
>
> Key: GTNPORTAL-2711
> URL: https://issues.jboss.org/browse/GTNPORTAL-2711
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Minh Hoang TO
> Labels: done, portal-s70
> Fix For: 3.6.0.Beta02
>
>
> I believe some data structures are not initialized in chromattic/jcr until first used. If multiple threads do this at the same time it causes an ItemExistsException to be thrown.
> To reproduce this issue I've slightly modified TestGadgetTokenInfoService in gadgets/core available here https://github.com/stianst/gatein-portal/tree/GTNPORTAL-2711. It may not fail the first time, so run it a few times if it doesn't.
> Stack trace:
> {code}
> org.chromattic.api.UndeclaredRepositoryException: javax.jcr.ItemExistsException: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41b
> aa4a6e, ParentID: 00exo0jcr0root0uuid0000000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or
> index violation: JCR_IDX_IPORTALTEST_PARENT: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uu
> id0000000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTE
> ST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.chromattic.core.DomainSession.save(DomainSession.java:181)
> at org.chromattic.core.api.ChromatticSessionImpl.save(ChromatticSessionImpl.java:246)
> at org.exoplatform.commons.chromattic.AbstractContext.close(AbstractContext.java:129)
> at org.exoplatform.commons.chromattic.LocalContext.close(LocalContext.java:56)
> at org.exoplatform.commons.chromattic.ChromatticLifeCycle.closeContext(ChromatticLifeCycle.java:306)
> at org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:49)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:50)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testGetToken(TestGadgetTokenInfoService.java:88)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: javax.jcr.ItemExistsException: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uuid00
> 00000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_P
> ARENT: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uuid0000000000000. Cause >>>> integrity c
> onstraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violati
> on: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.exoplatform.services.jcr.impl.core.SessionDataManager.commit(SessionDataManager.java:1565)
> at org.exoplatform.services.jcr.impl.core.ItemImpl.save(ItemImpl.java:706)
> at org.exoplatform.services.jcr.impl.core.SessionImpl.save(SessionImpl.java:1080)
> at org.exoplatform.commons.chromattic.PortalSessionLifeCycle.save(PortalSessionLifeCycle.java:56)
> at org.chromattic.core.jcr.SessionWrapperImpl.save(SessionWrapperImpl.java:274)
> at org.chromattic.core.DomainSessionImpl._save(DomainSessionImpl.java:640)
> at org.chromattic.core.DomainSession.save(DomainSession.java:178)
> ... 34 more
> Caused by: javax.jcr.ItemExistsException: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uuid00
> 00000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_P
> ARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.exoplatform.services.jcr.impl.storage.jdbc.SQLExceptionHandler.handleAddException(SQLExceptionHandler.java:141)
> at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.add(JDBCStorageConnection.java:746)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager.doAdd(WorkspacePersistentDataManager.java:1009)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager$ChangesLogPersister.save(WorkspacePersistentDataManager.java:662)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager.save(WorkspacePersistentDataManager.java:333)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.doSave(CacheableWorkspaceDataManager.java:1102)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.access$800(CacheableWorkspaceDataManager.java:93)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager$9.run(CacheableWorkspaceDataManager.java:1045)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager$9.run(CacheableWorkspaceDataManager.java:1042)
> at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedExceptionAction(SecurityHelper.java:310)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.save(CacheableWorkspaceDataManager.java:1041)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.save(CacheableWorkspaceDataManager.java:1007)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.ShareableSupportedWorkspaceDataManager.save(ShareableSupportedWorkspaceDataManager.java:176)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.VersionableWorkspaceDataManager.save(VersionableWorkspaceDataManager.java:334)
> at org.exoplatform.services.jcr.impl.dataflow.session.TransactionableDataManager.save(TransactionableDataManager.java:471)
> at org.exoplatform.services.jcr.impl.core.SessionDataManager.commit(SessionDataManager.java:1549)
> ... 40 more
> Caused by: java.sql.SQLException: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
> at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(Unknown Source)
> at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(Unknown Source)
> at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
> at org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.db.MultiDbJDBCConnection.addNodeRecord(MultiDbJDBCConnection.java:253)
> at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.add(JDBCStorageConnection.java:732)
> ... 54 more
> Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.hsqldb.error.Error.error(Unknown Source)
> at org.hsqldb.index.IndexAVLMemory.insert(Unknown Source)
> at org.hsqldb.persist.RowStoreAVL.indexRow(Unknown Source)
> at org.hsqldb.Table.insertSingleRow(Unknown Source)
> at org.hsqldb.StatementDML.insertSingleRow(Unknown Source)
> at org.hsqldb.StatementInsert.getResult(Unknown Source)
> at org.hsqldb.StatementDMQL.execute(Unknown Source)
> at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
> at org.hsqldb.Session.execute(Unknown Source)
> ... 59 more
> {code}
--
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, 9 months
[JBoss JIRA] (GTNPORTAL-3222) Checkbox selection on "add gadget into category" is lost after switch page by paginator
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3222?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3222:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 3.7.0.Final
Resolution: Done
> Checkbox selection on "add gadget into category" is lost after switch page by paginator
> ---------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3222
> URL: https://issues.jboss.org/browse/GTNPORTAL-3222
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Hai Nguyen
> Assignee: Hai Nguyen
> Priority: Minor
> Labels: backlogs
> Fix For: 3.7.0.Final
>
>
> 1. Go to Application registry page
> 2. Create a gadget (remote, or manual)
> 3. Click on link "Click here to add into categories "
> 4. Select some category by checkbox
> 5. Switch to page 2, select some category
> 6. Switch to page 1
> Actual result: - Categories selected at step 4 are unchecked
> Expect result: Categories selected at step 4 are still checked
--
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, 9 months
[JBoss JIRA] (GTNPORTAL-3220) Show wrong message when uncheck show publication date in add/edit node
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3220?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3220:
----------------------------------
Fix Version/s: 3.7.0.Final
> Show wrong message when uncheck show publication date in add/edit node
> ----------------------------------------------------------------------
>
> Key: GTNPORTAL-3220
> URL: https://issues.jboss.org/browse/GTNPORTAL-3220
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.1.Final
> Reporter: Son Tran
> Assignee: Son Tran
> Priority: Minor
> Labels: backlogs
> Fix For: 3.7.0.Final
>
>
> Add/edit a node
> In Page Node Setting tab:
> Check Show publication date
> Set Start Publication Date (02/25/2013 15:30:27) is greater than End Publication Date (02/24/2013 15:30:29)
> Uncheck show publication date
> Click Save
> => Show message alert :"The end date must be after the start date." -> NOK
> Expected output: The Publication date don't save after set publication date/time for node
--
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, 9 months
[JBoss JIRA] (GTNPORTAL-3220) Show wrong message when uncheck show publication date in add/edit node
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3220?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3220:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Show wrong message when uncheck show publication date in add/edit node
> ----------------------------------------------------------------------
>
> Key: GTNPORTAL-3220
> URL: https://issues.jboss.org/browse/GTNPORTAL-3220
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.1.Final
> Reporter: Son Tran
> Assignee: Son Tran
> Priority: Minor
> Labels: backlogs
> Fix For: 3.7.0.Final
>
>
> Add/edit a node
> In Page Node Setting tab:
> Check Show publication date
> Set Start Publication Date (02/25/2013 15:30:27) is greater than End Publication Date (02/24/2013 15:30:29)
> Uncheck show publication date
> Click Save
> => Show message alert :"The end date must be after the start date." -> NOK
> Expected output: The Publication date don't save after set publication date/time for node
--
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, 9 months