So you created this nice and shiny new hippster round-edges site for your client and allways press your thumbs on deployment to make it magically work on the production system. But what if we deploy to a different Webserver software? Now you might rapidly approach troubles and pain as you never had before, winding your brain about why the crap your CSS3 Polyfill accomplished with CSS3PIE doesn’t work as expected (and tested on your dev-site). This can cause a serious case of grey hair! Your stylesheet /** * Bootstrap 3 generic conditional stylesheet * taken from https://gist.github.com/coliff/5618329 */ .img-rounded{behavior:url(/scripts/PIE.htc)} .img-circle{behavior:url(/scripts/PIE.htc)} .table-bordered{behavior:url(/scripts/PIE.htc)} select,textarea,input,code,pre{behavior:url(/scripts/PIE.htc)} .input-group-addon{behavior:url(/scripts/PIE.htc)} .btn{behavior:url(/scripts/PIE.htc)} .dropdown-menu{behavior:url(/scripts/PIE.htc)} .panel{behavior:url(/scripts/PIE.htc)} .well{behavior:url(/scripts/PIE.htc)} .nav-tabs > li > a{behavior:url(/scripts/PIE.htc)} .nav-pills > li > a{behavior:url(/scripts/PIE.htc)} .navbar{behavior:url(/scripts/PIE.htc)} .navbar-nav > li > a{behavior:url(/scripts/PIE.htc)} .navbar-toggle{behavior:url(/scripts/PIE.htc)} .navbar-toggle .icon-bar{behavior:url(/scripts/PIE.htc)} .breadcrumb{behavior:url(/scripts/PIE.htc)} .pagination{behavior:url(/scripts/PIE.htc)} .pager li > a,.pager li > span{behavior:url(/scripts/PIE.htc)} .modal-content{behavior:url(/scripts/PIE.htc)} .tooltip-inner{behavior:url(/scripts/PIE.htc)} .popover{behavior:url(/scripts/PIE.htc)} .popover-title{behavior:url(/scripts/PIE.htc)} .alert{behavior:url(/scripts/PIE.htc)} .thumbnail,.img-thumbnail{behavior:url(/scripts/PIE.htc)} .label{behavior:url(/scripts/PIE.htc)} .badge{behavior:url(/scripts/PIE.htc)} .progress{behavior:url(/scripts/PIE.htc)} .accordian-group{behavior:url(/scripts/PIE.htc)} .carousel-indicators li{behavior:url(/scripts/PIE.htc)} .jumbotron{behavior:url(/scripts/PIE.htc)} Pretty neat, huh? WorksOnMyMachine! Freaks out in production. The hunt So you did everything right, the SauceLabs connect tool is d’accord with it, but there’s something fishy.. Checklist .htc files uploaded? CHECK Webserver delivers correct mimetype? CHECK Works as expected? NOPE Correct Checklist .htc files uploaded? CHECK Webserver delivers correct mimetype? CHECK Make sure the webserver doesn’t redirect you, whilst requesting the .htc file Works as expected? SURE Conclusion Never let your IE friends be redirected while requesting the .htc file. The server has to return a 200 response code.
If you're like me, you spend some time on reflecting, what's actually happened in the last year. This involves personal things and things that may affect the society in general. Ambitious OSS projects What affected me the most in the passing year, was the spirit of Open Source Software. Old dishes? NO! Starting April 2013 or so, i joined the Fluid powered TYPO3 project. What we are trying to archieve is as simple as it is ambitious: Make templating in TYPO3 CMS rock with fluid. This claim is somehow simple and powerful-but the real thing behind, is the gift of both using powerful tools and actually giving other people the possibility to use them as well, so we can raise the bar once again and be able to construct powerful, TYPO3 CMS-powered sites in a breeze. And I think we actually made the difference. - There are no hidden treasures in private repos, no exclusive toolchains.. All in the open. This is a both exciting, as well as stunning experience, and tasks vary from supporting users over hacking the code to discussing how we can push the boundaries any further. So why don't you contribute to the TYPO3 CMS Core? Evil voice on my shoulder One can't do anything and it's more interesting to live on the edge than needing to stuff holes in an old carpet. People? Yessir! The people you work with actually make the difference. Unless you're working from the couch, in the middle of the night, you need someone to talk about your projects, the roadmap, fooling around, misuse as Karma Buddy. In short-Björn and Claus; thank you. You know when, where, what. Any wishes for the next year? Sure. I can give you a brief list: peace and harmony for everybody (Just kidding, it's never gonna happen..) more traction for NodeJS in shared hosting environments (Don't ask..) more people that understand, where a enterprise CMS makes the difference [insert your point here] That's it. - Sorry, couldn't resist See you on the other side!
What’s probably the most annoying task when starting a new project, may be the initialization of your new project structure. This usually involves one or more of the following Tasks: Downloading the TYPO3 sources Unpack them to a local webserver Configure the base parameters (Database, ImageMagick, cURL..) Initialize the extension list via Extension Manager (which failed often on newer 6.x branches) Import the extensions you need, in the version you need Attempts to solve it While you can attempt to template projects (and you should really do that!), this could also lead to some yummy new trouble: outdated dependencies outdated core big blobs of sql (or in our case, t3d files) Composer While composer may be not the most common way to manage dependencies in the TYPO3, it could be a real advantage, using it. Composer manages dependencies with cascading versions, suggestions and exclusions as well as platform requirements such as enabled PHP extensions and versions. To get a quick overview, of what can be done, you can execute the following lines in your cli: curl -sS https://getcomposer.org/installer | php php composer.phar create-project --stability=dev ft3/fluxkitchen-distribution . This will fetch a project template from a GitHub project of mine and installs a chain of dependencies. But first, let’s examine the composer.json (I exluded the profane parts..): { // Defines the requirements "require": { // Thanks to the Lightwerk guys, we can define TYPO3 CMS dependencies via composer "typo3/cms": "6.1.x", // Here, a custom package is required, which has its own dependencies "ft3/fluxkitchen": "dev-master" }, "repositories": [ // Lightwerk composer repository { "type": "composer", "url": "http://composer.lightwerk.com/" }, // The composer package of the FluidTYPO3 project, generated with Satis { "type": "composer", "url": "http://fluidtypo3.github.io/composer-repo/" }, // You can even define your own packages on the fly, great for private packages { "type": "vcs", "url": "https://github.com/cedricziel/fluxkitchen" } ] } What will it do when issueing the command? Install composer.phar to your local workspace Clone the template project to your local workspace run composer install to resolve dependencies, recursively (!) The fluxkitchen repository itself defines no functionality, but shows the great possibilities. Its composer dependencies are defined as follows: "require": { // We need the composer installers! "composer/installers": "*", "ft3/fluidcontent": "*", "ft3/fluidpages": "*", "ft3/ft3_empty": "*" }, Recursive behaviour at its best. :-) Any of the above listed packages (except composer/installers) has a strong dependency to the ft3/flux package, which will be resolved dynamically. Result With this single line of command, you get: a current TYPO3 core ("typo3/cms": "6.1.x",) a set of extensions (most current versions): ft3_empty flux fluidpages fluidcontent fluxkitchen What else can composer do for us? Admittedly-we didnt reach all of our goals defined above, but I will keep fiddeling around with composer postInstall commands. That way, one could: fix permissions on a regular base (on each composer update for example) a post-install wizard to configure the database (install tool api?) install extensions (not just downloading them) via Core API … Outlook Let’s recall the list once again: Downloading the TYPO3 sources Unpack them to a local webserver Configure the base parameters (Database, ImageMagick, cURL..) Initialize the extension list via Extension Manager (which failed often on newer 6.x branches) partially solved. All extensions defined a depenencies are downloaded, which circumvents the need for it ;) Import the extensions you need, in the version you need Given you used the Provider Extension pattern, you could have a running TYPO3 installation with 0 overhead in minutes. I hope you like the approach-I will constantly try to evolve it and link follow-ups. What are your approaches to template projects? Links Composer fluxkitchen-distribution Github Project fluxkitchen Github Project Composer Post Install
