There is an effort right now to implement an API on django CMS that would permit "exotic" frontends and/or mobile device apps, etc., to access specific objects through a RESTful api. I'm pretty sure, when complete, this would address your goal here. If you'd like to help out with the effort (would be great!), join us on our Slack channel: *#django-cms-api.*
On Thursday, June 16, 2016 at 3:20:04 AM UTC-4, [email protected] wrote: > > Hey all, > > I'm trying to figure out how to set up django-cms so that in addition to > having urls for "domain:port/{lang}/{slugname}"resolve, rendering off of > the principal page template, I can also access > "domain:port/{lang}/partials/{slugname}", rendering using a different > template. As use case, I'm trying to get content authored using django-cms, > by slug, to generate only the HTML that the users created for consumption > by external sources. > > I had a look at the urls.py, which relies on cms.urls for its url > matching, and was wondering whether there was an easy way to tell the cms > section that I'd like a secondary route for slug content, to be rendered > using a specific template from the templates dir. > > Is this possible? And if not "out of the box", is it possible to > manipulate django-cms/cms/urls.py in some way to effect the additional URL > matching, and then set up template rendering using the secondary template > file in another part of the cms codebase? > > thanks, > > - Mike "Pomax" Kamermans > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to [email protected] --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/681a1754-fa7f-4301-b29e-b421a21e14b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
