Problem/Motivation

There is another view called views.view.events on my system.

Drupal\Core\Config\PreExistingConfigException: Configuration objects
(views.view.events) provided by recurring_events_views already exist in
active configuration.

Why not rename the view to views.view.recurring_events to reduce potential namespace collision

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork recurring_events-3269555

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

SocialNicheGuru created an issue. See original summary.

owenbush’s picture

owenbush commented

Thanks for this issue, avoiding naming conflicts is a good idea. I'll take a look at updating all the views to be more explicitly named.

owenbush opened merge request !30

owenbush’s picture

owenbush commented
Status: Active » Needs review

I have created an MR that changes the machine names of each of the 3 views in the recurring_events_views submodule. This is ready for review.

  • owenbush committed 8dad0f7 on 2.0.x 
    Issue #3269555 by owenbush: Rename the view so there is no name conflict

  • owenbush committed 4978eab on 8.x-1.x 
    Issue #3269555 by owenbush: Rename the view so there is no name conflict
owenbush’s picture

owenbush commented
Status: Needs review » Fixed

This has been merged into the dev branches 2.0.x and 8.x-1.x

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.