<div class="post<?php if ( $location != 'bottom' ) : ?>-top<?php endif; ?>-pagelinks<?php if ( $location == 'bottom' ) : ?> pl-right-side<?php endif;?>"><?php next_post_link('&nbsp;next: %link'); ?></div>
<div class="post<?php if ( $location != 'bottom' ) : ?>-top<?php endif; ?>-pagelinks<?php if ( $location == 'bottom' ) : ?> pl-right-side<?php endif;?>"><?php previous_post_link('prev: %link&nbsp;'); ?></div>

This is how I generate my ‘next post’ and ‘prev post’ for my theme.

So… adding to the filters:

add_filter( 'previous_post_link', array(&$this, 'link_shortner'), 10, 2);
add_filter( 'next_post_link', array(&$this, 'link_shortner'), 10, 2);

The heart of the code is in link_shortner.

/**
 * Shortner the link.
 * @since 1.3.0
 * @param $format
 * @param $link
 * @return Echo link.
 */
 function link_shortner($format, $link) {

 //  The RegEx Pattern
 $pattern = '/(.*?)(<a .*?>)(.*?)(<\/a>)/is';
 //  Pattern Of the Next/Previous Links
 preg_match($pattern, $format, $matches);

 if ( strlen($matches[3]) <= 60 )
 return $format;

 //  Replacement
 $replacement = '$1 $2 ' . mb_substr( $matches[3], 0, 60) . '... $4';
 //  Run Preg Replace
 $source = preg_replace($pattern, $replacement, $format, 1);
 return $source;
 }

The highlighted lines process the format that I use in the functions to call the next/prev links. Because we want to make sure we preserve the formatting we run off $format and not $link. After we have determined that the display text is passed a certain length, we are going to run a replacement making sure we keep all the other elements along as well.

And tada! We now have a shortened display link that won’t mess up the theme when the post title is too long. So if you have any questions be sure to ask them!

This experience as brought me to the top stress levels of doing programing full time and I can honestly say it wasn’t as bad as I thought I would get sitting at a computer and typing code for 8 hours of day. Over the past two months working, not only has my code syntax improved, but also speed up in typing code. Before doing code would take a me a while and now I can whip it out real fast and get the correct result 99.9% of the time. Since being there I have caught up on my Microsoft .NET and learned a whole new java script framework called ExtJS.

The 9 of us (now down to 8 because of a promotion at a co-worker’s store) have become really close friends and it’s nice meeting people all over this great company. Being at corporate I have met a lot of the corporate employees and field (district and store level) employees who come up to corporate for a variety of functions.

So I am home for a week and while I am not doing work here at home, I am going to try to get another WordPress plugin released (yay!) and update my blog which needs a serious code makeover with 3.0 coming out very soon! Be sure to follow my twitter feed and anything I post here to keep up to date with what I am doing and what is going on in my life.

add_action( 'wp_ajax_nopriv_<ACTION NAME>', <YOUR FUNCTION> );

…as doing…

add_action( 'wp_ajax_<ACTION NAME>', <YOUR FUNCTION> );

… is only for logged in users. So if you have a plugin that operates no matter which way users interface with the plugin, you must provide both action calls to make sure it all gets processed. Helpful tip.

Will be back shortly…

A few things to talk about later… but for now after my day.. 4am awake in NYC (5am but 4am from MN time) it’s been pretty close to 14 hours.

I can say that the documentation on the Woopra site is wrong, but in the process of being updated. The SOAP keys are incorrectly listed. We are going to be using the ‘Global’ query in this example.

Useful URLS:

1. http://api.woopra.com/v0/Analytics?WSDL – Overall Method Listing
2. http://api.woopra.com/v0/Analytics?xsd=1 – Current Methods with the fields needed to query them and in which order.
3. http://api.woopra.com/v0/Analytics?Tester — Run a sample query.

The keys that are valid are:

• website
• apiKey
• type^*
• dateFormat
• startDay
• endDay
• limit
• offset
• filters

^{* Only used if using the ‘getReferrers’ method}

The array must be sent in the order listed above and be excat in the formatting and spelling — otherwise it will not work correctly and you will be a sad panda.

It’s not because of the code or operation, but the way that it is designed. In WordPress we strive to have a great UI and UX team to be able to see the pitfalls of usability before we release WordPress to the masses. vBulletin is not free, so you/I expect a few things including this kind of testing.

Some of the aggravations I been having:

1. Information/Settings is all over the place.
2. Documentation/Help System – No where near complete. Some of the StyleVars have do description of what they change.
3. No “Live” Preview.
4. Not everything is in the StyleVar system to begin  with.

After “7 days” of working on a new design _{(It has taken me more time in reality, but this time does not include all the interruptions I had, or travel or work, etc.)} I have final come to the conclusion that after finishing my new vBulletin theme that the AdminCP which has been the same since vBulletin 3.x does not work for vBulletin 4.x.

One of my friends that is part of the vBulletin community has always asked if I was going to take on the task of redoing the AdminCP area, and I am seriously thinking about it now since vBulletin 4.x AdminCP system sucks. I would do this after I empty my queue.

The faster we can get reports back, the faster we can give you an early present for the holidays and for the New Year!

Translators: You have two weeks to get your translations into the system before Gold. Thanks!

Most of the text is done. All that is left is mock-ups of the design proposal. I should have it submitted to Matt (photomatt) by the next few days after Thanksgiving and then once we talk it over and make any corrections, I will post it here for everyone to review for comments and suggestions on changes.

Once I am done with talking with Matt, hopefully I can start dedicating 100% of my time to re-developing the system for either 3.0.x or 3.1.x release. (3.0.x would be preferable because of the longer cycle) With 2.9.x feature frozen and image editing now added into the system it will be much easier to complete this task.

One thing that was very cool since we already knew almost everyone background meeting everyone was just like lets continue this conversation we been having for years.

At the end of the 2nd day we all got together (the core contributors) to the WordPress code for a group shot. I think it’s the biggest group yet.

WordPress Core Contributors: WordCamp NYC 2009

You can find who is who by checking out the WordPress blog post below. Props to Chris Cochran for the great photo. He caught me with my eyes open.

Shane at WordCamp NYC 2009

Source: WordPress › Blog » Core Contributors at WordCamp NYC.