ClassicPress

Switch to ClassicPress

ClassicPress

Switch your WordPress installation to ClassicPress. Also a tool to try different versions of ClassicPress (also nightly builds or RC).

Download

More Info
This is a plugin for WordPress that switches your installation to ClassicPress.

Version 1.5 of this plugin also added a switcher tool for ClassicPress that can be used to install other versions, test nightly builds and even revert your site to WordPress.

The CMS for Creators

ClassicPress takes your website to the next level with the same features and functionality that you enjoyed with WordPress, but with more attention to the most common needs of a business website.

PLEASE NOTE: ClassicPress is stable software, but it is important to take a backup before switching a live production site to ClassicPress.

What version of WordPress does the plugin work with?

You can always see the latest supported version by going to Get ClassicPress.

Installation

To install a fresh version of ClassicPress on a new site, you do not need this plugin. See our installation instructions instead.

To install ClassicPress on a current WordPress site (switch a current WordPress site to ClassicPress):
1. Back up the current site files and database. You can do a manual backup in your hosting panel and export the database, or you can use a backup plugin.
2. Download the latest version of the ClassicPress migration plugin from the ClassicPress Plugin Directory.
3. Install the downloaded zip file from within the WordPress dashboard (“Plugins” -> “Add New” -> “Upload Plugin”).
4. Activate this plugin (“Switch to ClassicPress”) after it is installed.
5. Go to the settings of the ClassicPress migration plugin at “Tools” -> “Switch to ClassicPress”.
6. To proceed with the switch it is necessary that all pre-flight checks succeed, with a green or yellow check mark. A yellow check mark requires your attention, so read this information carefully.
7. Press the Switch this site to ClassicPress now! button.
8. The migration process may take a few minutes depending on your hosting provider, so go grab some water or a beverage of your choice 🙂.
9. When the process is finished, you should see the ClassicPress About screen.
10. To complete the migration process you must visit the Updates page and press the Re-Install Now button.
11. You may be prompted to upgrade ClassicPress immediately after switching from WordPress. This is normal, and it is safe to upgrade.
At this point it is safe to delete the “Switch to ClassicPress” plugin.

If something is wrong, please let us know in our support forum.

Frequently Asked Questions

Will my current plugins and themes work in ClassicPress?

Plugins that require Blocks might not work well in ClassicPress, you should test any plugins you plan to use and verify they work correctly.

If you see something unusual it may be a bug with ClassicPress, and you can get help in our support forum or GitHub.

How can I use this plugin with an unsupported version of WordPress?

This plugin currently supports migrating from WordPress versions starting at 4.9.0.

We update the plugin as quickly as possible when a new version of WordPress comes out, but we do need to test each new version for compatibility with the plugin first.

If you would like to migrate from a different version of WordPress at your own risk, you can use the following code in your current theme’s functions.php file or a mu-plugin to enable the migration:

add_filter( 'classicpress_ignore_wp_version', '__return_true' );

With each new WordPress release, it’s very helpful for us to have multiple reports of whether the migration plugin works with the new version.

You can use the filter above to test the migration process, and you can tell us about the results of your testing on GitHub or our support forum.

I need help with something else, what should I do?

Like all of ClassicPress, our support is a volunteer effort by the community.

If you need help with something, please let us know in our support forum or Zulip chat.

Screenshots

The plugin’s admin page with information and the controls to start the migration:

The plugin’s migration progress page:

The About ClassicPress screen that appears at the end of the migration:

Changelog

0.1.0
- The initial public release of this plugin. Switches to an early ClassicPress alpha release.
0.2.0
- Switches to ClassicPress 1.0.0-beta1 with working auto-updates.
- Also supports migrating multisite WordPress installations to ClassicPress.
0.3.0
- Switches to ClassicPress 1.0.0-beta1 without an intermediate upgrade step.
- Changes “Upgrade” back to “Migrate” to avoid confusion with plugin updates.
- Removes the “Switch” link from the plugins page when running ClassicPress.
0.4.0
- Support migrating from WP 5.0.
- Add a filter to allow overriding the WP version check.
- Remove unnecessary files and distribute a smaller plugin.
0.5.0
- Support migrating from WP up to 5.0.2.
- Switch to ClassicPress 1.0.0-beta2.
0.5.1
- Undo a change that was preventing some users from using the plugin.
0.5.2
- Support migrating from WP up to 5.0.3.
1.0.0
- Support migrating from WP up to 5.1.0.
- Switch to ClassicPress 1.0.0 by default.
- Add an advanced feature that allows switching to any version of WordPress or ClassicPress.
1.0.1
- Load the supported WordPress version and the target ClassicPress version from a remote API endpoint, so that a new release of the migration plugin is not required with every new WordPress or ClassicPress release.
1.1.0
- Change pre-existing composer.json from an error to a warning (details)
- Minor fix for disorganized/jumbled output in some cases (details)
1.2.0
- Add translation files and translate the plugin into Russian (details)
- Fix an issue with incorrect upgrade notices appearing immediately after a custom migration (details)
- Fix an issue with stale WordPress news items appearing in the dashboard after migrating to ClassicPress (details)
1.3.0
- Add Plugin and Theme check sections (details)
1.3.1
- Remove stray files from release
1.4.0
- Direct blocking issues to ClassicPress Forum (#82)
- Add plugin header checking (#83)
- Add theme header comparison check to compatibility logic (#76)
1.4.1
- Version Bump
1.5.0
- Add smart drop down to Advanced Controls
- Implement PHP version checking based on migration API endpoint
- Adjust checks, notifications and information text as needed for CP v2
- Warn that Migration requires Re-Install (reminder if you go back into the plugin)
- Chat link changed from Slack to Zulip
- Offer CP v1 & v2 current and one version back (unless no previous)
- Offer WP current, 6.2.x and 4.9.x (4.9 offered only if running PHP 7)
- Offer release version if running CP migration version
- Will not offer re-installation
- Suggest a ClassicPress Default theme
1.5.1
- Restrict Access to ‘can update core’
- Update GitHub Link
1.5.2
- Update Code to CPCS
1.5.3
- Change Plugin and Theme Checks to explain safest method, but only warn if not followed
- Change Core File check to show any modified files on the page rather than in the console
- Display override function info for unsupported WP versions when applicable
- Correct links and update wording as needed
1.6.0
- Fix “modified files” warning when locale is not en_US
- Update to Plugin and Theme Warnings
- Add override for WP version check in “General setting”
- Fixed Functions in admin-page.php
- Adding more support for translation
- Translation related fixes
- Validate custom migration URL
- Regenerate POT file
1.7.0
- Improve README.md file
- Improve i18n
- Change default Tagline on migration
- Change default Admin Color Scheme on migration from WordPress 7+
ClassicPress Pepper for Passwords

ClassicPress

For enhanced security add a "pepper" to password hashing.

Download

More Info
Overview

The ClassicPress Pepper Password Plugin is designed to enhance the security of user passwords by implementing a unique “pepper” mechanism. This plugin allows administrators to generate and manage a pepper string that is used in conjunction with password hashing, adding an additional layer of protection against unauthorized access.

Features
- Pepper Generation: Easily generate (or refresh) a random pepper string to enhance password security by clicking a button.
- Settings Menu: Access the plugin settings through the ClassicPress admin menu at Settings > Pepper.
- Automatic Activation: The plugin creates a pepper file upon activation, if it doesn’t already exist, to store the random Pepper string.
- User-Friendly Interface: Simple navigation and clear messages for users.
Manual Installation
1. Download the plugin .zip file.
2. Upload the pepper-password folder to the /wp-content/plugins/ directory via FTP, or visiting Plugins > Upload.
3. Activate the plugin through the Plugins menu in ClassicPress.
Installation
- Install the ClassicPress Directory Integration plugin and activate it on your site
- Visit Plugins > Install CP Plugins and search for ClassicPress Pepper Password Plugin
- You can install and activate the plugin by clicking the respective buttons.
Usage

Accessing Settings
- Navigate to Settings > Pepper in the ClassicPress admin dashboard to manage your pepper settings.
Generating a Pepper
- Click on the Enable Pepper or Renew Pepper button within the settings page to generate or renew the pepper string.
Important Notes
- Changing or deactivating this plugin will invalidate all stored password hashes, requiring users to reset their passwords.
- Ensure you have filesystem permissions set correctly for the plugin to function properly.
Contributing

Contributions are welcome! Please fork the repository and submit a pull request for any enhancements or bug fixes.

License

This plugin is licensed under the GPL v2 or later. Please see the LICENSE file for more details.

Support

For support or inquiries, please open an issue in the repository or contact the plugin author directly.
ClassicPress Directory Integration

ClassicPress

Install and update plugins from ClassicPress directory and keep ClassicPress themes updated.

Download

More Info
Features
- Plugins and themes from ClassicPress Directory now can update as WP.org plugins.
- Plugins from ClassicPress Directory now can be installed using the “Install CP Plugins” menu under “Plugins” menu.
- Themes from ClassicPress Directory now can be installed using the “Install CP Themes” menu under “Appearance” menu.
WP-CLI commands
- Flush transients: wp cpdi flush
Hooks

apply_filters( "cpdi_images_folder_{$plugin}", string $folder )

Filters the folder where we search for icons and banners.
The filtered path is relative to the plugin’s directory.
Default is /images.

Example:
add_filter( 'cpdi_images_folder_' . basename( __DIR__ ), function ( $source ) { return '/assets/images'; } );
Classic SEO

ClassicPress

SEO Plugin For ClassicPress Classic SEO is the first SEO plugin built specifically to work with ClassicPress. The plugin contains many essential SEO ...

Download

More Info
SEO Plugin For ClassicPress

Classic SEO is the first SEO plugin built specifically to work with ClassicPress. The plugin contains many essential SEO tools to help optimize your website.

Installation
- Head over to the Releases section of this GitHub repository.
- Expand the “Assets” dropdown by the latest release and download the classicpress-seo.zip file.
- Go to the “Plugins > Add New” section of your site’s dashboard and upload the zip file there using the “Upload Plugin” button.
Key Features
- Module Based System
- Google Schema Markup aka Rich Snippets
- XML Sitemap
- Optimize up to 5 Keywords
- Google Keyword Suggestion
- Redirection Manager
- Local SEO / Knowledge Graph
- SEO Optimized Breadcrumbs
- 404 Monitor
- Support for ACF
- Support for Classic Commerce
- Internal Linking Suggestions
- Role Manager
- Importers for Rank Math, Yoast, All In One SEO and The SEO Framework
Support

If you need support for Classic SEO or find a bug, you have threee choices:
- create an issue on the issues page
- create a topic in the ClassicPress forums.
- Look out for the #classic-seo channel on Slack
Changelog

v 2.3.0 / 2024-07-02
- IMPROVED: Add option to remove data on uninstall (in General Settings > Misc)
- REMOVED: Remove automatic deactivation of conflicting plugins (that wasn’t working)
- REMOVED: Remove unused Update class
- FIXED: Fix some more PHP deprecations
v 2.2.2 / 2024-06-20
- FIXED: Fix traits in authors sitemap (#173)
v 2.2.1 / 2024-01-05
- FIXED: Classic SEO prevents saving of metaboxes position (#167)
v 2.2.0 / 2023-09-25
- NEW: Support for PHP 8.1 and 8.2
- REMOVED: Support for PHP below 7.4
v 2.1.3 / 2023-05-25
- FIXED: SSL issues, deprecations
v 2.1.2 / 2023-02-03
- REMOVED: Remove REST API /disconnectSite endpoint (#150)
v 2.1.1 / 2023-01-25
- FIXED: Bad ZIP was attached to previous release
v 2.1.0 / 2023-01-24
- FIXED: Add support for PHP 8.0
v 2.0.1 / 2020-09-29
- FIXED: Missing semicolon
v 2.0.0 / 2020-09-29
- REMOVED: Google Search Console feature has been removed completely. See #112 for discussion. (#118)
- UPDATED: Replaced references to “WooCommerce” with “Classic Commerce” (#114) (props @simplycomputing)
- UPDATED: Update readme (#126)
- IMPROVED Minor CSS tweaks and accessibility improvements (#128)
- FIXED: Fix wrong field name in redirections cache (#119)
- FIXED: Fix display of CPSEO icon in admin menu (#123)
- FIXED: Fix display of icon and heading in CPSEO dashboard (#124)
- FIXED: Cleaned up some left over code (#122, #127)
v 1.0.0 / 2020-08-30
- FIXED: Fix for misaligned Classic SEO icon in top admin toolbar when viewing site #103
- FIXED: Remove empty title separator #104
- REMOVED: Remove legacy Rank Math help images #106
- UPDATED: Update language pot file #107
- UPDATED: Minor updates to help pages #108
- FIXED: Replace “ClassicPress-research” with “ClassicPress-plugins” #109
v 1.0.0-rc.1 / 2020-08-02
- IMPROVED: Clarify wording on Author Archives and Date Archives option settings #85
- IMPROVED: Add clear installation instructions to readme #89 (props @nylen)
- REMOVED: Auto Update setting removed. This was a legacy setting from RM and hasd no effect in CPSEO #86
- FIXED: Corrected misaligned CPSEO icon in top admin bar and left-hand nav menu #91
- FIXED: Fix Search Console stats database query syntax which caused “Unknown column” error in some installations #97 (props @nylen)
- FIXED: Fix a PHP notice (Undefined index: path) in Conditional::is_rest() #98 (props @nylen)
- FIXED: Fix for Search Console jQuery error which prevented SC cache from being cleared in General Settings #94
- FIXED: Excludes .gitignore and .gitattributes release builds via git archive #96 (props @nylen)
- FIXED: Clean up .gitignore #92 (props @nylen)
- FIXED: Removes extraneous ‘%s’ placeholder on Search Console settings page #100
- UPDATED: Minor CSS tweaks #95, #99
v 1.0.0-beta4 / 2020-05-24
- NEW: Add new title separator characters (#71)
- NEW: Add ‘%’ to CTR heading in Search Analytics view within Search Console (#72)
- NEW: Use native custom post types dashboard icon in Titles & Meta Setting (#75)
- IMPROVED: Output of SEO meta for pages created with page builders (#74)
- IMPROVED: Hide cpseo meta key data in custom fields on post edit page (#76)
- UPDATED: Help page content updated (#78)
- UPDATED: Translations (#79)
- FIXED: Dash menu not updating when module activated (#77)
- FIXED: Missing cpseo prefix in some settings (#81)
- FIXED: Removed broken link from title on Dashboard page (#73)
v 1.0.0-beta3 / 2020-04-03
- NEW: Add new Events schema properties to help with events that have been cancelled or postponed as a result of Covid-19
- UPDATED: Code Potent Update Manager updated to latest version
v 1.0.0-beta2 / 2020-02-14
- NEW: Add usage tracking notice and opt out (props xxsimoxx)
- FIX: Variables translations in help pages will now translate
- FIX: Fix for duplicate “view details” when GitHub updater is active (props xxsimoxx)
- FIX: Fix for PHP error when refreshing sitemap in Search Console
v 1.0.0-beta1 / 2020-02-08
- NEW: Integrated Code Potent’s Update Manager
- NEW: Check for WP_CLI (props xxsimoxx)
- IMPROVED: Services rich snippets (added missing properties)
- Moved to new ClassicPress-plugins GitHub repository
- Renamed dashicon image
- Remove other superfluous images
- Translation file updates
v 0.7.0 / 2020-01-17
- NEW: Adds importer for The SEO Framework
v 0.6.0 / 2019-12-28
- UPDATED: Now fully supports Classic Commerce
v 0.5.3 / 2019-12-21
- FIX: Fix for wrong message shown on post edit page when content length was between 500 and 600 words
- TWEAK: Minor tweaks to AIOSEO import
v 0.5.2 / 2019-12-20
- FIX: Fix for “Undefined variable: sitemap_settings” in class-aioseo.php
v 0.5.1 / 2019-12-20
- IMPROVED: All In One SEO import
v 0.5.0 / 2019-12-18
- NEW: Added All In One SEO import
- IMPROVED: Yoast import
v 0.4.4 / 2019-12-06
- FIX: Second fix for issue #24 – keywords from Rank Math not being imported
v 0.4.3 / 2019-12-05
- FIX: Fix for issue #24 – import from Rank Math not working as expected
v 0.4.2 / 2019-11-29
- NEW: Added charts on Search Console overview page
- FIX: minor bug fixes
v 0.4.1 / 2019-11-28
- FIX: Fix for PHP error: “Fatal error : Cannot redeclare Classic_SEO::define_constants() in /home/xxx/public_html/xxx/xxx/wp-content/plugins/classicpress-seo/classicpress-seo.php on line 223”
v 0.4.0 / 2019-11-28
- NEW: Added support for Google Search Console
v 0.3.3 / 2019-11-25
- FIX: Fix for #20: Plugin is not automatically deactivated when using PHP < 7.0.
v 0.3.2 / 2019-11-20
- FIX: Fix for #17: PHP error “call_user_func_array() expects parameter 1 to be a valid callback, function on_login not found or invalid function name”
v 0.3.1 / 2019-11-18
- FIX: Classic SEO icon size in admin menu
v 0.3.0 / 2019-11-18
- NEW: Plugin has new name. Now called Classic SEO as per [discussions on forums](https://forums.classicpress.net/t/plugin-theme-naming-conven