Re: [mezzanine-users] Extending Displayable Model, Views

2017-07-07 Thread marcusguttenplan
It's an ImportError (ImportError at /news Could not import 'news'. The path must be fully qualified.) and trying to follow the traceback have narrowed it down to either how I am importing the model in my views (if that's even necessary) or to how I am calling the defined `news` view in the app's

RE: [mezzanine-users] Extending Displayable Model, Views

2017-07-07 Thread Eduardo Rivas
Could you share the error message you’re getting? -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more optio

Re: [mezzanine-users] Extending Displayable Model, Views

2017-07-06 Thread marcusguttenplan
Getting closer! Imported into root with url(r'^news/',include('app.urls')), Throwing a new error about the path not being fully qualified, but progress. On Thursday, July 6, 2017 at 9:38:22 PM UTC-7, marcusgu...@gmail.com wrote: > > I originally put that url pattern into the root conf, but it w

Re: [mezzanine-users] Extending Displayable Model, Views

2017-07-06 Thread marcusguttenplan
I originally put that url pattern into the root conf, but it wasn't working there either. Embarrassingly, I'm not sure how to import my app's conf or define a new pattern that would point to it. This is what the root urls.py looks like: from __future__ import unicode_literals from django.conf.u

Re: [mezzanine-users] Extending Displayable Model, Views

2017-07-06 Thread Eduardo Rivas
I see you created a urlconf for your app, but have you added it to your root urls.py? If so, is if above or below Mezzanine's catch-all pattern? On Jul 6, 2017 9:12 PM, wrote: > Hi, thanks for such a great resource! I have googled around for a few days > and have made some headway this problem,