Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

symposion.boxes and symposion.cms #19

Open
barrachri opened this issue Nov 4, 2015 · 8 comments
Open

symposion.boxes and symposion.cms #19

barrachri opened this issue Nov 4, 2015 · 8 comments

Comments

@barrachri
Copy link

From the settings I see that "symposion.boxes" and "symposion.cms" are required.

But I get a ImportError: No module named boxes and cms.

@russel
Copy link

russel commented Nov 30, 2015

I just commented out the entries in settings.py and urls.py and at least I could get "python3 manage.py help" to work. I think that I am using a newer version of Symposion than this template project works with. I suspect you are in the same situation. I am hoping someone has a template project that work with the latest version of Symposion.

@paltman
Copy link
Member

paltman commented Nov 30, 2015

Symposion, the app, is undergoing quite a bit of refactoring, naming pulling out the reviews and submissions as it's own app. Once work starts stabalizing there we'll create a new starter project most likely in pinax-starter-projects.

@russel
Copy link

russel commented Dec 1, 2015

Is there a timescale for something "alpha". I was wondering about trying Symposion for ACCU 2016 programme management (this week!) to see if we can then use it for ACCU 2017 full cycle. I'd rather not use and set up a system that then needs a massive revamp if I can avoid it. However if I have to go back to Django 1.7 etc. then I have to do that.

@russel
Copy link

russel commented Dec 4, 2015

@paltman I just tried to install this exactly as per the instructions, but sadly it installs symposion==1.0b2.dev3
I guess the installation line in the requirements.txt needs amending so that this template project works pending the "big change".

@mynameisfashanu
Copy link

I just wanted to find out if this issue has been resolved, is there a symposion starter_project for django 1.9 ? thank you.

@sksdutra
Copy link

sksdutra commented May 18, 2017

I tryed to run the installer with Python 2.7 and Django 1.7.1 and I'm getting this annoying error: ImportError: No module named boxes

Please, how can I correct this?

@codersquid
Copy link
Contributor

I recently experimented with getting an old symposion conference site on symposion master, and it turns out that both the boxes and cms apps are gone. I don't have a MR for this, but as a starter

  • add a dependency to pinax-boxes
  • replace symposion.boxes with pinax.boxes in your settings file.

You'll need to update the templates to replace the old templatetags. There's some other cleanup that needs to be done, but I haven't done any more work.

I can't remember what else I ran in to. Off the top of my head,

  • symposion.cms is gone; use pinax-pages. there will be template changes you'll need for this.
  • Signup forms and views were removed from Symposion. You'll want to pull in the old SignupForm, SignupView, and LoginView, or write your own.
    • you'll need to update your account/signup and account/login urls to use your own view instead of symposion.views.LoginView etc.
  • markitup is no longer used.

If there isn't some docs on helping people upgrade from an older version of symposion, someone who is going through this process should take good notes to help create the docs. I went ahead and suggested for the old conference to just completely start over.

@codersquid
Copy link
Contributor

codersquid commented Jul 26, 2017

Also, there is a new github repo called PinaxCon that you can use as a reference, but it is a little behind symposion master so you may run into things that need to be tweaked.

Due to that, I think this repo and that one should pin symposion to a commit rather than master. Whenever symposion changes, then the next step would be to stand up PinaxCon to see what needs changing, if anything then update the requirements. Likewise this one. I bet some of that could be automated in a travis job or something?

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

No branches or pull requests

7 participants