Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-12150

Drupal (and other CMS?) logins throw fatal after 4.3 code is applied to a site

          Details

          • Type: Bug
          • Status: Done/Fixed
          • Priority: Major
          • Resolution: Won't Fix
          • Affects Version/s: 4.3.0
          • Fix Version/s: 4.3.0
          • Component/s: Core CiviCRM
          • Labels:
            None

            Description

            When upgrading from 4.1 or 4.2 to 4.3, if I try to login to my Drupal 7 site to run civicrm/upgrade - I immediately get a fatal error ("No such table) even though I am just viewing my Drupal home page (http://civicrm43/node/1).

            Although I can still navigate to http://civicrm43/civicrm/upgrade?reset=1 and get the upgrade screen - I think this behavior will be quite confusing to admins.

            I tested the same steps in a 4.1 -> 4.2 upgrade and the fatal is NOT thrown. Apparently 4.3 is executing some CiviCRM code at login which fails when an older DB is present.

              Attachments

                Activity

                  People

                  • Assignee:
                    kurund Kurund Jalmi
                    Reporter:
                    dgg David Greenberg
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: