Download

Download slickr_thematic_theme.tar.gz

Installation

Just download this file, un-tar it ($ tar -xvzf slickr_thematic_theme.tar.gz) and copy the extracted folder to wordpress/wp-content/plugins/slickr-gallery/themes. Then you can select the Thematic theme from the WordPress admin area under Settings -> Slickr Gallery -> Slickr Gallery Theme.

You’re welcome.


<?php
function add_js() {
$stylesheet_dir = get_bloginfo('stylesheet_directory');
$myscript = $stylesheet_dir . '/js/myscript.js';
$mootools = $stylesheet_dir . '/js/mootools.js';
wp_enqueue_script('mootools', $mootools, '', '1.2.4', false);
wp_enqueue_script('myscript', $myscript, array('mootools'), '1.0', false);
}
add_js();
?>


Notice how every parameter is used in the < ?php wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer ); ?> function even though all but the first one is supposed to be optional. Maybe its a PHP thing. Whatever.

I struggled with this, as the usual method of including a javascript library and an external javascript script did not work. Usually, I would do this:


<script style="text/javascript" src=<?php bloginfo('url'); ?>/wp-includes/js/jquery/jquery.js" ></style>
<script style="text/javascript" src=<?php bloginfo('template_directory'); ?>/myScript.js" ></style>


But that didn’t work at all, even when I included the jQuery.noConflict() line in my script. So I ended up going with this, which loads the jQuery library that is included with the wordpress installation and then loads my script without any conflicts:


<?php wp_enqueue_script( 'myScript', '/wp-content/themes/myTheme/myScript.js', array('jquery') ); ?>


The wordpress docs have very little to say about wp_enqueue_script(), the function that makes this possible. A good resource with examples of use can be found here:

http://nickohrn.com/loading-javascript-libraries-in-wordpress-plugins-with-wp_enqueue_script/

This was originally a reply to liverbones’ comment of my last post, but it became long so I gave it a home of its own.

Just about every day I run across some design or technical problem that I can only solve through blogs or message boards. Its an amazing resource, and I couldn’t get by without it. However, I find that the solutions are often lacking.

The problem is that the tech guru who is answering the question usually figured out the thing in question long ago, and can’t remember quite what their personal “Ah HAH!” moment was. So they leave the little stuff out. For instance, if you’re not used to linux command line stuff, and you install something that you have to initialize through the command line, you cannot just type in shell$ foo and expect it to work. Most likely, the command foo is not in your path. So you actually have to go to the file where the program is, then type in shell$ ./foo. The “.” tells your computer that the command can be found in this directory. But ask a linux guru how to initialize a program, and she will tell you “Just type in foo” at the command line. Its not that they don’t know how to do it right, its that they know it so well that they forgot to tell you. This why the best answers come from bloggers who are right in the heat of the moment, still trying to figure it out when they post.

For instance, I posted my GoDaddy entry just yesterday. But I had been working on getting wordpress set up on GoDaddy for hours. Actually, to be honest, days. This blog helped, as did the comments on this post, but it made everything seem so easy. Fact is, when I first uploaded the site, nothing worked at all.

I struggled with the wp-config file forever. Then I enabled pretty urls, which broke everything, and spent several hours downloading and uploading the .htaccess file trying to modify just the right thing. It was only after I gave up (because of a blog post that mentioned if you just wait, everything will work), waited two days, and tried again that it worked. Instantly. For no reason at all.

So my point is, because I treasure the thoughtful, generous people who document their sometimes painful journey through the trials of learning how to do stuff with computers, I am going to start blogging while I’m still trying to figure shit out.

This is a progress report on MilhollandCycles.com, website I am building for my brother Greg, who builds bicycles in our house in Portland. His bikes are great. He built me the coolest fillet braised mountain bike that languishes in the basement while I try to save enough cash to get paint and parts on it. I think about it every day, and when the sun is out and I’m not at work it kills me that I am not mountain biking every second.

So I built Greg a theme for wordpress. It was pretty straight forward. I love wordpress. The code is elegant and extensible, and you can do whatever the hell you want to with it. I built Greg’s theme on top of the default theme that comes with the wordpress download. switch around a few php include tags and give it a new style.css document and you’re in business. I host my sites in the webserver document folder on my laptop because I can’t get virtual domains to work, but that’s another post. Anyhow, its a great testing platform because I can view the sites as they are served from the apache server on my laptop. Most of the time its just like they are live on the ‘net. Not always though. Some of the plugins (lightbox in particular) didn’t work quite right.

Thankfully when I uploaded the site to godaddy (I know what you are thinking, don’t judge me!), everything miraculously worked. Plugins, pages, everything. Except pretty URLs, that broke everything. But it wasn’t THAT hard to fix, you just have to erase all of the stuff that wordpress adds to the .htaccess file and replace it with a clean one.

The thing that vexes me is no shell access. I didn’t even think about this when choosing hosting services, but godaddy does not allow shell access. That means that you have to manipulate SQL tables with phpMyAdmin. I do not like this program. Call me old fashioned, but I prefer the hands-approach. I just don’t trust the GUI to be messing with my SQL. Maybe I shouldn’t worry about it. Wordpress has done a fine job all on its own. But I am worried. Enough so that I won’t host another site on godaddy again. Sorry.

This time though, I’m starting fresh.  I was inspired by this post:

http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/

So I’m basing this site on the Sandbox theme, and I’m going to use Blueprint to get a jump on the CSS. It may be a while before I get to designing my own theme for this site because I have a couple projects in the pipe right now. Plus, I don’t know about you, but I am really digging the solid unstyled power of the Sandbox theme. I mean, its so pure, you know?

The last site I developed took a hair shy of 14 hours (!) to lay out in CSS. That is un-freaking-acceptable. I mean, I am really good at CSS. I know it backwards and forwards. By heart. But it is at its core a flawed and limited standard, so I’ve given up and I’m going to cheat anyway I can from now on. In a standards-compliant way, of course.