Archive | WordPress
This is the first release candidate for version 1.2.0 .
This release completes a significant amount of re-factoring to the core framework code including how entities, metrics, controllers, and views work. We have tried to maintain backwards compatibility with most API methods but it’s worth doing some testing on your metrics and controllers to ensure things are working. One area that proved difficult to maintain backwards compatibility for was controller authentication and OWA’s original permission scheme. Please see the below for more info on that.
Ok, now onto the good stuff.
New Features include:
- Entity Schema Creation. OWA entities can now create their own database tables. OWA’s object-relational-mapping layer has been extended to allow entities’s to create, drop, and alter their own database tables. This eliminates the need for a separate schema installation facility/file. This has been done in a way where it is now possible to write data access layers for support of databases other than MySQL.
- Database Schema Updates. OWA now provides an easy way for module developers to create and apply updates the database tables that the entities in their module create. See http://wiki.openwebanalytics.com/index.php?title=Schema_Updater for more info on how Schema updates work.
- Plug-able Controller Authentication. OWA has always had plug-able authentication but prior to this release it was plugable on a global basis. Now you can define which authentication method to use on a controller by controller basis.
- Widgets. OWA now features a number of widgets that can be placed on web pages. Developers can also now create their own widgets that can be used across views and modules.
- Roles & Responsibilities. OWA now has a new user authentication scheme that helps controllers check to see if the current user’s role has the necessary capabilities in order to execute the controller’s action. OWA now defines a core set of user roles and capabilities that developers can apply to their controllers. See the wiki here for more details.
- Log Named users. OWA will now log request from named users (including those of the host application framework) by default. You can disable this via the Settings UI. This replaces prior functionality where OWA did not log admin users by default.
- Metric Pagination. Much requested trend metrics can now page their results.
- Open Flash Charts. JPGraphs has been replaced with Open Flash Charts as the default charting package for all graphs.
- Updated Packages. Updates to Browscap, PHPmailer, PEAR Log
- Generic email view. OWA now provided a generic email view that controllers can use to send email messages
- Service Layer. OWA now has a shinny new service layer that implements a number of global framework objects and services. Some objects such as the configuration and requestContainer objects have moved here and are now accessible via coreAPI methods. Modules and services implemented via framework plugins will reside in this layer shortly.
- Form/Input Data Validations. Controllers can now validate request params and form input by calling a global validation service. Validation checks that are now built into OWA include: entityExists, required, stringMatch, entityDoesNotExist, subStringPosition, and stringLength. Developers can add additional validations as plugins.
- Compatible with WordPress v2.7.x
- Compatible with and requires MediaWiki v1.13
Bug Fixes Include:
- WordPress plugin now shows full url in WordPress plugin roster screen. Thanks to Nathan.
- Gallery2 plugin now correctly logs named users. Thanks to Tom.
- Many, many other bug fixes that were lost in the migration to the new Trac.
Wordpress 2.5 changed some things that might effect new installations of OWA. If you are having problems getting OWA to install under WP 2.5 give the latest SVN trunk a try as it contains fixes that should resolve the issues.
If no major bugs are reported we’ll package a new release by Sunday.
Quick release fixes a few critical bugs including one that was breaking wordpress feeds.Highly recommend that you update from RC2 if running OWA as a wordpress plugin. Just copy the new files over the old.
Keep those bug reports coming.
We are pleased to announce the availability of OWA 1.1.0rc2. This one took a while due to the integration of object caching and a new integration plugin for tracking Gallery2 (http://gallery.menalto.com) based sites. Quick summary of new or changed features in this release includes:
- Object Caching. OWA will now cache objects in an attempt to avoid hitting the database. This should speed up logging requests quite a bit.
- Gallery2 Integration. OWA can now be used to track Gallery2 based photo/media sites.
- Installs like a regular Gallery2 plugin
- Reports and admin interface are accessible via Gallery2′s admin screens
- Tracks views of all albums, photos and other media items
- owa-data Folder. All OWA or user generated content is now housed in a single folder. logs/ directory has been relocated here as well.
- Lots of bug fixes:
- set timeout on fetching news from openwebanalytics.com
- Fixed a bug in click tracking in IE7 (thanks to Mark Kaplun)
- Fixed SVN issue with version not being set properly
- Updated PEAR::LOG
- Introduced jquery as an include for UI re-factoring that will come in the near future.
- fixed a bug where WordPress feed tracking was broken due to WP2.2.x
- re-factored mediawiki plugin to use factory method to init owa
- Standalone Installer now no longer requires that the initial admin user password by set via e-mail. Instead it can now be set on the final page of the installer.
- Updated browscap database
- Mediawiki plugin no longer logs admin users.
- Re-factored Error logging - brand new error logging and debug class.
- Re-factored configuration overrides – this release changes the way that configuration overrides work by introducing a new set of config-file based overrides that are now applied last. This should help in a number of situation where you can different instances of OWA to play different roles.
This release re-organizes things a bit so I recommend a clean install of the files. There are no database schema changes so you should just be able to delete everything in the OWA directory (except for your conf/owa-config.php file) and just copy the new files into the old directory. SVN users can simply “SVN switch” to the 1.1.0rc2 tag directory and then “SVN up” to the latest release.This is a release candidate so please be sure to report any bugs to the mailing lists (trac is still closed unfortunately).