-
Notifications
You must be signed in to change notification settings - Fork 1
How to Install DjangoCMS Blog i.e. News
-
(Optional) Check whether blog is already installed.
- Open CMS Admin UI. Is section "DJANGO CMS BLOG" present?
- If so, a blog is already installed and active.
- Proceed to next step to check whether blog is configured.
﹡ In same column where Home page has 🏠. icon.
-
(Optional) Check whether blog is already configured.
- Open Blog/News page while logged in. Does admin toolbar have "Blog" link?
- If so, open CMS Pages in the Admin UI. Does Blog/News page have a 🧩.﹡
- If so, a blog is already configured.
- If not, proceed to next step to configure the blog.
﹡ In same column where Home page has 🏠. icon.
-
Add "NEWS / BLOG" settings to your
taccsite_cms/settings_local.py
. -
Add
taggit_autosuggest
URLs to yourtaccsite_cms/url_custom.py
. -
Restart server (if not already restarted by having edited
settings_local.py
).² -
Run migrations for the
djangocms_blog
app.¹docker exec -it core_cms sh -c "python manage.py migrate"
Operations to perform: Apply all migrations: djangocms_blog Running migrations: Applying djangocms_blog.0001_initial... OK Applying djangocms_blog.0002_post_sites... OK Applying djangocms_blog.0003_auto_20141201_2252... ...
-
Confirm
djangocms_blog
app is now installed.- Open CMS Administation UI. Section "DJANGO CMS BLOG" exists?
Also, if any CMS page is opened, there is a
djangocms_blog...
error. -
If
settings_local.py
hasBLOG_AUTO_SETUP = True
, then skip to step 12. -
Add Blog config i.e. "apphook" config.
- Open CMS Administation UI.
- In section "DJANGO CMS BLOG", add a Blog config.
- Talk a CMS admin aware of the client needs³ to set the following values:
- INSTANCE NAME: Uncertain. Set to the same value as "APPLICATION TITLE". (default: "Blog", suggested: ? )
- APPLICATION TITLE: Title of the
BlogConfig
instance created by Auto setup. (default: "Blog", suggested: "News") - OBJECT NAME: The CMS name for a Blog item. (default: "Article")
- (Optional) Ask a CMS admin aware of the client needs³ for remaining values.
-
Add Blog instance i.e. "apphook" to a Page.
- Open CMS Administation UI.
- In section "DJANGO CMS", add a Page.
- Talk a CMS admin aware of the client needs³ to set the following values:
- TITLE
- SLUG
- Save the page.
- Edit the Page's Advanced Settings.
- Set the following values:
- ATTACHED MENU: "Blog menu"
- APPLICATION: "Blog"
- APPLICATION CONFIGURATIONS: (appears only after choosing APPLICATION) (Check whether auto-set value is accurate.)
- Publish page.*
- Restart server.*
﹡ Page must be published before server restart. Otherwise, new page will not render blog content.
-
(Optional) Confirm Blog is configured i.e. "apphooks" are in place.
python3 manage.py cms list apphooks
BlogApp[instance: ...] (draft/published)
-
Confirm
djangocms_blog
app is now installed and active.- Open CMS Pages admin UI. Blog/News page has 🧩. icon?﹡
- Open Blog/News page while logged in. Admin toolbar has "Blog" link?
- Open CMS Administration UI. Section "DJANGO CMS BLOG" exists?
﹡ In same column where Home page has 🏠. icon.
-
Confirm new Blog instance is working.
- Add and publish an article. Article shows up on new page?
- Open new page while logged in. Page shows "No articles found"?
ℹ️ If article is not published, it will not show.
⁰ After FP-1487, the package djangocms_blog
might not be installed by default.
¹ Migrate after adding djangocms_blog
to INSTALLED_APPS
(which should happen as a result of adding "NEWS / BLOG" settings) or else migrations can not occur (because djangocms_blog
will not exist in the project to provide the migrations).
² See How to Restart the CMS Server.
³ A CMS admin on the CMD staff usually serves this role. Or maybe you serve this role.
TACC ACI WMA Core-CMS Project Documentation