Body: <p>After upgrading to CiviCRM 4.7.31 I began to get several errors while initially trying to send a test e-mail using an ACL-based user.  I noticed that these errors were not happening with the Administrator account.  Upon trying to reuse a previous e-mail I got the following error:</p>
  
  <pre><code>&gt; CiviCRM_API3_Exception: "DB Error: no such table"
  &gt; 
  &gt; #0 /public_html/www/sites/all/modules/civicrm/CRM/Mailing/Controller/Send.php(67):
  &gt; civicrm_api3("Mailing", "clone", (Array:1))
  &gt; #1 /public_html/www/sites/all/modules/civicrm/CRM/Core/Invoke.php(304):
  &gt; CRM_Mailing_Controller_Send-&gt;__construct("New Mailing", TRUE, "null",
  &gt; NULL, "false")
  &gt; #2 /public_html/www/sites/all/modules/civicrm/CRM/Core/Invoke.php(84):
  &gt; CRM_Core_Invoke::runItem((Array:14))
  &gt; #3 /public_html/www/sites/all/modules/civicrm/CRM/Core/Invoke.php(52):
  &gt; CRM_Core_Invoke::_invoke((Array:3))
  &gt; #4 /public_html/www/sites/all/modules/civicrm/drupal/civicrm.module(445):
  &gt; CRM_Core_Invoke::invoke((Array:3))
  &gt; #5 [internal function](): civicrm_invoke("mailing", "send")
  &gt; #6 /public_html/www/includes/menu.inc(527): call_user_func_array("civicrm_invoke", (Array:2))
  &gt; #7 /public_html/www/index.php(21): menu_execute_active_handler()
  &gt; #8 {main}
  </code></pre>
  
  <p>I believe that Civi builds a temporary table based on the active user's ACL settings.  This is why this behavior doesn't trigger when using the Administrator account.  Any ideas on how to fix this?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-10T13:51:45.003Z
Comments.Text: Where did you upgrade from (what version were you on prior to this)?
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-11T17:52:36.953Z
Comments.Text: Upgraded from 4.7.30.  Originally started to have problems such as Mail stuck on Saving and other nuances prior to upgrading.  Problems began after upgrading from 4.7.29 to 4.7.30.
Comments.UserDisplayName: R. Alfaro
Tags: <drupal><civimail><database><acl>
Title: CiviMail cannot create ACL recipient table after upgrading to CiviCRM 4.7.31
ThreadText: # CiviMail cannot create ACL recipient table after upgrading to CiviCRM 4.7.31
  
  (Asked by: username_0 on 2018-03-10)
  
  After upgrading to CiviCRM 4.7.31 I began to get several errors while initially trying to send a test e-mail using an ACL-based user. I noticed that these errors were not happening with the Administrator account. Upon trying to reuse a previous e-mail I got the following error:
  
  ```
  > CiviCRM_API3_Exception: "DB Error: no such table"
  > 
  > #0 /public_html/www/sites/all/modules/civicrm/CRM/Mailing/Controller/Send.php(67):
  > civicrm_api3("Mailing", "clone", (Array:1))
  > #1 /public_html/www/sites/all/modules/civicrm/CRM/Core/Invoke.php(304):
  > CRM_Mailing_Controller_Send->__construct("New Mailing", TRUE, "null",
  > NULL, "false")
  > #2 /public_html/www/sites/all/modules/civicrm/CRM/Core/Invoke.php(84):
  > CRM_Core_Invoke::runItem((Array:14))
  > #3 /public_html/www/sites/all/modules/civicrm/CRM/Core/Invoke.php(52):
  > CRM_Core_Invoke::_invoke((Array:3))
  > #4 /public_html/www/sites/all/modules/civicrm/drupal/civicrm.module(445):
  > CRM_Core_Invoke::invoke((Array:3))
  > #5 [internal function](): civicrm_invoke("mailing", "send")
  > #6 /public_html/www/includes/menu.inc(527): call_user_func_array("civicrm_invoke", (Array:2))
  > #7 /public_html/www/index.php(21): menu_execute_active_handler()
  > #8 {main}
  
  ```
  
  I believe that Civi builds a temporary table based on the active user's ACL settings. This is why this behavior doesn't trigger when using the Administrator account. Any ideas on how to fix this?
  
  **Tags:** drupal, civimail, database, acl
  
  > **Comments:**
  > **username_1**: Where did you upgrade from (what version were you on prior to this)?  
  > **username_0**: Upgraded from 4.7.30.  Originally started to have problems such as Mail stuck on Saving and other nuances prior to upgrading.  Problems began after upgrading from 4.7.29 to 4.7.30.  
  
  ---
  
  ## 0 answers
  
  