pyconca / 2013-web

a Django project for conference websites
https://2013.pycon.ca/
BSD 3-Clause "New" or "Revised" License
6 stars 9 forks source link

Remove the Symposion CMS behaviours entirely #7

Closed eloraburns closed 11 years ago

eloraburns commented 11 years ago

Try to avoid causing merge conflicts, so disabling may be a better thing than outright deletion.

Unless we can think of some reason to keep the CMS (but I don't think so, unless it can be configured to work like a wiki, then maybe…)

kayzhu commented 11 years ago

I would second this. I only remember using it on the PyCon NA site to register for the TiP BoF, but I assume it may not be necessary for us to have registration for any kind of BoF since we are a lot smaller.

Update: I realized that was not the case, the sponsorship pages and etc. are all created with the CMS. So, the discussion should be that whether we want to create pages such as "sponsors/prospectus/" through our own templates, or through that CMS. I probably missed something obvious, but the major reason we cannot use the CMS is because of i18n? If not, I am fine with either writing templates or use the CMS.

eloraburns commented 11 years ago

That's correct: the CMS does not support i18n, and making it support i18n still leaves us with page content in the database, which makes it hard to track changes (so that we can propagate those changes to translations).

kayzhu commented 11 years ago

Disabled CMS in 33e54a774a2380a6351f97b6b64f321e013e67f4.

Notes:

  1. url(r"^(?P<path>%s)$" % PAGE_RE, "page", name="cms_page"), is copied to urls.py because we need cms_page tag to work in symposion/templates/sponsorship/list.html.
  2. Without removing the CMS url from urls.py, only delete cms from INSTALLED_APPS and then remake the db will yield database error when visiting /sponsor/prospectus/ because the CMS route and the view still work. So I think we will have to remove the cms url as well but only keep 1).

Otherwise, we can close this issue :)

kayzhu commented 11 years ago

I realized that keeping url(r"^(?P<path>%s)$" % PAGE_RE, "page", name="cms_page"), is not a good approach, so instead I modified symposion/templates/sponsorship/list.html so that cms_page is not referenced at all.

This sacrifices a tiny little bit of upstream pushbility, but for now it seems like a good compromise.

eloraburns commented 11 years ago

:+1: eaf228edf581128353a37ac34de011231486b8e6