I know we've discussed this before internally.
The consensus was that it would be good to have but I'm not sure User
settings is the place for it.. although it might be the only place unless
we create yet another menu entry.
On Thursday, February 2, 2017 at 5:24:03 AM UTC-5, czpython wrote
The inconsistency is unfortunate, there's been some that were released
to PyPI and others that have not :(.
Since 3.3.1, I've started moving towards not pushing release candidates to
PyPI as a standard.
That said, I'm happy to shift towards releasing to PyPI if it gets more
traction in the
Hello all,
The django CMS core team just released the first release candidate for
version 3.4.
Download: https://github.com/divio/django-cms/archive/3.4.0rc1.zip
Documentation: http://docs.django-cms.org/en/latest/index.html
Release notes: http://docs.django-cms.org/en/latest/upgrade/3.4.html
Hello all,
The django CMS core team just released 3.4.1 and 3.3.3 maintenance versions.
Please report any issues you find to our issue tracker at
https://github.com/divio/django-cms/issues.
More information can be found on our blog
Hello Carlos,
I'm not sure I understand your question.
What are you trying to do?
On Monday, October 24, 2016 at 6:47:07 AM UTC-4, Carlos García wrote:
>
> Hi,
>
> How can I integrate a python function in a django-cms project?
>
--
Message URL:
Hello Jacob,
To expand a bit on my answer.
My definition of a non-documentation bug is something that impairs the
functioning of a component in the software.
The reported issue does not fit this criteria as the software itself
continues to function correctly regardless of the name of the
Hello Yanic,
I believe the issue might actually be in the way the cms tries to display
the apphook name when is not found.
Can you run the following in django shell (and paste the output):
from cms.models import Page
print(Page.objects.distinct().values_list('application_urls', flat=True))
o is fetch the placeholders
from the database instead of from the template, then just render the
structure markup for the ones that are in db but not present in template.
This would be a separate feature
from https://github.com/divio/django-cms/issues/4512.
On Monday, August 7, 2017 at 2:39:45 PM UTC-4
>
> django-cms 3.4.4
> Plugins will often be lost or left behind when a page's template is
> changed, where the placeholder names are different or there are different
> placeholders. There's no way to see plugins that are 'in the trash can' as
> it where.
> The work around currently is to
Hello,
Do you get an error?
And does this happen on django CMS 3.4.4 only?
On Monday, June 19, 2017 at 3:05:42 PM UTC-4, kamil selwa wrote:
>
> Great! Thank You
> One thing
> Page Permissions don't show up under default Django-1.10
> Rolling back to Django-1.9 fixed this.
> all the best
> Kamil
>
Moved from https://github.com/divio/django-cms/issues/6102
There is a permission to allow or disallow staff users the access to advanced
> settings.
> We don't want regular staff to be able to add/edit app hooks. We do
> however want them to be able to edit the redirect to and manual URL
>
11 matches
Mail list logo
