My initial thought was to use chmod to give all users write permissions to the folder in question. This couldn’t be done, however, as it opens up an obvious security hole.

So Next I checked out the QA site, and realized that the user and group owning the htdocs directory were daemon and bitnami, respectively. This was not the case on the prod server. So it became obvious that WordPress was hitting this directory as the daemon user, and did not have ownership rights to it. So I gave it to them:

chown -R daemon:bitnami /opt/bitnami/apps/wordpress/htdocs

And viola! The issue was resolved. This little jaunt down the rabbit hole, however, got me thinking about permissions as a whole when it comes to WordPress. I did some further reading and came across this great article regarding security on the wordpress platform. I highly suggest you give it a look.

If you only care about the meat and potatoes, as most developers often do, these two snippets are what you want. If you have shell access to your server, you can change file and folder permissions recursively with these bad boys, and set them to the correct permissions the WordPress team suggests.

For Folders:

find /path/to/your/wordpress/install/ -type d -exec chmod 755 {} \;

For Files:

find /path/to/your/wordpress/install/ -type f -exec chmod 644 {} \;

Good luck!

Well, we are officially making the transition to sublime as a team. I for one am happy, as this will make it much easier for us to share and version control many of the short cut benefits of this powerful coding tool. Its also an application that is very singular in how customizable it is, through preference files in JSON format.

One of said preference files is the tmTheme file, which is used for creating a color scheme for the codebase in sublime. Now, there are quite a number of good theme files out there, however none seem to play well with JSPs, at least not well enough for myself. I for one cannot have my JSTL tags the same color as my html. Blasphemy!

So, I proceeded to edit the theme to my liking, starting with a theme called “Tomorrow Night.” This started off well, however I came upon a stumbling block: the language file for JSP just wasn’t granular enough to color what I wanted. I could make JSP tags purple, but had no control over their child attributes or operators. This would not do.

Enter the tmLanguage file:

<!-- Targeting all of the JSP tags/attributes separately; This should let us color them however we want -->
<dict>
	<!-- Start by targeting all alphanumeric tags with colons in them -->
	<key>begin</key>
	<string>(</?)([a-zA-Z0-9]++(:)[a-zA-Z0-9]+)</string>
	<key>beginCaptures</key>
	<dict>
		<key>1</key>
		<dict>
			<key>name</key>
			<string>punctuation.section.embedded.dsp</string>
		</dict>
		<key>2</key>
		<dict>
			<key>name</key>
			<string>meta.tag.block.dsp</string>
		</dict>
	</dict>
	<!-- then target the closers purple -->
	<key>end</key>
	<string>(>)</string>
	<key>endCaptures</key>
	<dict>
		<key>1</key>
		<dict>
			<key>name</key>
			<string>punctuation.section.embedded.dsp</string>
		</dict>
		<key>2</key>
		<dict>
			<key>name</key>
			<string>meta.tag.block.dsp</string>
		</dict>
	</dict>
	<key>patterns</key>
	<array>
		<!-- target the substrings separately -->
		<dict>
			<key>match</key>
			<string>([""'])(?:(?=(\\?))\2.)*?\1</string>
			<key>name</key>
			<string>string</string>
		</dict>
		<!-- target the equals separately -->
		<dict>
			<key>match</key>
			<string>([=])</string>
			<key>name</key>
			<string>constant.other.color</string>
		</dict>
	</array>
</dict>

This guy let me add more granularity to the language targeting, such as looking for tags with the colon character in them, surrounded by anything alphanumeric. This is a very common structure in JSTL.

Once I set this up, I was able to target specific pieces in my JSP tags in order to color them. The specific string names that I setup are in red below, pointing to the specific part of the code that is targeted to color:

Anywho, I’ve placed the code on Github for your use. You will need to clone two separate repos, as I have one for both the theme and language file:
Day After Tomorrow Night Theme
Updated Sublime Jave bundle

Any questions, just let me know.
Enjoy!

I was working on styling some form elements tonight for a project, and needed to style my HTML5 placeholders differently then my input values, so they looked a bit differently when the user entered the code. Doesn’t look like the spec on this is even close to finalized, so I used some browser specific prepends.

I was working working with Less, an awesome tool for dynamic CSS; If you haven’t tried it, you should give it, or SASS, a go.

Anywho, I decided to write a mixin that I could user over and over again if needed, and the above is it. You would call the mixin like so, if you wanted the placeholders to all be black:

.ph(#000);

You could obviously replace the color style with whatever you would need, but this worked for me!

I was talking to a buddy tonight about moving my git config file there, and he had suggesting symlinking with Dropbox. Now, I just need to symlink the same file at home, and I’m working with the same settings on both machines!

[ ~ ]
$ cd ~/Dropbox/
[ ~/Dropbox ]
$ mkdir dotFiles
[ ~/Dropbox ]
$ mv ~/.gitconfig ~/Dropbox/dotFiles/
[ ~/Dropbox ]
$ ln -s ~/Dropbox/dotFiles/.gitconfig ~/.gitconfig

So I’ve been building a WordPress site hat is using a custom post type of “help.” As you can probably guess, this is for a help section. The data on these help pages is fairly extensive, so I set my post type up to be hierarchical. No problem so far.

Next, I setup a page template for these custom posts (single-help.php). This is where it got a bit tricky; I had three levels of data, all which needed a functional editor so users could input html, and each level needed its own layout, pulling in only its sub posts. So essentially, my page template ended up looking like so (albeit a bit more convoluted).

<?php
	// setup your arguments:
	$args = array(
		// We want to call all posts the custom post type 'help'
		'post_type' => 'help',
		'posts_per_page' => -1,
		'post_status' => 'publish',
		'order' => 'ASC',
		// Next, we want to see if the current post is a parent of any help posts
		'post_parent' => $post->ID
	);
	// We then pass these to a wordpress query, and setup our loop
	$loop = new WP_Query( $args );
?>
<?php if ($loop->have_posts()) : while ($loop->have_posts()) : $loop->the_post(); ?>
	<!-- This post has children, so we'll list them out -->
	<a href="<?php the_permalink() ?>" rel="bookmark"><?php the_title(); ?></a>
<?php endwhile; ?>
<?php else : ?>
	<!-- This post has no children -->
<?php endif; ?>

So basically, this code allowed my single-help file to handle all three levels of the help page hierarchy, loading in each when necessary.

Lemme know your thoughts. I’d love to clean this up a bit more.

Well, htaccess to the rescue! I added the following to my .htaccess file, which sped up my site considerably (and also upped my Page Speed score). I opted to set my headers to a long time for both images, css, and js for now, since I don’t really update the look of my site that often. When I do decide to, I’ll most likely rename my js and css files, and removed the old ones.

# Setting Cache Control Headers
# 480 weeks
<filesMatch ".(ico|pdf|flv|jpg|jpeg|png|gif|js|css|swf)$">
Header set Cache-Control "max-age=290304000, public"
</filesMatch>

# 2 DAYS
<filesMatch ".(xml|txt)$">
Header set Cache-Control "max-age=172800, public, must-revalidate"
</filesMatch>

# 2 HOURS
<filesMatch ".(html|htm)$">
Header set Cache-Control "max-age=7200, must-revalidate"
</filesMatch>

Anyone out there have any suggestions on ways to set cache control? This was my first attempt at it, and I’d love some feedback!

//forcing jquery to load the version we want
function my_scripts_method() {
    wp_deregister_script( 'jquery' );
    wp_register_script( 'jquery', 'https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js');
    wp_enqueue_script( 'jquery' );
}    

add_action('wp_enqueue_scripts', 'my_scripts_method');

Add this image to your site at your own risk! Scary times!

SOPA is too blunt. Please veto.

PROTECT IP Act Breaks The Internet from Fight for the Future on Vimeo.

Tell Congress not to censor the internet NOW! – http://www.fightforthefuture.org/pipa

PROTECT-IP is a bill that has been introduced in the Senate and the House and is moving quickly through Congress. It gives the government and corporations the ability to censor the net, in the name of protecting “creativity”. The law would let the government or corporations censor entire sites– they just have to convince a judge that the site is “dedicated to copyright infringement.”

The government has already wrongly shut down sites without any recourse to the site owner. Under this bill, sharing a video with anything copyrighted in it, or what sites like Youtube and Twitter do, would be considered illegal behavior according to this bill.

According to the Congressional Budget Office, this bill would cost us $47 million tax dollars a year — that’s for a fix that won’t work, disrupts the internet, stifles innovation, shuts out diverse voices, and censors the internet. This bill is bad for creativity and does not protect your rights.

Mozilla is taking action, and so can you.

AddType audio/ogg .ogg

And viola! HTML5 audio in Firefox.