'Access Denied' to Profile Registration Path after updating to 7-1.13 or 7.x-2.0-beta4 [#2829499]

After upgrading to the latest security release (from 7.x-1.12 to 7.x-1.13, as well as from 7.x-2.0-beta3 to 7.x-2.0-beta4), my custom registration path is no longer available via direct link and has disappeared from the menu. When logged in as anonymous, I get the message "Access denied. You must log in to view this page."

When logged in as admin (or anything else), I get 'You are not authorized to access this page." (This behavior is expected).

These updates prevent registration from custom paths unless visitors (in general) have permission to register for new accounts. However, this removes a desirable feature to disable the /user/register path while allowing custom registration paths.

Comments

Comment #1

22 November 2016 at 00:40

phandolin created an issue. See original summary.

Comment #2

phandolin CreditAttribution: phandolin as a volunteer commented 22 November 2016 at 00:41

Oh, I'm on the latest 7.52 Drupal core

Comment #3

phandolin CreditAttribution: phandolin as a volunteer commented 22 November 2016 at 18:18

Another possible clue, when I try to add a menu link, it gives this error "The path 'alumni-account/register' is either invalid or you do not have access to it."

Comment #4

noahott CreditAttribution: noahott as a volunteer commented 5 December 2016 at 16:18

The 1.13 update prevents registration from custom paths unless the visitors have permission to register for new accounts. That setting can be found under "Registration and cancelation" pane at /admin/config/people/accounts

Comment #5

paulmckibben

he/him

English

Atlanta, GA

CreditAttribution: paulmckibben at Turbojet Technologies for Mediacurrent commented 4 January 2017 at 20:35

Title:	'Access Denied' to Profile Registration Path after updating to 7-1.13	» 'Access Denied' to Profile Registration Path after updating to 7-1.13 or 7.x-2.0-beta4
Issue summary:	View changes

Updated the issue description to include 7.x-2.0-beta4. Also, although the comment in #4 is helpful, a desirable feature has been removed: it was previously possible to allow custom registration paths (with automatic role assignment) while disabling the general /user/register path.