Enano CMS

The Enano team is proud to announce the immediate release of Enano 1.0.2, codenamed Coblynau. This release fixes a number of bugs and includes a considerably more polished overall experience. A number of bugs are fixed, including a security fix. All ... [More] users are strongly encouraged to upgrade their websites immediately. Update: We found one bug in the upgrade script that kept the upgrade from completely finishing due to a missing dependency in the script. The tarballs have been updated. We're sorry for any inconvenience this may have caused. Release notes and changelog Release notes may be viewed in the usual way, on the release notes page for this release. Security issues Security issues should be reported through direct e-mail to the project administrator org>. Preferably, such e-mails should be encrypted; you can use this GPG public key. Obtaining support Support for this release is available in our support forum. Documentation is available at http://docs.enanocms.org/. Statistics This release contains 2,029,037 bytes of PHP code, amounting to 54,924 lines. Enjoy [Less]

The Enano team is proud to announce the immediate release of Enano 1.0.2, codenamed Coblynau. This release fixes a number of bugs and includes a considerably more polished overall experience. A number of bugs are fixed, including a security fix. All ... [More] users are strongly encouraged to upgrade their websites immediately. Update: We found one bug in the upgrade script that kept the upgrade from completely finishing due to a missing dependency in the script. The tarballs have been updated. We're sorry for any inconvenience this may have caused. Release notes and changelog Release notes may be viewed in the usual way, on the release notes page for this release. Security issues Security issues should be reported through direct e-mail to the project administrator enanocms <__DOT__> org>. Preferably, such e-mails should be encrypted; you can use this GPG public key. Obtaining support Support for this release is available in our support forum. Documentation is available at http://docs.enanocms.org/. Statistics This release contains 2,029,037 bytes of PHP code, amounting to 54,924 lines. Enjoy [Less]

The Enano team is proud to announce the immediate release of Enano 1.0.2, codenamed Coblynau. This release fixes a number of bugs and includes a considerably more polished overall experience. A number of bugs are fixed, including a security fix. All ... [More] users are strongly encouraged to upgrade their websites immediately. Update: We found one bug in the upgrade script that kept the upgrade from completely finishing due to a missing dependency in the script. The tarballs have been updated. We're sorry for any inconvenience this may have caused. Release notes and changelog Release notes may be viewed in the usual way, on the release notes page for this release. Security issues Security issues should be reported through direct e-mail to the project administrator . Preferably, such e-mails should be encrypted; you can use this GPG public key. Obtaining support Support for this release is available in our support forum. Documentation is available at http://docs.enanocms.org/. Statistics This release contains 2,029,037 bytes of PHP code, amounting to 54,924 lines. Enjoy [Less]

So we originally planned to release Enano 1.0.2, aka Coblynau, in early October. That was over a month ago. What happened? We've been finding a number of issues with the old and crusty code in Enano that hasn't been looked over in a while. Stuff like ... [More] XSS vulnerabilities in the admin panel. Since per-session keys that only last 15 minutes are always used on admin panel URLs, exploiting such vulnerabilities through CSRF is just a hair shy of impossible. Nevertheless, work is being done to patch these vulnerabilities. There have also been issues with installations not completing properly due to a number of reasons, and to help alleviate this we have modularized the installation process completely. The installation is now performed in "stages", with each stage having opportunity for throwing errors and allowing the installation to be stopped and resumed once the error is corrected. We're also working to make CAPTCHAs more secure by preventing multiple images of the same code from being requested. This is being done by changing the code each time a refresh of the image is performed. Lastly, we have been trying to improve compatibility with diverse ranges of servers. Not everyone will be running Enano on a VPS where they have root access and the latest Apache, PHP, and MySQL, and we realize that. We're trying hard to get Enano working well, especially on Windows platforms. One of the features added as a result of this campaign is the ability to scale images using the GD library instead of the default method, ImageMagick. Coblynau is now undergoing the final stages of testing and QA. We would greatly appreciate it if you could pull the latest revision from Mercurial (also in bz2 or zip) and give it a whirl. You might like the new features, and you'll love the additional stability. We hope to release by the end of the week of November 18. [Less]

I just realized that ntpd wasn't running on our server, so some of you may have noticed times being off by an hour in the forum. This should be fixed now; please let me know if it still seems off. Update: As of 7:20PM EST, it's still off because ntpd ... [More] isn't configured right. I'm still working to fix the problem. dandaman32 0:21, 18 November 2007 (UTC) [Less]

Enano's starting to see a rather diverse user base, and as some of you will know, we have been planning to localize Enano's strings and add a language framework. We're here to announce that work on this framework and the subsequent localization ... [More] process has begun. We are considering very carefully how we want this to be structured, and at this point it looks like language strings will be stored in XML or possibly JSON (due to limited XML support in PHP4) files, imported into the database during installation, and subsequently cached in PHP format so they can be include()'ed. The system will be plugin-extensible and will allow strings to be edited from the administration panel. All strings will be categorized. Update: A basic language framework has been implemented and you should be able to see it in the unstable branch in Mercurial. We've started localizing the UI, and it looks like it may end up a slow, painful process. Help is welcome wherever we can get it. [Less]

Thanks to an idea from Neal Gompa, we've moved the Mercurial repositories formerly hosted on Nighthawk (my development server) to the VPS. Our primary working copies will still be on Nighthawk, and a sync script is currently scheduled to pull all the ... [More] latest changes from Nighthawk every 2 hours. Anyone and everyone can always pull fresh Enano code from http://hg.enanocms.org/ from now on. [Less]

Apparently during the DSL modem meltdown last night, my NAT settings got messed up. As a result, our system was down for about 15 hours. I didn't even realize it until I got to work today, but it should be fixed by now. In a related note, I took the ... [More] liberty of replacing the light fixture mentioned a few news posts back during that time, so the downtime for Saturday won't be happening. [Less]

Due to the considerable number of issues in Loch Ness, the Enano team has made the decision to release a beta version of Enano 1.0.2, aka Coblynau, for public testing and evaluation. All known issues with Loch Ness are resolved in this beta, but as ... [More] with all test versions, we do not advise that administrators use this version on production websites. We are aiming to release the stable version of Coblynau in early October, and we plan to make no further database/schema changes. As a side note, there were no database changes between Loch Ness and Coblynau beta 1. If desired, you may change the version number in common.php (line 26) to avoid going through the process of running the upgrade script. [Less]

On Saturday, September 29 from 10:00-11:30 AM, our demo and Mercurial servers will go down for maintenance. As they are both hosted in-house, taking them down is unavoidable because a lighting fixture on the same circuit as the servers died a few ... [More] weeks ago. There's a chance I could get an extension cord for the power strip that runs the servers and have them up while the lighting fixture is worked on. [Less]