Phones and tablets are becoming the primary way the customers access content. Recently, we retired a series of iPhones from our family that had run their course.
Welcome to the blog. We talk about everything we do here, upcoming events, and a million other things.
Phones and tablets are becoming the primary way the customers access content. Recently, we retired a series of iPhones from our family that had run their course.
I think everyone's done it at this point.. They've got some legacy site that needs an older php version, and they switch MAMP over to using PHP 5.2.
It's Friday. And being that Friday is the kind of day where you celebrate the week, today I'm going to be celebrating the death of one of my favorite features of a Workhabiter.
I want to share some apps and tweaks that you may find useful if you do not like the way Mt Lion works/looks/feels out of the box...
At BADCamp, Workhabit gave a talk about the ongoing work we've been doing with iOS and Drupal. At Workhabit, we've been working for some time to bring first class support to Drupal for devices like iPads, iPhones, and other Apple devices like the new iPad Mini. Our belief is that building first class native app experiences on Drupal websites is revolutionary and exciting, and something that we've been working on as a company for a very long time.
Ive been getting emails more and more on the subject: oAuth and iOS with Drupal so Ive decided to consolidate all of those replies into one big blog post.
It seems like it is a bit tricky but its really simple once you understand all of the layers.
Features is a wonderful module, it allows you to put in code, pieces of functionality that is otherwise created in the UI. (For more information, look at these slides on features
Having been tasked with throwing up a new blog post on our shiny new site, I've decided to devote my first verbose rant to something that's an easily solved annoyance - SSH timeouts. On the projects I end up attached to, I often encounter people who aren't actually systems administrators.
Workhabit is hanging out in the biggest city in Europe: London! We're a silver sponsor at Drupalcon London. Several of our core team are out and about spending a week or two of August hanging out in London.
Come by and see us, or drop us a line if you're there and want to connect.
We've all seen it, those darn blocks that have to appear in-line in a node body, but we're often left scratching our heads as to how to get it in there.
The problem is that regions are only surfaced to the page template, and the region we need to add is a div inside of a node.
Well, with a couple of simple theme overrides, you can get there, and make it performant as well.
...Ran into an issue where Backup and Migrate wasn't cleaning up after itself - mysql dumps were sitting in /tmp, stacking up, and causing disks to fill up.
In the past year, we've worked with a number of fantastic clients. One of the things we've seen repeatedly is a desire by some clients to do work that is a "port" of the existing site to Drupal technologies. This is often not the right approach.
Drupal without drush is like a burger without cheese.
If you are running Drupal websites locally on your computer using the MAMP / MAMP Pro stack and are experiencing abnormally slow page loads, there are a couple of steps that should be taken to help increase performance.
Prerequisites:
We'll be doing some git-retrieval, meaning we need git installed. Being a sysadmin by trade, I'm naturally lazy, so I'm happy to just pull the git package from EPEL.
In a recent discovery credited to Aaron Stewart here at WorkHabit, it was found that there is an issue converting the cache_router and / or semaphore tables from MyISAM to InnoDB on a Pressflow database.
Over the course of our search for new developers for WorkHabit, I've often gotten a letter or message from Drupal Zealots large and small -- Drupal developers that were born and indoctrinated into the community and believe it's the best thing since sliced bread.
Drupal as a framework doesn't always lend itself well to detailed specifications — and many projects try very hard to do them to "contain risk" and get "a clear and exact" deliverable.
The agile approach is one a lot of people are becoming familiar with.
We've been getting reports of intermittent issues with transcoding on our CDN2 service.
After digging around for a while, we've found an issue where messages are not getting delivered through Amazon SQS to our transcode nodes.