Digital Strategy and Engineering
In the world of Digital Transformation, businesses are challenged to entirely rethink how Digital can give them a disruptive market advantage before their competitors disrupt them. Often companies find themselves unable to compete with their existing slow moving and risk averse information systems. The Digital landscape changes quickly and requires velocity and agility to adapt.
Wellington is again excited to host the DrupalSouth conference from February 14-16, 2014. This event will deliver three jam packed days of world-class sessions, training, talks, code sprints and networking opportunities with developers, designers, business and community leaders from the global Drupal community.
Speaking submissions are now being accepted for DrupalSouth conference sessions targeted at users of all levels, including:
Entities in Drupal 7 are really powerful. Predominantly because of the Fields module that can dynamically implement properties onto an Entity bundle through the Fields UI. This makes the Fields and Fields UI modules the key modules for driver content view and edit pages.
Programatically working with Panels in Drupal is a bit of a nightmare. Trying to figure out how to obtain the right panel display and discover the right load and save tasks can be an utter disaster as you try trace code through ctools, page manager and panels itself while trying to understand what a ctools task or handler is or how to load them.
If you're reading this blog post then you probably know by now that caching Drupal pages with varnish is pretty easy with Drupal 7. So long as the pages are anonymous. As soon as you're logged in however, the game changes. Infact as soon as you obtain a session with PHP, the game changes and you instead rely on block level caching and views and panels caching. For some sites that will be acceptable. But when you start to scale the amount of users hitting your site, PHP just can't keep up and you'll either start to run out of connections or max out your memory.
A while ago I blogged about one of the awesome powers of Drupal 7 - the ability to be database agnostic. The ability to migrate from one database server to another. A shift from one software product to another. Now while that isn't all that newer feature. Till now its been incredibily difficult to do. Till Drupal 7. Last week, I recieved an email asking me about how to migrate a SQLite database to MySQL. While i did try help remotely, I realised it would be much easier to write an open source script to do all the work. And considering the amount of conversation this particular conversation got at Drupalcon Chicago, I decided it was worth even making it into a module with a drush backend ability.
Drupal 7 is Officially released. After 2.5 years of community work, the much perfected Drupal 7 has been released in all its glory. Its features include a test driven code base with a built in test suite, a sparkling new object orientated database layer that supports not just MySQL and PostgreSQL but SQLite also, improved caching and theming layer, file streamers, a major overhaul of the user interface to make Drupal more intuitive for end users. [video:http://vimeo.com/18352872]
It may have taken me a whole day to wrap my head around the features API and how it applied to the workflow module but I finally got there. Today I wrote features support to the workflow module.
A friend of mine came around the other night, he just got himself a new iPhone. I'm not really a fan, but good on him. He asked me to let him connect to my wireless router then in a matter of minutes hew had control of my iTunes on a windows laptop of mine. Rather impressive.