Strange Toolbar display after upgrading CMS

28 views
Skip to first unread message

Philippe O. Wagner

unread,
Nov 25, 2016, 4:57:53 AM11/25/16
to django CMS developers
Hi all

Any ideas what went wrong here (see screenshot)? 



We updated from 3.1.4 to 3.3.0.

The language settings looks like this :
 
LANGUAGE_CODE = 'de'

LANGUAGES = (
    ('de', gettext('German')),
)

TRANSMETA_LANGUAGES = LANGUAGES # TODO: used?


CMS_LANGUAGES = {  
    1: [
        {
            'code': 'de',
            'name': gettext('Deutsch'),
            'fallbacks': [ ],
            'public': True,
            'redirect_on_fallback':False,
        },
    ],
    'default': {
        'fallbacks': ['de',],
        'redirect_on_fallback':True,
    }
}

This should be "german only" and no multiple redundant buttons, right?

Any hint is appreciated! 

Cheers,

Philippe
Screen Shot 2016-11-24 at 10.24.34.png

Sikora, Vadim

unread,
Nov 25, 2016, 6:17:20 AM11/25/16
to django-cms...@googlegroups.com
In my experience multiple toolbar buttons are a sign of stale .pyc files

Vadim Sikora

Frontend Teamlead
Divio AG | Riedtlistrasse 23, CH-8006 Zürich
Tel.: +41 44 480 12 70 | Mobile: +41 79 104-43-50
http://divio.com | http://aldryn.com

Divio is a core contributor to the open source content management system django CMS: http://www.django-cms.org

--
Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to django-cms-developers+unsub...@googlegroups.com
---
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 django-cms-developers+unsub...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/4412f24d-3af6-408a-9adb-03b070d1beb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Philippe O. Wagner

unread,
Nov 25, 2016, 10:13:54 AM11/25/16
to django CMS developers
Thanks Vadim for the suggestion.

We removed the .pyc/.pyo files directly after upgrading and double checked it now - with no success. 

Philippe O. Wagner

unread,
Nov 28, 2016, 4:45:35 AM11/28/16
to django CMS developers
SOLVED

The problem could be solved by rebuilding the virtualenv. An inconsistency in the site packages was the root for this effect.
Reply all
Reply to author
Forward
0 new messages