Jacob Rief

together with Django-CMS-3.5 it already supports Django-2.0. I unfortunately had no time to build a new release of djangocms-cascade and djangocms-bootstrap3, which are required for it.

According to django-CMS's-3.5 `setup.py`, Django-2.0 is not supported yet. Therefore django-SHOP still sticks with it. I'm sorry, this is not my fault.

I'm currently finishing release 1.0. You can have a look at this branch: https://github.com/awesto/django-shop/tree/drafts/py.test This is a major improvement over existing versions, with support for Bootstrap-4, py.test, django-CMS-3.5, and many...

Without having looked at it in detail, I would have chosen a similar solution: ``CustomFilterSet. get_render_context(...)`` would return a dict with two different filter_sets, say ``return dict(filter_set_tyre=filter_set_tyre, filter_set_disk=filter_set_disk)``. Then the...

you mean the exception template for "Internal Sever Error" in debug mode? @rfleschenberg any idea how to fix this?

Then you have a mismatch between the entries in table `django_migrations` and your current state of table schema. Try to migrate to the next step, ie. 0008 using `./manage.py migrate...

Which version of django-SHOP and django-post_office are you using? Check your settings, you should have ``` POST_OFFICE = { 'TEMPLATE_ENGINE': 'post_office', } ```

It would be helpful to know, which template file is referring the templatetag `html_email `.

The template `garantum/garantum/templates/garantum/email/base.html`seem to be from your own project. So you must fix it there.

The `requirements.txt` in example does indeed depend on djangoshop-stripe. Django-SHOP itself doesn't depend on Stripe. The framework shall (for good reasons) not depend on any PSP.