Answers.Body: <p>You are correct.  That is a bug.  here is the report - <a href="https://lab.civicrm.org/dev/core/-/issues/1865" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/-/issues/1865</a></p>
  <p>It's been fixed <a href="https://github.com/civicrm/civicrm-core/commit/bcbfa93e255ee15d9bd9e0f812b2a5a617458d73" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/commit/bcbfa93e255ee15d9bd9e0f812b2a5a617458d73</a>  and is planned for the next 5.27 release</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-14T20:06:42.640Z
Answers.Text: That fixed it - thank you!
Answers.UserDisplayName: themak
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-14T19:48:03.953Z
Answers.LastActivityDate: 2020-07-14T19:48:03.953Z
Answers.UserDisplayName: Kevin Cristiano
Body: <p>Using Mosaico 2.3 (2.4 does not work for us) &amp; traditional civimail.
  CiviCRM 5.27.1 WordPress 5.4.2</p>
  <p>All url's in civimail append ?civiwp=CiviCRM - causing errors when linking to wordpress pages. example.org becomes example.org/?civiwp=CiviCRM - This is fine for most URLs but causes issues with wordpress urls.</p>
  
Tags: <wordpress><civimail><mosaico>
Title: CiviMail adding ?civiwp=CiviCRM to all links - causing links to be bad
ThreadText: # CiviMail adding ?civiwp=CiviCRM to all links - causing links to be bad
  
  (Asked by: username_0 on 2020-07-14)
  
  Using Mosaico 2.3 (2.4 does not work for us) & traditional civimail.
  CiviCRM 5.27.1 WordPress 5.4.2
  
  All url's in civimail append ?civiwp=CiviCRM - causing errors when linking to wordpress pages. example.org becomes example.org/?civiwp=CiviCRM - This is fine for most URLs but causes issues with wordpress urls.
  
  **Tags:** wordpress, civimail, mosaico
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-07-14. Score: 2 | Accepted answer
  
  You are correct. That is a bug. here is the report - <https://lab.civicrm.org/dev/core/-/issues/1865>
  
  It's been fixed <https://github.com/civicrm/civicrm-core/commit/bcbfa93e255ee15d9bd9e0f812b2a5a617458d73> and is planned for the next 5.27 release
  
  > **Comments:**
  > **username_0**: That fixed it - thank you!  
  
  ---
  
  