GNOME Bugzilla – Bug 681383
Admin pages lost CSS and features
Last modified: 2012-10-07 23:38:25 UTC
http://l10n.gnome.org/admin/ looks like it has no CSS anymore. Worse that I have just added a new module[1], and the part to add the domain / directory is simply not there, so the new modules page[2] does not display any po files. [1] http://l10n.gnome.org/admin/stats/module/403/ [2] http://l10n.gnome.org/module/dconf/
I think that maybe that's because of Claude migrating to django 1.4? I will try to take a look at it.
(In reply to comment #1) > I think that maybe that's because of Claude migrating to django 1.4? Yes, it is. I temporarily added a STATIC_URL setting in local_settings.py and recreated the media/admin symlink, but the real fix is to migrate DL to staticfiles. I'm leaving the bug open for that task.
Care (In reply to comment #2) > I temporarily added a STATIC_URL setting in local_settings.py and recreated the > media/admin symlink, but the real fix is to migrate DL to staticfiles. I'm > leaving the bug open for that task. Care to elaborate/link to relevant documentation so that anyone (even myself :) can try to cook a patch for it?
Gil, the static-files documentation is here: https://docs.djangoproject.com/en/1.4/howto/static-files/
Created attachment 220759 [details] [review] Patch for bug nmbr:681383
Breno, thanks for the patch. It's a first step, but we will probably also need to separate "media" (uploads) and "static" files in different folders. However I wonder if we should first let the newtheme branch land (#681167), and then fix this one.
(In reply to comment #6) > However I wonder if we should first let the newtheme branch land (#681167), and > then fix this one. I'd like to point out that on the module pages I still cannot set the translation domain, so http://l10n.gnome.org/module/dconf/ is pretty much unusable.
(In reply to comment #7) > I'd like to point out that on the module pages I still cannot set the > translation domain, so http://l10n.gnome.org/module/dconf/ is pretty much > unusable. Fixed, it was a simple permission problem for the group "coordination_team".
Forgot to mark as fixed :)