The plugin I am going to cover in this post, is a brand new one; Avatars.

Functionality

The Avatars plugin has three key pieces of functionality:

Upload an image file using an FTP client, to the plugins images folder, called CustomAvatar.png and, via the Discussion settings page, set this as the default avatar to replace the Gravatars used by default.

The admin can, via the plugin Settings page, set an option to allow only local avatars which will use the default avatar rather than any Gravatar a user might be using.

Users can upload their own avatar which is stored in the media library.

Demo

This site is using the Avatars plugin; you can see this in the first comment of this post where you can see my IG avatar.

I’ve been involved with the ClassicPress project for a while now in a few different ways (such as writing FAQs and drafting plugin directory rules).

One of the things I have been working on is rewriting my plugins, to both improve the functionality and also to improve their adherence to coding standards and best practice. There was quite a few ways where I was not following best practice or where I had code which was not very secure.

Some plugins have had a near total rewrite while others have just been updated to do things in a more standardised and recommend way. Part of the reason I have done this, in fact been able to do this, is how welcoming and willing to offer advice the people in the ClassicPress community have been.

I have also written a number of new plugins which are all available for ClassicPress (they will also work with WordPress, but I have not submitted them to the WordPress Plugin Repository.

There have been quite a few people who have been willing to answer questions and offer assistance, but I will single out John Alarcon, known in the ClassicPress Community as Code Potent, who has gone out of his way to be of great help.

In this series of posts, I am going to give a brief introduction to each of the plugins I have available, along with links to plugin demos or examples and to my Development site where further details, download and support links are available.

This post is part of the series on Installing ClassicPress; ClassicPress is an open source fork of WordPress which aims to target the business market or those looking for a CMS with a focus on security, stability and flexibility.

Now that we know that the new ClassicPress site works I’d recommend editing your new wp-config.php file to change the authentication keys and salts. You will need to use your FTP client to make this change.

Open and edit your wp-config.php file and find the highlighted section. These are the authentication keys and salts used by ClassicPress for cookies and the like which it is recommended you change:

This post is part of the series on Installing ClassicPress; ClassicPress is an open source fork of WordPress which aims to target the business market or those looking for a CMS with a focus on security, stability and flexibility.

With ClassicPress installed, the next step in the installation is to test that the site works.

If you navigate to your web address followed by /wp-login.php you can enter the admin credentials created during the installation:

This post is part of the series on Installing ClassicPress; ClassicPress is an open source fork of WordPress which aims to target the business market or those looking for a CMS with a focus on security, stability and flexibility.

This post is part of the series on Installing ClassicPress; ClassicPress is an open source fork of WordPress which aims to target the business market or those looking for a CMS with a focus on security, stability and flexibility.

To download ClassicPress, visit their website and click the green Download ClassicPress button:

When I started this blog seven years ago, I opted to use WordPress as the content management system to build it on. It was both easy to use and flexible. I’ve taken advantage of that flexibility over the years to write a number of plugins to add new functionality.

However, in the most recent iterations of WordPress, ostensibly an open source project, but actually controlled by Automattic, has introduced the Gutenberg block editor which has, in my opinion, fundamentally broken the easy writing experience of WordPress. This lead me to start looking around at alternatives and, quite naturally due to the duration and extent of my use of WordPress, the hard fork of WordPress known as ClassicPress. The initial impetus around the fork was against Gutenberg, but it has taken a wider view of the issues around WordPress and is trying to set itself up so that no one person can dictate the future of the project (as Matt Mullenweg dictates for WordPress).

Having gotten involved in the project, I have helped to update some documentation (such as FAQs), draft some proposed rules for the plugin directory (intended for ClassicPress v2) and assist in a few other small ways (unfortunately, my PHP is not good enough to help update core files).

Over the course of this weekend I have migrated my websites to a new web host; hopefully, the only difference you will notice is that the sites are now being served over an https connection.

However, if you do notice any issues, images not loading or broken links (I’ve moved from a Windows hosting package to a Linux one so case now matters) ,for example, I’d appreciate you leaving a comment below with details.

Update: I forgot to mention, that when I migrated the sites to a new host, I also migrated them from WordPress to ClassicPress.

Dynamics GP Community

Login

Map of Visits

Disclaimer

This blog is a personal project; all opinions are my own and do not necessarily reflect those of my employer.

This blog and its content is provided "AS IS" with no warranty of any kind, either expressed or implied, made in relation to the accuracy, reliability or content of the information herein. The author shall not be liable for any direct, indirect, incidental or consequential damages arising out of the use of, or inability to use, information or opinions expressed in this site and confers no rights.

The links in this blog may lead to third-party Web sites to provide access to third-party resources to assist you in finding other services and/or technical support resources. Information at these sites may change without notice and azurecurve is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.