CRM-17009 event registration doesn't respect reg end date

          Details

          • Type: Bug
          • Status: Done/Fixed
          • Priority: Trivial
          • Resolution: Fixed/Completed
          • Affects Version/s: 4.6.6
          • Fix Version/s: 4.6.7
          • Component/s: CiviEvent
          • Labels:
            None
          • Documentation Required?:
            None
          • Funding Source:
            Core Team Funds

            Description

            event online registration does not respect the registration end date. I suspect this is related to the work on https://issues.civicrm.org/jira/browse/CRM-15564 – it's unclear if that issue was actually resolved (it was reopened and later closed, but there is no second PR).

            to reproduce:

            • create an event with a future date
            • enable online registration with a past end date
            • open the event reg form

            expected result: registration denied (past end date).
            actual result: registration remains available.

              Attachments

                Activity

                [CRM-17009] event registration doesn't respect reg end date
                Brian Shaughnessy added a comment -

                reproduced on the demo site here: http://d46.demo.civicrm.org/civicrm/event/register?id=7&reset=1

                Jitendra Purohit added a comment -

                Submitted a PR : https://github.com/civicrm/civicrm-core/pull/6487. It blocks the registrations if `registration end_date` is not empty and in the past. If `registration end_date` is empty, it checks for `event_end_date` and block the registration if it is in the past.

                Sudha Bisht added a comment -

                Tested working fine.

                  People

                  • Assignee:
                    Sudha Bisht
                    Reporter:
                    Brian Shaughnessy

                    Dates

                    • Created:
                      Updated:
                      Resolved: