Google Tag Manager dataLayer.get()

I wanted to use reuse data stored in our Google Tag Manager dataLayer variable and finally found an obscure slideshow reference on how to to actually do just that. google_tag_manager[“GTM-XXXX”].dataLayer.get(‘key’); If you’re using Google Tag Manager you’ll already have the var dataLayer = [{}]; setup on the page. You’re presumably using dataLayer.push() to populate it … Continue reading Google Tag Manager dataLayer.get()

We’re HIRING TWO WEB DESIGNER/DEVELOPER positions

The Sr. Web Designer role will be a front-end and PHP developer heavy, WordPress experience necessary kind of job where you’ll work directly with WordPress VIP (http://vip.wordpress.com/) to build sites for our brands (Chrysler Capital, Maserati Capital, RoadLoans, Santander Consumer USA, and more) in addition to building our core websites where customers can pay their … Continue reading We’re HIRING TWO WEB DESIGNER/DEVELOPER positions

Local, Dev, Staging, Production WordPress Workflow

I just wanted to share real quickly (because I’m pretty stoked) that after months (really, years) of development I finally have what I consider a professional workflow for WordPress development. Below is a graphical representation of what takes place. But it breaks down to this (with Git, but can easily be accomplished with SVN as … Continue reading Local, Dev, Staging, Production WordPress Workflow

Settling the WordPress Absolute vs Relative URL Debate

WordPress is somewhat notorious for using absolute URLs in its linking to images and other posts within content. Many have argued for both sides. It’s quite simple for me: relative URLs are easier for development, absolute URLs are smarter for live websites. There’s a compromise to be had. WordPress should add these shortcodes to core: … Continue reading Settling the WordPress Absolute vs Relative URL Debate

WordPress network in multiple environments with a single database

Problem I needed a way in my multisite setup to have multiple environments that shared the same database, but used different domains. server1.example.com server2.example.com example.com … each of those would point to the same database. This is easy to achieve in a standard WordPress install using define( ‘WP_HOME’, ‘http://server1.example.com’ ); and define( ‘WP_SITEURL’, ‘http://server1.example.com’ );. … Continue reading WordPress network in multiple environments with a single database