Loading...
 
Skip to main content
3
Page actions
Get a short URL Open in WebDAV

Tiki31

Tiki 31.0 is planned for October 2026

It is a Standard Term Support (STS) version and will be supported until Tiki 32.1 is released as per the Tiki lifecycle policy

No Tabs

Under Development https://gitlab.com/tikiwiki/tiki/-/tree/master

Tiki 31.0

1.1. Upgrade Notes

1.1.1. POP3 support removed from MailIn accounts


Tiki 31 no longer supports POP3 for MailIn accounts. Only IMAP is supported.

Before upgrading, administrators must review all existing MailIn accounts. Any account configured to use POP3 must be migrated to IMAP before upgrading to Tiki 31.

See the Webmail documentation for more information.

1.1.2. Removed: SecDB file-integrity checks


The SecDB file-integrity checking feature has been disabled because its current implementation caused significant maintenance overhead and was not sufficiently reliable.

The following actions have been removed from Settings → Security (`tiki-admin_security.php`):

    • Fast Scan, which searched for new or unrecognized files.
    • Deep Scan, which verified file hashes.
    • Rebuild Security Database, which recreated the file baseline.


Related SecDB checks and generation steps have also been removed or disabled in the CI and release scripts.

After upgrading, administrators can no longer run these file-integrity scans from the Tiki administration interface. No manual upgrade action is required.


The related CI checks and Tiki scripts have also been removed or disabled. Administrators no longer need to generate or maintain SecDB files.

1.1.3. Tracker attachments migration required


Tiki 31 removes the legacy tracker Attachments feature and the deprecated Attachment tracker field type.

Before upgrading, administrators must migrate any existing tracker attachments and remove any deprecated Attachment fields. The Tiki 31 database update will stop and refuse to continue if old tracker attachment data or deprecated Attachment fields are still present. This prevents existing data from being silently lost.

1.1.3.1. Migrate tracker attachments


If tracker items still have attachments, migrate them to a Files tracker field:

Create a Files field in the tracker if one does not already exist.
Run the following command:

Copy to clipboard
php console.php tracker <trackerId> <fieldId> [galleryId]


Where:

  • is the ID of the tracker.
  • is the ID of the Files field.
  • galleryId is optional. If omitted, the command uses the file gallery configured on the Files field, or the root gallery if no gallery is configured.


Orphan attachments, whose tracker item no longer exists, are removed automatically.

1.1.3.2. Remove deprecated Attachment fields


If any tracker still contains a deprecated Attachment field (field type A), remove it before upgrading:

Tracker > Fields > select the field > Remove

Once all tracker attachments have been migrated and all deprecated Attachment fields have been removed, run the database update again.

Important: Do not proceed with the Tiki 31 upgrade until these migration steps have been completed.

1.2. Known Issues


Include only important known issues affecting Tiki 31.0.

1.3. Major Changes


Use this section for significant architectural, behavioural, or system-wide changes.

1.4. Removals

  • [+] Removed POP3 support from mail accounts
  • [+] Removed: tracker "Attachments" tab and deprecated "Attachment" field type

1.5. New Features and Improvements

1.5.1. New

  • [+] Altcha CAPTCHA Support

1.5.2. User Interface and Navigation

1.5.2.1. Accessibility

1.5.2.2. Responsive Design

1.5.2.3. Navigation and Menus

1.5.2.4. Themes and Layout

1.5.2.5. Administration UX

1.5.3. Calendars & Events

1.5.4. Communications & Messaging

1.5.5. Editors

1.5.6. External Services Integrations

1.5.7. File Galleries & Attachments

1.5.8. Maps, Geolocation & Internationalisation

1.5.9. Plugins

1.5.10. Search

1.5.11. Security & Access Control

1.5.12. Trackers

1.5.13. Developer Tools & APIs

1.5.14. Miscellaneous

1.6. Infrastructure and Dependencies

1.6.1. Dependency Updates


Include noteworthy dependency changes with compatibility, security, or administrator impact.

1.6.2. Build System & Configuration

1.6.3. Developer Tools

1.7. Removals and Deprecations


Include removed or deprecated features, libraries, preferences, APIs, or functionality.

If a removal requires action before upgrading, put the complete instructions in Upgrade Notes and keep only a concise reference here.

1.8. Large-Scale Changes


Large-scale changes affect many files or multiple parts of Tiki. They may include major refactoring, architectural changes, broad feature improvements, or system-wide cleanup.

These changes are listed separately because their broad scope may increase the possibility of regressions.

1.9. References

Not yet started




Comments 1
Slideshow