Yesterday, May 1st., 2008, was the official release date of Etomite Prelude v1.0 which marks a major milestone in development. This release will prove to be the most stable and feature-rich release to date. The number of bug fixes, improvements, and overall performance enhancements is far too great to list them all here. Suffice it to say, a lot has changed. Anyone who is running an older release of Etomite is encouraged to upgrade. You won’t be disappointed.
So, what are some of the new features? Here is a short list:
- New manager skin
- New default page template
- New default installation content
- New default snippets
- Chunks now utilize permissions
- Integrated new release of EditArea code highlighter/editor
- Integrated new release of TinyMCE
- Integrated new pop-up calendar for date selections
- Addressed virtually all Bug Tracker issues
- Fixed multiple hidden bugs in the Etomite parser and API functions
The following configuration options were added to the Etomite configuration panel:
- Added global manager date display format selection
- Added global manager time display format selection
- Added empty cache default setting for documents
- Added show in menu default setting for documents
- Added Enable/Disable manager audit trail option
- Added maximum number of login attempts setting
- Added SQL debugger option
- Added Snippet debugger option
- Added Enable/Disable embedded PHP option
- Added inline viewable filetypes setting for the file manager
- Added viewable filetypes setting for the file manager
- Added editable filetypes setting for the file manager
- Added exclude paths setting for the file manager
- Added maximum upload size setting for the file manager (and elsewhere)
- Added display link-back to Etomite option
One major modification that was incorporated into the code base relates to how hosts are configuring newer versions of PHP on their servers. Issues with the PHP include_path setting were becoming a major problem and there was no easy solution. Re-writing every include statement within the entire code base was the only effective solution to the problem. This fix has been tested on at least one server known to exhibit this problem and everything is working perfectly.
The list goes on and on but this is all I can think of at the moment. While the new resources mentioned earlier won’t be installed during upgrades they will be installed if a new full installation is performed. That about wraps it up for now. This release marks the end of development of the Prelude code base branch and only minor bugs will be addressed from this point on. I need to rest up so we can get started on the next major release.
THE END
[...] Etomite Prelude v1.0 Released [...]