airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (Jira)" <j...@apache.org>
Subject [jira] [Updated] (AIRAVATA-3290) Ansible: automatically set wagtail site record
Date Wed, 19 Feb 2020 17:14:00 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Christie updated AIRAVATA-3290:
--------------------------------------
    Description: 
Automatically set a default wagtail site record with the correct domain name and site name.

Wagtail preview doesn't work until the site record has the correct domain name of the site.

Another option is to update the load_cms_data command to do this. Ansible only creates the
database and the wagtailcore_site table isn't there until migrations run, and the record actually
gets created by load_cms_data.

h5. TODO
- [x] Test what happens when there is already a default site, does it need to be deleted first?
-- yes any existing default site needs to be deleted first
- [x] Test when there is already a site record but not the default one
-- non-default record doesn't seem to matter
- [ ] print when site record already exists
- [x] call automatically when loading a wagtail theme (load_cms_data)
- [ ] when there is no root page, won't be able to create the default site record, but also
shouldn't allow deleting the old one and leaving it deleted (need to run in transaction)

Resources:
- https://www.codista.com/en/blog/create-wagtail-pages-programmatically/

  was:
Automatically set a default wagtail site record with the correct domain name and site name.

Wagtail preview doesn't work until the site record has the correct domain name of the site.

Another option is to update the load_cms_data command to do this. Ansible only creates the
database and the wagtailcore_site table isn't there until migrations run, and the record actually
gets created by load_cms_data.

h5. TODO
- [x] Test what happens when there is already a default site, does it need to be deleted first?
-- yes any existing default site needs to be deleted first
- [x] Test when there is already a site record but not the default one
-- non-default record doesn't seem to matter
- [ ] print when site record already exists
- [ ] call automatically when loading a wagtail theme (load_cms_data)

Resources:
- https://www.codista.com/en/blog/create-wagtail-pages-programmatically/


> Ansible: automatically set wagtail site record
> ----------------------------------------------
>
>                 Key: AIRAVATA-3290
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3290
>             Project: Airavata
>          Issue Type: Bug
>          Components: Django Portal
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> Automatically set a default wagtail site record with the correct domain name and site
name.
> Wagtail preview doesn't work until the site record has the correct domain name of the
site.
> Another option is to update the load_cms_data command to do this. Ansible only creates
the database and the wagtailcore_site table isn't there until migrations run, and the record
actually gets created by load_cms_data.
> h5. TODO
> - [x] Test what happens when there is already a default site, does it need to be deleted
first?
> -- yes any existing default site needs to be deleted first
> - [x] Test when there is already a site record but not the default one
> -- non-default record doesn't seem to matter
> - [ ] print when site record already exists
> - [x] call automatically when loading a wagtail theme (load_cms_data)
> - [ ] when there is no root page, won't be able to create the default site record, but
also shouldn't allow deleting the old one and leaving it deleted (need to run in transaction)
> Resources:
> - https://www.codista.com/en/blog/create-wagtail-pages-programmatically/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message