Its offline because I’m simply taking a break away from this business to work with a social media company not affiliated with real estate or real estate scripting.  By taking a break away from all the very strange and bizarre attacks from members of the OR forums I’m able to reduce my stress level by not partaking in their antics.

More than a year ago I was bitten by a nasty spider that caused some very serious infection issues and the break will allow me to recover faster as well.  I do still map out and build MLS integrated solutions using either RETS or IDX applications. I’m just not active in the freelance side of the business as it relates to doing design work at this time.

Now a few people have made comments about this little assault by the OR crew as a few months back I had to deal with reckless accusations about some of the products we publish. Any and all products we design specifically for use with Open-Realty® were pretty much put under attack. The reasons are still rather bizarre and not fully clear to me but what many tend to agree with is that jealousy is a painful emotion not easily overcome by those who are truly insecure. The assault, threat to sue (which I still laugh my ass off about) and the attempt to hijack all my code just burned me out and opened my eyes to some of  “People” in this industry.

Had we developed a half dozen tools specifically for use with WordPress, Drupal, Joomla or any other open source application we would likely have received some level of praise and appreciation by the community. However, with the Open-Realty® team this has proven not to be true as it does appear they do not share the spirit or ideology of the open source community.  Giving credit where credit is due is not really appear to be a concept they are willing to embrace.  In my eyes and from my perspective you don’t open up an application for contribution, ideas and member oriented support only to spit in their face because you fail to monetize it properly. So I decided to just quit for a while and regain perspective.

More on the big motivating factor.

It is interesting to note that the individual whom started these events a few months back is proving our point rather boldly.  Chad, the owner of WPRealty, had refunded a person their money after he realized it wasn’t just impossible to help this person, it was counter productive since the guy had literally zero experience in web development or management.  For that reason I wasn’t really surprised to read the frustrations from Ryan (aka the_sandking)  regarding this individual.  To me, its 100% clear when you have to respond to this loose cannon in a public forum whereby threatening to ban him if he didn’t listen to direction affirms our position for sending him packing.  Now maybe the OR team gets the point.  After all, this is the same crap we had to deal with before calling no joy and refunding the guys $30 which netted us brutal or should I say LIBEL abuse at the hands of the Open-Realty® forum administrators.

I’m keeping my blog until I figure out what to do with it and in the mean time removing all reference to Open-Realty® in terms that would even casually lead someone to believe that any post made is defamatory in nature.

Recommended IDX RETS MLS providers for WordPress, OpenRealty, Drupal and Joomla

For anyone interested in having their MLS feed for either IDX or RETS installed in their sites you should contact the following people depending on your needs.

WordPress MLS Integration with IDX or RETS

If you need to have your real estate listings put into WordPress I would suggest contacting WPRealty.org which is fully capable of providing this as a service for an exceptionally affordable price.  Alternatively UltimateIDX has a solution that will marry into almost any solution known including WordPress and how UltimateIDX differs is predominantly in the area of CRM related features for contact and lead management. UltimateIDX is only in 8 primary markets at this point but they map and add new markets with greater frequency now that they have moved the company to Las Vegas Nevada. Currently they are mapping for most southern states and California in addition to their existing markets.

OpenRealty MLS Integration with IDX or RETS

To put MLS listings into OpenRealty 2.5.6 – 2.5.8 you should contact WPRealty.org because they have the widest collection of scripts designed for this purpose that I’m aware of. Since WPRealty frequently builds open source real estate websites they are better suited in my opinion to handle your custom IDX / RETS solution.

Drupal Integration with IDX or RETS

For integrating your Drupal site with the IDX or RETS feed again I’d suggest WPRealty.org if your desire is to have your own stand alone solution where you are not obligated to a proprietary solution.  UltimateIDX is ideal for this. You get integration and full CRM features for sales and lead management.

Joomla Integration with IDX or RETS

Joomla is a great solution for Real Estate Websites and a few people come to mind when it comes to components specifically designed for Joomla 1.5.12+  The first component is our own which is titled JRealty and you can acquire a free copy by contacting the WPRealty group.   If however you require the integrated sales and lead management then again, I suggest UltimateIDX.

Each company has their strong points, two of them I know of intimately because I’ve been on their development team for years.  One thing strange about this business is the underlying loyalties that most people are not even aware exist.  Its the kind of business where everyone knows something about the other guy. Well here is the contact details list of those recommended solution providers I know something about.

UltimateIDX IDX / RETS Solutions
The UltimateIDX literally works with any solution I’ve encountered ideally suited for open source applications including those above mentioned along with Drupal, B2 Evolution and even Type Pad. UltimateIDX has a pretty good position in a niche market that provides MLS empowered type back office integration with most open source solutions. I’ve personally built dozens of sites using UltimateIDX and have yet to find a single client that regretted it. UltimateIDX is a paid solution requiring you to host on either their servers or those they have tested to support real estate type websites. UIDX is a grade 1 option.
http://www.ultimateidx.com

WPRealty WordPress Joomla OpenRealty Solutions
WPRealty is branded and serviced under many different titles and company site headings.  The team has many different product variants and has been building OpenRealty, Joomla and WordPress sites since the birth of each of those applications.  The team members are strong supporters of open source applications and can provide professional grade solutions at a fraction of the cost for similar proprietary ones. WPRealty is a grade 1 option.
http://www.wprealty.org

I’ll be back in full swing sometime in June 2010.

What if OpenRealty were to follow a paid support model like we opted for with WPRealty? Would it help or hurt OpenRealty in terms of the product overall? I was in this discussion recently with a friend of mine as we discussed a post made by pbFlash some time ago about the lack of financial support for OpenRealty over the years.  I had mentioned that if it were my decision, I would offer standard community support for OpenRealty in the forums as they now do but would also extend a type of preferred support license in order to finance the development of the application.  Having built WPRealty with a forked variant of OpenRealty, had it not been for support licenses, many bugs and features may not have been fixed so promptly. Here is my logic behind this notion regarding OpenRealty;

I know from experience that when I publish a free GNU/GPL plugin that the support is the one thing that kills us in terms of time and energy.  Although the financial investment in doing so is not without motive the cost to benefit ratio isn’t easily or accurately identified.  Since most the time we are seeking link bait when we publish any our OpenRealty or WordPress extensions we usually try to include basic documentation in hopes that little actual end user support would actually be needed or better expressed as “not required”.  Minimal support requirements do not apply when it comes to products that are more complex and feature rich such as OpenRealty.  The time and energy it takes to deliver support for such products can often tank the development as most energy is spent dealing with the day to day support.  But why pursue a paid support model?

Although a relatively new trend with the GNU/GPL applications, the support model isn’t at all unique.  Having been applied by many WordPress theme developers the idea has begun to catch on with greater frequency among those that develop GNU/GPL products.  Many of the finest GNU/GPL WordPress themes in use today were developed as a result of the financial support that funded the effort.  I’ve been noticing that many products once freely available for download are starting to restrict access in some respects to those who pay a donation or purchase an annual support licenses for preferred service. Following the same recipe that worked so well for theme development would lead someone to logically conclude that applications would experience similar success.

If OpenRealty were to follow this model I would speculate that the following things might take place.

• The reduction in relying on commercial addons to fund the applications development.
• More active involvement by those I would deem professional end users.
• Updates to core code with greater frequency.
• I would also expect to see more professional end user results with their projects.
• I think OpenRealty support would improve based on a simple idea that those that pay for support are often (not always) more capable end users.
• Lastly, I think it would be taken more seriously by real estate professionals.

Anyway these were just ideas and far apart from insinuating that they would follow this model it would none the less be interesting if in fact they did. Facts are facts and OpenRealty is the only stand alone application for listings management of its caliber anywhere on the web.  I’m interested in feedback so don’t be shy.

If you are building an XML feed export script for Real Estate listings then maybe these 15 XML and PHP Files will help.  What I include in the zip file is this; I created several XML masters I collected, organized and then keyed from various data feed services some of which are not edited at all, just some source formatting applied.  Then the PHP files were going to be used to essentially provide the XML output structure which would be coded to actually generate the XML file with the listings data.  I was about to create a generic generator as an example you  could build from but pressed for time I needed to put that off for a while.  I managed to knock out a single example for use with OpenRealty which is called citycribs-example. The code isn’t very tidy as it was used for testing the export speed against an OpenRealty database.

A quick note too about those XML files.  I will periodically update as the feed XML structure changes since I will be maintaining that feature within WPRealty.  Even though the feature does provide actual HTML files for the feed map quite similar to my WP Featured Listings plugin, the XML files must be updated for CRON update features to work properly so I’ll update this zip file when needed.  Here is the download link for the files.  http://www.jaredritchey.com/available-downloads/snippets/xml-feed-templates.zip

UPDATED! I tested this with WPRealty recently and the technique works fine.

Here is a quick little snippet that can be used in your Open-Realty® template to display an image rather than a text value for various fields.  I had a project recently that required the display of icons to represent data as opposed to text information.  If for example there was a ski lodge or swimming available for the particular listing the client wanted to display an icon for that feature as he figured the YES/NO wasn’t very appealing aesthetically in his listing details. What I came up with was a simple snippet to display an image or alternate image depending on the value available in the database.

The demo icons to the left would for instance be displayed as blue in color if the value was a yes and a subdued color if there was a NULL or NO value. When a visitor scans the search results they could quickly spot visual representation of key things of importance such as heated swimming pool, ski lodge or exercise room and so on.

Here is the simple way of handling similar scenarios.  First, you should determine where in your theme the images are to be displayed and make design provisions for that with sample mockup code. Images should always include ALT text so take that into account. Then, simply replace your mockup code with something similar to what I have outlined below.

Listing Details – Search Results – Template Code

Lets say that you want to display an icon for the virtual tour if the virtual tour actually has a value and the name of that field in your Open-Realty® database is “VirtualTour” You simply place the following code in either the listing details template or search results template of your choice where you want the image to be displayed at. By doing so, if the VirtualTour field has a value it will display the image I called vtour.jpg and if no value I have it set to display a space. I could have it display an alternate image or any value per se.

Keep in mind that you do not have to repeat most of this snippet if the results are to appear in the same section of the template.  When adding multiple instances you could add the require_once at the very top of your theme and call it globally.

[php]
<?php
$i=2;
require_once("functions.php");
$value = get_field_value(‘VirtualTour’);
if($value){
//echo($value);
echo("<a href=".$value." title="Virtual Tour"><img src="{baseurl}/template/default/images/vtour.jpg" title="virtual tour" /></a>");
}else{
echo("&nbsp;");
}
?>
[/php]

Open-Realty® functions.php File

In all Open-Realty® themes I build I now include a functions.php file in the template directory much like we do in WordPress themes. In fact, WordPress is where I took the idea from because some sites need custom features that really do not necessitate the creation of an addon. So in the functions.php file I’ll include code necessary to handle various things such as our custom form kit or even a simple registration bridge or basic menu management features. The example code below is taken from one of the functions.php file for this particular project. Simply copy it and create your own functions.php file for inclusion into the theme folder.

Be sure to pay special attention to the top line for require_once as this should be set as your full root path. If you are not sure of the actual path you could create a path.php file and add the following to it <?php echo __FILE__; ?> By uploading and then navigating to the file you should get the full path printed in the browser.

[php]
<?php
// this is the functions.php file
// set the path below before adding to your template directory
require_once("/home/MYDOMAIN/public_html/include/common.php");
function get_field_value($field_name)
{
global $config;
$listingID=-1;
if(isset($_GET['listingID']) && $_GET['action']==’listingview’)
{
$listingID=$_GET['listingID'];
$sql="select listingsdbelements_field_value from ".$config['table_prefix']."listingsdbelements where
listingsdbelements_field_name=’".$field_name."’ and listingsdb_id=".$listingID." LIMIT 1";
$select=mysql_query($sql);
$field_value=mysql_fetch_assoc($select);
if($field_value['listingsdbelements_field_value']){
return $field_value['listingsdbelements_field_value'];
}else{
return false;
}
}
}
?>
[/php]

Although this tutorial is basic, you could do as I do and make the fields to query an array of field so you do not have to replicate the code over and over within your template. By doing so your results could look like the following for example;

If you didn’t read the post regarding the similar OpenRealty script then this will help explain why something like this may be necessary. There are times people may install Joomla and then not use it for a period of time. Over time memory can fade and recovering your password using the normal process isn’t really an option because the email assigned to the account is no longer accessible. To make matters worse, there are actually hosting accounts that specialize in bulk hosting of Joomla or WordPress type sites that really don’t grant access to things like phpMyAdmin. What do you do? You use the script below to generate a temporary Super Administrators Account in order for you to reset or change your former account then you delete the file along with the temporary Super Administrators Account. Simply upload the script to your Joomla directory, navigate to it, and your done. It will create a super admin account called THEADMIN with the password of “password”. Its important to note that I set the number in the 9000 range because if you are not sure how many members you have this number is big enough to ensure you wont likely encounter an error. However, this number is so high that each and every new account created will follow this number so its something to consider changing if you want to keep the user ID lower.

But you might ask, why bother with creating a new account when we could simply reset the account to password? Well the very small script at the very bottom of this post will do just that providing the admin account hasn’t been renamed. Upload and access it the same way you would if you were creating the new account. Enjoy!

This one resets the existing super administrators account password to “password”

[snippet missing]

This one creates a new account and password.

[php]
<?php
/*
@ Copyright: (c)2007 – 2009 Jared Ritchey Design, All Rights Reserved.
@ Author URL: http://www.jaredritchey.com
@ Author Email: jared@jaredritchey.com
@ License: GNU/GPL Extended.
@ Config Notes: not knowing how many members are in your DB this has been set to create the account in the 9000 range.
*/

//////////////////////////////////////////////////////////////////////////////////////
// THIS SCRIPT IS USED TO CREATE AN ACCOUNT FOR THEADMIN WITH THE PASSWORD OF password
//////////////////////////////////////////////////////////////////////////////////////
require_once(‘configuration.php’);
$link = mysql_connect($mosConfig_host, $mosConfig_user, $mosConfig_password) or die("Could not connect : " . mysql_error());
mysql_select_db($mosConfig_db) or die("Could not select database");
echo "Database Host: " .$mosConfig_host."<br />";
echo "Database User: " .$mosConfig_user."<br />";
echo "Database Password: " .$mosConfig_password."<br />";
echo "Database: " .$mosConfig_db."<br />";

$sql= "INSERT INTO jos_core_acl_aro VALUES(9001, ‘users’, ’9491′, 0, ‘THEADMIN’, 0)";
mysql_query($sql);

$sql= "INSERT INTO jos_core_acl_groups_aro_map VALUES(25, ”, 9001)";
mysql_query($sql);

$sql= "INSERT INTO jos_users VALUES(9491, ‘THEADMIN’, ‘THEADMIN’, ‘someone@somewhere.com’, ’7d83778ac1e89412de7bad3e3470dc21′, ‘Super Administrator’, 0, 0, 25, ’2007-03-06 11:55:23′, ’2009-08-11 15:32:15′, ”, ‘editor=fckeditor\nexpired=\nexpired_time=’)";
mysql_query($sql);

//echo "<br /><br />";
die("Your SUPER ADMINISTRATOR Account was added – be sure to make modifications prior to continuing and delete this file.");
?>
[/php]

Have you ever wanted to reduce that long confusing looking and un-necessary search string in your “GET” type forms? In our line of work we may opt to use one of three primary tools in our projects; OpenRealty, UltimateIDX, or our home grown product we use on high end projects. Regardless of product, in each instance the search forms for the MLS Quick Search uses the form action type of “GET” and in doing so it passes the form value to the URL string for the query. But what happens when you have a null value or a field with NO value? Why bother to pass fields to your search string that have no value? Over time we noted that lengthy search strings regardless of empty values or not would reduce the response time for the results substantially when compared to shorter search strings.

This script was written to help in the reduction of processing burdens placed on servers for large search forms that use the GET method for form processing. It was designed in part to reduce the SQL search timeout issue common in Real Estate MLS Search forms that rely on the “GET” method to reduce the number of fields passed in the query string. If a search form field contains a NULL or no value it will not be passed on to the GET string.

With help from coder / blogger Greg Burghardt of Fundamental Disaster we hashed out this little snippet to achieve what we were after. The code has since been modified and has about 4 different variants in use but this one is the most true to the original.

You can download the snippet in a zip file from right here; SearchForms.zip

To use this script you should add a little php to display a variable in the body tag or you can simply permanently alter the body tag as follows;
EXAMPLE:
<body onload=”enableEmptyFields(document.something);”>

You must also add an onSubmit event handler (property) belonging to a Form object as follows:
EXAMPLE:
<form action=”the-name-of-your-script.php” method=”get” onsubmit=”disableEmptyFields(this);” name=”something”>

[javascript]
/* ############################### COPYRIGHT NOTICE BEGINS #############################
@ Copyright 2008 – 2009: WP Realty Team – Chad Broussard and Jared Ritchey
@ Copyright 2008: Greg Burghardt
@ Copyright URL: http://www.wprealty.org and http://fundamentaldisaster.blogspot.com/
@ Published by: Chad Broussard and Jared Ritchey
@ Scripting: In part by http://fundamentaldisaster.blogspot.com/ and Jared Ritchey Design
@ License: GNU / GPL
@ File Name: searchforms.js
############################### COPYRIGHT NOTICE ENDS ############################# */
/*
@ DISCLAIMER AND USAGE AND LICENSE:
You are free to use this script for whatever reason you so desire providing you leave the copyright details above in
tact as required and you do not redistribute this code rebranded as your own work. You are free to include this
code in any commercial or non-commercial application without further permission or obligation from WPRealty or
Chad Broussard. You may NOT republish this code absent of this copyright notice. LICENSED AS GNU/GPL Open Source
with provisions.
*/

function enableEmptyFields(form) {
var i = 0;
var field;
var j = 0;
var opt;
while (field = form.elements[i++]) {
switch (field.nodeName) {
case "input":
switch (field.type) {
case "checkbox":
case "radio":
field.disabled = !field.checked;
break;
default:
field.disabled = false;
break;
}
break;
case "select":
if (field.multiple) {
j = 0;
while (opt = field.options[j++]) {
opt.disabled = !opt.selected;
}
} else {
field.disabled = false;
}
break;
default:
field.disabled = false;
break;
}
}
}
function disableEmptyFields(form) {
var i = 0;
var field;
var j = 0;
var opt;

while (field = form.elements[i++]) {
switch (field.nodeName) {
case "input":
switch (field.type) {
case "checkbox":
case "radio":
field.disabled = !field.checked;
break;
default:
field.disabled = (field.value.length > 0) ? false : true;
break;
}
break;
case "select":
if (field.multiple) {
j = 0;
while (opt = field.options[j++]) {
opt.disabled = !opt.selected;
}
} else {
field.disabled = (field.value.length > 0) ? false : true;
}
break;
default:
field.disabled = (field.value.length > 0) ? false : true;
break;
}
}
}
[/javascript]

A true CMS solution would not require you to manipulate the structure of your content in order to alter the structure of your menu or other navigation elements. Yet, nearly all modern themes on the market today require that you alter the position or assignment of your content in order to change the structure of your navigation. WordPress codex outlines the methods and techniques on how to achieve this relatively easily so many theme developers usually employ the codex examples in order to give their theme the appearance of having rich menu management features. Having done this myself many dozens of times its difficult for some to conceive of a simpler way without writing custom functions specific to the theme as an alternative. For this reason and those I’ll cover below were motive in our creation of the fully open source free Menu Creator for WordPress.

After having built almost a hundred themes for WordPress clients and template resellers, the number one of the big challenges we had often faced was turning WordPress into a CMS to replace a system they were migrating (or escaping) from. A good CMS requires good menu management. Publishing a free WordPress menu management tool turned out to be more of a challenge in terms of informing people of its potential than we had expected. After all, the design and styling possibilities of the WP Menu Creator are nearly endless. Since we did not include any example menus with the distribution of the Menu Creator, it ended up hurting us in terms of perception that the Menu Creator was in some way incomplete. So, I’ll first explain our motive in keeping examples out of the distribution then move onto how to make menu management a part of your themes.

When we set out to build all of our free plugins, we knew in advance that in order to get WordPress to behave much like popular CMS solutions we needed to have a few important plugins. The need for menu management was obvious. Then came form generation, member grouping tools, news feeds, lead management, post planning, and in the case of Real Estate CMS sites, important feeds to things like Zillow or Dwellicious. What those CMS requirements gave us was a road map to the ideal WordPress CMS solution powered by for the most part with all of our current FREE GNU/GPL plugins. When I say “our” I’m referring to myself and The UltimateIDX whom of which pretty much finances all of these projects. When it came to our motive in keeping these tools very basic yet open for design possibilities we kept theme developers in mind since we are theme developers and knew what was needed, requested and expected in terms of ease of integration.

How to add Menu Management Support to your WordPress Themes

After having published so many plugins and addons it was planned from the start that we would not only extend the offer to theme developers of every classification but also take the time to assist with the inclusion of our plugins by providing code for the clean and easy implementation. Naturally we keep our tools and plugins as unbranded as can be realistically expected, but do require that the license information remain in the source code unchanged.

To revisit what I started above about the lack of any CSS in our plugins, it was important for us to make sure all theme developers could easily distribute the plugins and faithfully know that the rendered output would adopt their CSS. If the theme developer creates the navigation elements styled as expected, we knew they would want a reliable way of ensuring that our plugins would play along nicely. So, we included NO CSS menu examples within any of our plugins and opted instead to publish examples of code on The UltimateIDX, this blog and our others including some at Pro Real Estate Network.

This has been a pain, so after careful planning and organizing, we decided to setup a repository of sorts that would allow us to publish all code in one convenient place and beginning this weekend (September, 24th 2009) we are doing just that. If you are a theme developer in need of good menu management in your free or commercial efforts, don’t bother writing functions into your theme when you can easily distribute the WordPress Menu Creator. We will even give you the code to make it possible, FREE.

Today we finally got the 2.0 version back for our latest WordPress plugin that ties in full listings management to your WordPress site without the need to install OpenRealty and a bridge. Although we have built several bridging and integration plugins capable of working with OpenRealty, the process for managing those solutions can become challenging to most website owners. What was needed was a full blown solution that didn’t require you to trick, modify or substantially alter the method by which you blog in order to achieve a truly clean MLS IDX or RETS integration solution. Our brand spanking new plug-in does just that. It fully integrates not only standard listing editor features but provides a way for bloggers to add IDX RETS listings to their sites.

The new plugin allows for you to turn your WordPress Real Estate site into a full blown MLS empowered solution unlike anything ever produced before. But its not just for IDX or RETS empowered sites either. Part of our plan in building this new version was to make sure it would work with a few types of sites we have built in the past in particular those not associated with Real Estate. Automotive sites, Virtual Magazines, Online Classifieds, even a sports and gun shop site have been successfully built using the beta version of this new application. Although a precursor to the much more advanced version scheduled for release March of 2010. There is no shortage of features in this release however; A super clean listing integration and unique characteristics guaranteed to make your WordPress site a powerful listings manager.

In the past versions we attempted to provide a rather complex bridging and integration tool for use with your install of OpenRealty. Problems mounted however as each successive update of OpenRealty usually breaks all previous versions to some degree. One bug fix in OpenRealty would present additional bugs that could break the sites structure. We have moved past that in our new plugin.

Free GNU/GPL Real Estate Listings Manager Plugin

Here is a quick summary of the features for your review pending the release this Tuesday.

• Works fine with or without the All In One SEO Plugin, which was a requirement from the start.
• Works with almost any modern WordPress theme including those from StudioPress and iThemes.
• No need to bother with the installation of OpenRealty.
• A more advanced user registration widget is included.
• Powerful featured listings options allowing for you to put featured listings directly in posts throughout your site.
• Designed to work with the WordPress Menu Creator.
• Automatically generates title, meta and meta keywords based on user defined listings fields.
• Full inline documentation
• Contact / Client Tracking
• CSV Export / Import
• Export to Trulia, Google, Yahoo and other XML feeds.
• Easily create contact forms that integrate well with the listings management features of the plugin.
• The ONLY fully CSS/XHTML compliant output for listings data.
• Google maps on search results.
• Google maps on listing details pages.
• Ajax integrated contact forms.
• All features are template driven allowing for endless possibilities in design.
• More to come….

With this plugin and your favorite theme, you will have the only true fully featured easy to manage listings manager available for WordPress. Although there are many real estate WordPress themes that have listings features in them, NONE of them have the potential to integrate IDX or RETS data effectively. Framing is an absolute waste of the effort and alternative methods using modified versions of the NextGen gallery are not only counter productive, but impossible to manage for any number of listings beyond a few dozen. Contact me today for more details!

Ron Goodman provided us an example of the Menu Creator being used in his BFA Atahualpa WP Theme and details his steps to modification of the theme. Its worth the read for anyone considering the same thing. On the UltimateIDX we published 12 of the 16 new tutorials late last night and I’m actively setting up the new categories with links so you can few them. Our client, turned voice over expert, provided the voice overs for the video tutorials that run down the ways in which you can use the Menu Creator to its maximum potential. It also includes examples in converting existing themes to work with the WordPress Menu Creator.

Encouraging Theme Developers to use WP Menu Creator

Its been a busy week in getting theme developers to look at the Menu Creator in hopes they will alter their code to support the Menu Creator. After sending out only 300 emails to many different theme developers, I am pleased to see that 21 have currently responded and will distribute the WP Menu Creator in their next theme updates. The code we provide is super clean and easy to implement and in most cases theme developers can preserve backward compatibility with their existing theme users. The nice thing about the WP Menu Creator is that its free for distribution, is not branded, does not have advertising or other promotion links and is fully compliant with XHTML menu designs.