Current development on JAMWiki is primarily focused on maintenance rather than new features due to a lack of developer availability. If you are interested in working on JAMWiki please join the jamwiki-devel mailing list.

JAMWiki 0.0.7

Release Notes[edit]

IMPORTANT: While reasonably stable, the JAMWiki code is undergoing rapid development and should be considered beta software, not suitable for deployment on production systems. Also note that this version changes the database schema used in previous versions - see below for upgrade instructions.

JAMWiki 0.0.7 is now available for download as a WAR file suitable for deployment on a web application server. This release includes a new default look & feel, support for the Websphere application server, an update of the topic locking code, along with numerous code cleanups and bug fixes. See the changelog for a more complete list of changes and fixes.

To install the file simply deploy it like any other WAR file, restart the web application server, and then view the URL http://www.yourserver.com/context/ to begin the configuration process (context is the web application context root).

See the README.txt and CHANGELOG.txt files for additional details about this release. Additional information and documentation can be found at http://jamwiki.org/.

Changelog[edit]

  • BUG: Handle non ISO-8859-1 characters properly. May require additional configuration for some databases and application servers. Issue reported by Alexey.
  • BUG: Make web.xml and the taglib definitions more standards compliant. Note that this allows JAMWiki to run on Websphere.
  • FEATURE: Remove topic locking & implement a new edit screen to allow for manual resolution of edit conflicts.
  • FEATURE: Remove the old topic locking code including Special:LockList and Special:Unlock.
  • BUG: Replace CHAR columns in database with INTEGER to fix a problem with the H2 database - BREAKS ANY EXISTING INSTALLATION! See the release notes for the database update syntax.
  • FEATURE: Update to Alexey's new default style.
  • FEATURE: Do not include CSS information inline, instead make jamwiki.css an editable Wiki topic and load from that.
  • FEATURE: Hide passwords when updating values on the admin page.
  • BUG: Resolved some table syntax parsing issues.
  • BUG: If an error occurs the setup process might not create the StartingPoints topic.
  • BUG: Admin-only topics not marked admin-only during setup.
  • FEATURE: Recent changes and user contributions now have options to view latest 250 and 500 changes.
  • BUG: If a topic is saved with no changes, do not save a new version.
  • BUG: Remove redundant parsing code that was causing diffs to be shown when no diff was made.
  • FEATURE: Remove the "Cancel" option from the edit page.
  • FEATURE: Once setup is complete disable the setup screen.
  • FEATURE: Add option to reload recent changes to the admin screen (database persistency only).
  • FEATURE: Make more HTML code XHTML compliant.
  • FEATURE: Code cleanups including removal of unused files.
  • FEATURE: Default log level changed to "WARN".

Upgrade Instructions[edit]

To upgrade from JAMWiki 0.0.6, run the following SQL commands to update the database:



DROP database jam_notification;

alter table jam_topic drop constraint jam_fk_topic_locked_by;
alter table jam_topic drop column topic_locked_by;
alter table jam_topic drop column topic_lock_date;
alter table jam_topic drop column topic_lock_session_key;

/* change columns from CHAR to INTEGER */

alter table jam_wiki_user add column is_admin_new INTEGER DEFAULT 0 NOT NULL;
update jam_wiki_user set is_admin_new = 1 where is_admin = '1';
alter table jam_wiki_user drop column is_admin;
alter table jam_wiki_user rename column is_admin_new to is_admin;

alter table jam_topic add column topic_deleted_new INTEGER DEFAULT 0 NOT NULL;
update jam_topic set topic_deleted_new = 1 where topic_deleted = '1';
alter table jam_topic drop column topic_deleted;
alter table jam_topic rename column topic_deleted_new to topic_deleted;

alter table jam_topic add column topic_read_only_new INTEGER DEFAULT 0 NOT NULL;
update jam_topic set topic_read_only_new = 1 where topic_read_only = '1';
alter table jam_topic drop column topic_read_only;
alter table jam_topic rename column topic_read_only_new to topic_read_only;

alter table jam_topic add column topic_admin_only_new INTEGER DEFAULT 0 NOT NULL;
update jam_topic set topic_admin_only_new = 1 where topic_admin_only = '1';
alter table jam_topic drop column topic_admin_only;
alter table jam_topic rename column topic_admin_only_new to topic_admin_only;

alter table jam_file add column file_deleted_new INTEGER DEFAULT 0 NOT NULL;
update jam_file set file_deleted_new = 1 where file_deleted = '1';
alter table jam_file drop column file_deleted;
alter table jam_file rename column file_deleted_new to file_deleted;

alter table jam_file add column file_read_only_new INTEGER DEFAULT 0 NOT NULL;
update jam_file set file_read_only_new = 1 where file_read_only = '1';
alter table jam_file drop column file_read_only;
alter table jam_file rename column file_read_only_new to file_read_only;

alter table jam_file add column file_admin_only_new INTEGER DEFAULT 0 NOT NULL;
update jam_file set file_admin_only_new = 1 where file_admin_only = '1';
alter table jam_file drop column file_admin_only;
alter table jam_file rename column file_admin_only_new to file_admin_only;

To use the new default stylesheet, edit the "StyleSheet" topic in JAMWiki and paste in the contents of the /WEB-INF/classes/StyleSheet.txt file.