There are lots of reasons to that, the first one being, time is missing. I’ve been very busy with projects I built for clients around WordPress. I started working on some Android applications and I must say I love making those.

I will probably release my first app within a few weeks (well, when I find time).

In the meantime, I’ve been trying to work on ZdMultilang and fix all these issues you gave back to me but time is a big issue for me, wife, kids and a new job.

Yes, I recently got hired by one of the biggest Video Game company in the World as a Sys Engineer.

I’m also moving houses this month so don’t expect too much updates on the plugins.

By the way, if someone is willing to help on the development of ZdMultilang, you can contact me here and I will facilitate that.

I’m going to drop WordPress slowly as I don’t have much more time to work on that. But I will start making more apps for the Android pretty soon .

Following some of your requests and due to the fact that I had to look in order to make ZdMultilang work with the latest WordPress, Here is the updated article with explanation of how to integrate tinyMCE into your wordpress plugins.

So here is the code you need to include.

add_filter('admin_head','ShowTinyMCE');
function ShowTinyMCE() {
	// conditions here
	wp_enqueue_script( 'common' );
	wp_enqueue_script( 'jquery-color' );
	wp_print_scripts('editor');
	if (function_exists('add_thickbox')) add_thickbox();
	wp_print_scripts('media-upload');
	if (function_exists('wp_tiny_mce')) wp_tiny_mce();
	wp_admin_css();
	wp_enqueue_script('utils');
	do_action("admin_print_styles-post-php");
	do_action('admin_print_styles');
}

Don’t ask me to explain everything, I just found all these details while browsing the admin pages related to posts.

In order to do so, I need YOU. I will make all the improvements and bug fixes based on a priority list that I want you to help me build.
Below is a list of bugfixes and features that will be included in the next release (or two if I release first a version with full 2.8 compatibility)

1. Bug fixes

• Fix home page as a static page handling !
• Fix the save button in WordPress 2.8 Fixed since 1.2.3
• Issue with the Media Upload icon Fixed in the upcoming 1.2.4
• Better handling of permalinks detection (permalink with more than 2 char)

2. Features

• Allow to create different permalinks depending on the language
• Update the zd_multilang_menu function to add parameters (like displaying only some elements)
• Add an option to allow displaying all the languages including the current one in the widget.
• Make a better, up to date F.A.Q / Help page.
• Create a function to get the current language used.
• Handling of Widget title translation.
• Uninstall function with Database cleaning
• Write post in non default language only (find a way to do this…)
• Add a theme switching function according to current language (requested by AMN)
• Translation could have a different date than the original post.
• See if it can work with WP-Print

Now it’s up to you to help me add items to the list. Please read the comments before asking for a feature/bugfix as I will try to update the list as much as possible.

In fact, to include the tinyMCE editor you won’t use the same functions between 2.6.3 and 2.7 releases. More interesting is WP2.7 will need one more function to be able to display the editor.

Most of the time you will want to include this editor when working with posts, or when you want to enable your plugin users to enter information with the Wysiwyg editor (newsletter, advanced widgets, etc…)

WordPress 2.5.x and 2.6.x

Here is how to include the editor in one of your plugin’s admin panel.

1. Include this code in the admin_head hook

   add_filter('admin_head','zd_multilang_tinymce');
   
   function zd_multilang_tinymce() {
   	wp_admin_css('thickbox');
   	wp_print_scripts('post');
   	wp_print_scripts('editor');
   	add_thickbox();
   	wp_print_scripts('media-upload');
   	wp_print_scripts('jquery');
   	wp_print_scripts('jquery-ui-core');
   	wp_print_scripts('jquery-ui-tabs');
   }

2. Call the editor anywhere you need it to be displayed

   	the_editor($content_to_load);

WordPress 2.7

Here is how to include the editor in one of your plugin’s admin panel.

1. Include this code in the admin_head hook

   add_filter('admin_head','zd_multilang_tinymce');
   
   function zd_multilang_tinymce() {
   	wp_admin_css('thickbox');
   	wp_print_scripts('jquery-ui-core');
   	wp_print_scripts('jquery-ui-tabs');
   	wp_print_scripts('post');
   	wp_print_scripts('editor');
   	add_thickbox();
   	wp_print_scripts('media-upload');
   	if (function_exists('wp_tiny_mce')) wp_tiny_mce();
   // use the if condition because this function doesn't exist in version prior to 2.7
   }

2. Call the editor anywhere you need it to be displayed

   	the_editor($content_to_load);

Differences between versions.

As you can see, there is only one difference in the code between both version, but this is a major one as if you don’t call the wp_tiny_mce function, the editor will not work at all.

There are some other differences but mostly in the css classes as the design has been totally revamped. Therefore if you want to mimic the interface on both version you will need to add some classes and divs as you will see when I’ll publish ZdMultilang v1.1.2

By the way, I’m proud to announce that version 1.1.2 of ZdMultilang will be fully compatible with WordPress 2.7 and the interface will look much better in 2.6.3 and 2.7 than right now.

WordPress 2.8

For an updated version of this tutorial using WordPress 2.8, check this post.

I’ve been off for quite a long time on Zen-Dreams and this is mainly due to the fact that I’ve been rebuilding ZdStatistics.

ZdStatistics will be available next week in version 2.0. Why next week ? Simply because I need to test it before release, so it’s been installed on this blog and depending on the results I will get until next week I will improve it as much as I can.

Here is a list of the new features and modifications :

• Changed the flash chart to Google vizualisation so that it loads faster and can be compliant with any browser with javascript support.
• Export data to CSV files so that you can process them like you want
• Check Redirections of pages – do not log them. In fact sometimes a page was counted twice because the user specified an url without the pending / and wordpress did the redirection.
• Display tabs in the admin section optionally
• Search feature !
• Better Spam detection using an anti spam provider (default is spamhaus.org)
• Now recording hits with timezone as specified in your wordpress configuration.
• Geolocalisation is now using Google Maps to display visitors (needs a Google maps API key)
• Using a calendar to choose the time period you wish to see
• Debug option for a better support
  

1. Introduction to plugins
2. Plugin’s skeletton
3. Activation, Hooks & Filters
4. Widgets Definition

1. Widgets definition

A widget is, in fact, a plugin that will allow users to display a block on their sidebar. That being said, there are only one action to use in order to create a Widget.

This action is called widgets_init – therefore you can call it like this : add_action(‘widgets_init’, function_name);

Once you have done this, you will have to register two other functions inside this function_name function only if sidebars are available with your wordpress install.

Here is some code that can do the trick :

function function_name() {
	if ( !function_exists('register_sidebar_widget') || !function_exists('register_widget_control') )
		return;
	register_sidebar_widget(string $name,callback $function);
	// register_sidebar_widget takes the name of the widget and the function that will be used to display it.
	register_widget_control(string $name, callback $function2);
	// register_widget_control takes the name of the widget and the function that will be used to to change options (in the design panel).
}

That’s pretty all you need to know for Widgets. All the rest is non widget specific (options, actions and filters, api calls)

2. Sample Widget

Here below you will find a sample widget in written in fully object oriented php – not there is no option tab. This widget will only display a Simple Hello World with widget title customisable.

/*
Plugin Name: ZenDreams_Sample_Widget
Plugin URI: http://blog.zen-dreams.com/
Description: Sample Widget
Version: 1.0
Author: Anthony PETITBOIS
Author URI: http://blog.zen-dreams.com/
*/
class myWidget {

	function myWidget() {
		add_action('widgets_init', array(& $this, 'init_widget'));
	}

	function init_widget() {
		if ( !function_exists('register_sidebar_widget') || !function_exists('register_widget_control') )
			return;
		register_sidebar_widget(array('myWidget','widgets'),array(& $this, 'widget'));
		register_widget_control(array('myWidget', 'widgets'), array(& $this, 'widget_options'));
	}

	function widget($args) {
		global $wpdb;

		$WidgetTitle=get_option('mywidget_options');
		extract($args);

		echo $before_widget.$before_title.$WidgetTitle.$after_title;
		echo 'Hello World !';
		echo $after_widget;
	}

	function widget_options() {
		if ($_POST['mywidget_options']) {
			$option=$_POST['mywidget_options'];
			update_option('mywidget_options',$option);
		}
		$option=get_option('mywidget_options');
		echo '<label for="mywidget_options">Title : <input id="mywidget_options" name="mywidget_options" type="text" value="'.$option.'" /></label>';
	}
}
$myWidgetVariable= new myWidget ();

So I first needed to create the DAL.

The DAL must stay : easy to use, coherent (meaning no differences between different DBMS) and with no useless features.

So the first thing to do was to create a generic class encapsulating every aspect that will be generic enough to be DBMS not specific. This class is dna.database.class. It also allowed me to define the behavior and structure of inheriting classes.

Talking about inheritance, for now there are only four classes. MySQL, PostgreSQL, SQLite 2 and Oracle. Yes this means that the DNA-Framework will have support for all of these systems and probably more when I’ll create an ODBC class

So, briefly, I started the creation of the class system monday and today, the four classes exists and are able to :

• Execute SQL queries (anything)
• Select and browse through results
• Export as SQL or CSV result of a query
• Import from SQL and CSV
• Fetch various states (queries / dbms)

Below is an example of the same code executed on 4 different DBMS.

MySQL

SELECT * FROM MS_User
    -> anthony@mysql.com
    -> toto@mysql.com
INSERT INTO MS_User (Email) VALUES ('test@MySQL.com')
SELECT * FROM MS_User
    -> anthony@mysql.com
    -> toto@mysql.com
    -> test@MySQL.com
DELETE FROM MS_User WHERE Email='test@MySQL.com'
SELECT * FROM MS_User
    -> anthony@mysql.com
    -> toto@mysql.com
PostgreSQL

SELECT * FROM "MS_User"
    -> Anthony@PostgresQL.com
    -> toto@postgresql.com
INSERT INTO "MS_User" ("Email") VALUES ('test@PostgreSQL.com')
SELECT * FROM "MS_User"
    -> Anthony@PostgresQL.com
    -> toto@postgresql.com
    -> test@PostgreSQL.com
DELETE FROM "MS_User" WHERE "Email"='test@PostgreSQL.com'
SELECT * FROM "MS_User"
    -> Anthony@PostgresQL.com
    -> toto@postgresql.com
SQLite

SELECT * FROM MS_User
    -> anthony@sqlite.org
    -> toto@sqlite.org
INSERT INTO MS_User (Email) VALUES ('test@SQLite.com')
SELECT * FROM MS_User
    -> anthony@sqlite.org
    -> toto@sqlite.org
    -> test@SQLite.com
DELETE FROM MS_User WHERE Email='test@SQLite.com'
SELECT * FROM MS_User
    -> anthony@sqlite.org
    -> toto@sqlite.org
Oracle OCI

SELECT * FROM MS_User
    -> toto@oracle.com
    -> Anthony@oracle.com
INSERT INTO MS_User (EMAIL) VALUES ('test@Oracle OCI.com')
SELECT * FROM MS_User
    -> toto@oracle.com
    -> Anthony@oracle.com
    -> test@Oracle OCI.com
DELETE FROM MS_User WHERE EMAIL='test@Oracle OCI.com'
SELECT * FROM MS_User
    -> toto@oracle.com
    -> Anthony@oracle.com

First, I’m re-writing the DNA-Framework, I don’t know yet what will come out of it, probably something big I’m not sure yet if it will be released as OpenSource framework or not. I’ll decide that when version 1.0 will be ready.

And the other thing is I’m completly rewriting ZdStats with better spam detection and much more realistic filters. Even though I know that my filters are more permissive than google’s, my stats are also much more realistic. Why is that ? Simply because I don’t rely on javascript only, therefore I also count users that come to your website with javascript disabled (or google filtered)

This addition is only limited to the feeds. For example, you will see that at the bottom of this posts nothing special appears on the site, but a copyright will be displayed inside the RSS version of it.

This can also be used to add any HTML code you want, it can be added on top of the post or at the bottom of it.

You will also note that I removed the related content plugin, I didn’t find relevant the correlation made between posts and related content.

Here is a Question to the readers, would you like to see the plugin published ?

[Image credits : eJk]

This version is numbered 1.1.0 because of the number of improvements I made to the plugin. But before to talk about what I’ve changed, I’d like to thank all those who gave me their ideas and feedback on the plugin :

• Impulse for his help on solving a very annoying bug (two flags instead of one)
• Jeremy Clarke for his suggestion on displaying only translated posts
• Eduardo and Ferlo for their view of the SEO against the plugin
• Teneke for the bug due to UTF-8 character encoding
• Emmanuel Georjon for his comments on dashboard integration and other tips.

Changelog

• Added the possibility to switch default languages (meaning: exchange original posts/tags/cats with translated ones)
• Added translate links directly into the manage pages & into the Media zone of page/posts edition
• Added an option to generate permalinks for default language (ex-default behavior was always yes)
• Changed default character set as UTF-8
• Added an option to add “Translate with Google Translate” to untranslated posts
• Added an option to hide untranslated posts if they exists (ex-default : show all posts)