Category: News

ClassicPress made it to Softaculous!

Tim Hughes and James Nylen did it again. ClassicPress has been added to Softaculous in version 5.3.5. Now you can use the Softaculous one-click installer to install a new ClassicPress site, or import your existing installs into Softaculous as ClassicPress. Of course, it is important to know how to import these sites, so below you will find a tutorial.

Moving your site into Softaculous

If you currently have an existing ClassicPress installation that you want to move into Softaculous, here is how to do it.

Step 1: Disconnect your current install.

First, you need to disconnect your install from the current management system. If this does not apply to you, you can skip this step.

If you have a ClassicPress installation you are managing via Softaculous registered as WordPress, you will have to disconnect the existing install from Softaculous.

Reach the “All Installs” button located top right and click it.

Next, select the install you need to disconnect and click the red X

Disconnect the existing install from Softaculous

Now uncheck all the boxes as per the screenshot below, this will disconnect the install from Softaculous without touching the files and database.

Uncheck all the boxes

After this, click on Remove Install at the bottom of the page as shown here:

Remove Install

You will be warned that the operation can’t be reverted, click ok.

Step 2: Importing into Softaculous

Now, all you have to do is import the site in Softaculous linking it to ClassicPress, so that it can be managed via Softaculous.

Search for ClassicPress (in the Portals/CMS category) and select the ClassicPress page within the installer.

Click import as shown below:

Importing into Softaculous

On the tab From this Server fill in the required information (http/https and the folder) and click the Import button at the bottom of the page:

Fill in the required information

Step 3: Hold your breath

This page:

ClassicPress has been imported into Softaculous

means you successfully imported your install as ClassicPress in Softaculous!

Step 4: Rejoice


Introducing the 2020 ClassicPress Management Committee

The 2020 ClassicPress Management Committee Elections closed this morning at 12pm UTC, with a 47% turnout of eligible voters.

After verifying  the results, I am excited to introduce the 2020 ClassicPress Management Committee.

2020 Management Committee

  • Tim Hughes (@1stepforward)
  • Michelle Coe (@BlueSkyPhoenix)
  • John Alarcon (@CodePotent)
  • Elisabetta Carrara (@ElisabettaCarrara)
  • Charles Lecklider (@invisnet)
  • James Nylen (@james)
  • Patrick Klein (@klein)
  • Tim Kaye (@timkaye)
  • Wade Striebel (@wadestriebel)

The new committee members will take their place starting January 1st, 2020.

2019 Management Committee

We thank those that served on the ClassicPress Founding Committee, they were instrumental in moving the project forward in its infancy stage. All Founding Committee members will continue to be recognized by the Founding Committee status.

Election Time!

We are inviting all Trust Level 2 users and above to vote in the Management Committee Elections taking place right now. The vote is open from December 2nd 12:00 pm to December 9th 12:00 pm.

Vote Here

If the link above takes you to a 404 page that means you have not yet met the Trust Level 2 requirements.

The voting process

The voting page will have a poll where your votes can be cast. You have up to 9 votes that you can use, though you don’t have to use all 9 if you do not wish to. You also have the opportunity to change your votes as often as you like until the deadline. We wish everyone the best of luck.

The nominees

Based on the outcome of the Community Vote, there are 9 spots open for the 2020 Management Committee, and 10 eligible candidates have nominated themselves for membership in the 2020 Committee. To learn more about the nominees, visit their self-nominations:

Above list is in order of announcements and has no inherent bias towards any candidate.

Installatron now offers ClassicPress!

Thanks to the tireless work of Tim Hughes, with more than a little help from James Nylen, we are able to bring you joyous news. And it is something that is surely one step forward for ClassicPress. Installatron has decided to support ClassicPress in their popular auto-installer. Installatron makes installing ClassicPress even easier and we are very pleased that they’ve decided to include our CMS.

So, when will you start seeing ClassicPress becoming available as an option? Installatron added ClassicPress to their software in version 9.1.48-3. If you host your own Installatron, you should update to this version when you are able. If you are with a hosting provider and don’t control your own Installatron, ask them when they are planning to update.

Moving your site into Installatron

If you currently have an existing site and want to move it into Installatron, here is how you do it.

Step 1: Remove it from the current management system

If you have a site installed in Installatron as a WordPress site, you will first need to remove it from the existing management system. If this is not applicable in your case, you can skip this step.

Go to your application.

Click on the Advanced tab.

Click the checkbox to remove the application from Installatron and click Save All.

Step 2: Navigate to ClassicPress

Now, select the Installatron Applications Installer option from your control panel and go to the Application Browser. Choose ClassicPress from the Content Management section.

Step 3: Run the import

You will be importing an existing application, so choose this option from the menu to the right of the big Install this application button.

Choose the Continue button under From this account.

Then make sure the domain name format is correct (http or https, www or non-www, etc). When you have all the details correct, click the Import button (you can always change the details later).

Step 4: Celebrate

You should now be presented with a screen showing the details of your application. Congratulations… your ClassicPress site is now being recognized and correctly managed as a ClassicPress site by Installatron.

Self-nominations for the Committee of 2020 are now open

It is that time of year for closure, and that means a lot of looking back and forward. Many people are already doing their personal reflections and reviews of 2019. We are moving into the future, and in 2020, something entirely new is going to happen for the project. For the first time, the committee is getting a shake-up! The Founding Committee will pass the torch to a new committee. ClassicPress election time is coming up.

Nominating yourself

The election is open to all people with trust level 2 on our forums, which means we have a lot of potential candidates. If you are trust level 2 and wish to nominate yourself for a committee position, you can do this at the 2020 committee candidates category in the forums. Every TL2 user who wishes to run for a place in the committee must create a new thread in this category and you may use your post to explain why you wish to run. There should be no campaigning outside of your post in this category.

The new committee will have 9 members. Of the original Founding Committee, only 6 have decided to run in this election. You read that right, current committee members don’t just automatically join the new committee. They must be elected just like everyone else. Even if all 6 of them get elected, there will be 3 new committee members joining them, so the 2020 committee cannot/will not be only Founding Committee members. What I am trying to say here is that everyone has a chance and it is really important to nominate yourself if you think you can make a difference in the project.

With great power…

If you want to nominate yourself for the election, do be aware that there are certain expectations and responsibilities that come with being a committee member. It is important that you are among the people most invested in making ClassicPress a success. This means that it is expected that you are active in at least one of the teams working on ClassicPress (e.g. Community, Development, Security, etc.). It is also expected that you participate in most of the committee meetings. (Of course, it is always possible to miss one. However, this should be the exception, not the rule.)

The deadline to nominate yourself is November 20th at 11:59pm UTC time. For more information you can refer to the original announcement.

Directors Added to ClassicPress Limited

ClassicPress has, and always will be, a community-led project. My goal from the outset was to create a structure where democracy rules and no single person could change the direction of ClassicPress without oversight and checks and balances.

It is therefore with great pleasure that I announce the appointment of three new Directors to ClassicPress Limited.

Michelle Coe, James Nylen and Wade Striebel have been pivotal in shaping, building and delivering ClassicPress to a worldwide audience and they have proven through actions their commitment to the long-term success of ClassicPress. It is an honour to welcome them as Directors of ClassicPress Limited.

This is an exciting step in the journey of ClassicPress, and I hope over time we will explore more ways to officially give ownership of ClassicPress to the community who continues to bring it to life.

I’d also like to express my everlasting gratitude to my fellow committee members and members of the community. Your generosity and hard work in making ClassicPress a reality is a gift to the world.

Scott Bowler, Founder

Introducing ClassicPress 1.0.0: Aurora

Since ClassicPress began in August of 2018, our all-volunteer team has worked hard to bring ClassicPress to you. Today, we are pleased to announce the first official, stable release of ClassicPress: version 1.0.0, codenamed Aurora, available immediately.

Starting with Aurora, the ClassicPress v1 series is a long-term support (LTS) version for businesses who want the power and stability of WordPress 4.9.x and are seeking an equally stable alternative solution. Since all existing plugins and themes that are supported on WP 4.9.x are supported in ClassicPress 1.0.0, Aurora is also ideal for those that find that WordPress 5.0+ is no longer a fit for them.

ClassicPress 1.0.0 is based on the codebase of the WordPress 4.9 branch (currently WordPress version 4.9.9) and contains all changes from this version of WordPress, including the latest security fixes.

Of course, we’ve also made the codebase our own. Read on for more details…

Major changes from WordPress

  • Versioning strategy. We use the industry standard semver specification for predictable, logical ClassicPress version numbers.
  • Development process. ClassicPress is developed on GitHub, which allows us to take full advantage of development tools such as Travis CI and Renovate.
  • Security Updates.
    • GPG signed releases. We publish our releases using signed git tags and zip files served from GitHub, so that you know what you’re getting. Much more to come in future versions, including release verification during automatic and manual updates!
    • Updates. ClassicPress serves new version notifications from our own API servers, again with a well-tested and clearly-defined versioning policy.
    • PHP versions. ClassicPress requires PHP 5.6 or higher, as the first step in a strategy for encouraging ClassicPress users to keep their sites up to date. ClassicPress 1.0.0 also adds PHP 7.3 compatibility for all unit-tested code in the core software.
  • Translations. ClassicPress serves core translations from our own API servers. ClassicPress core is currently translated into 10 languages, and more to come with help from our community.
  • Admin dashboard. WordPress-specific features like community events and featured plugins have been removed and/or replaced with ClassicPress equivalents. For example, we’ve added a “Featured Petitions” widget to encourage community participation in our development process.
  • Renaming. We’ve renamed all visual aspects and comments/docblocks from WordPress to ClassicPress. For compatibility, class/function and file names have been left alone.
  • Installation. For new sites, ClassicPress has a re-branded installation process, with fewer steps. We also support installation using composer natively.
  • Simplifications. We’ve removed the Akismet and Hello Dolly plugins, but they can still be installed from the plugin directory. We’ll be making the core software even leaner in version 2.
  • Community. ClassicPress is what it is today due to input and support from our welcoming and thriving community. Thank you for helping us make ClassicPress a reality!

For a list of new or changed functions and filters in ClassicPress 1.0.0, see this post.

There are a lot of other places where we’ve been able to make small improvements to ClassicPress so far, such as better design and typography in parts of the admin dashboard, and other developer experience improvements. For more information, including links to download the release, installation instructions, and a more complete list of changes, please see the release notes on our forums.

We are excited about what the future holds for ClassicPress and encourage you to participate in the ClassicPress Community. We want to be the content management system of choice for businesses worldwide, and we need your support to succeed! Connect with us on Slack and join our forums and petitions sites to add your voice and vote to our community. Your contributions help ClassicPress continue to grow and thrive!

A word from Scott…

Today ClassicPress reaches a major milestone, and again I find myself without words to properly express my gratitude for each person in the Community who has worked to make Aurora happen. The time, effort and passion that has been dedicated to ClassicPress over these last several months has been awe-inspiring, and I am grateful for every hour each of you has given to the project. Thank you from the bottom of my heart. Truly, ClassicPress is Community-led, and I am thrilled to be a part of this journey with each of you.

I look forward to what comes next as we continue on toward creating a world-class content management system for businesses who want to have a powerful, versatile and predictable solution for their website needs.

– Scott Bowler

For more information, including links to download the release, installation instructions, and a more specific list of changes, please see the release announcement on our forums.

ClassicPress 1.0.0-rc2 is live!

Today we’re excited to announce the release of ClassicPress 1.0.0-rc2, available immediately.

Here is a list of the minor changes in this release, as compared to our last one, 1.0.0-rc1:

  • Remove files that were accidentally included in rc1
  • Avoid duplicated rewrite rules (WordPress and ClassicPress) in .htaccess after migration
  • Remove WP-only themes features, continuing from changes in rc1 (details)
  • Add some explanatory messages for the default themes, since both parent and child themes are included (details)
  • Use a consistent header for all About tabs in the dashboard (details)
  • Fix a PHP notice in the dashboard petitions widget (details)

Next steps

Testing is critical during the RC phase — if we have any new bugs in ClassicPress 1.0.0-rc2, we need to know now so that we can get them fixed before the final release!  Otherwise, the final release will be out on Tuesday, March 5, as previously mentioned.

We invite you to put your new or existing ClassicPress sites on rc2 as soon as possible, and let us know if you see any issues, especially with regard to any of the areas that we changed.

For more information, including links to download the release, installation instructions, and a more specific list of changes, please see the release announcement on our forums.

ClassicPress 1.0.0-rc1 is live!

Today we’re excited to announce the release of ClassicPress 1.0.0-rc1, available immediately.

We have now left the “beta” release stage, and we are one step closer to a full, stable release that will serve as our foundation for many more future releases.

Here is a short list of the most important changes in this release, as compared to our last one, 1.0.0-beta2:

  • Finish porting changes from WordPress for PHP 7.3 compatibility.
  • Remove most links to and features that use accounts.
  • Fix any known bugs that are new to ClassicPress.
  • Miscellaneous other “polish” such as better organization for new files and improving the experience around ClassicPress installation and default themes.

We need your help!

Testing is critical — if we have any new bugs in ClassicPress 1.0.0-rc1, we need to know now so that we can get them fixed before the final release!  We invite you to put your new or existing ClassicPress sites on rc1 as soon as possible, and let us know if you see any issues, especially with regard to any of the areas that we changed.

For more information, including links to download the release, installation instructions, and a more specific list of changes, please see the release announcement on our forums.

ClassicPress: A Six Month Review

Did you know that ClassicPress will be six months old this month? It’s true. This month, we will celebrate six months together as an organization. It’s been a very busy six months! In addition to preparing for the launch of ClassicPress v1, we have been laying a firm foundation within the organization that will serve us well as we grow. Creating a roadmap and a more formalized organizational structure are two essential building blocks of that foundation, and we are happy to announce that they have been completed and approved by the Founding Committee.

It’s All About Community

ClassicPress is proudly a democratic community-led organization. We believe that careful planning combined with the insight and collective wisdom of the ClassicPress community will ensure the success of ClassicPress for many years to come. We want to be able to rapidly change and adapt to meet the expressed needs of the ClassicPress community. Clear roles and boundaries will help us to avoid some of the pitfalls that other organizations have experienced.

We facilitate democratic discussion and decision making via our forums, and each member has a say in how ClassicPress evolves over time by sharing and voting for ideas on our petitions website. We are sensitive to the wide variety of needs presented by ClassicPress users, and we want to ensure that those who use ClassicPress find it to be a positive experience that supports them as they focus on their own personal and business goals.

Navigating the Future

With the understanding that every organization experiences conflict from time to time, we have also created some guidelines to help navigate those challenges successfully. Ultimately, all decisions made will be an effort to serve the best interest of the organization as a whole. That has been our vision from the beginning, and we understand that it will take time and effort to make that dream a reality.

The Founding Committee is made up of many kinds of people: designers, developers, marketing professionals, security experts, plugin and theme authors, attorneys, and more. We all have a common goal — to serve the ClassicPress community by creating a powerful, versatile and predictable content management system. If you are part of the ClassicPress community, thank you for your trust, your insight, and your contributions in the forums and elsewhere! If you’ve not yet joined us, we invite you to take the time to get to know us better. We plan to be around for a very long time.

Photo by Jennie Brown on Unsplash