The CMS for Creators. Stable. Lightweight. Instantly Familiar. Also known as the WordPress fork.

Installs: 2 996

Dependents: 1

Suggesters: 0

Security: 0

Stars: 42

Watchers: 13

Forks: 11


1.5.2 2023-02-02 16:32 UTC


<!DOCTYPE html>

	<meta name="viewport" content="width=device-width" />
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<title>ClassicPress &#8250; ReadMe</title>
	<link rel="stylesheet" href="wp-admin/css/install.css?ver=20190218" type="text/css" />

	<h1 id="logo">
		<a href="">ClassicPress</a>
	<p style="text-align: center">The CMS for Creators.<br>Stable. Lightweight. Instantly Familiar.</p>

	<h2 id="welcome">Welcome to ClassicPress!</h2>
	<p>You&#8217;ve just become part of a growing community of people who value the firm foundation WordPress 4.9.x
		provides for websites everywhere. <a href="">Guided by our
			community</a>, we can leverage our collective expertise to maintain and develop the ClassicPress platform as
		<em>the</em> content management system of choice for professionals, hobbyists, developers, sole-traders and
		<em>all</em> website creators worldwide.</p>
	<p>Our purpose is to provide a stable, secure, and instantly familiar content management system driven by the needs
		of the community. We invite you to connect with us and <a href="#resources">add your voice to the
	<p style="text-align: right">&#8212; The ClassicPress Directors</p>

	<h2 id="installation">Installation</h2>
	<p>For more information about installing ClassicPress, see our <a
			href="">installation documentation</a>.</p>
		<li>Download the latest release of ClassicPress from our <a
				href="">releases page</a>.</li>
		<li>Unzip the package in an empty directory and upload all the files to your server using a remote connection
			method such as SSH, SFTP, or FTP.</li>
		<li>Open <span class="file"><a href="wp-admin/install.php">wp-admin/install.php</a></span> in the browser. It
			will take you through the process to set up a <code>wp-config.php</code> file with the database connection
			<ol type="a">
				<li>If for some reason this doesn&#8217;t work: Open up <code>wp-config-sample.php</code> with a text
					editor and fill in the database connection details.</li>
				<li>Save the file as <code>wp-config.php</code> and upload it.</li>
				<li>Open <span class="file"><a href="wp-admin/install.php">wp-admin/install.php</a></span> in the
		<li>Once the configuration file is set up, the installer will set up the tables needed for the website. If there
			is an error, double check the <code>wp-config.php</code> file, and try again. If it fails again, please go
			to the <a href="" title="ClassicPress support">support forums</a>
			with as much data as you can gather.</li>
		<li><strong>If you did not enter a password, note the password given to you.</strong> If you did not provide a
			username, it will be <code>admin</code>.</li>
		<li>The installer should then go to the <a href="wp-login.php">login page</a>. Sign in with the username and
			password you chose during the installation. If a password was generated, it is possible to change it by
			clicking on the username in the top right corner after signing in. It is also possible to reach this Profile
			page by navigating to &#8220;Users&#8221; in the sidebar navigation and then selecting &#8220;Your
			Profile&#8221; from the sub-menu.</li>

	<h2 id="updating">Updating</h2>
	<h3>Using the Automatic Updater</h3>
	<p>If you are updating from beta version <code>1.0.0-beta1</code> or higher, you can use the automatic updater:</p>
		<li>Open <span class="file"><a href="wp-admin/update-core.php">wp-admin/update-core.php</a></span> in your
			browser and follow the instructions.</li>
		<li>That&#8217;s it!</li>

	<h3>Updating Manually</h3>
	<p>Updating manually can be done via remote connection methods such as SFTP (preferred) or FTP.</p>
	<p>For more information, see our <a
			href="">manual update
	<ol start="0">
		<li>Before doing anything, <strong>make sure you have a working backup of the entire site as well as the
		<li>Download the latest release of ClassicPress from our <a
				href="">releases page</a>.</li>
		<li>On your <strong>local computer</strong>, unzip the ClassicPress release file into a directory.</li>
		<li>On your <strong>local computer</strong>, remove the <code>wp-config-sample.php</code> file and the
			<code>wp-content</code> directory.</li>
		<li>Upload what's left over to your server, replacing the existing files (using either SSH or an application
			that connects over SFTP or FTP).</li>
		<li>Point the browser to <span class="file"><a href="wp-admin/upgrade.php">/wp-admin/upgrade.php</a></span> and
			follow the instructions.</li>

	<h2 id="migrating-from-wordpress">Migrating from WordPress</h2>
	<p>With the ClassicPress migration plugin, it is very easy to migrate existing sites from WordPress to ClassicPress.
		Please follow the <a
			documentation</a> for step-by-step instructions.</p>

	<h2 id="requirements">System Requirements</h2>
		<li><a href="">PHP</a> version <strong>5.6</strong> or higher.</li>
		<li><a href="">MySQL</a> version <strong>5.0</strong> or higher.</li>
		<li><a href="">Apache</a> version <strong>2.4</strong> server or higher.</li>

		<li><a href="" target="_blank" rel="noopener">PHP</a> version <strong>8.0</strong>
		<li><a href="" target="_blank" rel="noopener">MySQL</a> version <strong>5.7</strong> or
			higher or <a href="" target="_blank" rel="noopener">MariaDB</a> version
			<strong>10.3</strong> or higher.</li>
		<li><a href="" target="_blank" rel="noopener">Apache</a> <strong>2.4</strong>
			with&nbsp;mod_rewrite module, <a href="" target="_blank" rel="noopener">Nginx</a>, or
			<a href="" target="_blank" rel="noopener">LiteSpeed</a> server.</li>
		<li>An SSL certificate to support HTTPS (free from <a href="" target="_blank"
				rel="noopener">Let’s Encrypt</a>).</li>

	<h2 id="resources">Online Resources</h2>
	<p>If you have any questions that aren&#8217;t addressed in this document, please take advantage of
		ClassicPress&#8217; numerous online resources:</p>
		<dt><a href="">ClassicPress Homepage</a></dt>
		<dd>This is the starting point, with basic information about ClassicPress and links to all other resources in
			this list.</dd>
		<dt><a href="">ClassicPress Documentation</a></dt>
		<dd>Here you'll find up-to-date reference information about ClassicPress.</dd>
		<dt><a href="">ClassicPress Blog</a></dt>
		<dd>This is where you&#8217;ll find the latest updates and news related to ClassicPress as well as tutorials and
			other interesting snippets of information. Recent ClassicPress news appears in your administrative dashboard
			by default.</dd>
		<dt><a href="">ClassicPress Support Forums</a></dt>
		<dd>The support forums are a great way to get help from other ClassicPress users. Many community members and
			ClassicPress leaders are active here.</dd>
		<dt><a href="">ClassicPress Slack</a></dt>
		<dd>There is an active online chat channel that is used for discussion among people who use ClassicPress and
			plan its further development.</dd>
		<dt><a href="">ClassicPress Feature Requests</a></dt>
		<dd>Do you have an idea to make ClassicPress better? Consider sharing your idea on GitHub for the core team and the community to share feedback and, possibly, implement the feature.</dd>
		<dt><a href="">ClassicPress Governance</a></dt>
		<dd>Last but not least, read about the ClassicPress governance structure to understand how we do things and how
			you can help. ClassicPress is a community-driven and funded fork of WordPress that enables all stakeholders to
			shape the direction that the project takes. This page aims to explain how we handle this process to ensure
			that power doesn't become centralised and that every voice can be heard.</dd>

	<h2 id="share">Share the Love</h2>
	<p>ClassicPress has no multi-million dollar marketing campaign or celebrity sponsors, but we do have something even
		better: you and the rest of our community. If you enjoy ClassicPress, please consider:</p>
		<li>Participating in our <a href="">forums</a></li>
		<li>Telling a friend about ClassicPress</li>
		<li>Setting up a ClassicPress website for someone less knowledgeable than yourself</li>
		<li>Sharing your favorite article about us with your social media followers</li>
		<li>Writing a technical publication or other news organization to tell them about ClassicPress</li>
	<h2 id="fund">Community Funded</h2>
	<p>ClassicPress is a community-driven and funded free open source project. You contributions help ClassicPress pay infrastructure and administrative costs. There are several ways you can financially support ClassicPress:</p>
		<li><a href="" title="Donate to ClassicPress">Making a donation</a> to help us run the project (donations in the US are tax-deductible).</li>
		<li>If you have a business, <a href="">become a sponsor</a> to promote your brand to ClassicPress community. Sponsorships start at $250.</li>
		<li>Support ClassicPress on GitHub by <a href="">becoming a sponsor.</a></li>
		<li>Visit <a href="">ClassicPress Swag store</a> and buy ClassicPress-branded merchandise to show your support.</li>
	<h2 id="credits">Credits</h2>
	<p>ClassicPress is a hard fork of the <a href="">WordPress 4.9 branch</a>.
		WordPress itself is a fork of b2/caf&#233;log from Michel Valdrighi.</p>

	<h2 id="license">License</h2>
	<p>ClassicPress is free software, and is released under the terms of the <abbr
			title="GNU General Public License">GPL</abbr> version 2 or (at your option) any later version. See <a