We are looking forward to an interesting 2017 in the Foswiki space. There are several feature proposals under review which could be quite transforming for the next major Foswiki release.
There is good news for public facing Foswiki systems: you can now safely disable CGI sessions for guest users to gain a noticeable performance improvement. While previous releases already had that switch, user registration and password maintenance were negatively affected. Starting with this release it is safe now to deactivate CGI sessions for guests.There have been a couple of changes in how the “refresh” url parameter is used to force a new page to be generated: first, it has been removed from guest views to prevent crawlers from following the link and thus invalidating the cache. Second, only admin users are allowed to nuke all of the site’s page cache using
However, as things move forward, we thought you might enjoy some of the features and benefits backported to the 1.1.x platform in the form of this release. This is especially important if you are facing plugin upgrades for a Foswiki-1.1.x engine. Extensions that take advantage of the new features introduced during the 2.0 development cycle will be incompatible with Foswiki-1.1.9 and older. This release will help you keep them running on the Foswiki-1.1.x engine.
This release is also critical for any sites facing a server platform upgrade. Several Perl features and CPAN module changes released over the past couple of years are completely incompatible with Foswiki-1.1.x releases. Foswiki-1.1.10. Foswiki should be upgraded to Foswiki-1.1.10 or Foswiki-2.0.3 before any updates to Perl or CPAN modules.
Note that Foswiki 1.1.10 will be the last maintenance release of this series. The community is now focusing on future features for the upcoming Foswiki 2.1.0 release, while still bug-fixing the 2.0.x branch.
Foswiki 1.1.10 does not contain fixes for most of the security issues fixed in the Foswiki 2.0.x releases. Upgrade to the latest Foswiki 2.0 release is strongly recommended.Here are the complete release notes.
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.
Including this feature in the Foswiki 1.1 engine allows sites to begin migration activity on Foswiki 1.1 before the actual migration to Foswiki 2.0. It allows new extensions to ship with the new style ACLs and remain Foswiki 1.1 compatible.
The CALC and CALCULATE macros now encode < and > as entities, which prevents some paths used to insert script tags. If your user’s topics require CALC or CALCULATE to generate HTML, then you must enable the following setting:
* Set SPREADSHEETPLUGIN_ALLOWHTML=1
This setting can be set in the topic, web, user or site preferences.