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

Change Log crash - table entity_log_civireport does not exist

    Details

    • Type: Bug
    • Status: Open
    • Priority: Important
    • Resolution: Unresolved
    • Affects Version/s: 4.7.27, 4.7.29, 4.7.30
    • Fix Version/s: None
    • Component/s: Core CiviCRM
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      None
    • Funding Source:
      Needs Funding
    • Verified?:
      Yes

      Description

      I switched logging on, then clicked 'Change Log' and got 'Network error - could not reach the server.  An error traceback was created and can be recreated at willbacktrace.txt - attached.

      See stackexchange https://civicrm.stackexchange.com/questions/22811/change-log-crashes-table-entity-log-civireport-doesnt-exist-how-to-fix

      Please note that this has been reported by 2 different users, and of course switching logging on isn't an everyday occurrence!  I created a new install to try & reproduce, and also tried on http://dmaster.demo.civicrm.org but could not reproduce.  So appears to only affect upgraded systems - my client has been running CiviCRM for over 4 years (it at 4.7.27 & Drupal)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              clarkac Andy Clark
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: