This is no longer the latest release of ClassicPress!
You can find the latest release at the top of the Release Notes subforum.
We’re happy to announce the first release candidate for ClassicPress
1.1.0. This release contains two new features that we think the community will be happy with, as well as several months’ worth of smaller bugfixes. We’re happy with these changes but they need more testing by the community before a full release including automatic updates.
We encourage you to try out this release candidate by pasting the zipfile URL into the “Advanced” section of the migration plugin, and let us know if you see any issues. See instructions and links below, under the “Download this release → Existing ClassicPress sites” section.
New features since
Add an option to show the site’s custom logo on the login page instead of the ClassicPress logo. This is disabled by default, but it is a common way for sites to customize their own public-facing branding, and now changing this image doesn’t require any plugins. (details)
Add a new top-level Security page to the admin screen. This is a centralized place for plugins to register their security-related settings, to make them easier to find and audit. (details, documentation)
Minor changes and fixes since
- Update the list of files to remove during installation. This ensures that no extra files are left over after migration from WordPress. (details)
- Update the jQuery version string after the security patch applied in ClassicPress
- Add ClassicPress changelog links to the dashboard’s About page. (details)
- Fix potentially overlapping notices in the Themes section of the dashboard. (details)
- Fix potential upload failures of common text file types. (details)
- Fix an issue with published post dates when using the XML-RPC API, for example with external editors. (details)
- Fix a PHP notice in the dashboard petitions widget. (details)
- Fix a “Source map” browser warning related to a TinyMCE file. (details)
- Remove unnecessary
role="navigation"attribute from pagination elements. This is an improvement to HTML5 validation. (details)
- Remove angle brackets from link in password reset email. This caused problems with some email clients. (details)
- Update links to support/documentation pages in
- Include latest emoji code from WP. It will be possible to disable this feature in ClassicPress v2, but for now we’ve needed to keep it up to date to keep our builds passing. (details)
Development improvements and fixes since
- Provide a set of contribution guidelines for the core project. (details)
- Update/improve the ClassicPress project’s readme on GitHub. (details)
- Keep build dependencies up to date. (details)
- Modernize the build scripts and the
- Add initial automated tests for
- Miscellaneous other improvements to the build and automated tests. (details 1, details 2, details 3)
Download this release
and follow the installation instructions.
|Existing WordPress sites||Download the migration plugin and follow the migration instructions.|
|Existing ClassicPress sites||Use the “Advanced” section of the migration plugin to switch to the release build (same link as for “New sites” above). This version will be available using the built-in update mechanism when it is released as
The full changelog is available on GitHub.