XOOPS 2.7.5 Beta 2 — more fixes, a security advisory check for bundled librariesThe XOOPS Development Team is pleased to announce
XOOPS 2.7.5 Beta 2, the second test release of XOOPS 2.7.5. It is a maintenance release: it collects the bug fixes and hardening made since XOOPS 2.7.4 and adds a light/dark toggle to the Default and Transition admin themes. Beta 2 adds the fixes made since Beta 1, a check of the bundled libraries against published security advisories, and updated libraries. XOOPS 2.7.5 runs on PHP 8.2 through 8.6. This is a beta for testing: please try it on a copy of your site, not on a production site.
DOWNLOAD:
https://github.com/XOOPS/XoopsCore27/releasesNew since Beta 1- The Composer Packages panel of the control panel marks every bundled library whose installed version is covered by a published security advisory, with a link to the advisory. It asks Packagist at most once a day and sends the package names only
- The upgrade wizard asks you to confirm a current backup of the database, mainfile.php and xoops_data before the first patch, and clears the caches again after the last one
- Clearing the caches keeps the .htaccess, .user.ini, php.ini and web.config files a site has placed in the cache folders
Fixes since Beta 1- The fatal-error page shows the message and backtrace only to a webmaster while debugging is enabled, and is sent with HTTP 500 instead of 200. The debug panel and the Smarty debug console follow the debugLevel setting on every page
- Sign-in accepts the password exactly as it was set: a password with a leading or trailing space, or with angle brackets, could be set but not used to sign in
- xoops_data/.htaccess works on Apache 2.4 without mod_access_compat, where the old file caused HTTP 500 instead of 403. The shipped directories that had no index file get one, so Apache no longer lists their contents
- Every page sends X-Content-Type-Options: nosniff, and the search form no longer puts security tokens into the search URL
- Upgrade wizard: the Smarty 4 template repair keeps the original template until the repaired version is complete, the older patches (2.0.18 to 2.5.11) no longer stop with PHP 8 errors, and the character set conversion keeps empty-string column defaults
- The TinyMCE 5 and 7 image manager can delete images and categories again, and removes an image's file only when it lies inside the uploads folder
- Comments: links keep a module's extra parameters (such as a forum id) intact, and a new comment whose thread cannot be saved shows a message instead of a PHP error
- The file cache's garbage collection removes an entry once its own expiry has passed, and the cache 'lock' setting no longer stops reads with a TypeError
- The FineUploader endpoint reports I/O failures with an HTTP error status instead of success, and keeps the chunks for a retry
- The installer's path page checks again that mainfile.php, uploads and the xoops_data folders are writable, and no longer widens permissions to 0777
- A text sanitizer extension that cannot be loaded (such as flash, removed in 2.7.0) is skipped instead of stopping every page that shows BBCode, and an [img] tag works with a language pack that lacks the image texts
- Control panel: pages that choose another template after the header raise no warning, the user search popup keeps every selected group across pages, and a failed Profile registration step shows its errors
- XML-RPC (off by default, and now deprecated): /xmlrpc.php parses requests again, including indented ones, and accepts a name or password holding a quote or backslash. getPost returns a story that is not public (awaiting approval, scheduled or expired) to an administrator of the News module only
- PHP 8.6 is supported: a NUL byte in request input no longer stops a page with a ValueError there, and the unit and integration tests run on PHP 8.2 through 8.6. The XML parsers raise no deprecation notices on PHP 8.4 and later
Bundled libraries- XMF 1.3.4 RC3. Release notes: https://github.com/XOOPS/xmf/releases/tag/v1.3.4-RC3
- xoops/helpers 1.1.3: the native XOOPS cache returns cached values with their types intact, Filesystem::unzip() refuses archives that would write through links and caps the decompressed size, and a NUL byte in a path is reported as a failure instead of a ValueError on PHP 8.6
- xoops/smartyextensions 2.0.0 Beta1
- Smarty 4.6.0, which supports PHP 8.5 and 8.6, and Monolog 3.13.0, which hardens its line, redacting and syslog formatters
- php-debugbar 3.8.1, symfony/var-dumper 7.4.22, firebase/php-jwt 7.2.2, kint 6.1.1, symfony/polyfill-mbstring 1.43.3 and webmozart/assert 2.5.1
- New: composer/semver 3.6.0, which the advisory check uses, and xoops/moduletools 1.7.2 for module install, admin and test tooling
For theme and module developers- The smartyextensions plugins sanitize_url, linkify, pretty_print_json, format_phone_number, format_date, relative_time, format_currency, number_format, mask_email and datetime_diff, the direct output of xo_get_config and get_session_data, and <{asset_url}> of xoops/helpers now HTML-escape their own output. Remove any |escape after them, or the output is double-encoded. linkify takes plain text and shows HTML passed to it as text
- A module script that outputs CSS or JavaScript through the XOOPS bootstrap must send the matching Content-Type header, because every page now carries X-Content-Type-Options: nosniff
- xoops/helpers Cache: cache scalars and arrays. Objects come back as __PHP_Incomplete_Class, and a null result is not cached
- xoops/moduletools is bundled from Beta 2 on. ModuleTools provides reusable services under Xoops\ModuleTools\ without requiring an installed or active module, so a module can use it on any site running 2.7.5 Beta 2 or later
- The XMF 1.3.4 notes from Beta 1 still apply (Session and Serializer refuse objects and enums, MASK_ALLOW_HTML keeps only relative, http, https and mailto addresses, executeQueue(true) for GET writes)
Deprecated in 2.7.5XML-RPC is deprecated and will be removed in XOOPS 2.8.0: the /xmlrpc.php endpoint, its xmlrpc_enabled setting, and the Blogger, MetaWeblog, MovableType and XOOPS API classes in class/xml/rpc. The endpoint is off by default. A site that has enabled it keeps a working endpoint throughout 2.7.x and should plan for another way to publish before upgrading to 2.8.0.
Upgrading from 2.7.4 or 2.7.5 Beta 1Copy the new files over the web root and
run the upgrade wizard. There are no database changes since 2.7.4. The wizard's 2.7.5 patch updates xoops_data/.htaccess for Apache 2.4: it rewrites the file only when it still holds the two lines XOOPS shipped, and reports a file it cannot write.
- If xoopsconfig.php sets 'xmlrpc_enabled' => true, /xmlrpc.php now answers calls; until this release it rejected every request. Leave the setting off if you do not use XML-RPC
- If your site used the Dark admin theme, it now loads Transition; switch dark mode on with the toggle in the header. The leftover modules/system/themes/dark folder can be deleted
- If you copied extras/login.php (the SSL popup login) somewhere on your site, replace that copy: updating the core does not patch it
- A site running a custom template set should re-import it, as for any core template change
Upgrading from 2.7.3 or earlierCopy the new files over the web root and
run the upgrade wizard. From 2.7.3 it creates the user_2fa table and the two-factor preference, registers the SCEditor emoticons as smileys, and adds the Editors preferences. No mainfile.php changes are needed. Replace any copy of extras/login.php, because an older copy skips the two-factor step.
System requirementsPHP 8.2 to 8.6, MySQL 5.7+ or MariaDB 10.3+, and the sodium extension for two-factor authentication.
LanguagesBeta 2 adds nine English language constants since Beta 1: four upgrade wizard messages, one comment message and four texts of the Composer Packages panel in the admin themes. See docs/lang_diff.txt.
Thank you to everyone who tested Beta 1 and reported issues. Report problems with this beta at
https://github.com/XOOPS/XoopsCore27/issues