We signed up for an account just today and are fascinated by the system behind Flattr, being an alternative to classic banner or text ads when it comes to making some money out of your blog.

After your successful registration you need to add funds to your account being able to flattr things on the net you like. The minimum amount to flattr each month is EUR 2,-. At the end of each month, your monthly amount will be shared among all the things you flattred. By adding your own Flattr buttons to your website or blog, others are able to flattr your stuff in return.

ShabuShabu has three invites to share. So if you are interested in beta-testing Flattr, please write a comment to this post and we will send you an invitation code.

Have a look at the following function:

function shabushabu_change_group_tag_position()
{
	global $bp;
 
	if ( $bp->current_component == $bp->groups->slug )
	{
         	$bp->bp_options_nav['groups']['home']['position'] = 20;
	        $bp->bp_options_nav['groups']['home']['name'] = __( 'Activity', 'buddypress' );
 
	        if (  $bp->current_action == 'home' )
		        $bp->current_action = 'group-information';
	}
}
add_action( 'bp_init', 'shabushabu_change_group_tag_position' );

The first thing we need to do is declare the $bp global

global $bp;

To change the position of a tab we need to modify the bp_options_nav array. In this example we change the home tab position on a single group page to 20.

$bp->bp_options_nav['groups']['home']['position'] = 20;

The same way we can change the name of the tabs, like so:

$bp->bp_options_nav['groups']['home']['name'] = __( 'Activity', 'buddypress' );

Now, let’s pretend we created a new tab called Group Information using the Groups API. We already specified that the tab will be the first one, but the Home tab is still the default tab. We can change this by modifying current_action, like so (only on a group page and if the current_action was set to ‘home’):

if (  $bp->current_action == 'home' )
        $bp->current_action = 'group-information';

The only thing left to do is put the complete function into your plugin files and then add it to the bp_init hook

add_action( 'bp_init', 'shabushabu_change_group_tag_position' );

Let us know in the comments if you find this post useful!

A quick look around the net brought up a good few options:

• WP Job Ads (plugin)
• WP Job Board (plugin)
• JobPress (theme)

We actually went so far and bought a copy of JobPress (why re-invent the wheel?), it being a theme and thus giving us more flexibility, just to realize that this wasn’t exactly what we wanted or needed (bummer!). For one, it hadn’t been updated in quite a while. It seemed to be in a pre-WP 2.6 state. Just upgrading the theme to be able to utilize the power of 2.8 would have taken a full day.

We would have had to keep upgrading the theme ourselves as well. It doesn’t look like the author is interested in keeping JobPress up-to-date. It’s not what you’d expect from a product you paid money for. The code wasn’t written that efficiently and some features we wanted, like PayPal integration weren’t fully implemented. Also, JobPress is not GPL. In fact, it seems it doesn’t have any license attached. The author only told us that it was not GPL, but not, what it actually is.

In the end it boiled down to two choices. First, use JobPress, but heavily modify it (for all its disadvantages, it still does, what it’s meant to do). We wouldn’t be able to share the code, it not being GPL, but our job board would be up and running fairly soon, say a week. The other option would be to write our very own job board theme from scratch. It would take a lot longer, but we’d be able to do with it what we wanted, so we went with that choice and JobBoardr was born.

Basically, JobBoardr is a parent-theme, meaning that it can be modified easily through the use of child-themes. You can put all your changes into a separate theme that still uses the templates and functions of its parent-theme. This way none of your modifications get lost during an upgrade of the parent-theme.

There’s a bunch of other features as well, like localization, front-end accounts for both employers and employees, sending job applications as pdf to employers, premium job ads, 7 advanced widgets, an API (so other people can feature job ads on their site), automatic pdf invoice generation for companies posting a job, a complete backend for admins, through which many options can be changed and a few more…

Future features will include a lot of AJAX goodies, an affiliate programme and CV generation for employees, just to name a few. Plus, the job board engine will be GPL compatible. That’s the good news. The bad news is (for you anyways), that we will still need to charge for it. The price will be somewhere between €70 and €100. Our main reason for doing this is that job boards are making money for the people running it.

Here’s a little screenshot from what we have so far (things might change slightly):

At the moment we still consider JobBoardr unstable. The current version is 0.7 alpha. Once it reaches beta stage, we will upload a public hosted version and invite everybody to help test it. As a little incentive, we will give beta testers a discount. The bigger the help, the better the discount.

If you’re interested in helping with the beta testing or just want to be notified when JobBoardr reaches beta stage, then go to JobBoardr and submit your email address.

The features are very similar between the two plugins, which isn’t really surprising. They do the same thing, basically, but just display things in a different way. Read the changelog in readme.txt (included in the download) for a full list of changes.

Again, please let us know if you have any problems, find any bugs or just want to tell us how absolutely fabulous we are… For all of that please use the forum by clicking the link below!

EDIT: You will need the latest SVN version of NextGEN Gallery. A tutorial on how to set up SVN can be found here under Option 2

NextGEN ImageFlow, 118.77 KB

Cheers, Boris

So what’s new since the last beta? Basically it’s two new features. The first one let’s you insert shortcodes much much easier. Up until now you had to either remember all the shortcodes or copy/paste them from somewhere. From the first beta there were a few new shortcodes available, so it got all a bit difficult to remember all the options. Now you can click on the media button in the editor toolbar above the editor and there will be a new tab next to the NextGEN Gallery one. Just enter all your options and the shortcode appears in your editor. It’s just like magic!

The second new big feature is a widget, that lets you add any viewer with any configuration to any widget-enabled area. These widgets are probably less suitable for your normal sidebar, but who says that only sidebars can have widgets, eh? Might be good for a header…

As with any of our beta releases, please let us know any bugs in the forums. If this is the first time you try a beta of version 1.4, then please take 5 minutes and read through the changelog in the readme. There is also an inline help page available (which probably needs to be brought up-to-date after a few more features).

EDIT: You will need the latest SVN version of NextGEN Gallery. A tutorial on how to set up SVN can be found here under Option 2

NextGEN FlashViewer, 145.04 KB

Cheers, Boris

Option 1 – Changes by hand

First of all you will have to change something to a NextGEN Gallery core file, nggfunctions.php. Use FTP to get yourself a copy of that file and open it in your favorite editor, like Dreamweaver. Scroll down to about line 254 until you find these two lines:

254
255

// look for gallery-$template.php or pure gallery.php
$filename = ( empty($template) ) ? 'gallery' : 'gallery-' . $template;

Change these lines so that they look like this:

254
255
256

// look for gallery-$template.php or pure gallery.php
$filename = ( empty($template) ) ? 'gallery' : 'gallery-' . $template;
$gallery     = apply_filters( 'ngg_gallery_object', $gallery, $galleryID );

Then upload nggfunctions.php to your NextGEN Gallery folder in wp-content/plugins/.

Option 2 – TortoiseSVN

Another way to do this would be to work with the latest alpha release of NextGEN Gallery, where Alex has made the necessary changes already. This can be downloaded via SVN from Google Code. First of all you need a copy of TortoiseSVN (Windows only, although I’m sure you could find something similar for a Mac). Install it and then create a new folder somewhere on your computer. Right click on it, scroll down until you hit “SVN Checkout”. In the next window, write this line into “URL of repository”:

http://nextgen-gallery.googlecode.com/svn/trunk/

Leave the rest of the options like they are and click OK. This will compile the latest developement version of NextGEN Gallery for you.

It’s important to note that you cannot use this compiled version as is. SVN adds a lot of files that tell it about little changes in the files, so the next time you want to get the latest files it only downloads what actually changed. To get yourself a working copy you need to export the files like so: Right-click on the NextGEN Gallery folder->TortoiseSVN->Export… Then chose a folder into which to put the exported files and click ok. Now all those little helper files have been removed and you’ve got yourself a working copy which you can now upload to your plugins directory.

How to take advantage of those extra variable values…

Download gallery.php from whatever folder you keep your templates in (either ‘view’ in the NGG folder or ‘nggallery’ in your theme folder). The original looks like this:

19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

<?php if ($gallery->show_slideshow) { ?>
	<!-- Slideshow link -->
	<div class="slideshowlink">
		<a class="slideshowlink" href="<?php echo $gallery->slideshow_link ?>">
			<?php echo $gallery->slideshow_link_text ?>
		</a>
	</div>
<?php } ?>
 
<?php if ($gallery->show_piclens) { ?>
	<!-- Piclense link -->
	<div class="piclenselink">
		<a class="piclenselink" href="<?php echo $gallery->piclens_link ?>">
			<?php _e('[View with PicLens]','nggallery'); ?>
		</a>
	</div>
<?php } ?>

Now change it to look like this:

19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

<?php if ($gallery->show_slideshow) { ?>
	<!-- Slideshow link -->
	<div class="slideshowlink">
		<a class="slideshowlink" href="<?php echo $gallery->slideshow_link ?>">
			<?php echo $gallery->slideshow_link_text ?>
		</a>
	</div>
<?php } ?>
 
<?php if ($gallery->show_simple_link) { ?>
	<!-- SimpleViewer link -->
	<div class="slideshowlink">
		<a class="slideshowlink" href="<?php echo $gallery->simple_link ?>">
			<?php echo $gallery->simple_link_text ?>
		</a>
	</div>
<?php } ?>
 
<?php if ($gallery->show_piclens) { ?>
	<!-- Piclense link -->
	<div class="piclenselink">
		<a class="piclenselink" href="<?php echo $gallery->piclens_link ?>">
			<?php _e('[View with PicLens]','nggallery'); ?>
		</a>
	</div>
<?php } ?>

Lines 28-35 are the link for SimpleViewer. Of course you can add as many viewers as you like or change the HTML around. You can find the other variable values by adding this line to gallery.php and then refreshing your browser (don’t forget to delete this line later on):

<?php var_dump($gallery); ?>

Now, all you need is to download the new beta below and test some features. Of yourse, I’d like to know your opinions, any bugs or just what you liked. Please use the forum post for any bugs by following the link at the end of this post. Cheers, Boris!

EDIT: Please go to this post to download the latest beta release!

BP Xtra Signup, 137.59 KB

There are quite a few new features available. Some aren’t fully functional yet, but that shouldn’t interfere with the normal operation of the plugin. Here’s a short list of new features:

• Settings can now be overridden through custom fields (This doesn’t work for some settings yet!)
• Any viewer can now be set as default NGG slideshow
• 8 new album templates for use in themes (situated in folder /view)
• Notification about new versions
• Color Picker for the backend
• New shortcodes:

  [fv-tags gallery="" width="" height="" viewer="" link="" title=""]
  [fv-thumb id="" width="" height="" viewer="" link="" title=""]
  [fv-rand max="" width="" height="" viewer="" link="" title=""]
  [fv-recent max="" width="" height="" viewer="" link="" title=""]
  [fv-album id="" width="" height="" viewer="" link="" title=""]

Features that might make it:

• Add viewer links on top of galleries, like (View with SimpleViewer). For this I will need to add a filter to NextGEN Gallery. Alex will add the changes to the next NGG version. This feature will become available depending on when this will be released.
• Some extra smaller usability stuff in the backend.
• Reply to this post and suggest a feature. I will pick one and include it!

So far there has been only some rudimentary testing and some things might not work yet as advertised, so installation on a production environment is not recommended. If you would like to test the new version and help us out a little, then you can download it here:

EDIT: Please go to this post to download the latest beta release!

BP Advanced SEO, 83.27 KB

First I was just gonna redesign my personal travel blog Travel-Junkie.com. The more I looked into how WP themes worked the more I realized that themes are just like plugins. Just bigger and in some ways even better. When you start utilizing your functions.php file your theme isn’t only a theme, it becomes a plugin as well.

So, at the moment Ignite is at version 0.1, just at the start of its life. By the time it will be released it will have grown to maybe version 0.3 and be fit to power your WP blog without any major glitches. By the time we have reached version 0.5, hopefully all of those left-over glitches will have been removed and we will release our Ignite Theme Club, which will be built on BuddyPress, bbpress and obviously WP. Basic membership will be free. Premium membership will cost you a little bit (actual price hasn’t been set yet). There will be a community, forums, child themes, Ignite components to download and a fuzzy warm feeling in your stomach.

Now, lets have a look at some of the features:

Plugin Architecture

Ignite comes with an in-built basic plugins system, that works similar to WordPress plugins. Some of those plugins will be included with the theme, others you can download as you need them. Ignite plugins aren’t the same as WP plugins, they are just little add-ons, some of them even for WP plugins, like image or video search. Ignite will be extremely modular. So far there are 25 plugins that extend Ignite functionality.

Plugin Support

Ignite supports a wide range of popular plugins, like WordTube, NextGEN Gallery or All In One SEO.

Only one CSS/JS file!

Ignite lets you add all your CSS/JS files (theme and plugins) into one gzipped, minified file. This means less HTTP requests, which means that your site will respond faster. Should you chose to implement all .htaccess recommendations Ignite will score an 88 (out of 100) with a primed cache at Yahoo’s performance test for fast websites (tested with Firefox’ YSlow extension). The only way to score more is to use a CDN, like Googles AJAX Libraries and reduce HTTP requests by using less background images or combining them in css sprites.

Widgets

Custom built widgets that replace the default WordPress widgets to offer you more options. In addition to that there are 3 more widgets that add other functionality, like post series or postmetadata.

Templates

Many custom templates to make it as easy for you as possible to add extra pages, like an author or category overview.

Special Templates

A templating system that lets you modify almost anything without having to wade through murky code. We have tried to remove as much code as possible from the depths of the Ignite files. These template files can be copied over to your child theme, where you can adjust them without any loss during an Ignite update.

SEO

In-built SEO, from titles, descriptions and keywords to clean URLs, stop words and canonical links.

Hooks & Filters

Almost anything can be hooked into or can have filters applied to it, making Ignite extremely flexible.

Multi Language Support

Ignite is not only fully localized, it has also in-built support for many popular multi language plugins like qTranslate, Polyglot and Language Switcher.

Post Image

Ignite has various methods of ensuring that no blog post comes without an image to display on index and archive pages.

Dropdown Menu

A menu you have full control over. You decide which pages to show in it!

Theme options

Options that help you rather than slow you down and make your site bulky. Less is more, so the most basic version of Ignite ships only with 12 options, all adjustable through the backend. Ignite plugins can add their own admin page and their own options.

By the time the first version of Ignite will be released there will be 5-6 sites (all our personal and commercial sites) to check it out (including this one). All of these themes will have been realized through child themes and will have been redesigned. As we will release these themes we will post about them and how we turned them into Ignite child themes here.

We will also compile a vast documentation about the inner workings of Ignite, the use of child themes and other relevant points of interest, so adjusting Ignite to what you want it to do will become very easy. For everybody not comfortable with PHP, HTML or CSS there will be the premium theme club membership.

We hope that this little taste of Ignite has got you drooling as much as it has us :) We certainly are very excited about the possibilities that Ignite will offer us. Who knows, by the time the first release comes about there will probably be more features for you to get excited about…

Yours truly,
Boris

We hereby proudly announce that one of ShabuShabu´s WP-Plugins found its way into the print media. The current “PC Pr@xis-Sonderheft Nr. 3 – OpenSource – Magazin für freie Software” is totally dedicated to WordPress, being one of the most popular OpenSource Content Management Systems (CMS). On 98 pages the reader finds among other things an introduction to WordPress, its history, hints for professionals, hosting solutions as well as a short overview of the vast amount of existing plugins increasing the functionality of this fantastic CMS.

On page 51 the author is describing NextGEN Gallery, a plugin written by Alex Rabe and NextGEN FlashViewer, a plugin for NextGEN Gallery, written by Boris Glumpler, co-founder of ShabuShabu-Webdesign. The reader gets to know that NextGEN FlashViewer is “very helpful” for “advanced webmasters for implementing interesting flash effects like picture sliders or a rotating carousel”. He is also getting informed, that NextGEN Flashviewer can be downloaded at WordPress.org while a corresponding installation guide can be found at travel-junkie.com.

As you probably know, we have forwarded the above URL to ShabuShabu-Webdesign, leaving travel-junkie.com to its original subject: travelling the world on low budget.

The PC Pr@xis article can be found here as a pdf-file (a profound knowledge of German language would be quite useful).

There are new versions of NextGEN Gallery, NextGEN FlashViewer and NextGEN Imageflow out now. If you haven´t upgraded to them yet, now would be a perfect time of doing so.

Cheers!

Upgrade and installation procedures can be found here