Features:

Categories / Tags SEO Settings Localization.

You can localize:

• Term title;
• Breadcrumbs title;
• Canonical URL;
• Meta description;
• Meta keywords.

Post SEO Settings Localization

• Post title;
• Breadcrumbs title;
• Focus keyword;
• Meta description;
• Meta keywords and redirect.

SEO Variables Localization

Title templates localization.

XML Sitemap Localization

All XML sitemaps ( root, post, tags, pages, etc ) localization.

Grab Stella for “SEO by Yoast” for $8.95 in our store! Make your website visible for the search queries in the languages you want!

Source: Stella Addon For “SEO by Yoast” Is Out! by Theme.fm

Localization of custom strings

Use stella_translate_string function to localize strings on the site depending on language.
NOTE: requires Stella 1.3

Usage

stella_translate_string( $filter_name, $original_string, $translations_array );

Parameters

$filter_name
Name of filter, which will be localized.

$original_string
String Value.

$translations_array
Array with translations. In keys – language code ( en, de, ru, etc ). In values – corresponding translation.

Examples

First example will be about image source. Imagine you have some picture in your theme. You may have something like this:

 <?php $template_uri = get_template_directory_uri();
       echo "<img src='$template_uri/images/flower.png'/>";
 ?> 

Ok, you want another picture, for instance, in Russian and German languages. First, add filter to picture filename:

 <?php $template_uri = get_template_directory_uri();
       $picture_filename = apply_filters( 'picture_filename', 'flower.png' );
       echo "<img src='$template_uri/images/$picture_filename'/>";
 ?> 

Second step: use stella_translate_string function.
Add this code to functions.php in your theme:

add_action( 'stella_init', 'stella_functions' );
function stella_functions(){
    stella_translate_string( 'picture_filename', 'flower.png', array( 'ru'=>'flower-ru.png', 'de'=>'flower-de.png', ) );
} 

That’s all! You got localized picture.

Now let’s look at another example.
In Stella 1.3 we have added filters to language names, so you can localize them. Imagine you have two languages: English and Russian. Lets make Stella language switcher widget more friendly. Add this code to functions.php in your theme:

add_action( 'stella_init', 'stella_functions' );
function stella_functions(){
    // Here we tell stella to localize language name 'English'
     stella_translate_string( 'stella_lang_name', 'English', array( 'en'=>'English', 'ru'=>'Английский', ) );
    // .. and here to localize language name 'Russian'
     stella_translate_string( 'stella_lang_name', 'Russian', array( 'en'=>'Russian', 'ru'=>'Русский', ) );
    // ... and widget title
     stella_translate_string( 'stella_language_widget_title', 'Language', array( 'en'=>'Select language','ru'=>'Выберите язык', ) );
} 

That’s how the switcher looks in two languages:

NOTICE: You can use stella_translate_filter ( do not need to pass $original_string value ) instead stella_translate_string since 1.3.48!

I hope you will find this tool very useful. Please send us your suggestions. Thanks ;)

Source: Stella API reference: Custom Localizations. Part 3 by Theme.fm

What’s new:

• Filters to language names – ‘stella_lang_name’;
• New API function: ‘stella_translate_string’.

Read our new tutorial “Stella API reference: custom localizations. Part 3” to see how they work ;) By the way, be sure to check two previous articles (part 1, part 2) on Stella API, they’re really great if for plugin customization.

Fixed: 

• Correct localization of website title;
• WordPress in a subdirectory ( not root directory of web server );
• Query vars mode ( non-permalinks situation ).

So, thanks again for your feedback! We will keep bringing new features, hope you’re enjoying our plugin. Bye =)

Source: Stella localization plugin for WordPress hits version 1.3 by Theme.fm

Howdy!
I’m continuing to tell you about Stella API. Today we will be looking at post thumbnails.

Localization of custom post thumbnails

If you have more than one post thumbnail ( for example using “Multiple Post Thumbnails” plugin) localize it with stella_translate_custom_thumbnail function.

Usage

 stella_translate_custom_thumbnail( $label, $id, $post_http://theme.fm/?p=4673&preview=truetype );

Parameters

$label
The name of the post thumbnail to display in the admin metabox

$id
Used to build the CSS class for the admin meta box. Must be the same as in thumbnail, which will be localized

$post_type
The post type to register this thumbnail for. Must be the same as in thumbnail, which will be localized

Example

Using “Multiple Post Thumbnails” plugin you must already have something like this:

 if (class_exists('MultiPostThumbnails')) {
    new MultiPostThumbnails( array( 'label' => 'Really big image', 'id' => 'really-big-image', 'post_type' => 'post', ) );
} 

Ok, now tell Stella to localize it:
Add this code to your functions.php:

add_action( 'stella_parameters', 'stella_functions', 1 );
function stella_functions(){
    stella_translate_custom_thumbnail( 'Really big image', 'really-big-image', 'post' );
}

 
NOTE: use ‘stella_init’ action instead ‘stella_parametres’ since Stella 1.3 version.

Thanks for your interest in Stella. Please, don’t be shy and leave comments on what else you want to localize. Stay tuned, goodbye!

Source: Stella API reference: Custom Localizations. Part 2 by Theme.fm

localization of custom single input metabox

If you have some single input metaboxes, for example, links to video, localize it using

stella_translate_custom_field  function. Lets look a bit closer:

Usage

stella_translate_custom_field( $id, $field_name, $title, $post_type, $context ); 

Parameters

$id
HTML ‘id’ attribute of the edit screen section. Must be the same as in metabox, which will be

localized

$field_name
Label of the input field

$title
Title of the edit screen section, visible to user

$post_type
The type of Write screen on which to show the edit screen section

$context
The part of the page where the edit screen section should be shown

Example

Imagine you already register metabox. So you have something like this:

add_action( 'add_meta_boxes', 'add_single_input_meta_box', 1); 
function add_single_input_meta_box(){ 
   add_meta_box( 'video', 'Link url', 'add_fields', 'post', 'normal' ); 
}
function add_fields(){ 
    global $post; 
    $link = get_post_meta( $post->ID, 'link', true );
    $wp_nonce = wp_create_nonce( 'meta_noncename' );
    $meta_html = <<<meta_html
    <input type="hidden" name="meta_noncename" id="meta_noncename" value="$wp_nonce" />
    <div class="project-options">
       <div class="clearfix">
         <label>Link:</label>
         <input type="text" name="_link" value="$link"/>
       </div>
    </div>
    meta_html;
    echo $meta_html;
}

Now, lets tell Stella to localize metabox.
Add this code to your functions.php:

add_action( 'stella_parameters', 'stella_functions', 1 );
function(){
    stella_translate_custom_field( 'video', 'link', 'Link url', 'post', 'normal' );
}

NOTE: use ‘stella_init’ action instead ‘stella_parametres’ since Stella 1.3 version.

That’s it. Next post will be about post thumbnail localization. See you later!

Source: Stella API reference: Custom Localizations. Part 1 by Theme.fm

Happy weekend, everyone! We got new updates for WPMU Bar and Stella! And from now on you can try Stella – it now has it’s own Demo-Stage!

Stella just got it’s own demo stage

The part we like the most is a Demo Stage for Stella – our multilingual content management and localization WordPress plugin. Our readers asked for it, so we are rolling out demo stand v. 1.0. We will improve it basing on your feedback – please, leave your comments! You can see what it looks like and play with it a bit by logging in (user: demo / pass: stella). By the way, the demo stage uses full version of Stella.

Free version of Stella plugin for WordPress

It’s here, at last! Free version of Stella plugin for WordPress a great tool for localization if you got a small website and want to use only two languages. This is great for bloggers, because it has all the basic functionality and remains simple and fast, just like the full version. You can see the limitations in the table below.

Free Version of WPMU Bar

We also got a free version of WPMU Bar plugin for WordPress. Now readers can easily navigate through your WordPress multisite. It’s an upper bar with the drop down menu of available websites list =) Free version has no social sharing buttons, doesn’t support custom logo and background. The main functionality is still there, as well as the bar opening and closing animation. The free version of WPMU Bar Plugin for WordPress can be found at wordpress.org ;)

Source: Free Versions of Stella and WPMU Bar Plugins for WordPress. Demo Stage for Stella! by Theme.fm

After we learned how to create new roles and played with users’ capabilities, I’d like to tell you about the user area. This is a place on the website, available to blog users or customers only. Imagine that we need an online shop, where a registered user can download your price list or you need to display your custom information to various users, there could be dozens of different scenarios. This features makes your website more user friendly, with additional options. By the way, we already had a similar project and I well, it was really interesting to work on it. So without further do – let’s start!

User Authorization Through a New Custom Login Form

To create a custom login form at your custom page, first of all you need to make a simple HTML form, like this:

Class Custom_Login {
    function __construct(){
        add_shortcode( 'custom-login-form', array( $this, 'view_login_form' ) );
    }

    function view_login_form(){
        $home_url = home_url( '' );
        $redirect_url = home_url( 'profile' );
        echo <<<HTML
        <form id="login" name="loginform" action="$home_url/wp-login.php"" method="post">
            <dl>
                <dt><label>Username:</label></dt>
                <dd><input type="text" value="" id="form_user_email" name="log" /></dd>
            </dl>
        <dl>
                <dt><label>Password:</label></dt>
                <dd><input type="password" value="" id="form_user_password" name="pwd"/></dd>
        </dl>
            <div>
                <input type="submit" name="wp-submit" id="wp-submit" value="Log In" tabindex="100" />
                <input type="hidden" name="redirect_to" value="$redirect_url" />
                <input type="hidden" name="testcookie" value="1" />
            </div>
        </form>
HTML;
    }
}
new Custom_Login();

This form sends data to wp-login.php page, which, in turn, authorizes or redirects user to login page. This is a very simple method to use, we’re just creating the form and submitting it to the correct address, WordPress does everything itself and it’s really cool! If you paid attention, you noticed that login form uses hidden input field named “redirect_to” to proceed user to profile page after logging. You can redirect anywhere, but in this piece of code I used a profile page (but it’s not created yet).

Ok, everything here is clear. Please pay attention to input names, WordPress uses only this kind of names. By the way, an input named testcookie is used to check browser cookie support. You can wrap this html code in a theme template or a widget, but I decided to call this form with a shortcode. Therefore, now we go to the dashboard and create a new page named “Login Page” with one shortcode “[custom-login-form]”. Voila, everything works! Now, let’s move to the next chapter.

Create User Area

Well, at first let’s define a user area is. It’s a simple page which shows user’s personal data. For example, suppose that the address of this page will be {host_url}/profile. So, when users visit a page with the address /profile, they should see their personal info. Okay, but how can we do it ?

We can wrap this script into a plugin, or use as a page template. In my opinion, the page template is the easiest, and not so difficult to support. Put this file into your theme (for example: page-profile.php).

<?php
/**
 * Template Name: User profile page
 */

get_header();

if ( !is_user_logged_in() ) {
wp_die('Access Denied!');
}

get_footer();

Actually, almost everything is done, most of the code for your custom profile is written. On the profile page, first we need to check whether a user is authorized or not.

NOTE: is_user_logged_in() – this function returns boolean values. ‘True’ if user is logged in, ‘false’ if not.

After that,  we can show required information to all users. Remembering the previous article, we can display various information for different roles. After the all checks, we get user data and display it:

<?php
/**
 * Template Name: User profile page
 */

if ( !is_user_logged_in() ) {
    wp_die('Access Denied!');
}

get_header();

$user = wp_get_current_user();
$current_role = array_keys($user->wp_capabilities);
$current_role = $current_role[0];

switch ($current_role) {
    case 'author':
        // content for author
        break;
    case 'editor':
        // content for editor
        break;
    case 'contributor':
        // content for contributor
        break;
    default:
	 // content for other roles
	 break;

}

get_footer();
?>

Now we need to create a new page in your dashboard and assign it to our profile template – ‘User profile page’. Custom user profile page is good, but some users don’t really need to see it, so let’s hide the dashboard. So, how to deny access to dashboard for certain users or roles ?

add_action('admin_init', 'denied_access');

/**
 * Denied access to admin panel for non-admin users
 */
function denied_access() {
	$user = wp_get_current_user();
	$current_role = array_keys($user->wp_capabilities);
	$current_role = $current_role[0];
	if ($current_role != 'administrator' && $current_role != 'custom_administrator')
		wp_redirect( home_url() );
}

// if you need, this hide the admin bar
add_filter('show_admin_bar', '__return_false');

Conclusion

This brings us to the end of the second part in the series. Well, guys, today we’ve cleared up what else can we do with WordPress users. We’ve created custom login form with the help of shortcode and we have also looked how to create a user’s profile page with a few simple codes.

I hope you enjoyed reading my article and learnt something new. Please, feel free to leave your feedback below. Have a nice theme!

Source: WordPress Users (Part II: User Area) by Theme.fm

Among all, WordPress Dashboard shows most recent updates and activity at your website. It’s nice to have useful things at hand, so let’s expand this functionality a little and create a custom widget for the WordPress Dashboard.

Today we’ll create a custom widget which displays the latest tweets from a custom user.
To do this, we use the wp_add_dashboard_widget function to register a new dashboard widget for your blog.

wp_add_dashboard_widget(
    $widget_id,
    $widget_name,
    $callback,
    $control_callback = null
)

Getting Started

Let’s add a simple new widget to WordPress dashboard. First, open your plugin or functions.php file and write something like this:

add_action( 'wp_dashboard_setup', 'twitter_dashboard_setup' );
function twitter_dashboard_setup() {
    wp_add_dashboard_widget(
        'twitter-dashboard-widget',
        'Recent Tweets',
        'twitter_dashboard_content',
        $control_callback = null
    );
}

We set the function twitter_dashboard_setup that adds a widget with twitter-dashboard-widget id, and name it “Recent Tweets”. Then we hook it into the dashboard setup process, where twitter_dashboard_content is the callback function with actual contents of our widget. Here’s what the function looks like:

function twitter_dashboard_content() {
    echo 'Hello, World!';
}

There – we just told twitter_dashboard_content() function to say “Hello, World!”. And that’s it! Go to you admin main page – you can see our new widget at the bottom of the page. Just drag it around and place wherever you want!

Output latest tweets

We just created a dashboard widget – now let’s make it show something useful! Specifically, the latest tweets from custom user. Do do this, we will use GET statuses/user_timeline API from Twitter, to load tweets, and twitter-provided script and render them on the widget.

To put these scripts in WordPress, we will use admin_enqueue_scripts action hook to target our scripts to main WordPress admin page. Let’s write a function with hooks, that checks current page and loads scripts only when needed.

add_action( 'admin_enqueue_scripts', array( &$this, 'dashboard_engine' ) );
function twitter_dashboard_engine( $hook ) {
    if( 'index.php' != $hook )
        return; 

    wp_enqueue_script(
        'twitter_blogger',
        'http://twitter.com/javascripts/blogger.js',
        null, null, true
    );
    wp_enqueue_script(
        'twitter_user_timeline',
        'http://twitter.com/statuses/user_timeline/themefm.json?callback=twitterCallback2&count=3',
        null, null, true
    );
 }

Of course, you can change themefm to whatever you want ;) Also, you can set the number of output tweets by changing count number. Now we need to rewrite twitter_dashboard_content() function with specified in twitter-provided script structure. Exactly, we need to specify ul list with twitter_update_list id. Below, you can find the final version of the code listing.

add_action( 'wp_dashboard_setup', 'twitter_dashboard_setup' );
add_action( 'admin_enqueue_scripts', 'twitter_dashboard_engine' );
function twitter_dashboard_setup() {
    wp_add_dashboard_widget(
        'twitter-dashboard-widget',
        'Recent Tweets' ,
        'twitter_dashboard_content',
        $control_callback = null
    );
} 

function twitter_dashboard_content() {
    echo '<ul id="twitter_update_list"><li>&nbsp;</li></ul>';
} 

function twitter_dashboard_engine( $hook ) {
    if( 'index.php' != $hook )
        return; 

    wp_enqueue_script(
        'twitter_blogger',
        'http://twitter.com/javascripts/blogger.js',
        null, null, true
    ); 

    wp_enqueue_script(
        'twitter_user_timeline',
        'http://twitter.com/statuses/user_timeline/themefm.json?callback=twitterCallback2&count=3',
        null, null, true
    );
}

Conclusion

Congratulations – you’ve just created your own WordPress dashboard widget! Thank you for reading, I hope you like this tutorial and everything was clear enough and easy to understand. Feel free to ask questions in comments, and don’t forget to fan our page on Facebook!

Source: WordPress Tutorial: Create Your Custom WordPress Dashboard Widget by Theme.fm

As we once mentioned, creating your mobile app is not the only challenge for an indie developer. In fact, development is fun, if you love it! But after your app is all ready and published, it needs promotion, and a place where you can showcase your app out there on the Net. Here comes Social Media. It helps you spread the word, informing people and creating awareness… Does it help? Definitely. Still, it would be nice to get a showcase platform, that lets you present you app. We know it, we’ve got our own apps, and we want to help you out!

We are proud to present you TheStore.fm – a simple service that instantly creates a landing page for your iPhone app! It’s a little website that lets you showcase your app just in a few steps: sign up, fill up the fields, publish. As a result, you get a clean storefront page for your app. No worries about hosting, domain name purchase, setting up your server or any other routine things. Find out about other features:

We love TheStore.fm for it’s extreme simplicity. Let’s follow some steps to see what TheStore.fm has to offer!

Let’s say you got an app called “Theme.fm” =) The first step would be signing up to create an account – just enter your email address.

Hurry up and check your email: your password just arrived! Log in to your WordPress dashboard – just like at any other WP website: http://thestore.fm/your-app-name/wp-admin. In our case, the link would look like http://thestore.fm/themefm/wp-admin.

Then, you need to fill the page with your app info. This would be step two. As you can see – the process is as simple as ever. And, you probably have all the descriptions and slogans, since you submitted your app to the AppStore =)

Edit the price tag, add a link to the AppStore, upload your app screenshots, and edit the description of your product.

That’s it! You get a perfect webpage to showcase your app. Save it and share the link! And it’s completely free!

We are excited to launch TheStore.fm – a simple platform that instantly creates a beatiful landing page to promote your iPhone app.

Definitely, we are not stopping here: more features for the app showcase platform are on the  way. In the next updates, we plan to include iPad showcase layout, portrait and landscape, social sharing buttons, domain mapping – in case you already have a domain name registered, – and of course,  more themes for your landing pages to choose from!

Create your pages, enjoy – and don’t hesitate to let us know your suggestions on how we can improve TheStore.fm!

Source: TheStore.fm – Instant Storefront for Your iPhone App by Theme.fm

Great news for our plugins users! New versions of  WPMU Bar (ver 1.1) and Stella (1.2.37) plugins support automatic updates from our server! It is just like the standard WordPress update:

To get the latest version just click “update now” and voilà, here it is!

Once more, we are happy to update our beloved Stella Plugin for WordPress. It allows you to seamlessly manage your multilingual content via tabs in the standard “Edit Post” page.

1. Step one: select languages you want to use in your blog.
2. Step two: fill your tabs with related content.
3. Step three: click “Publish”.

Piece of cake! And it’s just the tip of the iceberg =)

See what’s new in Stella 1.2.37 after the break.

First of all, we improved our widget. You can now localize the title:

We also changed options page a bit: we got a new “Display empty field notices” switcher. Turn it off if you wouldn’t like the plugin to remind you of the empty fields.

At last, we’ve fixed the following bugs:

• Search bug;
• Menu localization bug;
• Post localization bug (the issue with “Transfer default language content”).

Source: New Version of Stella! + Automatic Updates for our Plugins by Theme.fm