Details

    • Branch Version/s:
      6.1.x
    • Backported to Branch:
      Committed
    • Business Value:
      3
    • Similar Issues:
      Show 5 results 

      Description

      1. go to web content edition page
      2. go to Schedule section
      3. uncheck "Never Auto-expire" checkbox
      4. set Expiration date to somewhere between Display Date and current date and time.
      5. Press Publish button
      6. Edit that web content again and go to Schedule section

      Effect: "never Auto-expire" is still checked despite the fact that there was no warning window, no error message nor exception in console. There is nothing wrong in setting date from past but it seems Liferay decides for user what is good and what is wrong without telling him that. Also this behaviour is not documented anywhere so possibly this is a bug.

        Issue Links

          Activity

          Hide
          Sergio Gonzalez added a comment -

          Juan is going to take a look at the logic in JournalArticleLocalServiceImpl:

          if (status == WorkflowConstants.STATUS_APPROVED) {
          Date expirationDate = article.getExpirationDate();

          if ((expirationDate != null) && expirationDate.before(now))

          { neverExpire = true; article.setExpirationDate(null); }

          }

          Show
          Sergio Gonzalez added a comment - Juan is going to take a look at the logic in JournalArticleLocalServiceImpl: if (status == WorkflowConstants.STATUS_APPROVED) { Date expirationDate = article.getExpirationDate(); if ((expirationDate != null) && expirationDate.before(now)) { neverExpire = true; article.setExpirationDate(null); } }
          Hide
          Michael Saechang added a comment -

          Committed on:
          Portal 6.2.x GIT ID: 6f64be48188ffaff36b693ae17fea198a745851e.

          Show
          Michael Saechang added a comment - Committed on: Portal 6.2.x GIT ID: 6f64be48188ffaff36b693ae17fea198a745851e.
          Hide
          Ginson Ren added a comment -

          PASSED Manual Testing following the steps in the description.

          Reproduced on:
          Tomcat 7.0 + MySQL 5. Portal 6.1.20 EE GA2.

          "Never Auto-expire" is still checked.

          Fixed on:
          Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: bb0a587f9b79470896590002198fa99472763983.
          Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 601e73e2faa6c1954d351c9e01b0193918f2cf03.

          User cannot publish the web content and the page will show "Your request failed to complete. Please enter a valid expiration date."

          Show
          Ginson Ren added a comment - PASSED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + MySQL 5. Portal 6.1.20 EE GA2. "Never Auto-expire" is still checked. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: bb0a587f9b79470896590002198fa99472763983. Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 601e73e2faa6c1954d351c9e01b0193918f2cf03. User cannot publish the web content and the page will show "Your request failed to complete. Please enter a valid expiration date."

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                2 years, 44 weeks, 5 days ago

                Development

                  Structure Helper Panel