So it's out now, iWiccle CMS Community Builder 1.0! Building and releasing it has been a massive endeavor, yet it's only the dawn of things to come. iWiccle and Wiccle will continue to evolve at a fast pace, filling in the market need for dynamic and easy-to-control Web 2.0 applications.
You can update your iWiccle install at any time as future versions roll out; you can just rewrite the files in your folders with the files from the latest bundle. Database changes may/will only happen between larger versions, and an installer will take care of your transit towards better wiccling. If you spot a bug, please comment here or send mail to us.
There are a huge number of features that didn't make it into v1.0 but that are almost complete. iWiccle isn't the end — it's the beginning, the first taste of things to come.
The admin panel will nearly double in size and features once all is said and done, and the front-end will also get a bit more in the days to come once we get some loose ends tied up.
We also have a number of other modules almost complete, rolled out with future Wiccle versions. Expect to see a tentative feature roadmap for future releases published within the week. By the end of the week, iWiccle enhancements will also be rolled out at Wiccle.com, currently running on an early beta of the Wiccle core.
There were also four minor bugs and issues in the very first download (released at 4 AM our time) that have been fixed in the now updated download:
- Events module default page was set wrong and showed blank (/modules/events/events_core.php)
- Installer had an unreferenced $error variable (caused a notice in phase 2, no error).
- Some file clutter has been removed from /modules/events (dummy sql files from testing).
- Admin > Wiccle News, a broken div hid the newsfeed from displaying (/core/admin/admin_skin_home.php).










February

That image.... ⋅ Markus July 9, 2009, 03:13 PM
Installer Question ⋅ tdcaron July 10, 2009, 12:53 AM
Script not executed ⋅ Markus July 10, 2009, 11:29 AM
Hi Tim, I replied to your other comment in more detail. It looks like PHP execution is off under the subdomain you are trying to run the installer at.