- assume your code doesn't use any deprecated from versions below Symfony 2.3
- update dependencies from 2.3 to 2.7
- do not support "deprecated", be "Symfony3-ready"
- list tasks component by component, bundle by bundle.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
/** | |
* Adds Filters Automatically from Array Keys | |
*/ | |
add_action('genesis_meta', 'bw_add_array_filters_genesis_attr'); | |
function bw_add_array_filters_genesis_attr() | |
{ | |
$filters = bw_merge_genesis_attr_classes(); | |
foreach(array_keys($filters) as $context) { |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?php | |
final class EmailValueObject | |
{ | |
private $mailbox; | |
private $host; | |
public function __construct($email) | |
{ | |
if (false === strpos($email, '@')) { |
I'm describing my workflow in these articles, before I start my next Symphony project. Mostly for myself, to iron out my recurring problems, it is based on solid git techniques, taking heed of advice learned from Symphony community members, many many tips on the web, and flicking through the pages of O'Reilly's Version Control with git.
The core aim of this article, is to get a good Symphony development and deployment environment using git as the basis for the organisation, and have it written down for reference.
This workflow can be applied to any project, in theory, that has a starting point being a private remote git repo.