We have moved to Github. Please open tickets there.

Opened 2 years ago

Closed 2 years ago

#3036 closed Defect (duplicate)

Remember referring url

Reported by: haydo Owned by:
Priority: normal Milestone: Elgg 1.8.0
Component: Core Version: 1.8 Beta
Severity: annoying Keywords:
Cc: brett@… Difficulty: easy

Description

Done a search for this but couldn't find an existing ticket, however apologize if this has already been covered.

It would be great if Elgg could remember referring urls.

For example, a user gets a notification via email about a forum topic. They click on the link however aren't logged in so can't view topic and get sent to login. They login but don't get redirected to the topic.

That way the user doesn't have to go find the group then topic themselves or return to their email again. Would make it a lot simpler i think and wouldn't take too much to do either.

Change History (4)

comment:1 Changed 2 years ago by cash

  • Difficulty set to easy
  • Milestone changed from Needs Review to Elgg 1.8

Looks like somewhere in 1.8 development this was broken...

comment:2 Changed 2 years ago by cash

  • Resolution set to fixed
  • Status changed from new to closed

(In [svn:8567]) Fixes #3036 moved setting of forward url to before login in case session variables are being lost

comment:3 Changed 2 years ago by haydo

  • Resolution fixed deleted
  • Status changed from closed to reopened

Adding to this ticket.

If your not logged in and try to view non public content eg 'friends only', nothing will obviously be returned in get_entity(), however no session is created to keep the referrer url in this particular scenario. I think a referrer url session should be created and made use of if they do login at that very point.

This is the case in 1.7 anyway, this maybe not be the case in 1.8 which i need to check again this week.

What do you think Cash?

comment:4 Changed 2 years ago by cash

  • Resolution set to duplicate
  • Status changed from reopened to closed

I'm closing this as a duplicate of #2814.

The redirect works for pages like settings (or anything that uses a gatekeeper function). It does not work when a page cannot access an entity.

Note: See TracTickets for help on using tickets.