Have you been working on our local machine on a new project. Now you are at the point where you need to get your initial progress where the client can do some content entry, or perhaps a second developer is going to start working with you, or perhaps a themer needs to start accessing the code... what ever the reason for needing to broaden the development environment, that's one option for what you can do.

We are going to utilize our local machine, WebEnabled, and unfuddle. The goal being revision controlled files, in an accessible setting (http://).

The power and flexibility of the jquery library is pretty awesome.  There are a number of reasons that you may want load the files one at a time, or the individual .js files on an as needed basis.

Last week, I completed a blog post on getting jQuery up and running (http://blogthingee.com/blog/getting-jquery-ui-working-drupal-6x)... Now we can see if it is working.

For now, let's just assume you want them all the time, and you want to test them right now, or you simply want to test that you have all of the jquery ui goodness at your fingertips, here is how I would go about it...

After several attempts, I believe that I have a pretty good system/process for getting jquery ui to work with drupal 6.x.  So I guess it's time to share :)

1. Check Current Jquery Version.
2. Update Jquery with Jquery Update Module
3. Download Jquery UI Module
4. Download the support files for the Jquery UI Module
5. Enable the Jquery UI Module

I would first check and make sure your current version of jquery is working/running on the site, as this entire process (which I have done several times for both fun and work) has worked best for me if I do each step in turn, then verity what I have done...

The site shows a View profile of bloggers and lives at the url "/blogs".  Unfortunately, this save View became visible at "/blogs/{anyrandomword}".  This was not the desired result.  To further this specific instance, I realized that my path for the teaser view of each bloggers' post's was at the dynamic url of "/blogs/{username}".

This is the tale of a sites with their own classified ads, when they wanted to track how often users who post a classified, were "contacted". Their goal was to be able to see if the classified were successful, based on the volume of responses to the classified ads. A great idea... now I have to implement it.

The setup and layout for this content type is pretty basic.. The Classified Listing is displayed as a panel. The top half is info about the listing (node), and the bottom half is a contact form (send user email form), that sends and email to the user who posted the listing, from the logged in user.

I was working with the date module today and wanted to remove the (All Day) that appeared after the date when the field was rendered to the screen.

I found a great post here... http://www.pridedesign.ie/content/drupal-date-field-remove-all-day

To summarise, it seems that a good way to turn it off (altogether) is just to override a theme function. Edit you template.php and add the following code:


function _date_all_day_label() {
return '';
}


However,

I looked for this a few times and didn't find it so I decided to write a quick blog post for future themers to discover. You see Drupal is full of forms and fields. There are any number of reasons that you may want an element on a form to be identified by a unique class or ID. I ran into this today when I wanted to theme a fieldset, provided by a module, that didn't have a class on the fieldset. Now there are many ways to theme a fieldset by using the divs that contain the fieldset. However, sometimes it's nice to just have a theme set for a fieldset, and apply that class when and where you need it.

Last week I wrote about preprocess functions and wanted to do a little follow-up because I was having even more fun making changes, adjustments, and alterations.  There is so much here for themers, there is an excess of options and they can be organized and structured very well.  Again, as I often say, I do not profess to be a php-guy (I continue to get better, and using it daily now, someday I will be where I want to be with it...) so this structure and framework has been completely awesome for me.  So what's next with preprocess...