You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2019/07/23 09:52:00 UTC
[jira] [Closed] (AIRAVATA-3171) Django portal has two different
home pages. There should be only one home page
[ https://issues.apache.org/jira/browse/AIRAVATA-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eroma closed AIRAVATA-3171.
---------------------------
Resolution: Fixed
This is tested in https://django.staging.seagrid.org/
Both places are now linked with https://django.staging.seagrid.org/. This link manageed by the Wagtail CMS.
> Django portal has two different home pages. There should be only one home page
> ------------------------------------------------------------------------------
>
> Key: AIRAVATA-3171
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3171
> Project: Airavata
> Issue Type: Sub-task
> Components: Django Portal
> Affects Versions: 0.18
> Environment: https://django.staging.seagrid.org/
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Major
>
> 1. In Django portal if user clicks on the gateway logo on top left user will be in the gateway home page, which has placeholders for Settings and other main gateway spaces.
> 2. If user clicks on the gateway name, then the user is taken to the gateway theme home page managed by the CMS.
> 3. This is confusing, both logo and the name links should navigate user to the gateway home page with other information child pages. - https://django.staging.seagrid.org/
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)