The auto-created AdminSite in Django is a nifty feature for creating an administrative view of your model classes. Somehow it is not perfect, even if you want to customized it. To guide you to my problem and solution you've to know, that I implemented the SoftDelete behaviour for model classes as described by Greg Allard. It simply adds a 'deleted' field to each model marking it as deleted if its deleted in the admin site (or in some application) but never really gets deleted from the database. So in the admin site there is this field 'deleted' displayed, if you have configured it.

The Problem

My project has 2 different 'usergroups', the editors and the superusers. Superusers should see the 'deleted' fields, the others not. Unfortunatly that is not possible out of the box with Django.

The solution

I'm not the first one struggling with the user dependent display of model fields. Luke Plant found a solution for an older version of Django dealing with the field display in the add/change view. Later he updated the thing as the Django version grew. I adapted some lines of his last code for the add/change view and wrote something new to also handle the history view (that lists all model ob jects). I divided it into 2 subclasses of admin.ModelAdmin for better abstraction: one for the handling the user dependent queryset for SoftDelete and one for the display of the fields.

SoftDeleteModelAdmin

As the superusers should see the deleted field and the others not, we'll only query for the field if there is a superuser. Quite logical. The class uses the proper queryset and also returns a deleted objects if directly requested (beautyfied code @ snipt.org):

class SoftDeleteModelAdmin(admin.ModelAdmin):
  def queryset(self, request):
    if request.user.is_superuser:
      qs = self.model._default_manager.all_with_deleted()
    else:
      qs = self.model._default_manager.all()
    ordering = self.ordering or ()
    if ordering:
      qs = qs.order_by(*ordering)
    return qs

  ## If a specific record was requested, return it even if it's deleted
  def get(self, *args, **kwargs):
    return self.all_with_deleted().get(*args, **kwargs)

  ## If pk was specified as a kwarg, return even if it's deleted
  def filter(self, *args, **kwargs):
    if 'pk' in kwargs:
       return self.all_with_deleted().filter(*args, **kwargs)
    return self.get_query_set().filter(*args, **kwargs)

UserDependentModelAdmin

For the display of the field depending on the current user you have to inherit from the UserDependentModelAdmin class as listed below. Adjust the ModelAdmin class and add 'list_display_editors' (for all users != superuser) and 'list_display_superuser' (for superusers) tuples with the field names for the appropriate user (I'll only use a field called 'name' and the 'deleted' field):

class SomeAdmin(SoftDeleteModelAdmin, UserDependentModelAdmin):
  list_display = ()

  # editor fields and fieldsets
  list_display_editor = ('name',)
  fieldsets_editor = [(None, { 'fields': ['name'] })]

  # superuser fields and fieldsets
  list_display_superuser = list_display_editor + ('deleted',)
  fieldsets_superuser = [(None, { 'fields': ['name', 'deleted'] })]

All other magic is done by the UserDependentModelAdmin class. It simply changes the list_display field in the history view depending on the user and sets some prerequisites.  The 'get_fieldset' method returns the fields for the add/change view, this is nearly the same code Luke Plant wrote. (beautified code @ snipt.org)

csrf_protect_m = method_decorator(csrf_protect)

## User dependent admin model.
# This class allows to specify tuples of the listed fields and displayed fieldsets
# for the editors and superusers.
class UserDependentModelAdmin(admin.ModelAdmin):
  ## Class constructor, adding actions an/or links for the user fields.
  # @param model      the model the admin site is created for
  # @param admin_site the admin site
  def __init__(self, model, admin_site):
    # this is performed regularly on the list_display tuple
    # do the same for the additional list_display fields
    self._add_actions_and_links_for_list_display('editor')
    self._add_actions_and_links_for_list_display('superuser')
    super(UserDependentModelAdmin, self).__init__(model, admin_site)

  ## Adds actions and/or links for the list_display tuple of the given user
  # definid list_type.
  # @param list_type  the list_display type, currently 'editor' for editors or 'superuser' for superuser
  def _add_actions_and_links_for_list_display(self, list_type):
    if 'action_checkbox' not in getattr(self, 'list_display_' + list_type) and self.actions is not None:
      setattr(
        self,
       'list_display_' + list_type,
       ['action_checkbox'] +  list(getattr(self, 'list_display_' + list_type))
      )
    if not self.list_display_links:
    for name in getattr(self, 'list_display_' + list_type):
      if name != 'action_checkbox':
        self.list_display_links = [name]
      break

  ## View for listing the models.
  # Adjusts the list_display tuple according to the current user.
  # @param request        the sent request
  # @param extra_content  an additional context
  @csrf_protect_m
  def changelist_view(self, request, extra_context=None):
    if request.user.is_superuser:
      self.list_display = self.list_display_superuser
    else:
      self.list_display = self.list_display_editor
    return super(UserDependentModelAdmin, self).changelist_view(request, extra_context=extra_context)

  ## Returns the fieldsets depending on the user.
  # @param request    the sent request
  # @param obj        the model object if already persisted
  def get_fieldsets(self, request, obj=None):
    user = request.user
    if user is None or user.is_anonymous():
      # never get here normally
      return ()
    else:           
      if user.is_superuser:
        return self.fieldsets_superuser
      else:
        return self.fieldsets_editor

If you're interested in the script, head over to its project page and check the appropriate pages like the Changelog and the Installation and Requirements page. Feel free to download and comment  it.

As I'm moving the domain to a new server these days it could be possible that zoe.vc isn't reachable for some hours or even days. So don't be confused - everything will be alright after the movement is finished. Comments are disabled meanwhile.

Thanks for your understanding!

I'm using Windows Vista Business x64 as os and for SVN the wonderful, free and easy VisualSVN Server. Next ugly thing on The Bug Genie is that there is no documentation for the modules. I found an entry in the forums how to use the integration in windows, but that did not work out of the box. But the code is already within the module, what is good.

So open modules/svn_integration/post_commit.php from your buggenie installation directory and adjust this line with your path to the bugtracker installation dir:

define('BUGS2_INCLUDE_PATH', 'D:\\xampp\\htdocs\\bugs\\');

Then create a batch file in the same directory called post-commit.bat. You can see the source below, copy it and adjust the following variables. I used the code from the forum post and adjusted it a little. Remember that urls with whitespaces do not work, create a symlink or rename your directories:

• Path to svnlook.exe (you see my VisualSVN Server resides in D:\VisualSVN_Server, the default location C:\Program Files (x86)\VisualSVN Server does not work because of the whitespaces) VisualSVN Server has all the svn tools in its bin directory.

SET SVNLOOK=D:\VisualSVN_Server\bin\svnlook.exe

• The path to your php executable. I used XAMPP, so it is in D:\xampp\php\php.exe if installed in root on drive D.

SET PHP=D:\xampp\php\php.exe

• The path to your SVN directory. This is where svn stores its data.

SET SVN_PATH=D:\svn\

• The post-commit hook we create later takes two arguments from VisualSVN Server, the path and the revision. Unfortunatly VisualSVN Server uses the url as path which collides with the svnlook command we use to determine if a bug was mentioned in a revision comment, as svnlook wants the real file path.
  So we have to adjust the url to a path. As there is no real substring functionality for windows batch (or I did not search long enough) we simply count the length of our SVN url. In my case VisualSVN Server listens at https://amanda:8443/svn/, so a repository would be at https://amanda:8443/svn/my_repos. The server root (https://amanda:8443/svn/) has a length length of 24. Change the 24 to the length of your url. The batch then combines the SVN_PATH and your repository path to the local path, D:\svn\myrepos in my case here.

SET REPOS=%REPOS:~24%

• Once again, set the path to your installation directory of the bugtracker (replace D:\xampp\htdocs\bugs with your path):

%PHP% -f "D:\xampp\htdocs\bugs\modules\svn_integration\post-commit.php" "%AUTHOR%" "%REV%" "%COMMIT_MSG%" "%CHANGED%"

After your saved the file, open VisualSVN Server and the properties of your repository. Select the the Hooks tab and doubleclick the Post-commit hook. Enter the path to the batch file with the 2 arguments path and revision, in my case I entered "D:\xampp\htdocs\bugs\modules\svn_integration\post-commit.bat %1 %2", where %1 is the repository path and %2 the revision number.

Finally you have to install either WebSVN (which I prefer) or ViewVC and specify the path to your repository (in my case it is http://localhost/websvn/listing.php?repname=my_repos&) in The Bug Genie module settings for svn_integration.

One final and important hint: your user in the bugtracker has to have the same username as in SVN. By default, the first user in the tracker has the username "Administrator". My SVN user does not have the name "Administrator", so I logged out of the tracker, changed the property "uname" of the MySQL table "bugs2_users" for the admin to my SVN username, logged in and then everything worked fine.

As always, feel free to add comments and spread the word

And here the post-commit.bat code:

@echo off
SET REV=%2
SET REPOS=%1

REM path to svnlook (remember that paths with whitespace do not work e.g. C:\Program Files --> use mklink to create a path without)
SET SVNLOOK=D:\VisualSVN_Server\bin\svnlook.exe

REM path to php executable
SET PHP=D:\xampp\php\php.exe

REM path to svn (not url!)
SET SVN_PATH=D:\svn\

REM maps the svn url to the svn path - straightforward but the easiest way
REM replace with the length of your svn url e.g. 24 for https://amanda:8443/svn/
SET REPOS=%REPOS:~24%

SET REPOS=%SVN_PATH%%REPOS:/=\%

%SVNLOOK% log -r %REV% "%REPOS%" > COMMIT_MSG
REM SET THE COMMIT_MSG FROM THE FILE. The file is expected to contain only one line with this value
FOR /F "delims=" %%A IN (COMMIT_MSG) DO SET COMMIT_MSG=%%A
echo COMMIT_MSG=%COMMIT_MSG%

%SVNLOOK% changed -r %REV% "%REPOS%" > CHANGED
REM SET THE CHANGED FROM THE FILE. The file is expected to contain only one line with this value
FOR /F %%A IN (CHANGED) DO SET CHANGED=%%A
echo COMMIT_MSG=%CHANGED%

%SVNLOOK% author -r %REV% "%REPOS%" > AUTHOR
REM SET THE AUTHOR FROM THE FILE. The file is expected to contain only one line with this value
FOR /F %%A IN (AUTHOR) DO SET AUTHOR=%%A
echo COMMIT_MSG=%AUTHOR%

%PHP% -r "echo urlencode($argv[1]);" "%COMMIT_MSG%" > URL_COMMIT_MSG
REM SET THE URL_COMMIT_MSG FROM THE FILE. The file is expected to contain only one line with this value
FOR /F %%A IN (URL_COMMIT_MSG) DO SET URL_COMMIT_MSG=%%A
echo COMMIT_MSG=%URL_COMMIT_MSG%

%PHP% -f "D:\xampp\htdocs\bugs\modules\svn_integration\post-commit.php" "%AUTHOR%" "%REV%" "%COMMIT_MSG%" "%CHANGED%"

Vor kurzem habe ich ein schönes Skript zum Sichern einer MySQL-Datenbank und anschließendem Versenden des Backups per Email hier gefunden.

Das Skript ist an sich ganz gut, aber mir hat es strukturell nicht gefallen, da man die Datenbankzugangsdaten inline eintragen muss und es ausserdem nur für eine Datenbank funktioniert. Deswegen habe ich das ganze ein wenig umgeschrieben und stelle das hier gerne zum Download bereit.

Was kann es?

• Backup mehrerer Datenbanken
• Versenden der Backups an mehrere Empfänger

Es wird dabei pro Datenbank eine Email versendet und auf dem Server bleiben keine Dateien liegen. Das ganze ist auch noch einfach zu konfigurieren.

Wie benutze ich das?

• Aktuelle Version (0.1) herunterladen
• Daten in backup.php anpassen (ist alles kommentiert)
• alles in ein Verzeichnis deiner Wahl hochladen
• ggf. einen cronjob anlegen, der das Skript periodisch ausführen

Hier die backup.php, welche die entsprechenden Klassen aufruft und das Backup anstößt (ist auch im Download mit enthalten):

ini_set('error_reporting', E_ALL);
// include the files
require_once 'MySQLConfig.php';
require_once 'MySQLBackup.php';
 
// add some databases to backup
// the domain will be appended to the email subject and is also included within the sql file for identification.
$cfgHost0 = new MySQLConfig('username0', 'password0', 'database_name0', 'domain0');
$cfgHost1 = new MySQLConfig('username1', 'password1', 'database_name1', 'domain1');
 
$backup = new MySQLBackup();
// the path to the directory where this script is resided
$backup->setExecutionPath('/srv/domain/backup/');
// add the database configs to backup
$backup->addDatabaseToBackup($cfgHost0);
$backup->addDatabaseToBackup($cfgHost1);
// the sender of the backup mail
$backup->setSender('admin@yourdomain.com');
// add some people to receive the backup
$backup->addRecipient('john@yourdomain.com');
$backup->addRecipient('frank@yourdomain.com');
// execute the whole thing
$backup->backup();

Falls es Probleme und/oder Anregungen gibt, bitte diesen Post kommentieren, danke!

PS: zum Anlegen eine Cronjobs per SSH auf deinem Server einloggen, dann "crontab -e" ausführen, dann z.B. "0 2 * * 0,3 wget http://yourdomain.com/backup/backup.php -nc -q -O /dev/null" für eine Ausführung Sonntags und Mittwochs um 2 Uhr nachts einfügen. Mit ":wq" speichern und die Datei schliessen, dann sollte es schon funktionieren

Platz 3 nimmt das XAMPP Projekt ein. Mit dieser tollen Sammlung bekommt man alles, was man braucht, um lokal mehr oder minder schöne Webseiten zu entwickeln: Webserver, Datenbank und Emailversendeding. Und man kann es überall mit hin nehmen, z.B. auf den USB Stick.
In der goldenen Mitte steht SVN, die Open-Source-Lösung zur Softwareversionierung. Da ich ja ein alter Windows-Hase bin, nutze ich VisualSVN, den meiner Meinung nach besten und schönsten SVN-Server für Windows, und TortoiseSVN als Client. SVN hat mir schon mehrfach den Arsch gerettet, zum Glück committe ich immer relativ häfig. Auch unverzichtbar beim Entwickeln von TYPO3-Extensions.
Platz Numero Uno nimmt eindeutig die Eclipse IDE bei mir ein. Ohne dieses wertvolle Tool entsteht eigentlich keine Zeile Code. Die Vorteile liegen auf der Hand: kostet nix, zuverlässig, schier unendlich erweiterbar. Ich nutze dabei das Bundle "Eclipse IDE für Java EE Developers", welches zusätzlich mit PDT, Subclipse und dem Google Appengine SDK gepimpt ist. Damit ist eigentlich alles, was ich so programmiere, abgedeckt.

Ich könnte noch ein wenig weiter auflisten, aber das ist jetzt nicht Sinn der Sache. Also nochmal kurz:

1. Eclipse
2. SVN
3. XAMPP

So, und nun her mit meiner X-BOX!

Im Blog von Dmitry Dulepov stehen einige Dinge über Typo3 Performance, die man sich mal zu Herzen nehmen sollte. #2 war mir bisher noch nicht bekannt.

class tx_extkey_piX extends tslib_pibase {
   function main() {
      $this->sys_language_uid = (int) t3lib_div::_GP('L');
      ...
   }
}

Dazu habe ich diesen nützlichen Blogeintrag von Markus Giesen gefunden: Typo3 mySQL-Datenbank auf UTF-8 umstellen bzw. konvertieren

Jedoch ist bei mir im Export nie die Kollation festgeschrieben, diesen Schritt konnte ich de facto überspringen. Auch hatte ich keinen phpMyAdmin, also mussten die Kommandos für die SQL-Konsole zum Anpassen der Kollation her:

Anzeigen der verfügbaren Kollationen auf dem Server:

SHOW COLLATION
SHOW COLLATION LIKE 'utf%'

Ändern der Kollation der aktuellen Datenbank:

ALTER DATABASE DEFAULT COLLATE utf8_general_ci

Und danach weiter nach Markus Giesens Anleitung verfahren und alles wird gut