Marc Neuhaus mneuhaus

Prolog

one issue that regularily occurs to me in a development project is how to keep in sync with the database. This is often no problem if you develop it yourself, alone. But if you're developing a project with more than one person the generally accepted best practice is to develop locally, commit changes and then deploy to the testing/staging/production. This is all and well with code of course. But keeping the database in sync is quite a hassle sometimes. Most systems provide at least schema-migrations or other means of analysing + patching the database. But what about the data itself? Currently there are 2-3 Scenarios that you could do:

develop locally and regularily dump the production database and import it locally
- pro: fast project because everything is local and easily to develop
- con: you regularily get out of sync and need to redo stuff manually or override the database
open up the production/staging database and let every local developer use that
pro: everyone uses the same dat

	TYPO3:
	Flow:
	persistence:
	doctrine:
	filters:
	soft-deleteable: 'Gedmo\SoftDeleteable\Filter\SoftDeleteableFilter'

	<f:security.ifAuthenticated>
	<f:then>
	<a>Log out...</a>
	</f:then>
	<f:else>
	<form>
	login kopiert aus der Login extension
	</form>
	</f:else>
	</f:security.ifAuthenticated>

	{
	"TYPO3.Neos": {
	"[TASK] Adjust to dimension support in TYPO3CR": "27489",
	"[WIP][FEATURE] Support l10n for nodes": "27490",
	"[FEATURE] Add LanguageMenuImplementation": "27382",
	"[WIP][TASK] Adjustment for first level cache": "27398",
	"[TASK] Reload the nodeTree if the content dimensions change": "27383"
	},
	"TYPO3.TYPO3CR": {
	"[FEATURE] Flexible content dimensions (and localization)": "27483",

	<?php
	/*
	Plugin Name: CodeStyling Localization
	Plugin URI: http://www.code-styling.de/english/development/wordpress-plugin-codestyling-localization-en
	Description: You can manage and edit all gettext translation files (.po/.mo) directly out of your WordPress Admin Center without any need of an external editor. It automatically detects the gettext ready components like <b>WordPress</b> itself or any <b>Plugin</b> / <b>Theme</b> supporting gettext, is able to scan the related source files and can assists you using <b>Google Translate API</b> or <b>Microsoft Translator API</b> during translation.This plugin supports <b>WordPress MU</b> and allows explicit <b>WPMU Plugin</b> translation too. It newly introduces ignore-case and regular expression search during translation. <b>BuddyPress</b> and <b>bbPress</b> as part of BuddyPress can be translated too. Produces transalation files are 100% compatible to <b>PoEdit</b>.
	Version: 1.99.30
	Author: Heiko Rabe
	Author URI: http://www.code-styling.de/english/
	Text Domain

	<?php
	function path() {
	$paths = func_get_args();

	$prefix = '';
	$suffix = '';

	if (substr(current($paths), 0, 1) == DIRECTORY_SEPARATOR) {
	$prefix = DIRECTORY_SEPARATOR;
	}

	<article <?php post_class(); ?>>
	<div class="row">
	<div class="col-xs-3">
	<?php
	if (get_the_post_thumbnail()) {
	echo get_the_post_thumbnail($post_id, 'news-thumbnail', array('class' => 'img-responsive'));
	} else {
	echo 'kein thumbnail vorhanden';
	}
	?>

	// farben

	@white: #f2f2f2;
	@regwhite: #ffffff;
	@brown: #4c4238;
	@darkbrown: #353029;
	@beige: #b4a188;
	@blue: #006cba;

	// defaults

	<?php
	namespace TYPO3\Expose\ViewHelpers;

	/* *
	* This script belongs to the TYPO3 Flow package "TYPO3.Expose". *
	* *
	* It is free software; you can redistribute it and/or modify it under *
	* the terms of the GNU Lesser General Public License, either version 3 *
	* of the License, or (at your option) any later version. *
	* *

	TYPO3:
	TypoScript:
	handleRenderingExceptions: throw