Permanent Link to Objects in Course forwards to Join Page

1 Initial Problem

• A permanent link is sent to a user -  it is a link to a wiki within a course. The user is not a member of that course. 
• If the user clicks on the link, after logging the user is dumped on the dashboard without an error message.
• The user therefore does not know why the desired object was not opened.

2 Conceptual Summary

When such a link is opened and the course is online and the user has "view" permission, the user should be dumped on the join page or the info page, depending on the registration settings of the course.

The Join Page opens, when the Registration Procedure is set to:

• Join Directly
• Join with Course Password
• Request Membership

Then the user can join the course. (And if join directly is activated, the desired object/page opens, after joining the course).


The info page opens, when the Registration Procedure is set to

• No Self-enrolment

Then the user knows: "Okay, I have to contact the course admin to get him to add me."

If a user opens such a link and the course is offline or blocked for him because of RBAC, the user should receive a suitable error message.

3 User Interface Modifications

3.1 List of Affected Views

Perhaps new error messages in dashboard for offline or rbac blocked courses?

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

No new user interfaces

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Privacy Information

No additional Personal Data are stored.

6 Security Implications

No security implications.

7 Contact

• Author of the Request: Strassner, Denis [dstrassner], Tödt, Alexandra [atoedt]
  
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

9 Discussion

10 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.