Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 5.1.0
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 5 results 

      Description

      Through two methods, allow users to change default login page.

      Method 1: In My Account, list all available communites and allow the user to select which page is default

      Method 2: On each page, add a link to allow "Make this my home page". This would be a theme item, so all we really need is a method to call in our theme that will allow us to use that functionality.

      When done, please post how to call the "Make this my default page" link as a comment in this issue.

        Issue Links

          Activity

          Hide
          Iain Hutchinson added a comment -

          I would also like to see the option on this where the default community can be specified and locked for a user. This would for example allow a community to be defined for a group of people, providing information that you want them to always see on login, but (assuming they have the privileges) they can also have their own private community to display portlets that may not appear in the main community, but which they have access to.

          Show
          Iain Hutchinson added a comment - I would also like to see the option on this where the default community can be specified and locked for a user. This would for example allow a community to be defined for a group of people, providing information that you want them to always see on login, but (assuming they have the privileges) they can also have their own private community to display portlets that may not appear in the main community, but which they have access to.
          Hide
          Neil Griffin added a comment -

          Just wanted to encourage you all to keep this one on the 4.2.1 radar screen if possible. I just ran into a new requirement for this exact feature.

          Best,

          Neil

          Show
          Neil Griffin added a comment - Just wanted to encourage you all to keep this one on the 4.2.1 radar screen if possible. I just ran into a new requirement for this exact feature. Best, Neil
          Hide
          Neil Griffin added a comment -

          Just wanted to clarify my requirement a little. I need to have communities like:

          • Member
          • Silver Member
          • Gold Member
          • Platinum Member

          And if a user makes a $donation$, I want to be able (as the administrator) to easily set the default community for that user to the appropriate membership level. So if Method#1 listed above will give the administrator that ability, then that would satisfy my requirement.

          Thanks,

          Neil

          Show
          Neil Griffin added a comment - Just wanted to clarify my requirement a little. I need to have communities like: Member Silver Member Gold Member Platinum Member And if a user makes a $donation$, I want to be able (as the administrator) to easily set the default community for that user to the appropriate membership level. So if Method#1 listed above will give the administrator that ability, then that would satisfy my requirement. Thanks, Neil
          Hide
          Eric Kuzmack added a comment -

          I'd like to add my thoughts on this - what we'd like is basically a link between a virtual host, organization, location, guest; and private communities for that host, along with defaults for users created "via" that virtual host. For example:

          www.a.com --> guest community "A-GUEST" --> create new user --> creates user in org "A" with defaults to private community "A-PRIV"
          www.b.com --> guest community "B-GUEST" --> create new user --> creates user in org "B" with defaults to private community "B-PRIV"

          when a user for either site logs in, then are automatically brought to their specific private community.

          I would think a fairly simple interface could be used to map the relationship between the virtual host and the default communities, as well as the ability to create a new virtual environment (host, org, location, guest, and private) programatically based on a template environment, or perhaps an "inheritance" model where a base host, etc... is setup and then others can just inherit from that base, using a new URL as the starting point.

          Along these lines, we'd also need the ability for the same person to create accounts across multiple web sites as if they were completely independent - i.e. jsmith@hotmail.com could register at www.a.com and www.b.com without ever knowing they were running on the same instance of liferay.

          By enabling this model, it allows for a scalable hosting model.

          Show
          Eric Kuzmack added a comment - I'd like to add my thoughts on this - what we'd like is basically a link between a virtual host, organization, location, guest; and private communities for that host, along with defaults for users created "via" that virtual host. For example: www.a.com --> guest community "A-GUEST" --> create new user --> creates user in org "A" with defaults to private community "A-PRIV" www.b.com --> guest community "B-GUEST" --> create new user --> creates user in org "B" with defaults to private community "B-PRIV" when a user for either site logs in, then are automatically brought to their specific private community. I would think a fairly simple interface could be used to map the relationship between the virtual host and the default communities, as well as the ability to create a new virtual environment (host, org, location, guest, and private) programatically based on a template environment, or perhaps an "inheritance" model where a base host, etc... is setup and then others can just inherit from that base, using a new URL as the starting point. Along these lines, we'd also need the ability for the same person to create accounts across multiple web sites as if they were completely independent - i.e. jsmith@hotmail.com could register at www.a.com and www.b.com without ever knowing they were running on the same instance of liferay. By enabling this model, it allows for a scalable hosting model.
          Hide
          Iain Hutchinson added a comment -

          Hi Brian,

          Any chance this can be kept for 4.4.1 as I am waiting to complete some work based on this feature. Would really appreciate it if it does not slip again.

          Thanks,

          Iain

          Show
          Iain Hutchinson added a comment - Hi Brian, Any chance this can be kept for 4.4.1 as I am waiting to complete some work based on this feature. Would really appreciate it if it does not slip again. Thanks, Iain

            People

            • Assignee:
              Michael Young
              Reporter:
              Brett Swaim
            • Votes:
              23 Vote for this issue
              Watchers:
              22 Start watching this issue

              Dates

              • Created:
                Updated:

                Development

                  Structure Helper Panel