-
Notifications
You must be signed in to change notification settings - Fork 79
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
No module named app_resolver #7
Comments
|
Environment: Request Method: GET Django Version: 1.4.2 Traceback:
Exception Type: ImportError at /djangojs/urls |
OK, it seems to be specific to django-cms way of resolving apps: https://github.com/divio/django-cms/blob/master/cms/appresolver.py. I'll try to fix this issue as soon as possible (I never used django-cms, I'll need to investigate). |
Can you provide a sample project to reproduce the bug ? |
django-cms is using this appresolver to resolve extra apps that doesn't exist in INSTALLED_APPS, so if there dynamic apps connected to pages, appresolver is puting urls of apps to root cms urls. |
here's your sample: https://github.com/szelga/js-cms-test (sorry if it's too late). |
OK, i managed to fix it: szelga@10d5082 |
It's never too late !!! I will look at your sample project et your fix ASAP. 2 possibilities:
|
I can't reproduce the bug with the sample project. |
have you created (and published) any django-cms pages? |
Yep, I created pages with and without application, nested pages... no errors. I excuded admin URLs for better readabiity: JS_URLS_NAMESPACES_EXCLUDE = (
'admin',
) and got this: {
"django_js_urls": "/djangojs/urls",
"myapp-view2": "/test/",
"js_catalog": "/djangojs/translation",
"django_js_context": "/djangojs/context",
"pages-root": "/",
"django_js_init": "/djangojs/init.js",
"pages-details-by-slug": "/<slug>/"
} Are you expecting the pages to appears in ? |
|
OK, I'll test it today. |
OK, I reproduce the bug but I need to restart the server. I just took the try...except part of your fix, not the refactoring. |
And thanks for the fix ! |
after using 0.3.2 version I get this error No module named app_resolver?
The text was updated successfully, but these errors were encountered: