Every now and then a client is irritated by the fact language names appear in their native language and are not localized properly. An example would be:

Sorry, this entry is only available in Български.

My first encounter with this problem ended up hard-coding some lines for code into the plugin inself. After some time I needed to update the core and the plugin and totally forgot I did something there. Of course I lost my changes. With a better understanding of WordPress and the concepts it’s based on I once again went for that task. I was able to hook to qTranslate loading proccess at the point when it determines the language of the loaded page and apply its own localization methods to accomplish my goal.

First thing you need to do is to change your language name so it uses the qTranslate Quicktags.

qTranslate – Edit language screen

The following piece of code will set filter to the qtranslate_language hook and kinda use it as an action rather than a filter. Tricky part here is that qtranslate_language is very early hook. It fires upon plugins_loaded action. This means theme’s functions.php is no good in this case. To be able to hook to it we need to place this code into a plugin.

While creating a plugin may be an overkill for a several lines of code, a MU plugin seems far more suitable for the purpose. It loads before any other regular plugin and guarantees the availability of every single one action and filter set in plugins.

1. Go to your /wp-content/mu-plugins/ directory. If it doesn’t exists on your install create it.
2. Create a qtranslate.mu.php file for example (may be any name) and place the code below into that file.

<?php
function qtrans_translate_lang_names( $language ) {

 if ( is_admin() && $_GET['page'] == 'qtranslate' )
 return $language;

 global $q_config;
 $q_config['language_name'] = array_map( 'qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage', $q_config['language_name'] );

 return $language;
}
add_filter('qtranslate_language', 'qtrans_translate_lang_names' );

Now your language names should be localized in every page even admin screens, except qTranslate Settings pages.

The post qTranslate – Localize language names appeared first on Zlatko Zlatev.

I hardly can recall a dicent WP theme having nicely working (and looking) comment template. If that’s the case for you would probably like to try the Jetpack Comments extension as a module of the Jetpack plugin for WordPress. Automattic is providing some of the WordPress.com awesomeness as a plugin for self-hosted installations.

To get to the point I will suggest a way to support JetPack Comments in themes. The important thing to know is this module depends exclusively on the comment_form template tag. If your comments.php is not using it, you won’t get Jetpack Comments working.

How to get it working without completely annihilating your comments template.

<!-- just after walking existing comments -->
<div id="respond">
<?php if ( did_action( 'jetpack_comments_loaded' ) ) : ?>
<?php comment_form(); ?>
<?php else: ?>
<!-- here comes default theme's comment form -->
<?php endif; ?>
</div>

That’s how i enabled Jetpack Comment here using the Roots Theme where comment_form wasn’t used also. Now if I need to disable Jetpack for some reason Roots’ default comment form will kick in.

The post Support JetPack Comments in WordPress themes. appeared first on Zlatko Zlatev.

    // Set author_name as current user's nicename to get correct posts
    $posts_query->set( 'author_name', $user->user_nicename );

This could be useful if you want to show user’s blog posts as the query_var above tells WordPress to do exactly that. If WordPress fails to return posts $wp->handle_404(); comes along and sets the 404 despite the fact bbPress is trying to prevent it earlier on parse_query action.

I rolled my own fix.

function bbp_fix_users_404_headers() {
    if ( ! function_exists( 'bbpress' ) ) return;       
    $bbp = bbpress();

    if ( !empty( $bbp->displayed_user ) && is_404() ) {
        global $wp_query;
        $wp_query->is_404 = false;
        status_header( 200 );
    }
}
add_action( 'wp', 'bbp_fix_users_404_headers' );

Personally i put these in MU file as i often need to set hooks before plugins’ run-time. For this one theme’s functions.php is OK too.

The post bbPress 2.x – Cure 404 header in Users Profiles appeared first on Zlatko Zlatev.

I’ve put together a plugin to do what the snippet above used to do. I believe it’s far more bug free than its predecessor so please use it instead. Plugin should work with Gravity Forms 1.6.2+ so no guaranties for earlier versions!

Download Gravity Forms Upload Rules

Original Post

There are already a couple of projects that needed file upload functionality (image upload to be specific) so we needed a solution for file size and image dimensions limitations. To be honest I was quite surprised when I found out GravityForms isn’t offering such functionality by far. It’s offering great hooks though.

function public_news_image_validation( $valid_obj ) {
  if ( empty( $_FILES ) ) return $valid_obj;
  $form_id = $valid_obj['form']['id'];
  $formFields = &$valid_obj['form']['fields'];
  $page_number = GFFormDisplay::get_source_page( $form_id );
  foreach ( $formFields as &$field ) {
  if ( $page_number > 0 && $field["pageNumber"] != $page_number ) continue; //paged form scenario - only validate fields that are on current page
    if ( in_array( 
        ( $field_type = RGFormsModel::get_input_type($field) ), 
        array( 'fileupload', 'post_image' ) 
      ) 
    ) {

      $field_id = $field['id'];
      $input_name = 'input_' . $field_id;

      if ( $field['failed_validation'] ) return $valid_obj;
      $file_info = RGFormsModel::get_temp_filename( $form_id, $input_name );
      $temp_filepath = RGFormsModel::get_upload_path($form_id) . "/tmp/" . $file_info["temp_filename"];

      if ( file_exists( $temp_filepath ) ) {
        $bytes = filesize( $temp_filepath );
        $dims = @getimagesize( $temp_filepath );
      }
      elseif ( isset( $_FILES[$input_name] ) && !empty( $_FILES[$input_name] ) )  {
        $bytes = $_FILES[$input_name]['size'];
        $dims = @getimagesize( $_FILES[$input_name]['tmp_name'] );
      } 
      else return $valid_obj;
      $max_size = 1024*300; // 300kb
      if ( $bytes > $max_size ) {

        unset( RGFormsModel::$uploaded_files[$form_id][$input_name] );
        unset( $_FILES[$input_name] );
        $field['failed_validation'] = true;
        $field['validation_message'] = sprintf( __( 'File upload size (%s) exceeded', 'gravityforms' ), $max_size/1024 . 'kb' );
        $valid_obj['is_valid'] = false;
        return $valid_obj;
      }
      if ( ! empty( $dims ) && is_array( $dims ) ) {
        list( $up_width, $up_height ) = $dims;
        if ( min( $up_width, $up_height ) < 300 ) { //smallest image size should be at least 300px

          unset( RGFormsModel::$uploaded_files[$form_id][$input_name] );
          unset( $_FILES[$input_name] );
          $field['failed_validation'] = true;
          $field['validation_message'] = sprintf( __( 'Image should be at least %s', 'gravityforms' ), '300x300 (px)' );
          $valid_obj['is_valid'] = false;
          //return $valid_obj;
        }
      }
    }
  }
  return $valid_obj;
}

add_action( 'gform_validation_3', 'public_news_image_validation' );

EDIT: Added paged forms compatibility.

The post Limit file size and image dimensions in Gravity Forms upload fields appeared first on Zlatko Zlatev.

class My_Network {

	public static function clean_admin_bar() {
		global $wp_admin_bar;

		if ( count( $wp_admin_bar->user->blogs ) > 1 || is_super_admin() ) return;

		$wp_admin_bar->remove_menu( 'my-sites' );
	}
}
add_action( 'wp_before_admin_bar_render', array( 'My_Network', 'clean_admin_bar' ) );

We basicly check wheather user is super admin or is registered to more than one site. If it’s not we wipe the whole “My Sites” stuff leaving the admin bar as it’s in any regular WordPress installation.

The post Get rid of “My Sites” admin bar menu in MultiSite appeared first on Zlatko Zlatev.