Skip to content

Releases

XOOPS 2.7.5 Beta1

XOOPS 2.7.5 Beta1 Pre-release
Pre-release

Choose a tag to compare

@mambax7 mambax7 released this 12 Nov 23:02
10bf608

XOOPS 2.7.5 Beta 1 — maintenance release with a dark mode for the admin themes

The XOOPS Development Team announces XOOPS 2.7.5 Beta 1, the first 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, adds a light/dark toggle to the Default
and Transition admin themes, and updates the bundled XMF library. XOOPS 2.7.5
runs on PHP 8.2 through 8.5.

Download XOOPS 2.7.5 Beta 1:
https://github.com/XOOPS/XoopsCore27/releases

This is a beta: please test it on a copy of your site, not on a production
site, and report problems on the issue tracker.


Admin themes: light and dark

  • Default and Transition have a light/dark toggle in the header that
    remembers your choice.
  • Default adds dark styling for module panels, permission grids and
    SCEditor.
  • The standalone Dark theme is removed. A site that had selected it loads
    Transition, where the header toggle switches dark mode on.
  • The System section in the Modern theme's sidebar is hidden when the user has
    no system menu items.

Fixes since 2.7.4

  • Uploads. The media uploader accepts .webp images again (#301), reports
    only the current file's errors when a request names several upload fields,
    and strips every inner executable extension from a file name.
  • Themes. The theme selector block works again after a theme was chosen
    through a URL, and the admin redirect page renders in the theme it was built
    for.
  • Editors. Editor forms stay within the content column across themes;
    SCEditor toolbars wrap, restored drafts open visually and image previews fit.
  • Upgrade wizard. It no longer re-applies the 2.3.3-to-2.4.0 patch after
    2.7.3, and its Smarty 4 template repair no longer quotes across two adjacent
    tags (#294); it also restores templates damaged by earlier runs.
  • Protector. It writes its sanitised request values back again, matches
    reliable IPs exactly or by subnet, counts every password login against the
    submitted user name, and never drops tables of the working prefix.
  • Sign-in and sessions. An expired session is refused on every lookup, a
    remember-me login starts a fresh session ID, and LDAP and Active Directory
    sign-in refuses an empty password.
  • Administrator permissions are tightened in the System and Profile user
    admin, the block admin and the module list. Registration and profile edits
    can no longer write rank, post-count or credential columns.
  • Text handling. Automatic linking works only on text between tags, BBCode
    arguments cannot rewrite an earlier tag's attribute, and Markdown rendering
    bounds its work on untrusted text.
  • Images. image.php serves a picture with the type its content decodes
    as, limits the filters applied to an edited image and sends nosniff on
    every response.
  • Cache. The file cache refuses keys that contain a path.

Bundled libraries

  • XMF 1.3.4 RC1 (release notes).
    It tightens input filtering, safe serialization, search highlighting and
    database identifier quoting.
  • symfony/yaml 7.4.23, which bounds the time its parser spends on a crafted
    document.

For module developers

XMF 1.3.4 rejects some input that 1.3.3 accepted:

  • Xmf\Module\Helper\Session no longer stores or returns objects and enums.
    Store scalars and arrays (an enum as its backing value).
  • Xmf\Security\Serializer rejects a stored object or enum unless its class is
    passed as allowed.
  • HTML accepted through Xmf\Request with MASK_ALLOW_HTML keeps link and
    image addresses only when they are relative or use http, https or
    mailto. data:, tel: and ftp: addresses are removed.
  • Xmf\Database\Tables::executeQueue() needs executeQueue(true) to write
    from a GET request.
  • Xmf\Module\Helper::getHandler() accepts only letters, digits and _ in a
    handler name.

Upgrading from 2.7.4

Copy the new files over the web root. There are no database changes since
2.7.4; running the upgrade wizard is harmless but not required.

  • 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 is no longer offered in the theme
    selector and 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 earlier

Copy 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. The notes under "Upgrading from 2.7.4" apply
as well; in particular, replace any copy of extras/login.php, because an
older copy skips the two-factor step.

System requirements

PHP 8.2 to 8.5, MySQL 5.7+ or MariaDB 10.3+, and the PHP sodium extension for
two-factor authentication.

Languages

XOOPS 2.7.5 adds one English language constant, the "Dark mode" label of the
Default and Transition admin themes. Language packs are maintained at
XoopsLanguages.

Full changes: docs/changelog.270.txt. Language changes: docs/lang_diff.txt.

Thank you to everyone who submitted pull requests, reported issues and tested
the 2.7.4 release.

XOOPS 2.7.4

Choose a tag to compare

@mambax7 mambax7 released this 17 Oct 04:06
3615ff8

XOOPS 2.7.4 Final

2.7.4 went through Beta 1, Beta 2, RC 1 and RC 2 between September and October. Final collects everything from that cycle plus the fixes made since RC 2. There are no new features since RC 2.

Two-factor authentication in the core

Every member can protect their account with a second step at login.

  • Two methods. A time-based authenticator app (Google Authenticator,
    Microsoft Authenticator, Aegis, FreeOTP, or any password manager that
    generates TOTP codes), or a six-digit code mailed to the member's address.
  • Recovery codes. Ten one-time codes at enrolment, for the day the phone
    or the mailbox is out of reach. Members can replace them from Edit Account.
  • Lock-out protection. Five wrong codes lock the second step for fifteen
    minutes and the member is notified by e-mail.
  • Administrators can reset a member's factor from the Users page, and an
    operator locked out of the site has a documented escape hatch in
    docs/2fa-operations.md.
  • Off by default. Switch it to "Optional" in System Preferences and every
    member may enrol. Nobody is forced.
  • Secrets are encrypted at rest with a site key. Mailed codes are stored
    hashed and expire after ten minutes. Remember-me cookies are bound to the
    enrolled factor, so a reset invalidates them.
  • Every login path that cannot show a challenge (the upgrade wizard, XML-RPC,
    the SSL popup) refuses an account that must present its factor.

Editors

  • SCEditor is now a full visual editor. It edits with its complete
    toolbar and keeps XOOPS BBCode intact across visual and source modes. Its
    emoticons are registered as XOOPS smileys. It is the default editor for new
    installs; an upgraded site keeps its current editor settings.
  • Markdown support. EasyMDE stores Markdown in the existing text columns
    and MyTextSanitizer renders it with Parsedown in safe mode, so modules get
    Markdown without a schema change.
  • New Editors preference category in System Preferences for toolbar and
    editor settings.
  • MyTextSanitizer renders the tags SCEditor's toolbar writes: [sub],
    [sup], [s], [justify], [hr], [ol] and tables.
  • TinyMCE 7 is updated to 7.9.3.

Security hardening

The cycle included a review of the core with CodeQL, Snyk, SonarCloud,
Scrutinizer and manual audits. The main results:

  • Form security tokens no longer depend on the browser's User-Agent. A
    token is a random value compared in constant time, so a browser update or a
    privacy extension between opening and submitting a form no longer rejects
    it. Protector's admin pages use the same core token.
  • One same-site check for every redirect. Login, post-login and
    theme-switch return addresses refuse targets written with backslashes,
    encoded slashes, HTML entities or embedded line breaks.
  • Remember-me tokens are revoked when the password changes, and a
    restored session ends for a deactivated account.
  • Registration is validated at the save step, not only at step 1, and a
    comment must belong to the requesting module on edit, save and delete.
  • Uploads are deleted only inside the upload directory. The image
    manager and the smilies, rank and avatar admin pages resolve a stored file
    name before they delete it. The TinyMCE image manager checks category
    permissions on upload and delete.
  • Protected database dumps are written only under XOOPS_VAR_PATH, into
    a directory guarded by a deny-all .htaccess.
  • Cache ids use a random site key instead of the database credentials,
    and the installer renames itself and its cleanup script with random names.
  • LDAP and Active Directory fail closed when StartTLS was requested and
    failed.
  • Server configuration. xoops_lib/.htaccess works on Apache 2.4 without
    mod_access_compat, PHPMailer's unused OAuth helper is removed from the
    vendor tree, and reCAPTCHA v2 verifies over POST so the secret key stays out
    of server logs.
  • Confirmation pages, error lists and the SQL built by the legacy
    XoopsTopic and XoopsTree helpers are escaped and quoted.

Since RC 2

  • XMF 1.3.3. Proxy headers (proxy_env) are honoured only when the
    direct peer is listed in the new proxy_trusted setting, as addresses or
    CIDR ranges. Sites that set proxy_env must add proxy_trusted in
    xoops_data/configs/xoopsconfig.php; until then the peer address is used.
    Forwarded headers are parsed per RFC 7239.
  • image.php no longer crashes on PHP 8.3+ when an angle is requested.
  • LDAP and Active Directory logins on PHP 8.3+ no longer emit a deprecation,
    and a bare IPv6 server address is handled.
  • Values stored as XOBJ_DTYPE_UNICODE_ARRAY reload as the array that was
    stored. Values such as café or a+b lost characters before.
  • The |replace and |escape modifiers no longer emit PHP 8.6 deprecations,
    and templates can use |sprintf without a Smarty notice.
  • Library refresh: HTML Purifier 4.19.1, Monolog 3.12.1, Smarty 4.5.8,
    TCPDF 6.11.4, symfony/var-dumper and symfony/yaml 7.4.21, firebase/php-jwt
    7.2.1, Punic 3.8.2, webmozart/assert 2.5.0.

The full list is in docs/changelog.270.txt.

Upgrading to 2.7.4

From 2.7.4 RC 2: copy the new files over the web root. There are no
database changes since RC 2, so the upgrade wizard is not required. If your
site sets proxy_env, add proxy_trusted as described above.

From XOOPS 2.7.3 or a 2.7.4 beta: copy the new files over the web root
and run the upgrade wizard. It creates the user_2fa table and the
two-factor preference, registers the SCEditor emoticons as smileys, adds the
Editors preferences and updates the System module. No mainfile.php changes
are needed.

  • Two-factor authentication needs the PHP sodium extension; the wizard
    reports whether it is available.
  • Every remembered device logs in once more after the upgrade.
  • If you copied extras/login.php elsewhere on your site, replace or remove
    that copy.
  • A site running a custom template set should re-import it.

From 2.5.11 or earlier: follow the
XOOPS Install and Upgrade Guide.
Run upgrade/preflight.php first; 2.7 moved to Smarty 4 and some older
themes need changes.

System requirements

  • PHP 8.2 to 8.5
  • MySQL 5.7+ or MariaDB 10.3+
  • The PHP sodium extension for two-factor authentication

What's Changed

  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #180
  • Version correction by @mambax7 in #182
  • fix(upgrade): report stalled patch tasks instead of re-queuing silently by @mambax7 in #184
  • refactor(system): move front-end MENUS_* labels out of the admin lang… by @mambax7 in #185
  • security(imagemanager): check category permissions in the editor plugin and pass insert codes as data by @mambax7 in #186
  • security(profile): validate a new account at the save step, not only at step 1 by @mambax7 in #187
  • security(session): end restored sessions for inactive accounts and refresh groups per request by @mambax7 in #188
  • security: tighten the upgrade gate, directory TLS and the comment edit form by @mambax7 in #189
  • fix(system): define _AM_SYSTEM_USERS_NO_SUCH_USER for the users admin page by @mambax7 in #190
  • chore(tinymce): update TinyMCE 7 from 7.9.2 to 7.9.3 by @mambax7 in #193
  • security(session): revoke remember-me tokens when the stored password hash changes by @mambax7 in #194
  • fix(user): clear the remember-me cookie on logout only when a cookie name is configured by @mambax7 in #195
  • security(comment): require a posted or deleted comment to belong to the requesting module by @mambax7 in #196
  • docs(changelog): add the 2.7.4 Beta 1 release notes by @mambax7 in #197
  • fix(profile): guard the logout cookie name in the profile module's own logout too by @mambax7 in #198
  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #199
  • refactor(login): split password login into authenticate and establish-session helpers by @mambax7 in #201
  • chore(deps): bump orhun/git-cliff-action from 4.8.0 to 4.9.0 by @dependabot[bot] in #200
  • chore(deps): bump postcss-selector-parser from 6.1.2 to 6.1.4 in /htdocs/themes/xtailwind by @dependabot[bot] in #202
  • chore(deps): bump postcss-selector-parser from 6.1.2 to 6.1.4 in /htdocs/themes/xtailwind2 by @dependabot[bot] in #203
  • feat(token): extend the token handler for recovery codes and delete tokens with the account by @mambax7 in #204
  • security(2fa): add the two-factor storage layer by @mambax7 in #205
  • security(2fa): challenge a login that carries a second factor and bind sessions and cookies to it by @mambax7 in #206
  • feat(2fa): complete management, preflight and MySQL coverage by @mambax7 in #207
  • feat(2fa): e-mail codes as a second method, themed pages, clearer setup by @mambax7 in https://github.com/XOO...
Read more

XOOPS 2.7.4 RC2

XOOPS 2.7.4 RC2 Pre-release
Pre-release

Choose a tag to compare

@mambax7 mambax7 released this 06 Oct 12:44
fd93928

XOOPS 2.7.4 RC 2 — security hardening ahead of the final release

The XOOPS Development Team is pleased to announce XOOPS 2.7.4 RC 2, the
second release candidate for XOOPS 2.7.4. RC 2 adds no new features. It
collects the security hardening and bug fixes made since RC 1, after a review
of the core with CodeQL, Snyk, SonarCloud, Scrutinizer and manual audits.

XOOPS 2.7.4 brings two-factor authentication into the core, makes SCEditor a
full visual editor and the default for new sites, and adds Markdown support
through EasyMDE. It runs on PHP 8.2 through 8.5.

Please test RC 2 on a staging copy of your site and report anything you find.
Unless something serious turns up, the next release is 2.7.4 Final.

Download XOOPS 2.7.4 RC 2:
https://github.com/XOOPS/XoopsCore27/releases


What's new since RC 1

Forms and redirects

  • Form security tokens no longer depend on the browser's User-Agent. A
    token is now a random value compared in constant time. A browser update, a
    privacy extension or a "desktop site" toggle between opening and submitting
    a form no longer rejects it. Forms opened before the upgrade still submit.
  • Protector uses the core form token. Its admin pages check the same
    token as the rest of XOOPS. XoopsGTicket is deprecated and now wraps the
    core token, so modules that still call it keep working.
  • One same-site check for redirects. Login, post-login and theme-switch
    return addresses share one check. It refuses targets written with
    backslashes, encoded slashes, HTML entities or embedded line breaks, and
    sends them to the home page instead.
  • Escaped confirmation pages and error lists. xoops_confirm() escapes
    every field, value and label, and the object and login error lists are
    escaped too.

Files and storage

  • Uploads are deleted only inside the upload directory. The image
    manager and the smilies, user-rank and avatar admin pages resolve a stored
    file name before they delete it.
  • Protected database dumps. A dump is written only under XOOPS_VAR_PATH,
    into a directory guarded by a deny-all .htaccess and private to the PHP
    user.
  • Cache ids use a site key. The group part of theme and block cache ids
    is keyed with a random site key in xoops_data/data instead of the database
    credentials.
  • Random installer names. The installer renames itself and names its
    cleanup script with random_bytes(). Only the installing session can finish
    the clean-up.
  • Protector writes its ban files atomically and rejects an uploaded image
    it cannot inspect instead of staging it in uploads/.

Server configuration

  • xoops_lib/.htaccess works on Apache 2.4 without mod_access_compat,
    where the old rules returned a 500 error instead of denying access.
  • PHPMailer's unused OAuth helper is removed from the bundled vendor
    tree, and a Composer script removes it again after every vendor refresh.
  • reCAPTCHA v2 verifies over POST, so the secret key no longer appears in
    proxy or server logs.
  • The bundled XMF library is updated to 1.3.2, which tightens the tag and
    attribute filtering used for request input.

Fixes

  • The optional confirmation step for deleting notifications works again.
  • Deleting a user rank or avatar that no longer exists shows an error instead
    of a fatal error.
  • Uploading an image to a database-stored category reports a failed upload
    instead of stopping with a fatal error.
  • The TinyMCE 5 and 7 image managers no longer double-encode their target
    field.
  • Errors that were silenced with @ (cache, avatar and debug clean-up,
    session start-up, upgrade-script clean-up) are now handled or reported.

What's Changed

  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #226
  • Fixing typos in docs directory by @peter279k in #227
  • Fix typos in htdocs directory by @peter279k in #228
  • security(system): harden file-tree loading message and workflow permissions by @mambax7 in #229
  • security(cookies): route the editor sample through xoops_setcookie and sniff raw calls by @mambax7 in #230
  • security(sceditor): cast the emoticon display flag to int in the smiles INSERT by @mambax7 in #231
  • chore(snyk): exclude third-party packages from Snyk Code by @mambax7 in #235
  • security(redirect): one same-site policy for login, profile and theme redirects by @mambax7 in #232
  • security(confirm): escape confirmation form fields and HTML error lists by @mambax7 in #233
  • security(sql): quote legacy tree, topic and block-rebuild SQL by @mambax7 in #234
  • test(style): add the standard file header to the redirect, confirm and notification tests by @mambax7 in #236
  • test(style): put the file header before declare() in SystemMenusTreeTest by @mambax7 in #239
  • security(redirect): send the post-login redirect through the shared same-site policy by @mambax7 in #237
  • chore(hooks): require the standard file header in new test files by @mambax7 in #238
  • security(protector): reject upload images that cannot be inspected by @mambax7 in #241
  • chore(hooks): require the copyright tags in new PHP files by @mambax7 in #240
  • fix(images): contain image deletes and check database-stored uploads by @mambax7 in #242
  • security(maintenance): refuse to write a database dump into an unguarded directory by @mambax7 in #243
  • fix(protector): write the ban-list and .htaccess files completely and atomically by @mambax7 in #244
  • chore(hardening): replace the error-suppressed calls Scrutinizer flagged by @mambax7 in #245
  • chore(hooks): require both copyright tags in new PHP files by @mambax7 in #246
  • fix(admin): remove smiley, rank and avatar images through the containment helper by @mambax7 in #247
  • fix(admin): stop the user-rank and avatar deletes on a missing record by @mambax7 in #248
  • chore(database): let isResultSet() narrow the result for static analysis by @mambax7 in #249
  • chore(hooks): warn on new language constants read outside a canonical guard by @mambax7 in #250
  • security(captcha): verify reCAPTCHA v2 with a POST, the secret in the body by @mambax7 in #251
  • security(xoops_lib): remove PHPMailer's OAuth helper script and keep it out of vendor by @mambax7 in #252
  • security(xoops_lib): deny web access to the trust path in Apache 2.4 syntax by @mambax7 in #253
  • security(csrf): stop binding the session token to the User-Agent header by @mambax7 in #254
  • security(protector): check admin forms with the core CSRF token; make XoopsGTicket an adapter by @mambax7 in #256
  • security: close the remaining Snyk backlog items (installer suffix, cache-id key, admin feed error, dead preferences branch) by @mambax7 in #257
  • chore(ci): exclude bundled libraries, theme docs and disabled Protector filters from Scrutinizer by @mambax7 in #258

New Contributors

Full Changelog: v2.7.4-RC1...v2.7.4-RC2

XOOPS 2.7.4 RC1

XOOPS 2.7.4 RC1 Pre-release
Pre-release

Choose a tag to compare

@mambax7 mambax7 released this 26 Sep 04:51
06f50ed

XOOPS 2.7.4 RC 1 — two-factor authentication & a new editor experience

This release brings two-factor authentication into the core, makes SCEditor a full visual editor and the default for new sites, adds Markdown support through EasyMDE, and continues the security hardening of the 2.7 line.

The feature set is final. Please test this release candidate on a staging copy of your site and report anything you find before the final release.


Two-factor authentication

Members can protect their account with a second step at login.

  • Two methods. A time-based authenticator app (Google Authenticator,
    Microsoft Authenticator, Aegis, FreeOTP, or any password manager that
    generates TOTP codes), or a six-digit code mailed to the member's address.
  • Recovery codes. Ten one-time codes at enrolment, for the day the phone or
    the mailbox is out of reach.
  • Lockout. Five wrong codes lock the second step for fifteen minutes, and
    the member is notified by e-mail.
  • Self-service. Members enrol, disable and replace their recovery codes from
    Edit Account. Administrators can reset a member's factor from Users, and an
    operator locked out of the site has a documented recovery procedure.
  • Off by default. Switch it to "Optional" in System Preferences and every
    member may enrol; nobody is forced.
  • Protected at rest. Authenticator secrets are encrypted with a site key;
    mailed codes are stored hashed and expire after ten minutes.

Editors

  • SCEditor edits visually with its full toolbar and keeps XOOPS BBCode
    intact across visual and source modes. Its emoticons are registered as XOOPS
    smileys, and new installs use it as the default editor.
  • System > Preferences > Editors configures SCEditor's toolbar buttons,
    plugins, emoticons, resizing, auto-expand, spellcheck, size and the image
    category for dropped images.
  • Markdown through EasyMDE. Markdown is stored in the existing text columns
    and rendered with Parsedown in safe mode; the editor preview uses the same
    renderer.
  • More BBCode. MyTextSanitizer renders the tags SCEditor writes: [sub],
    [sup], [s], [justify], [hr], [ol] and tables.
  • TinyMCE 7.9.3. The bundled TinyMCE 7 is updated to the current 7.x
    release, which carries three content-sanitisation fixes.

Security hardening

  • Remember-me tokens are revoked when the password changes, including a
    lost-password reset.
  • A restored session ends for a deactivated account, and group membership is
    read from the database on every request, so a removed group right takes
    effect immediately.
  • Registration validates the account again at the save step, not only at the
    first step.
  • Comment editing and deletion check that the comment belongs to the module
    handling the request.
  • The TinyMCE image manager checks category permissions for upload, delete and
    listing, as the core image manager does.
  • The upgrade wizard admits webmasters only.
  • The LDAP and Active Directory adapters stop when a requested StartTLS
    connection fails, instead of continuing without it.
  • Editor output is tightened: BBCode attributes and rendered Markdown are
    restored only where they belong, and SCEditor's visual view checks link
    schemes.

Fixes

  • The upgrade wizard reports a patch task that cannot complete, instead of
    re-queuing it silently, and no longer re-queues the 2.5.10-to-2.5.11 patch on
    every run.
  • The Modern admin theme shows its redirect notifications again, in light,
    dark and right-to-left layouts.
  • The Administration Menu link in the user block is shown only to
    administrators.
  • Several legacy classes load again on PHP 8: the tar and zip downloaders, the
    XML-RPC parser, and XoopsTpl::fetchFromData().
  • An unknown user ID in the users admin shows a message instead of an error
    page, and logout works on sites with remember-me turned off.

Changed since Beta 2

The editor work (SCEditor, the Editors preferences, Markdown), the upgrade
wizard fix, the Modern theme notifications, the user-block fix, the PHP 8
legacy-class fixes, and translatable upgrade-wizard messages are new in RC 1.
The System module moves to 2.1.13; the upgrade wizard applies it.

What's Changed

  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #210
  • fix(theme/modern): restore visible jGrowl notifications by @mambax7 in #211
  • chore(deps): bump codecov/codecov-action from 7.0.0 to 7.1.0 by @dependabot[bot] in #215
  • re-added XOOPS Version to System Info by @ggoffy in #213
  • fix isadmin display problem by @ggoffy in #216
  • fix(upgrade): stop the wizard re-queueing the 2.5.11 patch on every run by @mambax7 in #217
  • feat(editor): central editor support with Markdown and SCEditor by @mambax7 in #218
  • chore(deps): bump SonarSource/sonarqube-scan-action from 8.2.1 to 8.2.2 by @dependabot[bot] in #219
  • chore(deps): bump codecov/codecov-action from 7.1.0 to 7.1.1 by @dependabot[bot] in #220
  • chore(deps): bump orhun/git-cliff-action from 4.9.0 to 4.9.1 by @dependabot[bot] in #221
  • chore(language): normalize quoting in English language files by @mambax7 in #222
  • fix(upgrade): translate the 2.7.4 patch messages; open the RC 1 logs by @mambax7 in #223
  • fix(core): load the downloaders and XML-RPC parser on PHP 8 by @mambax7 in #224
  • Chore/274 rc1 release prep by @mambax7 in #225

Full Changelog: v2.7.4-Beta2...v2.7.4-RC1

XOOPS 2.7.4 Beta2

XOOPS 2.7.4 Beta2 Pre-release
Pre-release

Choose a tag to compare

@mambax7 mambax7 released this 13 Sep 10:10
3b16bb3

XOOPS 2.7.4 Beta 2 — two-factor authentication

The XOOPS Development Team announces XOOPS 2.7.4 Beta 2. The headline is
two-factor authentication built into the core: any member can protect their
account with a second step at sign-in, using an authenticator app or a
six-digit code sent by e-mail. XOOPS 2.7.4 runs on PHP 8.2 through 8.5.

Download XOOPS 2.7.4 Beta 2:
https://github.com/XOOPS/XoopsCore27/releases

This is a beta: please test it on a copy of your site and report problems on the issue tracker.


Two-factor authentication

Off by default. Set Two-factor authentication to Optional in System
Preferences and members may enrol; nobody is forced, and nothing changes for a
site that leaves it off.

  • Two methods. A time-based authenticator app (Google Authenticator,
    Microsoft Authenticator, Aegis, FreeOTP, or any password manager that
    generates TOTP codes), or a six-digit code mailed to the member's address.
  • Ten one-time recovery codes at enrolment, for the day the phone or the
    mailbox is out of reach. They are shown once and work once each.
  • Throttled. Five wrong codes lock the second step for fifteen minutes and
    the member is notified by e-mail. A recovery code still works during the lock.
  • Bound sessions. Remember-me cookies are tied to the enrolled factor, so a
    reset invalidates them, and every authenticated request checks the factor.
  • Self-service. Members enrol, replace their recovery codes and disable the
    factor from Edit Account, each action behind their current password.
  • Administrator reset from System → Users, behind the administrator's own
    password, which disables the member's factor, revokes their recovery codes and
    mails them. A file-based escape hatch exists for an operator locked out of the
    site; see docs/2fa-operations.md.
  • Secrets at rest. Authenticator secrets are sealed with a site key kept
    outside the database. Mailed codes are stored as a hash of a MAC taken under
    that key, so a reader of the database cannot recover a live code.

The login paths that cannot present a challenge — the upgrade wizard, XML-RPC
and the SSL popup — refuse an account that must present its factor, rather than
letting it through.

Also in this beta

  • Account deletion now removes the member's tokens and factor row, and no longer
    fails half-way.
  • The login flow is split into reusable helpers, and session rotation is refused
    rather than ignored when it fails.
  • A MySQL integration job runs concurrency and installed-site tests on PHP 8.2
    through 8.5 on every change.

Upgrading from 2.7.3 or Beta 1

Copy the new htdocs/ over the web root and run the upgrade wizard; it
creates the user_2fa table and the new preference, and checks for the PHP
sodium extension that two-factor requires. Complete the wizard's final System
module update so the two-factor templates register. A site running a custom
template set should re-import that set, as for any core template change. No
mainfile.php changes are needed.

System requirements

PHP 8.2 to 8.5, MySQL 5.7+ or MariaDB 10.3+, and the PHP sodium extension for
two-factor authentication.

Full changes: docs/changelog.270.txt. Language changes: docs/lang_diff.txt.

What's Changed

  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #199
  • refactor(login): split password login into authenticate and establish-session helpers by @mambax7 in #201
  • chore(deps): bump orhun/git-cliff-action from 4.8.0 to 4.9.0 by @dependabot[bot] in #200
  • chore(deps): bump postcss-selector-parser from 6.1.2 to 6.1.4 in /htdocs/themes/xtailwind by @dependabot[bot] in #202
  • chore(deps): bump postcss-selector-parser from 6.1.2 to 6.1.4 in /htdocs/themes/xtailwind2 by @dependabot[bot] in #203
  • feat(token): extend the token handler for recovery codes and delete tokens with the account by @mambax7 in #204
  • security(2fa): add the two-factor storage layer by @mambax7 in #205
  • security(2fa): challenge a login that carries a second factor and bind sessions and cookies to it by @mambax7 in #206
  • feat(2fa): complete management, preflight and MySQL coverage by @mambax7 in #207
  • feat(2fa): e-mail codes as a second method, themed pages, clearer setup by @mambax7 in #208
  • chore(release): prepare 2.7.4 Beta 2 by @mambax7 in #209

Full Changelog: v2.7.4-Beta1...v2.7.4-Beta2

XOOPS 2.7.4 Beta1

XOOPS 2.7.4 Beta1 Pre-release
Pre-release

Choose a tag to compare

@mambax7 mambax7 released this 10 Sep 04:33
8b4b206

XOOPS 2.7.4 Beta 1 — session and comment hardening

The XOOPS Development Team announces XOOPS 2.7.4 Beta 1, a security-focused
update to the 2.7 line. It closes seven authorisation and session gaps found in
a review of the 2.7.3 core, updates the bundled TinyMCE 7 to a release with
content-sanitisation fixes, and repairs an upgrade-wizard fault that could stall
a site on an old patch. XOOPS 2.7.4 runs on PHP 8.2 through 8.5.

Download XOOPS 2.7.4 Beta 1:
https://github.com/XOOPS/XoopsCore27/releases

This is a beta: please test it on a copy of your site and report problems on the issue tracker.


Security

  • Remember-me tokens are revoked when the password changes. The token now
    carries a keyed fingerprint of the stored password hash. A password change
    through any path, a lost-password reset included, invalidates every earlier
    token. Sessions restored from the session store are unaffected. (#194)
  • Deactivated accounts lose their sessions. A restored session ends when the
    account is inactive, whether it came from the session store or the remember-me
    cookie, and group membership is resolved from the database on every request,
    so a demotion applies on the next request. (#188)
  • Registration is validated at the save step. The step number is supplied by
    the client; the save step now requires that step 1 passed in this session and
    re-validates the identity values it is about to insert. (#187)
  • Comments belong to their module. Editing, saving and deleting a comment now
    require it to belong to the module whose endpoint received the request, so an
    administrator of one module cannot act on another module's comments. (#189, #196)
  • The TinyMCE image manager checks category permissions. Upload requires write
    access to the selected category, delete requires write access to the image's
    own category, and listing requires read access, as the core image manager
    already required. (#186)
  • The upgrade wizard is gated on webmaster membership at every entry point;
    two of them had accepted a module-level admin right that can be delegated. (#189)
  • LDAP and Active Directory fail closed on a failed StartTLS instead of
    continuing to bind over the plain connection. (#189)

Fixes

  • The upgrade wizard reports a stalled patch task instead of re-queuing it
    silently on every click, and shows no server paths while doing so. Sites stuck
    on the 2.5.11 patch with an undeletable index.html now see which files are
    affected. (#184)
  • The users admin no longer fails with an undefined constant on an unknown user
    id. (#190)
  • Logging out, or restoring a deactivated account, no longer fails on sites where
    remember-me is disabled. (#188, #195, #198)
  • A registration flow that finished and then received a further request no longer
    fails in the step merge. (#187)

Editors

  • TinyMCE 7 is updated from 7.9.2 to 7.9.3, which carries three content
    sanitisation fixes, one of them in the media plugin that the XOOPS settings
    enable. The bundled TinyMCE 5 stays at 5.10.9: its corresponding fix is not
    publicly distributed, so treat TinyMCE 5 as unpatched and prefer TinyMCE 7. (#193)

Language

  • The ten front-end labels of the default system menu move from the admin
    language file to language/<lang>/menus/menus.php, the file the resolver
    tries first. Names and values are unchanged, so existing translations and
    seeded menu rows keep working. (#185)
  • One constant is added; see docs/lang_diff.txt. (#190)

Upgrading

  • No database changes. The upgrade wizard has nothing to apply for 2.7.3 to
    2.7.4; replace the files and clear the cache as usual.
  • Remembered logins issued before this release are rejected once: each
    remembered device signs in again one time and receives a token with the new
    claim.
  • Translation packs need the moved menu labels only if they override them; the
    English values apply otherwise.

Thanks

Thank you to everyone who tests the beta and reports back. The complete list of
changes is in docs/changelog.270.txt, and the commit-level changelog is
generated into CHANGELOG.md on release.

What's Changed

  • fix(upgrade): report stalled patch tasks instead of re-queuing silently by @mambax7 in #184
  • refactor(system): move front-end MENUS_* labels out of the admin lang… by @mambax7 in #185
  • security(imagemanager): check category permissions in the editor plugin and pass insert codes as data by @mambax7 in #186
  • security(profile): validate a new account at the save step, not only at step 1 by @mambax7 in #187
  • security(session): end restored sessions for inactive accounts and refresh groups per request by @mambax7 in #188
  • security: tighten the upgrade gate, directory TLS and the comment edit form by @mambax7 in #189
  • fix(system): define _AM_SYSTEM_USERS_NO_SUCH_USER for the users admin page by @mambax7 in #190
  • chore(tinymce): update TinyMCE 7 from 7.9.2 to 7.9.3 by @mambax7 in #193
  • security(session): revoke remember-me tokens when the stored password hash changes by @mambax7 in #194
  • fix(user): clear the remember-me cookie on logout only when a cookie name is configured by @mambax7 in #195
  • security(comment): require a posted or deleted comment to belong to the requesting module by @mambax7 in #196
  • docs(changelog): add the 2.7.4 Beta 1 release notes by @mambax7 in #197
  • fix(profile): guard the logout cookie name in the profile module's own logout too by @mambax7 in #198

Full Changelog: v2.7.3b...v2.7.4-Beta1

XOOPS 2.7.3

Choose a tag to compare

@mambax7 mambax7 released this 24 Aug 12:59
6ad0a0c

PHP 8.6 Compatibility:

  • replace the deprecated is_long() alias with is_int() in FunctionsUserTest, the lone repository-wide occurrence; PHP 8.6 deprecates the is_long/is_integer/is_double/doubleval type-alias functions and first-party htdocs/ code has none (mamba)
  • use bare returns in the four early-exit constructors (class/file/file.php, class/uploader.php, class/xoopsform/formdhtmltextarea.php, class/xoopsform/formselectuser.php): PHP 8.6 deprecates returning a value from __construct() at compile time; new never delivered these values, so the change is behavior-preserving. Verified by token scan - 7 constructor value-returns before, 0 after - and pinned by a direct-invocation test that observes the yielded value (mamba)
  • complete the session save-handler contract ahead of PHP 8.6: add create_sid() (with SessionIdInterface) so the 8.6 deprecation for object handlers lacking it never fires - PHP 9.0 makes the method mandatory; teach updateTimestamp() to insert the row a brand-new empty session is missing, because 8.6 routes such a session there instead of write(), and a bare UPDATE would never create it, leaving strict mode to reject the ID and regenerate it on every request - gated on read() having found no row for the ID, so a session destroyed by a parallel logout keeps its timestamp-only UPDATE and cannot be resurrected with stale data; pin session.use_strict_mode to 1, the 8.6 default, on 8.2-8.5 as well, reporting via E_USER_WARNING when the pin is impossible because output preceded session bootstrap (mamba) in #169
  • drop the imagedestroy() calls, deprecated in PHP 8.5 and no-ops since 8.0 (a GdImage frees itself when its last reference goes away): image.php, the image CAPTCHA renderer (whose required-GD-function check no longer lists it, and whose branch-on-destroy-failure unwinds to a plain unset), and Protector's module_icon.php; the remaining occurrences are inside the vendored TCPDF, which is upstream's to change (mamba) in #179

Kernel:

  • deprecate the XOBJ_DTYPE_UNICODE_* object datatypes (16-21), which url-encode on write and url-decode on read — a pre-UTF-8 workaround that bloats storage and breaks LIKE/FULLTEXT search on modern utf8mb4 installs. Notice only, behavior unchanged: initVar() reports a deprecation when one is used (guarded so it is safe during early bootstrap, before the logger exists) and the constant block carries an @deprecated doc naming the non-unicode successors; data migration is planned for 2.8 and constant removal for 4.0 (mamba)

Security:

  • harden the tplsets template browser, editor, restore, and save endpoints: drop the second urldecode() (PHP already decoded the request once; re-decoding re-materialized %00 and %2f as live bytes) and reject interior NUL bytes explicitly at ingestion at all four sites - getString()'s trim() silently drops edge NULs (so such a value arrives as a valid NUL-free path and faces the same containment checks as any other input) while an interior one passes intact, verified by execution; the accessors themselves stay as they were, because Xmf's PATH filter truncates at the first byte outside its ASCII set, which would break accented or CJK theme paths and turn a Windows restore path into a bare drive letter - with realpath() inside try and ValueError caught as a backstop at all four sites (browser, editor, restore, and the save in main.php), false realpath() results refused, root-plus-separator containment so a sibling like themes2 cannot satisfy a bare prefix check, is_file() required in the editor, save, and restore paths so a directory (even the themes root via path_file=/) never reaches the file handlers, the folder listing switched to the canonical path it just validated, reads pinned to POST to match the JS callers, the template-extension allowlist enforced at the editor as well as the save, the legacy escape() dropped from the tree JS (jQuery already encodes once, so spaced and non-ASCII folder names finally reach the server intact - the removed second decode had been load-bearing for that double-encode), the editor/restore AJAX bodies switched to object form so paths containing & or + survive, restore switched to the validated relative path (ending the server-path leak into admin HTML and the Windows absolute-path special case), a failed backup copy() now aborts the save, the file-listing onclick arguments JS-encoded with json_encode() before HTML-escaping (htmlentities() alone left an apostrophe filename free to break the JS literal), the editor form kept to its single CSRF token with the restore validating it via check(false) so the save can still spend it, the hidden path_file field re-derived from the validated path, the dead file/ext fields dropped, the backup delegated to the shared xoops_write_file_atomically() helper, whose atomic rename() replaces a planted symlink at .back instead of following it (copy() follows an existing link and PHP's emulated fopen('x') follows a dangling one, both verified by execution; an attacker who could exploit the helper's residual reopen-by-name window already has write access inside themes/ and could replace the templates directly), a symlinked .back refused by the restore and its delete-then-rename replaced by a single atomic rename() so a failed restore can no longer leave neither file, the listing/editor output aligned on htmlspecialchars(ENT_QUOTES | ENT_SUBSTITUTE, UTF-8) with json_encode(JSON_INVALID_UTF8_SUBSTITUTE) for the JS arguments - without the SUBSTITUTE flags a non-UTF-8 filename produced a JS parse error or an empty editor textarea that a save would write over the real file, both verified by execution - and tpls_edit_file() slimmed to the two parameters it actually uses (mamba) in #176
  • extract the tplsets path-containment contract into the shared PathGuard class (resolveDir/resolveFile: NUL refusal with a ValueError backstop, false-realpath refusal, boundary-aware root containment so a sibling like themes2 never satisfies a prefix check, is_dir/is_file by mode, case-insensitive extension allowlist, canonical result), refactor all four endpoints onto the one implementation, and pin the contract with a truth-table PHPUnit suite that runs against a real fixture tree - traversal, NUL masks, a directory named like a stylesheet, symlink escape refused and an internal symlink canonicalized - and harden the four tpls_generate_surcharge write loops through one checked writer: fopen() verified (an unchecked false handle is a PHP 8 TypeError at fwrite()) and fwrite() compared against false so an empty template source still counts as written (mamba) in #178
  • close image.php's remote-image branch. With ONLY_LOCAL_IMAGES flipped to false the raw request URL reached getimagesize() and file_get_contents(), honoring http://, phar:// and data:// — an SSRF and phar-deserialization surface — and the branch had never worked for anyone anyway: it truncated every rooted URL to a single character (substr($imageUrl, 0, 1) where substr($imageUrl, 1) was meant), so no real-world behavior is lost. The constant stays and the branch now refuses the request, so a fork that flips it fails closed instead of fatal (mamba) in #179
  • require a valid session token to log out. profile's user.php tore the session down on a bare GET, so any third-party page could end a visitor's session at will (forced-logout CSRF). A tokenless request now renders a POST confirmation carrying the token instead of acting immediately, which keeps every existing user.php?op=logout link working — including the ones baked into cached theme and block templates — at the cost of one extra click (mamba) in #179
  • stop reflecting the raw QUERY_STRING into redirect Location headers at all eight sites (three pm preload events, four profile preload events, and profile's register.php activation redirect). PHP already blocks CRLF in headers, so this was never header splitting, but an attacker-shaped query string reflected verbatim invites cache-poisoning and phishing parameter injection; the string is now parsed with parse_str() — which mirrors how the redirect target itself reads the parameters — and re-emitted with http_build_query(), so every reflected byte is RFC 3986-safe or a valid escape by construction, hostile input becomes inert encoding instead of costing the visitor their query, and a long urlencoded xoops_redirect survives (the 2000-byte cap is header-size sanity only); the rebuild lives in include/file_safety.php as xoops_rebuildQueryString() — one implementation shared by all three call sites — and is pinned by a unit test (mamba) in #179

Search:

  • render the search "Show all" / "Show all by user" results again: system_search.tpl tested a guard no request could satisfy ($nomatch is left unassigned when a module returns rows and set true when it does not, but the template tested isset() && != true), so neither the result list nor the no-match message had rendered since the guard was rewritten. The block now opens on empty($nomatch), the no-match message becomes a proper else branch, the optional values that become reachable again (showall, uname, time, and the pagination links) are guarded, and the xswatch5 override's guards are aligned the same way (mamba); reported by CHCCD in #161
  • validate the show-all search request before rendering: search.php built a theme and fired the header events before checking that the requested module exists, is active, is searchable, and is readable by the visitor, and its permission id checks now compare strictly. The row normaliser owns the row's shape — an integer uid (default 0) and string link and title — so a module search plugin returning loose types can no longer put a non-numeric uid into getUnameFromId() or the userinfo link; the show-all loop had been writing its uid cast to a stray key of the outer array while the row's own uid passed through untouched (mamba); reported by CHCCD in #162

Caching:

  • send a well-formed Cache-Control header from bro...
Read more

XOOPS 2.7.3 RC1

XOOPS 2.7.3 RC1 Pre-release
Pre-release

Choose a tag to compare

@mambax7 mambax7 released this 11 Aug 05:23
5a7ae41

Editors:

  • add SCEditor as an optional BBCode editor, selectable from the editor preference dropdown alongside the existing editors. The 3.2.1 distribution ships bundled under minified/ (MIT, licence text included), so no separate download is needed and an upgrade is a wholesale replacement of that directory (mamba) in #152
  • lock SCEditor in source mode deliberately: startInSourceMode is set and both sourceMode(false) and toggleSourceMode() are guarded, so existing content never passes through a WYSIWYG round-trip that could rewrite or drop XOOPS-specific BBCode such as [siteurl], [d], named [size=] values or arbitrary smilie codes. Toolbar buttons insert at the caret and never re-serialise the rest of the document (mamba) in #152
  • render one shared dhtml toolbar for every renderer. The same editor showed a different toolbar in the control panel than on the front end, and different again between front-end themes: renderFormDhtmlTAXoopsCode() and renderFormDhtmlTATypography() were independently hand-written HTML in five renderers, and since no admin theme selects a renderer the control panel fell back to the Legacy one, whose Bootstrap class names no admin theme defines. XoopsDhtmlToolbar now produces the toolbar once and all five renderers delegate to it, with framework-neutral xo-edtb-* classes. The two protected helpers are kept as thin delegates for any third-party subclass that calls or overrides them (mamba) in #151
  • repair the dhtml toolbar's no-selection actions (mamba) in #151

Compatibility:

  • repair [code] and [quote] rendering on PHP 8.3+. highlight_string() changed in 8.3, returning "<pre><code style=...>" with real newlines where earlier versions returned "<code><span style=...>" with <br /> and &nbsp;. The extension located its opening marker with strpos($buffer, '<?php ') and added a hard-coded 14; on 8.3+ that strpos() returns false, false + 14 evaluates to 14, and the first fourteen characters of real output were cut, leaving a block beginning with the literal text le="color: #000000">. The marker is now found with a pattern accepting either encoding and its length taken from the match (mamba) in #150
  • keep code-block whitespace intact and scope the trailing-break trim to XOOPS' own boxes (mamba) in #150
  • drop deprecated curl_close() calls for PHP 8.5 (mamba) in #153
  • drop ReflectionProperty::setAccessible() from the test bootstrap; a no-op since 8.1 and deprecated in 8.5, and emitted during bootstrap it contaminated the output of every test asserting on a clean stream (mamba) in #157

Debugging and logging:

  • offer the error screen to one declared owner instead of whichever module registered last. Ownership resolves in three steps, first answer wins: an explicit token in xoops_data/data/debug.php, else the token a provider recorded at install, else 'core'. Four constants publish the result on every request - XOOPS_ERROR_SCREEN_OWNER, _SOURCE, _STATUS and _MESSAGE - so a diagnostics page can answer "who owns the error screen here?" (mamba) in #157
  • hand the handlers back when a provider registers and then fails to activate, keyed on the reported outcome rather than on the catch, since both reference providers wrap their own activation and report 'error' without throwing at core (mamba) in #157
  • detect and report a contested error screen: a second module reporting, a listener registering after the accepted report, and a silent registration nobody reported. All three compare both the error and the exception handler, because PHP hands them out independently (mamba) in #157
  • make error-screen ownership a compare-and-set under the lock; read-then-write let two concurrent installs both believe they had claimed the seat (mamba) in #157
  • add an opt-in error_screen_strict setting, for a site that wants the developer gate enforced by core rather than left advisory to the provider (mamba) in #157

Security:

  • escape element values in all five form renderers, which wrote them straight into quoted attributes and textarea bodies. Values now route through a shared XoopsFormRendererValueEscapeTrait, and toolbar and TextSanitizer extension handlers build their JavaScript arguments with json_encode rather than htmlspecialchars, which is the correct encoder for a JS string literal inside an HTML attribute (mamba) in #151
  • escape module-manifest values (name, dirname, adminindex, version, image) at the point of output on the install, uninstall, update and activate log pages; getInfo() returns these raw whatever format is requested, and several were interpolated into href and src attributes unescaped (mamba) in #155
  • build the testdata link's filesystem probe from the directory actually being installed - basename() plus a strict character allowlist - so a manifest value cannot point the file_exists() check outside the module's own directory (mamba) in #155
  • enforce authorization on the image category create, update and delete handlers, which validated the CSRF token but not the caller's permission; the admin check governed only which controls were rendered (mamba) in #151
  • remove three stale copies of core renderers under the TinyMCE image-manager plugins, which were installed as the global renderer so those screens never received core renderer changes; the endpoints now xoops_load() the core class (mamba) in #151
  • guard getByDirname() on the module uninstall and update confirm screens (mamba) in #156

Database:

  • render an empty IN list as a constant predicate. Criteria::render() emitted the literal IN (), which MySQL rejects as a syntax error; an empty set is now 1=0 for IN and 1=1 for NOT IN. Returning an empty fragment would be wrong, since CriteriaCompo drops empty fragments and the condition would silently match every row. This also fixes search.php, which built mid IN () for any user whose module-read permission list was empty (mamba) in #154
  • preserve the caller's PHP type in an IN array: an int renders as an SQL integer, anything else as a quoted string literal. Previously a numeric-looking string was cast, so a text-column search for '001' rendered IN (1), which MySQL evaluates numerically and matches against '1', '01' and ' 1'; a list of '001' and '1' collapsed to IN (1,1). Integer columns are unaffected (mamba) in #154

Filesystem:

  • treat drive-letter and UNC paths as absolute in XoopsFolderHandler::isAbsolute(), which accepted C:/ but not C:\ while isWindowsPath() twenty lines above matched the opposite spelling. PHP's dirname() and realpath() return the backslash form on Windows, so cd() treated absolute paths as relative, built a path that does not exist and left pwd() null - which is why the file cache engine had never initialised on Windows. UNC paths were never matched at all (mamba) in #157

Tests:

  • cover the error-screen seam in 28 cases, each in its own process, since the seam publishes its outcome as constants and constants are defined once per process. The fixture spec crosses that boundary as base64, because raw JSON through escapeshellarg() is silently mangled on Windows (mamba) in #157
  • stop two tests leaking state into the rest of the suite: MyTextSanitizerTest popped two handler frames believing displayTarea() installed them, when XoopsLogger::getInstance() installs them and only on its first call in the process; and LostPassSecurityTest never cleared its rate-limit cache, so with an idLimit of 3 the suite was reproducible exactly twice in one working copy and failed on the third run (mamba) in #157

What's Changed

  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #149
  • fix(criteria): render empty IN lists as a constant and convert core callers by @mambax7 in #154
  • fix(textsanitizer): repair [code] and [quote] rendering on PHP 8.3+ by @mambax7 in #150
  • fix(php85): drop deprecated curl_close() calls by @mambax7 in #153
  • Feat/shared dhtml toolbar by @mambax7 in #151
  • feat(editor): add SCEditor as an optional BBCode editor by @mambax7 in #152
  • security(system): harden module admin log output and testdata path by @mambax7 in #155
  • fix(system): guard getByDirname() on the uninstall and update confirm screens by @mambax7 in #156
  • File-based debug configuration, and the error-screen provider seam by @mambax7 in #157
  • 2.7.3 RC1 by @mambax7 in #158
  • Fix/debug gate on upgraded sites by @mambax7 in #159

Full Changelog: v2.7.3-Beta1...v2.7.3-RC1

XOOPS 2.7.3 Beta1

XOOPS 2.7.3 Beta1 Pre-release
Pre-release

Choose a tag to compare

@mambax7 mambax7 released this 28 Jul 11:21
180d208

What's Changed

  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #129
  • chore(deps): patch nanoid/postcss advisory and track npm in Dependabot by @mambax7 in #131
  • compat: PHP 8.5 hardening and who-is-online tracking for 2.7.3-Beta1 by @mambax7 in #130
  • chore(deps-dev): bump @tailwindcss/typography from 0.5.19 to 0.5.20 in /htdocs/themes/xtailwind2 in the npm-build group by @dependabot[bot] in #132
  • chore(deps-dev): bump @tailwindcss/typography from 0.5.19 to 0.5.20 in /htdocs/themes/xtailwind in the npm-build group by @dependabot[bot] in #133
  • chore(ci): stop proposing Tailwind and DaisyUI major bumps by @mambax7 in #138
  • security(logger): escape untrusted values in the debug panel by @mambax7 in #140
  • feat(debug): central debug config and a rotating file logger by @mambax7 in #139
  • docs(changelog): stop the generator emitting merge and dependency noise by @mambax7 in #141
  • docs(changelog): add curated 2.7.3 Beta 1 release notes by @mambax7 in #142
  • fix(database): return the documented failure value for a non-result argument by @mambax7 in #143
  • feat(logger): make debug.log readable at a glance by @mambax7 in #144
  • fix(core): stop the login redirect accumulating escaped ampersands by @mambax7 in #145
  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #146
  • docs(changelog): merge the split Database section and record the redirect fix by @mambax7 in #147
  • fix(profile): assign redirect_page so the default theme's login form is clean by @mambax7 in #148

Full Changelog: v2.7.2...v2.7.3-Beta1

XOOPS 2.7.2

Choose a tag to compare

@mambax7 mambax7 released this 24 Jul 09:48
b8d447f

What's Changed

  • docs(changelog): regenerate CHANGELOG.md by @github-actions[bot] in #125
  • chore(deps): bump actions/checkout from 7.0.0 to 7.0.1 by @dependabot[bot] in #127
  • fix(installer): repair fresh install and re-install on PHP 8.1+ (2.7.2) by @mambax7 in #128

Full Changelog: v2.7.1...v2.7.2