Skip to content
This repository has been archived by the owner on Mar 28, 2018. It is now read-only.

Port 2015 tools to 2016 website #89

Closed
jefftriplett opened this issue Apr 5, 2016 · 6 comments
Closed

Port 2015 tools to 2016 website #89

jefftriplett opened this issue Apr 5, 2016 · 6 comments

Comments

@jefftriplett
Copy link
Member

jefftriplett commented Apr 5, 2016

We need to port our 2015 tools into the 2016 code base. This allows Guidebook and some of our other tools to work properly.

These are the requirements:

  1. Update Views: 2015 views into the 2016 views.
  2. Update Urls: We need to port all of the djangocon.views.* views from the 2015 website into the 2016 website
  3. Add missing requirements to our project's requirements.txt. (possibly: unidecode, tablib, unicodecsv, ...)
  4. Adjust Symposion imports which might have changed. Example: Biblion is now Pinax-Blog
  5. Update View Security: Update @login_required views to only allow superuser access. Example 1 and Example 2.
@sul4bh
Copy link
Contributor

sul4bh commented Apr 6, 2016

I can work on this. Here is my plan of action:

  1. Add missing requirements
  2. Adjust imports
  3. Update Views
  4. Update view Security
  5. Update Urls

What do you guys think about having a https://2016.djangocon.us/data page(accessible to superusers only) that has a list of all downloadable CSVs? It will save us from having to remember the CSV urls.

@jefftriplett
Copy link
Member Author

@sul4bh great idea, that'd be perfect!

@sul4bh
Copy link
Contributor

sul4bh commented Apr 7, 2016

I ran into an issue regarding pinax-symposium and have submitted an issue upstream (pinax/symposion#131). I am hoping to hear from them soon.

Do we need schedule_json() and guidebook_news_feed() for 2016?

@jefftriplett
Copy link
Member Author

@sul4bh Thanks for the update. The Sponsor.objects.active() call can be changed to Sponsor.objects.filter(active=True) if that gets you past a blocker. Ultimately fixing Symposion upstream though helps everyone so thank you for opening that issue.

Yes, we do need schedule_json and guidebook_news_feed for Guidebook and the Program Guide integration. Hopefully, updating the Biblion references to use Pinax-Blog is just switching imports.

Let me know if you have questions and thanks again!

@sul4bh
Copy link
Contributor

sul4bh commented Apr 8, 2016

Thanks for the tips Jeff. Just created pr #93

@jefftriplett
Copy link
Member Author

Thanks again!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants