We are releasing iWiccle 1.01 on Monday, addressing the minor bugs that crept in when we prepared iWiccle 1.0 for launch. There will be a seamless upgrade patch. Here are a few notes to all those who are experimenting with iWiccle and looking at how to tailor it to their needs. Drop in your comments and let us know how to make it better.

Those eager to test their iWiccle 1.0 and notify us of any bugs are encouraged to do so — we'll do our very best to address every possible problem report, and as much of the feature requests we can handle. If you get errors, you may want to switch on the debug screen.

Just append &debug=on to the end of the URL and it'll start a debug session. Whenever you want to switch it off, use &debug=off. When reporting an error, please supply us with the following:

• The complete URL on which the error occurs.
• A description of what you did (or just loaded the page).
• Any errors shown on the screen or in the debug screen.

In the image above, you see a bug in progress in the events module — the /modules/events_config.php file has a redundant reference to a table that will only be employed in Wiccle, integrated with the eCommerce triple module. Simply comment out line #76 (...post_sql_join) controlling module extensions to the iWiccle core, and you're good.

If you spot anything else that requires fixing, please report in the comments to this post, or by e-mail to .