Strapi Release: 3.0.0-beta.20.3

TL;DR

Strapi v3.0.0-beta.20.3 brings several enhancements and bug fixes to improve the overall functionality and user experience. Key improvements include better search logic, optional password fields when editing users, fixes for upload plugin issues, and enhanced documentation. This release also transitions community support from Stack Overflow and Spectrum to GitHub Discussions.

Highlight of the Release

• Password field is now optional when editing users
• Improved search logic in the database
• Community support moved to GitHub Discussions
• Fixed upload plugin issues with thumbnails and breakpoints
• Proper plugin uninstallation with folder deletion

Migration Guide

No significant migration steps are required for this beta release. However, users should be aware of the following changes:

1. Community Support: If you were previously using Stack Overflow or Spectrum for Strapi support, you should now use GitHub Discussions.

2. App Engine Deployments: If you're deploying to Google App Engine, update your HOST variable to '0.0.0.0' instead of using a domain-specific value to avoid connectivity issues.

3. Heroku Deployments: If you're experiencing SSL certificate issues with Heroku, refer to the updated documentation for fixes.

Upgrade Recommendations

This beta release contains several important bug fixes and enhancements that improve the overall stability and functionality of Strapi. It's recommended to upgrade if you're experiencing any of the specific issues addressed in this release, particularly:

• Issues with password fields when editing users
• Problems with the upload plugin and file relationships
• Search functionality limitations
• Plugin uninstallation problems

As this is a beta release, it's advisable to test thoroughly in a non-production environment before upgrading your production instances.

Bug Fixes

Database and Framework Fixes

• Fixed an issue where pool settings weren't preserved when using a schema
• Fixed search logic to properly handle MongoDB IDs and prevent fall-through in model search when a plugin is specified
• Fixed Date test failures due to timezone differences
• Removed password field from retrieved data for better security

Upload Plugin Fixes

• Added proper path folder for thumbnail and breakpoints images (fixes issue #5934)
• Implemented pruning of obsolete files relations on startup to prevent broken references when deleting content types

Plugin Management

• Fixed plugin uninstallation by adding functionality to properly delete folders with files (fixes issue #5302)

New Features

Community Support on GitHub Discussions

Strapi has moved community support from Stack Overflow and Spectrum to GitHub Discussions. This centralizes the community interaction in one place, making it easier for users to find help and share knowledge.

Optional Password Field When Editing

The password field is now optional when editing users, improving the user experience by not requiring password re-entry for simple profile updates.

Security Updates

Password Field Security

The password field is now removed from retrieved data in the content manager, enhancing security by preventing accidental exposure of password hashes in API responses or admin panel views.

Performance Improvements

Search Performance

The search logic has been improved to handle MongoDB IDs more efficiently and prevent fall-through in model search methods when a plugin is specified. This results in more accurate and faster search operations.

Database Connection Handling

Pool settings are now properly preserved when using a schema, ensuring that all connection parameters (including createTimeoutMillis and other settings) are maintained throughout the application lifecycle.

Impact Summary

This release focuses on quality-of-life improvements and bug fixes rather than introducing major new features. The changes to search logic and database handling will improve reliability for all users, while the fix for password fields during user editing enhances the admin experience.

The upload plugin fixes address important issues with file relationships and thumbnail paths that could cause problems in production environments. The move to GitHub Discussions centralizes community support in one location, making it easier for users to get help.

For developers, the ability to properly uninstall plugins with folder deletion and the preservation of pool settings when using schemas will lead to a more robust development experience.

Overall, this beta release continues to stabilize the platform as it moves toward a stable 3.0 release.

Full Release Notes