Support for Nephila opensource applications. Come and join the discussion! (PS: We are hiring)
Hello, I wanted to know if it is possible to filter the posts to show on the blog only those with a past publish date. Now if I create a post inserting a future date on the published_date field, it shows in the blog posts list, and in the category post list. Thank you so much
@agajankush blog post has a single placeholder where you can add any plugin you need. if you need multiple placeholders you can have a look at static placeholders (http://docs.django-cms.org/en/latest/introduction/02-templates_placeholders.html#static-placeholders), but adding different static placeholder for each post is a bit hackish
@alessandro87_gitlab this should already be the case. the
published manager 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
@agajankush in that case you can use django cms' static placeholders, which are made exactly for your use case
you only need to customize the
you only need to customize the
post_list.html template (https://github.com/nephila/djangocms-blog/blob/develop/djangocms_blog/templates/djangocms_blog/post_list.html) to fit your design
Look at that Thank you @yakky
you're welcome :)
Then just add the placeholder on the page wherever you want,
Getting this error when I try to upload an image in djangocms_text_ckeditor
Hi @Amrizhan, since every website is different, django CMS (or even django) applications will only give you basic templates to work with. It is your role to make those templates work with your particular website. If don't have any particularly good HTML/CSS skills, this task can prove to be difficult. I suggest you to start from an already existing design. You can find plenty of HTML templates on the web. My advice is to start with Bootstrap 4 templates as it's easier to start with. I like to use Cololib's templates as they are free to experiment with and only cost USD 21.- once you are ready to remove the copyrights inside the footer. If you don't want to adapt those templates for your website, you can checkout my implementation of Colorlib's template on my website. Hope this helps you. Have a nice experience using django CMS !
Hi!
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 @pablojr1971, your production environment (your Heroku server) is something completely different from your development environment (your laptop). Generally, you should use more robust databases in production such as PostgreSQL for exemple, while in development you might want to use a simple mySQL database inside a file. In other words, what is in your development website is not what's on your real production website. You'll have to recreate what you have already made in development. There are various tools for exporting your Django-CMS plugins in JSON format to export it easily from one Django-CMS server to another. You should checkout djangocms-transfer if you have already a lot of data inside your development server. Hope this helps. Have fun with Django CMS ! EDIT: You can also create your production database from the development's one, but since you're new to Django(-CMS), I wouldn't recommend that you do so as it can be tricky.
Thank you @wasertech_gitlab !
In case somebody is interested, this is what worked for me
https://stackoverflow.com/a/62570272/2510389
In case somebody is interested, this is what worked for me
https://stackoverflow.com/a/62570272/2510389
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?
The dynamic 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.
we have not used it for massive deployments with many sites to it (IIRC our max is 3), but we have not had any concurrency issues, so it should be fine with larger setups
Thanks @yakky
We're not looking at a particularly large setup yet (unless sales go very well!!). What we want is an easy to maintain system which offers flexibility and lower server costs than what we've been doing lately by setting up very specific applications each with their own stack.
We're not looking at a particularly large setup yet (unless sales go very well!!). What we want is an easy to maintain system which offers flexibility and lower server costs than what we've been doing lately by setting up very specific applications each with their own stack.
Do you think it'll work on a 2.2 site? The repo says support for 1.11, but I've not looked at how it's setup yet to see if 2.2 is a no-go.
there is a PR to make it work on django 2.2 (nephila/djangocms-multisite#27), but it needs some polishing before merge
I might have some time to give this repo some love early next week with the kid on vacation :)
I should be able to release a version tested on Django 2.2 / 3
In a few days
and it would be awesome to have more feedback on it
A guy I work with was keen to start trying out CMS & pushing code so I tried to install that PR, found some issues & thought I'd make some fixes, drop some old python & I ended up with a new PR worthy fork; nephila/djangocms-multisite#29
🎉
Thanks @yakky
I can see that on github, but not on pypi; https://pypi.org/project/djangocms-multisite/
I can see that on github, but not on pypi; https://pypi.org/project/djangocms-multisite/