Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't require CiviEvent permission to create repeating activity #13405

Merged

Conversation

davejenx
Copy link
Contributor

@davejenx davejenx commented Jan 4, 2019

Overview

See https://lab.civicrm.org/dev/core/issues/640
Creating a repeating activity through the UI gives an Access Denied error unless the user has "access CiviEvent" permission.

Steps to replicate

  1. Log in as a user without "access CiviEvent" permission.
  2. From contact summary, Activities tab, click New Activity, choose e.g. Meeting.
  3. Expand the "Repeat Activity" section, Click the "After" radio button, Save.

Before

Confirm dialog is blank. Error message appears:
"Access Denied / Ensure you are still logged in and have permission to access this feature.".
On clicking Confirm, the instances are created and listed.

After

Confirm dialog lists the instances that will be created.
On clicking Confirm, the instances are created and listed.

Technical Details

Problem occurs because the confirm dialog uses a path that requires "access CiviEvent" permission. In CRM/Core/xml/Menu/Misc.xml:

  <item>
     <path>civicrm/recurringentity/preview</path>
     <page_callback>CRM_Core_Page_RecurringEntityPreview</page_callback>
     <access_arguments>access CiviCRM,access CiviEvent</access_arguments>
     <title>Confirm dates</title>
  </item>

Problem is resolved by removing ",access CiviEvent".

@civibot
Copy link

civibot bot commented Jan 4, 2019

(Standard links)

@civibot civibot bot added the master label Jan 4, 2019
@seamuslee001
Copy link
Contributor

(CiviCRM Review Template WORD-1.2)

@seamuslee001 seamuslee001 merged commit 775ddeb into civicrm:master Jan 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants