Following the release of iWiccle 1.10 last week, we received several reports on how iWiccle worked and quirked with some versions of Microsoft's Internet Explorer. Since broad market technology support is a priority, we decided to give it the attention it requires and get it off our list of issues to deal with, and squeezed a couple of nifty improvements and new features, too.

As the result of last week's endeavors, following many long hours of IE-specific debugging and tinkering with with HTML, CSS and JavaScript, the issue is finally under control, and all but a few advanced admin DOM manipulation features are near-identical or identical across browsers. A few more days were spent with debugging, feature improvements, and adding of some features our members had been hoping for --- including SMTP mails, language pack support and diverse e-mail notifications!

Please download and install iWiccle 1.11 and see what it can do for you, your community, and website. You can see a test installation online at our temporary demo site. The main demo will be upgraded in the course of tomorrow, and along with that the upgrade bundle from 1.01 --- over 1.10 and straight to iWiccle 1.11 --- will be available. Remember to check in at the forums and share your experiences and suggestions after taking the latest version for a spin --- as you will find out, we try to do our best to respond to members' requests, expanding iWiccle to meet everyone's demands.

New iWiccle Features since version 1.01

Tied up with work on version 1.11 as we were, the new features of version 1.10 were never explored in detail. Here's a quick and unordered list of new features since our previous big release from a month back, iWiccle 1.01.

• Improved registration and user management.
• Site Mail & e-mail notifications of tracked content and received site mail messages.
• Favorites feature extended for post, parent and category-level content tracking with customizable tracking auto-expiry options.
• Much improved Internet Explorer 7 and 8 support.
• Message wall and status box over AJAX, online status at Member Portal.
• Improved Site Mail management.
• Six color variants to default skin.
• Cleaner and more symmetric templates.
• Language pack support (Beta).
• SMTP mail support and improved e-mail handling.
• iWiccle Free footer ad color scheme customization in templates.
• New and extended builder units for better content customization precision.
• Uploaded image association and memory on a per-unit basis in the Builder custom content CMS area.
• Builder DOM manipulation improvements for more consistent pre-pageload WYSIWYG results.
• Improved TinyMCE WYSIWYG content editor configuration.
• Custom content page search over AJAX, featuring unit-precision search (leading you directly to the matching page segment) and result peeking.
• Improved dependency and permission checks for installation.
• Easier and faster installation, added inline installation help.
• Birthday, age and zodiac sign support in member profiles.
• Secure auto-login feature with user and admin customizable login expiry times.
• 50 bugs off the checklist, 50 more off the list.
• Hundreds of general code improvements.

And a whole lot more that escaped the list! Much can happen within a month, and much much more will happen over the month to come, as we turn our focus back to Wiccle 1.0 development. We have dozens of confirmed new features rolling in into both Wiccle and iWiccle, iWiccle being the open-source beneficiary of our commercial ventures and development time.

iWiccle remains resource-friendly!

Earlier the question was asked, "How heavy is iWiccle? How much memory does it take?" Despite the growing list of features and tight development schedules, we've managed to keep resource-usage amicably under control. Current per-load / per-post average memory usage is a bit under 3 MB, media operations excluded (as their memory imprint is relative to the size of the processed media), and processing time averages in the range of 0.15-0.30 seconds on our test and development servers.

While looking at the above, bear in mind that there is still much to be done in the way of improved dependency management, and iWiccle doesn't even use a cache-system yet! Cache support is in the roadmap for the upcoming release of Wiccle 1.0, and with the benefits integrated from that, you can expect to see the memory and CPU imprint of both iWiccle and the future Wiccle editions continue to compare favorably to the vast majority of comparable applications.