theode

Did you ever need to connect multiple language plugins? I know this is a niche, but from my long lasting experience I know that sometimes you need such a thing.
Maybe you don’t like the widgets your translation plugin provides. So you maybe need something else.
Try this if you are in need for a language widget which has no function except to be a widget.
Here is an example:
Imagine you have some people in your company providing their own translation but for some reason you also need machine translations of your content. In our specific case it was the plugin Global Translator and WPML. Of course all these plugins have their own widgets, but getting mad if you try to use them both because their widgets only work with the single plugin. So there was a need for a widget which has no function behind it to simply connect two plugins.
You need to configure the WPML part for the languages with your own translations and the Global Translator part for those without.
In the no function language widget you simply choose the language codes with a comma seperated list. It even works if you need other names for your languages. Just replace the flag to your name for example rename de.png to german.png and use /german as your language base.

No Function Language Widget

With this you can bridge the gap between multiple translation plugins. It is a no function language widget with multiple options.

Casey Bisson

Matthew Batchelder

methnen

camwyn

<ol>
<li>This section needs development.</li>
<li>Adds featured comments selected by editors</li>
<li>Adds ability for users to flag comments</li>
<li>Adds ability for users to fave comments</li>
<li>Adds support for registering new comment types and statuses, similar to WP core’s <code>register_post_type()</code>, see the section on registering custom comment types</li>
</ol>
<h4>History</h4>
Featured comments were originally introduced in bSocial (<a href="https://wordpress.org/plugins/bsocial/" rel="ugc">plugin repo</a>, <a href="https://github.com/misterbisson/bsocial" rel="nofollow ugc">github</a>), but have moved here. New bSocial commenting features will be developed in this plugin.
<h4>In the WordPress.org plugin repo</h4>
Eventually here: https://wordpress.org/plugins/bsocial-comments/
<h4>Fork me!</h4>
This plugin is on Github: https://github.com/misterbisson/bsocial-comments
<h4>Build status</h4>
<a href="https://travis-ci.org/misterbisson/bsocial-comments" rel="nofollow ugc">Master build status at Travis-CI</a>: <a href="https://travis-ci.org/misterbisson/bsocial-comments" rel="nofollow ugc"></a>
<h3>Registering custom comment types</h3>
Custom comment types
<pre><code>`php
</code></pre>
$args = array( 
 ‘labels’ => array( 
 ‘name’ => ‘Faves’, 
 ‘singular_name’ => ‘Fave’, 
 ‘edit_item’ => ‘Edit Fave’, 
 ‘update_item’ => ‘Update Fave’, 
 ‘view_item’ => ‘View Fave’, 
 ‘all_items’ => ‘All Faves’, 
 ), 
 ‘description’ => ‘Comment faves’, 
 ‘public’ => TRUE, 
 ‘show_ui’ => TRUE, 
 ‘admin_actions’ => array( ‘trash’, ‘untrash’, ‘delete’ ), 
 ‘statuses’ => array( 
 ‘feedback’, 
 ‘trash’, 
 ), 
);
bsocial_comments()->register()->comment_type( ‘fave’, $args ); 
 `
Custom comment statuses
<pre><code>`php
</code></pre>
$args = array( 
 ‘label’ => ‘Feedback’, 
 ‘label_count’ => _n_noop( ‘Feedback (%s)’, ‘Feedback (%s)’ ), 
 ‘status_links_show’ => TRUE, 
 ‘include_in_all’ => FALSE, 
);
bsocial_comments()->register()->comment_status( ‘feedback’, $args ); 
 `

No Function Language Widget vs bSocial comments