publishedmanager method ensure that only posts with start date in the past are shown. Be aware that as admin in edit mode, you will see all the future published post (by design) to ensure you can reach them. But as anonymous user you should only see "past" published posts, if this is not the case, it's definitely a bug
post_list.htmltemplate (https://github.com/nephila/djangocms-blog/blob/develop/djangocms_blog/templates/djangocms_blog/post_list.html) to fit your design
On my laptop I'm building a Django CMS site. It has a few pages, including one with an instance of djangocms-blog.
When I try to deploy it to Heroku, after I do the schema migrations I can see there is no data related to the djangocms-blog.
I must be missing something as I'm just starting with django CMS.
How do I migrate the data of my CMS pages and the rest, to my production environment in Heroku?
I tried looking into the docs but I couldnt find anything. Does this mean I have to use DIVIO?
Thanks in advance for your help
Hello, I'm looking at putting together a CMS project with multi-site support. I've setup lots of CMS projects, but never with multiple sites from the same system.
What's the status of djangocms-multisite?
SITE_ID is the kind of approach we're looking for to make things as dynamic as possible. The ultimate goal being to add a
Client object to the database & their site start working without having to change the django project.
Does anybody know of a solution to authentication between domains?
We're creating a CMS platform (single database), using djangocms-multisite which will create a Site object for a client when they're added to our
Client table. I'll use the CMS api to create some default content, but then when navigating to those new pages on that site, I need a solution to be authenticated.
If it's a subdomain it's just done with
SESSION_COOKIE_DOMAIN but in all likelihood we'll be looking at top level domains pointing at our system & creating site objects for them.