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.

You will now be able to add pictures directly from the editor without having to find the correct URL.

Regarding the problem with the editor load, is due to the cforms II plugin – see this support issue.

If you need the cforms II plugin and Zdmultilang at the same time, I would advise you to deactivate the WP Editor Button support in your general settings (in the cformsII panel) as shown below :

You will notice that there is no time specification for this roadmap as I won’t publish a new version of the plugin until I find it necessary. Some of the functionalities and bug correction are already done but as I said, I will only publish it when tests will prove it rock solid.

• Exclude authenticated users from the stats (depending of an option)
• Add time taken to load the page and SQL queries (in order to optimize your plugins)
• Problem with accents in geolocalisation to be corrected.
• TopX pageviews and TopY referers Widget.
• function to be use in your themes to show pageviews per post.
• Following where your users are leaving.

Do not hesitate to leave a comment for any request or comment so that I will include them in a future release.

Changelog:

• Added default options, when installing the plugin, you won’t have to put the filters yourself, they will be automatically added (if not present).
• Better date calculation, it’s now PHP4 compatible
• Monthly Average (projection made according to the period you selected).
• When you do an upgrade, GeoLiteCity.dat will be erased, if so, the plugin will alert you to download one (if you need this functionnality). It will tell you where to get it and where to put it.
• Links to IP history navigation anywhere an IP adress is displayed.
• Detail of a pageview anywhere a time & date is displayed.
• Google Maps integration (via links) for each geolocalisation. This will allow you to discover new places

As always, don’t hesitate to leave comments and feedbacks.

Just download it here

Changelog :

• Addition of an entry deletion directly from the hour summary view
• Addition of IP deletion. This will delete all visits from a specific IP adress.

Of course, the package is upto date on the Documentation page.

These two new function will allow you to delete spammer visits without overloading your filters, because most of the time spammers won’t come back using the same IP.

Here is a lsit of functions :

• Display a summary of visits (week, month, trimester, semester and year)
• Display Pageviews and visitors with daily precision
• Referring pages
• Used keywords
• Localization of your visitors
• Browser / OS

The statistics are collected and instantly processed, or not, as you can decide this using an option. You can also separate feeds from real pageviews, exclude some IPs from being collected (@home, @work, @school, etc…) and choose to collect robots pageviews or not.

You can download it here : ZdStats Package.

The documentation is here

All this means that I’ll be able to fetch useful statistics directly from my own wordpress installation, I’ll be able to decide the filters in place for Bots/spammers/etc… and will not rely on hidden filters functionalities. Moreover, this means that your filters in this plugin are options ! YOU can decide of what is filtered or not. The more people will share their options, the more reliable the system will become.

The system is built this way, Three options:

• First, a list of IPs excluded from collection (useful for home IP, @work IP, etc…)
• Second, a list of User Agents corresponding to Robots with a name association (example : Mediapartners-Google => Google Adsense)
• The Third is a list of IP adresses considered as spammer or robots with non site friendly UserAgents.

Once these options are set, the data collection is started and allows you to consult statistics

Of course, administration pages are excluded, so are 404 errors. This is a question I ask myself, should I include them with a specific code so that we can find broken links ?

For the moment, only three main functionalities are coded : Summary for a specific period (chosen from a dropdown) with visitors and pageviews. Daily detail hour by hour. And finally, indexation from Search Engines.

I’m giving myself two weeks before publication of the First version of the system, but be aware that it’s already working as it’s installed on this very blog.

Meanwhile, do not hesitate to leave comments here for queries and suggestions so that I can work on them and include them.

Thanks for your support

In order to install the plug-in, just download this archive into your wp-content/plugins folder, unzip it and then activate it using wordpress administration panel.

Once you did that, you just have to edit your theme’s index.php file and add the following code where you want to display the page list :

<?php if (function_exists ('index_pagination')) index_pagination(); ?>

After doing this, you just have to define the css classes to display the page list as you like.
Default class names for pagination are :

• pagination => Default classname for the ul element that will display the list.
• pagination_el => Default classname il for page elements
• pagination_selected => Default classname for currently selected page.

One important this to know about this plug-in is the parameter list that can be used when calling the function.
index_pagination function takes a maximum of 6 parameters, listed below :

1. nb_before => Number of elements to display before currently selected page (if any), default value:3
2. nb_after =>Number of elements to display after currently selected page (if any), default value:3.
3. sep => Separator text, default value : “…”
4. list_class => Css class name to use for ul element (default: pagination)
5. default_class => Css class name for elements within the list (default: pagination_el)
6. selected_class => Css class name for currently selected page (default: pagination_selected)

In the end, it may look like this (depending of your css code) :