Answers.Body: <p>The <code>esspeaker</code> part is coming from the civimobile extension: <a href="https://civicrm.org/extensions/civimobileapi" rel="nofollow noreferrer">https://civicrm.org/extensions/civimobileapi</a></p>
  <p>Might want to file an issue there if it's not already fixed in a recent version: <a href="https://lab.civicrm.org/extensions/civimobileapi" rel="nofollow noreferrer">https://lab.civicrm.org/extensions/civimobileapi</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-23T15:34:34.300Z
Answers.Text: Ah. Hadn't thought of that, thanks. Extensions (minus Payment Shared) are all up to date.
Answers.UserDisplayName: Michael Matthews
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-07-23T14:50:08.897Z
Answers.LastActivityDate: 2022-07-23T14:50:08.897Z
Answers.UserDisplayName: Demerit
Body: <p>CiviCRM 5.50.1, WordPress 6.0.1, 8.0.28.</p>
  <p>Someone recently tried to add an Agenda to an Event in CiviCRM, and kept getting a network error. I took a look, and yeah, going to the Agenda tab seems to cause a crash. The log file shows lots of stuff, but this:</p>
  <p>[nativecode=1055 ** Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'civicrm_members.esspeaker.id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by]</p>
  <p>seems to be the most useful entry. I've seen this type of error in other posts, but nothing for the event Agenda. Most of the hits I find suggest these should have been fixed by now, so, is this a bug in CiviCRM? Not seeing anything that looks like a bug fix note in newer versions.</p>
  <p>I'm hesitant to reconfigure SQL to turn off only_full_group_by as a workaround unless that's the only way around this (and honestly, there was no need for an Agenda, as that seems to be a bit more than a text note anyway based on the fact that it cares so much about the database).</p>
  <p>Any other ideas / fixes? I'll probably upgrade the system tomorrow as it looks like 5.51.1 may fix another bug we've hit (automatic renewal during contribution) and will update this note if I get the update done and it resolves the issue.</p>
  <p>Thanks.</p>
  <p>Michael</p>
  
Tags: <civievent><error><database>
Title: Trying to edit Agenda tab in Events gives a DB error
ThreadText: # Trying to edit Agenda tab in Events gives a DB error
  
  (Asked by: username_0 on 2022-07-23)
  
  CiviCRM 5.50.1, WordPress 6.0.1, 8.0.28.
  
  Someone recently tried to add an Agenda to an Event in CiviCRM, and kept getting a network error. I took a look, and yeah, going to the Agenda tab seems to cause a crash. The log file shows lots of stuff, but this:
  
  [nativecode=1055 \*\* Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'civicrm\_members.esspeaker.id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql\_mode=only\_full\_group\_by]
  
  seems to be the most useful entry. I've seen this type of error in other posts, but nothing for the event Agenda. Most of the hits I find suggest these should have been fixed by now, so, is this a bug in CiviCRM? Not seeing anything that looks like a bug fix note in newer versions.
  
  I'm hesitant to reconfigure SQL to turn off only\_full\_group\_by as a workaround unless that's the only way around this (and honestly, there was no need for an Agenda, as that seems to be a bit more than a text note anyway based on the fact that it cares so much about the database).
  
  Any other ideas / fixes? I'll probably upgrade the system tomorrow as it looks like 5.51.1 may fix another bug we've hit (automatic renewal during contribution) and will update this note if I get the update done and it resolves the issue.
  
  Thanks.
  
  username_0
  
  **Tags:** civievent, error, database
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-07-23. Score: 0
  
  The `esspeaker` part is coming from the civimobile extension: <https://civicrm.org/extensions/civimobileapi>
  
  Might want to file an issue there if it's not already fixed in a recent version: <https://lab.civicrm.org/extensions/civimobileapi>
  
  > **Comments:**
  > **username_0**: Ah. Hadn't thought of that, thanks. Extensions (minus Payment Shared) are all up to date.  
  
  ---
  
  