Foswiki Release 1.1.10

Foswiki - The Free and Open Source Wiki

Foswiki is an enterprise collaboration and information sharing tool targeted for professional use in many types of organizations: from small businesses to multi-nationals, from one-product open source groups, to worldwide research networks.

Foswiki is a wiki: fundamentally, a website with editable web pages. It looks like a normal web site but it encourages contributions, edits, updates, questions, and answers from its users. It's a powerful way of enabling a community to communicate asynchronously using intranet and public internet websites. Foswiki is simple to learn and use. It aims to provide a transparent way for you to publish and exchange your ideas with others over the web and eliminates the one-webmaster syndrome of outdated intranet content.

Foswiki is a structured wiki with tools that enable users without programming skills to build powerful yet simple applications to process information and support workflows. Developers can extend the functionality of Foswiki with plugins.

Foswiki is the old TWiki project under a new name. Restrictions on the use of the TWiki brand resulted in many of its developers continuing the project under the new Foswiki name. Foswiki is backwards compatible with all content from older TWiki installations. Foswiki 1.1 ships with a TWikiCompatibilityPlugin, thus enabling most extensions made for TWiki to work under Foswiki. Since the start of the Foswiki project there have been several releases of TWiki, However there have been very few functionality changes, and the useful changes have all been tracked in Foswiki, so topics and wiki applications supported by TWiki should also work with Foswiki.

Foswiki is released under the GNU General Public License.

Foswiki Releases

• Foswiki 1.1.0 was built 04 Oct 2010. It is a release with more than 270 bug fixes relative to 1.0.10 and more than 680 bug fixes relative to 1.0.0. And the release adds more than 100 enhancements. Foswiki 1.1.0 introduces jQuery Javascript user interface framework, improved topic history display, new QUERY and FORMAT macros, better userinterfaces for groups, much improved WYSIWYG editor, facelift of the default skin, much improved configure tool, and many more enhancements.
• Foswiki 1.1.1 was built 25 Oct 2010. It is a release that fixes some important bugs that were introduced in 1.1.0. It is highly recommended that all running 1.1.0 upgrade to 1.1.1.
• Foswiki 1.1.2 was built 09 Nov 2010. It is a release that fixes some very important bugs incl. a security related bug. Installations running 1.1.0 and 1.1.1 should be upgraded to 1.1.2
• Foswiki 1.1.3 was built 16 Apr 2011. It is a release that fixes more than 150 bugs. jQuery has been updated to 1.4.3. The default PatternSkin has some usability improvements.
• Foswiki 1.1.4 was built 20 Dec 2011. It is a release that fixes some very important including some security related issues. It contains 143 fixes and 27 enhancements. jQuery has been updated to 1.7.1.
• Foswiki 1.1.5 was built 10 Apr 2012. It is a release that fixes some very important issues including some security related issues. It contains 100 fixes and 20 enhancements.
• Foswiki 1.1.6 was built 02 Dec 2012. It is a release that fixes some important issues including some minor security related issues. It contains 94 fixes and 27 enhancements.
• Foswiki 1.1.7 was built 01 Feb 2013. It is a release that fixes CVE-2012-6329 and CVE-2012-6330. It contains 20 fixes and 4 enhancements.
• Foswiki 1.1.8 was built 28 Feb 2013. It is a release that fixes CVE-2013-1666. It contains 4 fixes.
• Foswiki 1.1.9 was built 18 Nov 2013. It is a release that contains 44 fixes and 4 enhancements.
• Foswiki 1.1.10 was built 23 Nov 2015. It is a release that contains 8 fixes and 8 enhancements.

Foswiki 1.1.10 is indended to be the final patch release in the Foswiki 1.1 Release stream.

Pre-installed Extensions

Foswiki 1.1 ships with the following:

• Plugins: AutoViewTemplatePlugin, CommentPlugin, EditTablePlugin, EmptyPlugin, HistoryPlugin, InterwikiPlugin, JQueryPlugin, PreferencesPlugin, RenderListPlugin, SlideShowPlugin, SmiliesPlugin, SpreadSheetPlugin, TablePlugin, TinyMCEPlugin, TwistyPlugin, WysiwygPlugin
• Contribs: CompareRevisionsAddOn, FamFamFamContrib, JSCalendarContrib, MailerContrib, PatchFoswikiContrib, TipsContrib, TopicUserMappingContrib
• Skins: PatternSkin
• Compatibility support - TWikiCompatibilityPlugin

Important changes in Foswiki 1.1.10 (This release)

Foswiki 1.1.10 is a compatibility release for sites unable to upgrade to Foswiki 2.0. It contains fixes for Perl and CPAN compatibility issues that can arise after a system upgrade. It has been tested with perl versions 5.8.8 thru 5.23. It also contains backports of important Foswiki 2.0 features necessary for compatibility with extensions released for Foswiki 2.0.

ACL Changes

Foswiki 1.1.10 backports the new wildcard ACL. ALLOW and DENY rules can now be set to "*" asterisk, which means always match. In Foswiki 2.0, this is used to deprecate the old "Empty" deny rule. Foswiki 1.1.10 still supports the empty deny rules, but also supports the "ALLOW *" for allow all.

SpreadSheetPlugin changes

• Set SPREADSHEETPLUGIN_ALLOWHTML=1

Important changes in Foswiki 1.1.9

• The %TOPICLIST% macro now omits topics that cannot be read by the user. Foswiki should not reveal the presence of topics to users who don't have the authority to view the topic.
• Login using url parameters has been restricted. Details below..

Release 1.1.9 addresses several issues that impact sites that have upgraded or will upgrade to newer versions of perl and CPAN modules. We strongly recommend that foswiki be upgraded to 1.1.9 prior to updating to a new release of perl or CPAN modules.

JQuery upgrade

• Update {JQueryPlugin}{JQueryVersion} to version 1.8.3
• Disable {JQueryPlugin}{Plugins}{Tooltip}{Enabled} and
• Enable {JQueryPlugin}{Plugins}{'UI::Tooltip'}{Enabled}

Changes to login using URL parameters

• username and password will only be accepted on POST type operations. a simple GET url with username and password will not accept the supplied credentials.
  • The previous behaviour can be restored by enabling $Foswiki::cfg{Session}{AcceptUserPwParamOnGET} in the configuration
• username and password will only be accepted as login credentials on the view, viewauth and login scripts.
  • Other scripts can be authorized by configuring $Foswiki::cfg{Session}{AcceptUserPwParam}

Improved compatibility with Perl 5.18+

• The order of search results order when the requested sort has duplicates is unpredictable. Ex: When sorting by "modified", the order of multiple topics modified at the exact same time will be unpredictable. (Task Item12618)
• The order of groups presented by %USERINFO and %GROUPINFO macros is unpredictable. As a result, the order of groups listed by the WikiGroups topic change on each page view. (Task Item12635)
• The order of data in a perl formatted %QUERY result is unpredictable. (No plan to fix)

Any data internally stored by Foswiki or extensions using a perl hash array will be presented in unpredictable order.

Important changes in Foswiki 1.1.8

Release 1.1.8 also includes a configuration checker that will report an error if a vulnerable version of Locale::Maketext is installed.

Important changes in Foswiki 1.1.7

Release 1.1.7 also includes a security fix for configure that reduces exposure of important passwords in confirmation and log messages.

Module version strings and new module dependency in 1.1.6 and 1.1.7

• Sites using Perl 5.10.1 or newer have the correct version of version.
• Sites on older versions of perl should install the latest version using CPAN or their system's package manager.

Before upgrading to Foswiki 1.1.6 or 1.1.7, verify that the installed version of CPAN:version is at least version 0.77. If not, upgrade CPAN:version before attempting to upgrade Foswiki! For example:

 perl -Mversion -e 'print "$version::VERSION\n"'
0.9901

Note: Extensions may not have been upgraded to use the new 'dotted-decimal' version string format for dependency checking. If an extension includes a dependency on an SVN-style revision, Foswiki 1.1.6 assumes that the dependency is satisfied by a 'dotted-decimal' version.

Wysiwyg / TinyMCE Editor changes

• Ex. if a InlineWikiWord is changed to ADifferentWikiWord, the link will now point to ADifferentWikiWord, which is probably what the user intended.

Force Default Host URL toggle

New configuration parameter {Register}{ExpireAfter}

When upgrading, a new setting is needed for PatternSkin

• Ensure that SitePreferences or DefaultPreferences have the setting for PATTERNSKIN_JQUERY_THEME.

     * Set PATTERNSKIN_JQUERY_THEME = PatternSkinTheme

• Be sure to run through an edit / save cycle in bin/configure.

$Foswiki::cfg{JQueryPlugin}{Themes}{PatternSkinTheme}{Url} =
'$Foswiki::cfg{PubUrlPath}/$Foswiki::cfg{SystemWebName}/PatternSkinTheme/jquery-ui.css';
$Foswiki::cfg{JQueryPlugin}{Themes}{PatternSkinTheme}{Enabled} = 1;

Font changes

A change made in 1.1.6 changed the default size and family of the body font. This change resulted in unexpected word wrap in tables that had column widths set to avoid wrapping. Foswiki 1.1.7 reverts the font setting back to that of Foswiki 1.1.5. Changes to the skin that impact layout should not have been made in a patch release.

Minor change to Main.WebHome

Important changes in Foswiki 1.1.6

Release 1.1.6 is a security focused and bug fix release. There are a number of fixes and small enhancements designed to improve the security of Foswiki.

Default format of "New Topic" links has changed.

JQuery version updates

• The default version of JQuery has been bumped to JQuery 1.8.2
• All versions of jquery older than 1.7.1 have been removed.

Be sure to run configure and verify that the JQuery version is set to one still available, and preferably the default 1.8.2.

Registration handling

• The check for duplicate email regisrations is now applied to pending registrations.
• Code has been added to remove stale registration approval requests.

Wysiwyg / TinyMCE Editor changes

• All links are now represented as real HTML links in TMCE. Editing the link text displayed in-line only updates the link text, including auto-linked WikiWords. Click the link icon to update the actual link target.
  • Ex. if a InlineWikiWord is changed to ADifferentWikiWord, the link will become [[InlineWikiWord][ADifferentWikiWord]]
• Verbatim blocks that are hidden will now display and can be edited.
• Escaped WikiWords will no longer display as links when edited.
• Major issues with loss of white-space and line breaks while editing have been corrected.
• It is now possible to position the cursor above/below blocks that start or end a topic.
• HTML entities added to topics when Ctrl-i or Ctrl-b are used for Italics / Bold are now removed on save.
• Multi-line TML tables can now be edited.
• NOAUTOLINK and <noautolink> blocks are now handled correctly.
• JQuery Chili highlighter classes are now all available from the context menu of a verbatim block.
• New tables inserted with wysiwyg now show the expected borders.
• TinyMCE has been updated to release 3.4.9

Insecure dependency errors when using LOCALEs

Setting a Locale in the configuration causes internal errors because of perl's mechanisms used to protect applications from potentially untrusted input. The systems Locale strings are considered "Tainted" and Foswiki fails with taint errors. At this point we don't have a good solution. Significant work is being done for future releases to resolve this issue.

A serious performance problem when renaming topics has been resolved

The resolution results in a change to what is renamed. Prior to this resolution, an extra scan of the entire web was performed. The new behavior is that "Incoming" links (Links pointing to the topic being renamed) will be listed and updated when their checkbox is checked. However "Outgoing" links (links internal to the renamed topic, pointing to other topics in the original web) will not be updated.

Performance problems when logs are "Rotated" at end of month.

The plainfile logger was using too much resources when rotating the logs at end of month. This has been improved somewhat, however there still can be issues for very busy sites. To help resolve this, the settings for the "Compatibility Logger" have been restored to the configuration. The compatibility logger writes to "date-stamped" filenames instead of doing an end-of-month rotation.

As an alternative, there is a new Foswiki:Extensions.LogDispatchContrib for more advanced logging. This extension will be the default logger in Foswiki 1.2.

JQuery Chili highlighter is enabled by default.

This was temporarily disabled because Firefox and Safari had errors which will corrupt the highlighted text. Recent browser releases have resolved this issue, and Chili is again enabled by default. It may still be necessary to disable Chili if your user community still is using the buggy browsers.

configure now backs up the configuration

Markup within input fields are no longer rendered

   <input ... text=' WikiWord *bold* text'>   previously was rendered,  on 1.1.6 will be shown exactly as written.
   <input ... text='<nop>WikiWord' >     Is acceptable,  but the <nop> is unnecessary.
   <input ... text='<literal>some *bold* text</literal' >   The <literal> tags MUST be removed

Sandbox System topic updated with improved validation of new topic name

Important changes in Foswiki 1.1.5

Release 1.1.5 is a security focused release. There are a number of fixes and small enhancements designed to improve the security of Foswiki.

API Change

• Foswiki::Func::getScriptUrlPath() has been removed from deprecation, and enhanced with a new calling convention to be consistent with Foswiki::Func::getScriptUrl().

Improvements to User Registration

• The complete fix for CVE-2012-1004 has been integrated, including pluggable field validations in the User Mapper. If your installation uses a custom user mapper, there is a new function in the base user mapper lib/Foswiki/Users.pm that performs registration field validations. Override this method in your custom user mapper to add site specific validations.
• The user registration and group management API calls now all return error messages describing any failures. All errors are processed through MAKETEXT so that they are translated to the selected language.
• New options can reject duplicate registrations using the same email, and can either white-list or black-list email domains from registering.

Improvements to .htpasswd handling

• The HtPasswdUser password manager has been changed to globally cache the password file if enabled. In an installation running fcgi or mod_perl, this will reduce the overhead of reading the file for each transaction.
• The .htpasswd lock file is now configurable. There was a small risk that when multiple foswiki installations shared a common .htpasswd file, simultaneous updates would not be prevented, resulting in file corruption.
• The default for {Htpasswd}{Encoding} has been changed to apache-md5. We strongly recommend that installations migrate away from crypt encoding - the prior default. crypt truncates passwords at 8 characters.
• The {Htpasswd}{AutoDetect} option is enabled by default. This ensures that an existing .htpasswd file cannot be accidentally corrupted due to the change in default encoding.
• A new password encoding hash has been added. bcrypt encoding. (Ref. http://yorickpeterse.com/articles/use-bcrypt-fool )

Better session support for mixed http and https environments

If your foswiki is set up to accept both https and http requests, your users may find themselves logged out much faster than desired.

Changes to the configure password handling

Changes to Statistics processing

• The Foswiki configuration has a new parameter: {Stats}{AutoCreateTopic} (Default is disabled)
• The statistics script has a new parameter: -autocreate 1 or autocreate=1 (Default is 0 or disabled)
• The statistics script must now only be run using POST. HTML GET should never result in an update.

Changes to PlainFile logger to improve log rotation

This behavior has been corrected, however sites where rotation was failing may have extremely large log files. When foswiki performs the rotation at the beginning of the next month, rotation can take an extended time, resulting in extended response time.

• The directory containing the log files must be writable.
• Archive files named [logfile].YYYYMM must not exist for any records in the current [logfile].log file.
  • For example, if events.log contains an event dated 2012-01-15:, then the archive file events.201201 must not exist.

• Quiesce the web server to prevent logging activity
• Upgrade to 1.1.5, which will install the updated lib/Foswiki/Logger/PlainFile.pm
• Reset the timestamps to the previous month on the logfile requiring rotation
  • touch -t 201202280101 events.log will set the timestamp to February 28th on a linux/unix system.
  • Windows users will need to install a 3rd party tool to change timestamps, or wait for the next month
• Change to the bin directory and run the view script from the shell as the web user.
  • sudo -u www ./view (Actual user will vary depending on the distribution)

Important changes in Foswiki 1.1.4

1.1.3 may have changed some form.name MetaData to contain fully-qualified (with web name prefix) values

Please note, you may be unaffected by https://foswiki.org/Tasks/Item10874 if:

• You have never used Foswiki 1.1.3
• You are not QuerySearching form.name MetaData for exact topic-only (without web prefix) values, or
• Your users are not adding or changing DataForms on their topics via the edit screen's "add/change form" button, or
• Your installation is using Foswiki:Extensions.NatEditPlugin

Description

   * Set WEBFORMS = MyForm

   * Set WEBFORMS = TheWeb/TheSubWeb.MyForm

%SEARCH{"form.name='MyForm'" type="query" ...}%

%SEARCH{"form.name='MyForm' OR form.name='TheWeb/SomeSubWeb.MyForm'" type="query" ...}%

%SEARCH{"form.name=~'\bMyForm$'" type="query" ...}%

Email enhancements

Significant enhancements were made to the Foswiki email implementation. These changes increase our compatibility with email services like Google's gmail, add enterprise features like S/MIME signed mail, and add a test facility to help the administrator better diagnose email problems before testing registration.

• Item10521: Implement SSL support, which adds direct support for gmail.
• Item10522: Implement S/MIME support for signed email using either sendmail or the Net::SMTP methods.
• Item10523: Add configure parameter to select GMT or Servertime in generated email messages
• Item10919: Implement an Email test function in configure.

Email linking improvements in Foswiki topic rendering.

• Item10905: Unable to include spaces in the query string of mailto links
• Item10660: Some email address autolinking doesn't work
• Item11059: Email address followed by a dot generates email link with dot included

Also the detection of email addresses in topics is significantly improved and is much closer to the Email address specification in RFC:5322 and the mailto URL specifications in RFC:3696.

Password Authentication enhancements Item9164 and Item10962

• With this change, it is now possible to migrate to an alternate password Encoding without invalidating existing user passwords.
• The performance of HtpasswdUser.pm has been improved by up to 30% with large .htpasswd files
• A new encryption mode - apache-md5 has been added. This official Apache variation on MD5 encoding is compatible with the passwords generated by the htpasswd -m command.
• The encoding previously labeled md5 has been renamed to htdigest-md5 and is compatible with the encoding generated by the Apache htdigest command. The config setting will be modified by a config checker the first time you run configure after upgrade. It is recommended to save your configuration.
  • Note that it is also now possible to modify the {AuthRealm} setting without invalidating existing passwords.
• Cross-platform compatibility issues between Linux, Apple OSX and MS Windows have been resolved and .htpasswd files should be portable regardless of the selected encoding.
• The Crypt::PasswdMD5 CPAN module is required for the apache-md5 encoding, as well as for better cross-platform compatibility.

Note: It is strongly recommended that sites using the old default "crypt" encoding migrate to a stronger method. The crypt method truncates passwords at 8 characters and silently discards the rest. For the highest security, choose htdigest-md5 encoding with Apache htdigest authentication. If using Template authentication, if possible use a SSL client connection - HTTPS.

Changes to User Registration topics Item1539

Changes to Foswiki Logging - Item10637, Item11157

• An Expert parameter is provided to use a mask (x.x.x.x) instead of the hashed IP address where absolute anonymity is required.
• Note that AUTHENTICATION FAILURE messages are never obfuscated. This permits tools like fail2ban to be used to block penetration attempts.

Major JQuery changes

• Foswiki has been updated to include JQuery 1.7.1, and this is now the default version of JQuery. After installing Foswiki 1.1.4, be sure to visit bin/configure and verify that the JQuery Plugin is configured to use this version.
• The JQuery Autocomplete plugin has been replaced by the incompatible JQueryUI Autocomplete widget. If your site has implemented forms using the old version of Autocomplete, they will not work until converted to the new API. See https://foswiki.org/Support/JQueryMigrationGuide
• The JQuery Textboxtlist plugin has been updated with an incompatible version. See the above referenced JQueryMigrationGuide for details.
• The JQuery Chili syntax highlighting plugin is incompatible with Firefox 7 and Safari Rev. 6-17-2011.

Changes to Store

• If a topic is modified (file revision date of file is newer than the date of the .txt,v file):
  • The TOPICINFO metadata stored with the topic textfile is ignored.
  • Modified by is reported as UnknownUser
  • Modified timestamp is the file timestamp
  • Revision number is 1 greater than the last revision known to RCS.
  • Topic comment is pending, indicating there are changes not yet checked into RCS.
  • The next change to the topic under Foswiki control will record the external changes into RCS, and create a new revision for the changes saved in this iteration.
• If a topic rcs .txt,v file is newer than the topic file
  • The TOPICINFO is trusted
  • This avoids unnecessary overhead by the RCS system.
• If a topic is modified externally and checked into RCS outside of Foswiki control, it is very important to generate a valid TOPICINFO line or the data reported by Foswiki will be incorrect.

Note that Foswiki also now requires that the %META:TOPICINFO be the first line of the file.

Changes to SpreadSheetPlugin

• LEFTSTRING position of first character would vary.
• LISTUNIQUE would fail to eliminate duplicate entries due to leading or trailing spaces.

• SPLIT( separator, text ) -- split a string into a list.
• HEXENCODE and HEXDECODE -- Encode and decode a string to/from printable hex.
• XOR( list ) Logical XOR of integers in a list.
• BITXOR( list ) -- Bitwise XOR of integers in a list.
• BITXOR( string ) -- Bitwise NOT operation on the string.
• LISTNONEMPTY( list ) -- Remove all empty elements from a list
• WHILE( condition, do ) -- Repeat the "do" function while the "condition" remains true.
• isodate formats -- ISO 8601 week support.
• DOY -- Day of Year dates: DOYyyyy.ddd for example to specify the ddd day of yyyy

Changes to JSCalendarContrib.

Important changes in Foswiki 1.1.3

SEARCHDEFAULTTTYPE restored

• It only applies to the WebSearch and WebSearchAdvanced. On Foswiki 1.0 it also applied to the %SEARCH macro.
• The (ignored) default in DefaultPreferences is keyword, but on 1.1, WebSearch defaulted to word
• WebSearchAdvanced had a hardcoded default of word on both 1.0 and 1.1. This is changed to use the SEARCHDEFAULTTTYPE setting.
• The historical mis-spelling (SEARCHDEFAULTTTYPE) is preserved.

Important Changes in Foswiki 1.1.2

Changes to %GROUPS% and %GROUPINFO% Macros

JQueryPlugin update to jQuery 1.4.3

1. set {JQueryVersion} in configure under Extensions → JQueryPlugin to 1.4.4
2. Clear browser cache
3. test non-default plugins and any custom jQuery javascript code for compatibility with jQuery 1.4.3.

Improved handling of legacy logging format

Foswiki 1.1 changed the logging format and the default location of the log files. See below for more information.

Important changes in Foswiki 1.1.0

Foswiki 1.1 has many improvements that end users as well as administrators will appreciate. In addition Foswiki 1.1 comes with a lot of "under the hood" improvements to the core code, with the goal of making it easier to plug in work from other projects, such as jQuery, KinoSearch, Solr and others. Work has been made to improve the definition of internal APIs to allow other not-yet-written modules, such as store implementations, to plug in. Most of these modifications should be invisible to the end user and the admin, but are important to position Foswiki for the next generation of improvements. Here is a list of the most important enhancements in Foswiki 1.1.0

Adoption of the jQuery Javascript user interface framework

New macros enabled by jQuery

• BUTTON{"text" ...} -- renders a nice button
• TABPANE{...}, ENDTABPANE, TAB{"text" ...}, ENDTAB -- tabpane widget
• JQICON{"name" ...} -- render an image
• JQICONPATH{"name"} -- render the urlpath to an image
• JQPLUGINS{"plugins" … } -- display a summary of avaliable plugins
• JQREQUIRE{"plugin, plugin, … "} -- enable a plugin on the current page
• JQTHEME{"name" ...} -- switch jQuery UI theme
• POPUPWINDOW{"topic" ...} -- opens a topic or url in a new window

Powerful new QUERY macro

• supports formatted access to formfields and other meta-data in topics using the same syntax as is used in IF and SEARCH statements,
• gives access to all meta-data, including that added by extensions,
• supports reporting values using JSON and other standards, simplifying the retrieval of meta-data for REST applications,
• replaces the FORMFIELD macro for most applications.

Re-architecting of the SEARCH macro

FORMAT macro

WikiGroups have add & remove user interface

For developers additional API's have been added to the Foswiki code to allow these Forms to also be used for non-Foswiki user and group backends.

With some configuration, Foswiki can also add users to groups on registration - either automatically, or allowing the users to select groups to join.

TinyMCEPlugin updates

• Smarter attach dialogue
• Background autosave feature has been enabled (saves to local browser storage at 3 minute intervals)
• New context (right-click) menu:
  • Set syntax highlighting classes on verbatim blocks
  • table rows/columns may be duplicated, cells merged/split
• Customisation via the TINYMCEPLUGIN_INIT preference has been improved. Read the upgrade advice if you are upgrading a Foswiki installation which uses a custom TINYMCEPLUGIN_INIT preference setting.

Testing configuration variables in %IF

"Copy topic" now copies attachments

Tailoring of user registration made easier.

This means that your tailored version in Main web will not be overwritten by future upgrades.

Easy tailoring of reset/change password and change email forms

TMPL:DEFs may now access previous (overridden) TMPL:DEF

New Logging architecture and location for log files

Migration considerations

Logging Configuration

• As of Release 1.1.6, the Compatibility logger can be configured using the configure web interface. On extremely busy systems with very large log files, the Compaibility logger provides better performance at month end because it does not "rotate" the log files.
• Some very old (pre-Foswiki) Extensions write directly to Log File configured in $Foswiki::cfg{LogFileName}. Foswiki will attempt to set a reasonable default value to maintain backwards compatibility. It is recommended to configure this filename if you run old pre-Foswiki extensions that write directly to the log.

$Foswiki::cfg{Log}{Implementation} = 'Foswiki::Logger::PlainFile';
$Foswiki::cfg{Log}{view} = 1;
$Foswiki::cfg{Log}{search} = 1;
$Foswiki::cfg{Log}{changes} = 1;
$Foswiki::cfg{Log}{rdiff} = 1;
$Foswiki::cfg{Log}{edit} = 1;
$Foswiki::cfg{Log}{save} = 1;
$Foswiki::cfg{Log}{upload} = 1;
$Foswiki::cfg{Log}{attach} = 1;
$Foswiki::cfg{Log}{rename} = 1;
$Foswiki::cfg{Log}{register} = 1;
$Foswiki::cfg{ConfigurationLogName} = 'foswiki-root/data/configurationlog.txt';
$Foswiki::cfg{DebugFileName} = 'foswiki-root/data/debug.txt';
$Foswiki::cfg{LogFileName} = 'foswiki-root/data/log%DATE%.txt';
$Foswiki::cfg{WarningFileName} = 'foswiki-root/data/warn%DATE%.txt';

$Foswiki::cfg{Log}{Dir} = '$Foswiki::cfg{WorkingDir}/logs';
$Foswiki::cfg{Log}{Implementation} = 'Foswiki::Logger::PlainFile';
$Foswiki::cfg{Log}{Action} = {
          'search' => 1,
          'rest' => 1,
          'viewfile' => 1,
          'edit' => 1,
          'register' => 1,
          'save' => 1,
          'rename' => 1,
          'changes' => 1,
          'view' => 1,
          'rdiff' => 1,
          'upload' => 1,
          'attach' => 1
        };
$Foswiki::cfg{DebugFileName} = '';
$Foswiki::cfg{LogFileName} = '';
$Foswiki::cfg{WarningFileName} = '';

Logging of access failures

• working/logs/configure.log
• working/logs/events.log

configure user interface revamp

Configure file system checks

Because of prior inconsistencies in the files distributed with Foswiki and TWiki core and extensions, migration of older Foswiki or TWiki installs may see excessive errors reported by configure. You are recommended to correct the file system permissions.

Newer modern icon set for Document Graphics

Table Plugin has been improved

Sorting has been improved so the plugin can now better handle mix of formats and even empty cells.

!1 Notes for extension authors

API Enhancements

• copyAttachment

• saveTopic (ignorepermissions)

Deprecated handlers

Deprecated handlers will continue to work as documented in 1.1 and for the immediate future, but will be removed in a future release. Extension authors are strongly recommended to implement the new handlers as soon as possible.

Deprecated Foswiki::Func functions

Refactored Foswiki::Store and new Foswiki::Meta functions

Tainting

$validWebName = Foswiki::Sandbox::untaint(
    $webName, \&Foswiki::Sandbox::validateWebName);
$validTopicName = Foswiki::Sandbox::untaint(
    $topicName, \&Foswiki::Sandbox::validateWebName);

$ENV{FOSWIKI_ASSERTS} = 1;

Foswiki Release 1.1.0 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.1 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.2 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.3 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.4 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.5 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.6 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.7 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.8 Details

Fixes

Foswiki Patch Release 1.1.9 Details

Fixes

Enhancements

Foswiki Patch Release 1.1.10 Details

Fixes

Enhancements