-
Notifications
You must be signed in to change notification settings - Fork 32
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
"Change Email Setting for this Group" Link is not working in E-Mail #206
Comments
This seems incorrect to me. As far as I can see, Is it possible that you're using another plugin that changes the URL of this group settings panel? Perhaps BuddyBoss does this? If so, then it should be that plugin's responsibility to filter the BPGES URL to reflect the changed location. I can probably provide a template for how this filter should look, but first I'd like confirmation that you are in fact seeing the URL in question - |
I not use BuddyBoss. I have Buddypress and BBPress installed. What is the "normal" URL to the authors group notification config look like? I thought this is the normal link to the group config groups/[groupslug]/[userslug]/edit-details/ |
The URL for users to edit their notification preferences for a single group is: The only 'edit-details' URL I'm aware of is |
I have the problem that users get a link in the email to configure the setting for the notifications of the group and it is not working. They get a 404 page.
The link they get is like:
https://test.de/?action=bpnoaccess&auth=1&redirect_to=https%3A%2F%2Ftest.de%2Fgroups%2Fgroupname%2Fnotifications%2F
I think the redirect_to link is not correct because it misses the user slug between the groupname and notifications. This is where i find the notification settings page normaly: https://test.de/groups/groupname/USERSLUG/notifications/
I can not find how to fix that. Is it a problem in the plugin or in my configuration? Has anybody a solution for me?
Should normally the buddypress redirect the logged in user to his own notification setting page?
The text was updated successfully, but these errors were encountered: