Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,011
    • Issues 1,011
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • Core
  • Issues
  • #1005

Closed
Open
Created May 31, 2019 by haystack@haystack🤔Developer

"Confirm this subscription" URL generated by MailingEventSubscribe API should always be a front-end URL

Following on from discussion on this WordPress issue, it seems that the code in CiviCRM Core which generates the URL for use in the subscription confirmation email triggered via the MailingEventSubscribe API does not always force the URL to be a front-end URL.

This can be reproduced by using the CiviCRM API Explorer in WordPress but also applies (as is the case for the reporter) when a form is submitted via the standard WordPress AJAX route of admin_url('admin-ajax.php').

PR to follow.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
5.15.0
Milestone
5.15.0
Assign milestone
Time tracking
None
Due date
None