Needs work
Project:
Profile2 Registration Path
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 Dec 2012 at 18:46 UTC
Updated:
12 Mar 2017 at 09:35 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
TelFiRE commented+1
Comment #2
pandorawombat commentedAnyone have any luck with this?
Comment #3
grasmash commentedThis isn't really a p2rp issue– it's a drupal access issue.
There are a number of modules that modify Drupal's default 403 behavior:
Comment #4
TelFiRE commentedUh, I don't want to change my 403s, I want them to be sent to a page that isn't a 403... am I missing something
Comment #5
codesmithComment #6
luthien commentedI kept getting ACCESS DENIED error after an user logins to the site and tries to visit any of the profile pages below:
[path], [path]/register, [path]/login, and [path]/password
if using user/, user/register, user/login, and user/pssword everything works fine.
With profile2 unique registration path all I get is a 403 error. It looks like a problem with the module, not a drupal access issue.
Comment #7
luthien commentedI used the custom error module to add a redirect. I was unable to get it to work with rules.
Comment #8
luksakCreated a first patch which fixes this issue. Might need some work.
Comment #10
Exploratus commented+1
Comment #11
loparr commentedI solved it with rules path module. Just redirect logged in user to "user" path.
Comment #12
ladybug_3777 commentedI was looking for a simple redirect solution for this 403 as well. I'll check out the rules path module.
Comment #13
sgdev commentedThe Drupal Rules module can be used to accomplish this without the need for additional modules.
Add an event of "User has logged in" and an action of "Page redirect." Then simply add whatever path to which you'd like the logged in user to be redirected.
Comment #14
chrisfree commentedThe way that core handles this is actually pretty clever. I wonder if it would be best to replicate that behavior by default? I was able to accomplish this by duplicating the way core does it:
If there isn't something terribly wrong with this approach, I'd be happy to whip up a patch to accomplish this in a more generic way via this module.
Comment #15
addiction2code commentedI was thinking about going the rules route but it doesn't really make sense since I'm also using LoginToboggan which redirects users to a login if access is denied. If a user is to login using one of those pages I would assume they wouldn't be redirected to the correct destination.
Comment #16
luxpir commentedI did it the same as loparr in #11.
See: https://www.drupal.org/node/2224359#comment-11803930 for more info.
Comment #17
waqarit commented#14 is nice way to do this.
Comment #18
ikeigenwijs commented#14 ++