Category: Tools

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'; } );
Update Manager

Simone Fioravanti

Push updates for your ClassicPress plugins and themes from GitHub or other remote sources.

Download

More Info
Painlessly push updates to your ClassicPress plugin and theme users! Serve updates from GitHub, your own site, or somewhere in the cloud. 100% integrated with the ClassicPress update process; super-slim and performant. Incredibly easy!

With the Update Manager plugin for ClassicPress, developers can push plugin and theme updates out to their end users with ease! This isn’t a fork of a WordPress plugin – this is a brand new plugin built specifically for ClassicPress!

Remote Updates made Easy

No matter where you host your plugin or theme code – GitHub, BitBucket, AWS, or even your own website – the Update Manager plugin makes quick work of pushing updates to your end users. A fantastic tool for plugin and theme developers, agencies, and freelancers!

Simple & Lightweight

The Update Manager only requires that you add a single file to your plugin or theme – and it’s under 30k! There’s no libraries to think about. There’s no huge files to add bloat. There’s no complicated steps to trip you up! And, best of all, your users don’t have to install an extra plugin just to deal with updates.

Complete Integration

The Update Manager plugin is fully integrated with ClassicPress’ core update process. Adding your own icons, banners, and screenshots is as simple as dropping your images into the right directory. When your users click for information about your plugin in their dashboard, the popup windows look fantastic, complete with details, imagery, changelog, reviews…and more! Themes look great, too!

Plugin Integration

To setup a plugin to work with the Update Manager, the following general steps are recommended. This page details each of the steps and describes how to use the plugin going forward.
1. Install and activate the Update Manager plugin on your own site.
2. Add the Update Client file to your own plugin.
3. Create an update endpoint in the Update Manager.
4. Test the endpoint in a browser.
5. Test the update on an actual site.
6. Publish the endpoint.
Install the Update Manager Plugin
1. Install the Update Manager plugin according to the installation instructions.
2. Navigate to Dashboard > Update Manager > Plugins > Add New – this is where you will be managing your plugin updates.
Adding the Update Client file to a Plugin
1. Copy the UpdateClient.class.php file (from the Update Manager plugin) into your plugin’s file structure.
2. Set namespace to a unique value; line 22.
3. Set UPDATE_SERVER to the URL where your Update Manager plugin is installed; line 25.
4. Set USE_DIRECTORY to true to skip loading the class starting from ClassicPress v.2; line 30.
5. Set SECURE_SOURCE to the starting part of the URL of the updated zip file if you want to add an extra layer of security; line 35. See line 236 to understand how check is done.
6. Set UPDATE_TYPE to plugin or theme; line 38.
7. Use require_once('/path/to/UpdateClient.class.php') in your plugin’s primary PHP file to run the update client.
Creating an Update Endpoint for a Plugin
1. Navigate to Dashboard > Update Manager > Plugins > Add New
2. Set the Endpoint Identifier for your plugin; ie, my-plugin-folder/my-plugin-file.php.
3. Add your Plugin Details to the editor; if you have a readme.txt file, you can copy it right in.
4. Optionally, add URLs for any Testing Domains that can receive test updates.
5. Optionally, add contact methods for receiving Notifications of issues.
6. Click Publish to make the update immediately available.
Viewing an Update Endpoint in the Browser

If your update endpoint isn’t working as expected, neither will your update. So, before even testing the update process, it’s a good idea to call up the endpoint in a browser and verify that it looks like valid JSON data. The following steps will allow you to view endpoints in the browser. This is not available for endpoints in Draft status.
1. Navigate to Dashboard > Update Manager > Plugins
2. Hover over any of the listed endpoints and click View Endpoint.
Pushing an Update to all Plugin Users

When you create a new version of your plugin, you’ll need to push it out to your end users. To do this:
1. Navigate to Dashboard > Update Manager > Plugins
2. Click to Edit the particular endpoint.
3. Update the Plugin Details section to reflect the new version’s details.
4. Click to Update the endpoint.
Pushing an Update to Limited Users for Testing Purposes
1. Navigate to Dashboard > Update Manager > Plugins
2. Click to Edit an endpoint.
3. Set the Status to Pending Review.
4. Click to Update the endpoint.
With the plugin in Pending Review status, the update will be made available only to those domains specified in the Testing Domains field. Note that if you are trying to test an update on a plugin that is installed on the same server as the Update Manager plugin, you must still whitelist the domain, otherwise it will not receive the update notification.

Promoting Feedback from your Test Team
1. Navigate to Dashboard > Update Manager > Plugins
2. Click to Edit an endpoint.
3. Add one or more contact methods to the Notifications field.
4. Click to Update the endpoint.
This field accepts multiple email addresses and a single URL, separated by commas. The order is not important. If you supply email addresses, a link will be crafted that prepopulates an email with some basic information. If you supply a URL, it will be used to point the user toward a feedback form, GitHub repo, or wherever. If you supply email(s) and URL, both options will be offered. These links will appear in the test notice that appears in the modal windows.

Pushing Alpha, Beta, and Release Candidate Versions

Semantic versioning is used throughout. You can push updates for alpha, beta, and release candidate versions without any trouble. Let’s say you wanted to run through the basic steps with a version 1.0.0 plugin. You might release a plugin at 1.0.0-alpha. Next, you could bump the version to 1.0.0-beta… and then 1.0.0-rc1, and then 1.0.0-rc2, and then 1.0.0. Each version in that chain succeeds the previous. Here’s the upgrade path, a bit more visually.

1.0.0-alpha < 1.0.0-beta < 1.0.0-rc1 < 1.0.0-rc2 < 1.0.0

Supplemental Note: You can also push sequential updates for a given pre-release (alpha, beta, or RC version). For example, 1.0.0-alpha1 is less than 1.0.0-alpha2 which is less than 1.0.0-alpha3, which is less than…well, you get the idea.

Using Custom Images

You can use your own plugin banner and icon images to improve the end user experience. If you have these images, create an /images/ directory in your plugin and drop them there. They will be automatically discovered and you are free to mix and match any of the following filetypes. If you prefer, you can define your own custom image path; see the filters documentation. If you do not have such images, the default system image will be used for the icon, and your plugin modal windows just won’t have a header graphic. The following are supported:

Normal Images

SVG: icon.svg, banner.svg
PNG: icon-128.png, banner-772x250.png
JPG: icon-128.jpg, banner-772x250.jpg

Retina Images

SVG: icon.svg, banner.svg
PNG: icon-256.png, banner-1544x500.png
JPG: icon-256.jpg, banner-1544x500.jpg

Screenshots

PNG: screenshot-1.png, screenshot-2..png, …
JPG: screenshot-1.jpg, screenshot-2.jpg, …

Note: Screenshots are displayed from lowest to highest, however, they need not be sequentially named. The plugin will find them regardless and will apply the correct caption(s) to the correct image(s).

Theme Integration

To setup a theme to work with the Update Manager, the following general steps are recommended. This page details each of the steps and describes how to use the plugin going forward.
1. Install and activate the Update Manager plugin on your own site.
2. Add the Update Client file to your own theme.
3. Create an update endpoint in the Update Manager.
4. Test the endpoint in a browser.
5. Test the update on an actual site.
6. Publish the endpoint.
Install the Update Manager Plugin
1. Install the Update Manager plugin according to the installation instructions.
2. Navigate to Dashboard > Update Manager > Themes > Add New – this is where you will be managing your theme updates.
Adding the Update Client file to a Theme
1. Copy the UpdateClient.class.php file (from the Update Manager plugin) into your theme’s file structure.
2. Set namespace to a unique value; line 25.
3. Set UPDATE_SERVER to the URL where your Update Manager plugin is installed; line 28.
4. Set UPDATE_TYPE to ‘theme’; line 31.
5. Use require_once('/path/to/UpdateClient.class.php') in your theme’s functions.php file to run the update client.
Creating an Update Endpoint for a Theme
1. Navigate to Dashboard > Update Manager > Themes > Add New
2. Set the Endpoint Identifier for your theme; ie, my-theme-directory-name.
3. Add your Theme Details to the editor; if you have a readme.txt file, you can copy it right in.
4. Optionally, add URLs for any Testing Domains that can receive test updates.
5. Optionally, add contact methods for receiving Notifications of issues.
6. Click Publish to make the update immediately available.
Viewing an Update Endpoint in the Browser

If your update endpoint isn’t working as expected, neither will your update. So, before even testing the update process, it’s a good idea to call up the endpoint in a browser and verify that it looks like valid JSON data. The following steps will allow you to view endpoints in the browser. This is not available for endpoints in Draft status.
1. Navigate to Dashboard > Update Manager > Themes
2. Hover over any of the listed endpoints and click View Endpoint.
Pushing an Update to all Theme Users

When you create a new version of your theme, you’ll need to push it out to your end users. To do this:
1. Navigate to Dashboard > Update Manager > Themes
2. Click to Edit the particular endpoint.
3. Update the Theme Details section to reflect the new version’s details.
4. Click to Update the endpoint.
Pushing an Update to Limited Users for Testing Purposes
1. Navigate to Dashboard > Update Manager > Themes
2. Click to Edit an endpoint.
3. Set the Status to Pending Review.
4. Click to Update the endpoint.
With the theme in Pending Review status, the update will be made available only to those domains specified in the Testing Domains field. Note that if you are trying to test an update on a theme that is installed on the same server as the Update Manager plugin, you must still whitelist the domain, otherwise it will not receive the update notification.

Promoting Feedback from your Test Team
1. Navigate to Dashboard > Update Manager > Themes
2. Click to Edit an endpoint.
3. Add one or more contact methods to the Notifications field.
4. Click to Update the endpoint.
This field accepts multiple email addresses and a single URL, separated by commas. The order is not important. If you supply email addresses, a link will be crafted that prepopulates an email with some basic information. If you supply a URL, it will be used to point the user toward a feedback form, GitHub repo, or wherever. If you supply email(s) and URL, both options will be offered. These links will appear in the test notice that appears in the modal windows.

Pushing Alpha, Beta, and Release Candidate Versions

Semantic versioning is used throughout. You can push updates for alpha, beta, and release candidate versions without any trouble. Let’s say you wanted to run through the basic steps with a version 1.0.0 theme. You might release a theme at 1.0.0-alpha. Next, you could bump the version to 1.0.0-beta… and then 1.0.0-rc1, and then 1.0.0-rc2, and then 1.0.0. Each version in that chain succeeds the previous. Here’s the upgrade path, a bit more visually.

1.0.0-alpha < 1.0.0-beta < 1.0.0-rc1 < 1.0.0-rc2 < 1.0.0

Supplemental Note: You can also push sequential updates for a given pre-release (alpha, beta, or RC version). For example, 1.0.0-alpha1 is less than 1.0.0-alpha2 which is less than 1.0.0-alpha3, which is less than…well, you get the idea.

Transient Inspector

Dashboard > Update Manager > Transients

The Update Manager plugin contains functionality that allows you to view and delete the transients related to plugin and theme updates. This functionality provides a reliable method of forcing an update check, regardless of when the last check took place. Note that this functionality reveals all update data, so, even if a plugin or theme is not integrated with the Update Manager plugin, its update data can be viewed (and deleted) here.

Inspecting Transient Data

Clicking the Plugin Update Data or Theme Update Data tabs will reveal the data stored in your database related to plugin and theme updates. The data is only presented for informational purposes and is not editable on these screens.

Previewing Updates

Clicking the Update Data tab will show plugin and theme update information on the same screen and in a more reader-friendly format.

Delete Plugin Transients

Clicking the text link to delete Plugin transients will delete the data stored in the options table as _site_transient_update_plugins. With this transient data deleted, the system will check for plugin updates on the next page load regardless of when the last update check took place.

Delete Theme Transients

Clicking the text link to delete Theme transients will delete the data stored in the options table as _site_transient_update_themes. With this transient data deleted, the system will check for theme updates on the next page load regardless of when the last update check took place.

Delete Both Transients

Clicking the text link to delete Both transients will delete the data stored in the options table for both _site_transient_update_plugins and _site_transient_update_themes. With this transient data deleted, the system will check for both plugin and theme updates on the next page load regardless of when the last update took place.

Processing Incoming Requests

To work with the data received from incoming requests, the following filter can be added to a utility plugin. This might be used for tracking installations or adding/removing values to/from the request before querying the endpoint for data. This filter accepts 1 argument, $request. Replace {component-type} with either plugin or theme, depending on the type of request you are trying to filter.
```
function some_function_name($request) {

     // Do your processing here.

    // Return the processed request.
    return $request;
}
add_filter('codepotent_update_manager_filter_{component-type}_request', 'some_function_name');
```
Processing Outgoing Responses

When a request is received by the Update Manager plugin, the relevant plugin (or theme) data is assembled and passed back as a response to the calling site. This filter allows final processing of that data before it is returned to the calling site. This filter accepts 2 arguments, data and request and returns the possible-amended data.
```
function some_function_name($data, $request) {

     // Do your processing on $data here.

    // Return the processed data.
    return $data;
}
add_filter('codepotent_update_manager_filter_parsed_component_data', 'some_function_name', 10, 2);
```
Active Installations

The Update Manager plugin does not track or know how many active installations there are of any given plugin. If you are otherwise tracking those numbers, you can filter them into the remote modal windows by adding the following filter to a utility plugin. The filter accepts only uses the first of the two arguments, $number. Replace {identifier} with your plugin identifier, ie, my-plugin-dir/my-plugin-file.php.
```
function some_function_name($number, $identifier) {
    return $number;
}
add_filter('codepotent_update_manager_{identifier}_active_installs', 'some_function_name', 10, 2);
```
Admin Menu

Position To change the admin menu item’s position, this filter can be added to a utility plugin. See also the following table of menu position values.
```
function some_function_name($position) {
    return 22;
}
add_filter('codepotent_update_manager_menu_pos', 'some_function_name');
```
Menu Item Positions 1: Top of menu 2: below Dashboard 5: below Posts 10: below Media 20: below Pages 25: below Comments 60: below first separator 65: below Plugins 70: below Users 75: below Tools 80: below Settings 100: below second separator null: below Comments, in natural order; default

Plugin Images Path & URL

These filters can be used if you already have a particular directory schema under which your plugin’s images are stored. These filters would be used in your own plugin.

Plugin-specific filters

Those new filters prevents plugins from accidentally overwrite other’s path.
```
function new_custom_image_path($path) {
	return plugin_dir_path(__FILE__).'beautifulimages';
}
add_filter('codepotent_update_manager_{plugin-slug}_image_path', 'new_custom_image_path');

function new_custom_image_url($url) {
	return plugin_dir_url(__FILE__).'beautifulimages';
}
add_filter('codepotent_update_manager_{plugin-slug}_image_url', 'new_custom_image_url');
```
Global filters (deprecated since version 2.3.0)

Note that you should always check for the right plugin slug before altering the path, as shown in the examples here. Be sure to replace {plugin-slug} with the slug of your own plugin.
```
function my_custom_image_path($path) {
    if (strpos($path, {plugin-slug}) !== false) {
        $path = '/path/to/your-site/wp-content/plugins/your-plugin-name/assets/images';
    }
    return $path;
}
add_filter('codepotent_update_manager_image_path', 'my_custom_image_path');

function my_custom_image_url($url) {
    if (strpos($path, {plugin-slug}) !== false) {
        $path = 'https://yoursite.com/wp-content/plugins/your-plugin-name/assets/images';
    }
    return $path;
}
add_filter('codepotent_update_manager_image_url', 'my_custom_image_url');
```
Filter Notification

Email Properties If you are using the notification features for endpoints to allow your testers to contact you with feedback, you can filter the default subject and body of the email message with the following filters.
```
function some_function_name($subject) {
    return 'Some custom subject line';
}
add_filter('codepotent_update_manager_notification_email_subject', 'some_function_name');

function some_function_name($body) {
    $body = 'A line followed by two blank lines.'."nn";
    $body .= 'Another line...';
    return $body;
}
add_filter('codepotent_update_manager_notification_email_body', 'some_function_name');
```
Footer Credit

For extension authors, this filter allows for a credit link to be appended to the Code Potent footer text. This filter accepts a single argument, $text, which is an empty string, by default. Note that all HTML is stripped, except for the tag. The URLs can be as long as needed, but, the visible text and links may be truncated at 50 characters. This filter is for adding a credit link, not for marketing text and upsells; misusing this feature will cause it to be removed.
```
function some_function_name($text) {
    return 'Featuring <a href="#">My Extension</a> by <a href="#">Author Name</a>';
}
add_filter('codepotent_update_manager_extension_footer_{your-slug-here}', 'some_function_name');
```
Request body

This filter allows to add fields to the request made by the UpdateClient.class.php. It’s useful for plugin authors that wants to pass data to some Update Manager extension. For example Stats for Update Manager uses it to allow plugin authors to give their users the choice to opt-in or out from their site being counted usage in statistics.
```
function some_function_name($body) {
	if( 'no' === get_option( 'my-slug-usage-statistics' ) ) {
		$body['sfum'] = 'no-log';
	}
	return $body;
}
add_filter('codepotent_update_manager_filter_{your-slug-here}_client_request', 'some_function_name');
```
Manual Installation
- Download the zip file to your local computer
- Login to your ClassicPress website.
- Navigate to Dashboard > Plugins > Add New > Upload Plugin
- Upload the zip file to your site
- Click to Install the plugin
- Click to Activate the plugin
Tag Cloud

azurecurve

Description The plugin integrates with the standard ClassicPress tag cloud, but allows tags to be excluded and easy control of other settings such as ...

Download

More Info
The plugin integrates with the standard ClassicPress tag cloud, but allows tags to be excluded and easy control of other settings such as min and max font sizes, the sort order and number of tags to include.

This plugin is multisite compatible; each site can be set to use network settings or locally defined ones.

Installation
- Download the latest release of the plugin from GitHub.
- Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
- Activate the plugin.
- Configure relevant settings via the configuration page in the admin control panel (azurecurve menu).
- Deploy the Tag Cloud widget.
Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugins languages folder; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

Changelog

Version 1.2.7
- Update plugin header for compatibility with ClasssicPress v2.
Version 1.2.6
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
Version 1.2.5
- Update readme file for compatibility with ClassicPress Director.
Version 1.2.4
- Fix bug with selected tags not displaying correctly in admin settings page.
Version 1.2.3
- Update readme files.
- Update language template.
- Fix bug with azurecurve menu.
Version 1.2.2
- Update azurecurve menu.
- Update readme files.
Version 1.2.1
- Update azurecurve menu and logo.
Version 1.2.0
- Fix plugin action link to use admin_url() function.
- Rewrite option handling so defaults not stored in database on plugin initialisation.
- Add plugin icon and banner.
- Update azurecurve plugin menu.
Version 1.1.4
- Fix bug with setting of default options.
- Fix bug with plugin menu.
- Update plugin menu css.
Version 1.1.3
- Rewrite default option creation function to resolve several bugs.
- Upgrade azurecurve plugin to store available plugins in options.
Version 1.1.2
- Update Update Manager class to v2.0.0.
- Update action link.
- Update azurecurve menu icon with compressed image.
Version 1.1.1
- Fix bug with incorrect language load text domain.
Version 1.1.0
- Add integration with Update Manager for automatic updates.
- Fix issue with display of azurecurve menu.
- Change settings page heading.
- Add load_plugin_textdomain to handle translations.
Version 1.0.1
- Update azurecurve menu for easier maintenance.
- Move require of azurecurve menu below security check.
Version 1.0.0
- Initial release for ClassicPress forked from azurecurve Tag Cloud WordPress Plugin.
Other Notes

azurecurve was one of the first plugin developers to start developing for ClassicPress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The other plugins available from azurecurve are:
- Add Open Graph Tags – details / download
- Add Twitter Cards – details / download
- Avatars – details / download
- BBCode – details / download
- Breadcrumbs – details / download
- Call-out Boxes – details / download
- Check Plugin Status – details / download
- Code – details / download
- Comment Validator – details / download
- Conditional Links – details / download
- Contact Forms – details / download
- Disable FLoC – details / download
- Display After Post Content – details / download
- Estimated Read Time – details / download
- Events – details / download
- Filtered Categories – details / download
- Flags – details / download
- Floating Featured Image – details / download
- Gallery From Folder – [details](https://development.azurecurve.co.uk/classicpress-plugi
SMTP

azurecurve

Description Simple Mail Transport Protocol (SMTP) plugin will intercept the standard wp_mail and send emails via an SMTP server using PHPMAILER. When ...

Download

More Info
Simple Mail Transport Protocol (SMTP) plugin will intercept the standard wp_mail and send emails via an SMTP server using PHPMAILER.

When activating for the first time, settings can be imported from Easy WP SMTP.

This plugin is multisite compatible; each site will need settings to be configured in the admin dashboard.

Installation
- Download the latest release of the plugin from GitHub.
- Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
- Activate the plugin.
- Configure relevant settings via the configuration page in the admin control panel (azurecurve menu).
Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugins languages folder and can also be downloaded from the plugin page on azurecurve|Development; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

Changelog

Version 2.1.6
- Update plugin header for compatibility with ClasssicPress v2.
Version 2.1.5
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
Version 2.1.4
- Fix developer name variable bug.
Version 2.1.3
- Update readme file for compatibility with ClassicPress Directory.
Version 2.1.2
- Fix Update Manager View Details link (contributed by xxsimoxx).
Version 2.1.1
- Fix bug with PHP mailer exception in send_test_email function (contributed by xxsimoxx).
Version 2.1.0
- Fix incorrect update server path; plugin will need to be manually updated if 2.0.0 or 2.0.1 was installed.
Version 2.0.1
- Fix issue with namespace in Update Manager class.
- Standardise handling of developer name and url.
- Update language template.
- Update instructions tab.
Version 2.0.0
- Refactor code to improve maintainability, to use a namespace and improve security.
- Update language template.
- Update Update Manager to version 2.4.3.
Version 1.4.3
- Update readme files.
- Update language template.
- Remove unused style related functions.
- Fix bug with azurecurve menu.
- Fix issue with PHPMailer caused by ClassicPress v1.4.0 release (contributed by xxsimoxx).
Version 1.4.2
- Fix bug with php notice when sending test email.
- Fix missing settings page title.
Version 1.4.1
- Fix bug with azurecurve menu.
Version 1.4.0
- Only replace from email with that from settings when from is set to admin email.
- Improve sanitization and escaping.
- Improve security by using wp_safe_redirect.
- Load Admin Dashboard jQuery in footer.
Version 1.3.1
- Update azurecurve menu and logo.
Version 1.3.0
- Remove debug erroneously included.
Version 1.2.0
- Add import of Easy WP SMTP settings on first activation (contributed by xxsimoxx).
Version 1.1.0
- Fix bad TLS cert in plain text auth (contributed by xxsimoxx).
- Option to allow no authentication when username not set.
- Add uninstall method.
Version 1.0.0
- Initial release.
Other Notes

azurecurve was one of the first plugin developers to start developing for Classicpress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The other plugins available from azurecurve are:
- Add Open Graph Tags – details / download
- Add Twitter Cards – details / download
- Avatars – details / download
- BBCode – details / download
- Breadcrumbs – details / download
- Call-out Boxes – details / download
- Check Plugin Status – details / download
- Code – details / download
- Comment Validator – details / download
- Conditional Links – details / download
- Contact Forms – details / download
- Disable FLoC – details / download
- Display After Post Content – details / download
- Estimated Read Time – details / download
- Events – details / download
- Filtered Categories – details / [download](https://github.com/azur
Check Plugin Status

azurecurve

Description This plugin allows you to check the status of plugins on your site: Are they in the WordPress Repository. Do they use a 3rd party update ...

Download

More Info
This plugin allows you to check the status of plugins on your site:
- Are they in the WordPress Repository.
- Do they use a 3rd party update mechanism such as Update Manager from Code Potent
- Are they supported on ClassicPress or on WordPress 5+.
- Are they up-to-date.
Exception handling has been built in for Contact Form 7 and Google Sitemap Generator which report a different slug in the API to the slug on the WordPress Repository.

Installation
- Download the latest release of the plugin from GitHub.
- Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
- Activate the plugin.
- Configure settings.
Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugins languages folder; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

Changelog

Version 1.1.3
- Update readme file for compatibility with ClassicPress Directory.
Version 1.1.2
- Update readme files.
- Update language template.
- Fix bug with azurecurve menu.
Version 1.1.1
- Update azurecurve menu.
- Update readme files.
Version 1.1.0
- Update azurecurve logo.
- Update translations to escape strings.
Version 1.0.1
- Fix handling of unset variables.
Version 1.0.0
- Initial release.
Other Notes

azurecurve was one of the first plugin developers to start developing for ClassicPress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The other plugins available from azurecurve are:
- Add Open Graph Tags – details / download
- Add Twitter Cards – details / download
- Avatars – details / download
- BBCode – details / download
- Breadcrumbs – details / download
- Call-out Boxes – details / download
- Code – details / download
- Comment Validator – details / download
- Conditional Links – details / download
- Contact Forms – details / download
- Disable FLoC – details / download
- Display After Post Content – details / download
- Estimated Read Time – details / download
- Events – details / download
- Filtered Categories – details / download
- Flags – details / download
- Floating Featured Image – details / download
- From Twitter – details / download
- Gallery From Folder – details / download
- Get GitHub File – details / download
- Icons – details / download
- Images – details / download
- Insult Generator – details / download
- Load Admin CSS – details / download
- Loop Injection – details / download
- Maintena
Snippets

azurecurve

Description Allows snippets of HTML, PHP, JavaScript and CSS to be created; an alternative to using a functions.php file or adding styles to a child t ...

Download

More Info
Allows snippets of HTML, PHP, JavaScript and CSS to be created; an alternative to using a functions.php file or adding styles to a child theme.

Snippets can be used to create re-usable HTML or JavaScript snippets or to create PHP to add_actions or add_filters without needing to add them to the functions.php file or create a plugin.

The following types of snippet can be created:
- HTML – can be loaded using the shortcode.
- Internal CSS – automatically added as internal stylesheet.
- CSS Stylesheet – automatically loaded.
- Internal JavaScript – automatically added as internal JavaScript.
- JavaScript File – automatically loaded.
- PHP – can be loaded using the shortcode (advanced mode only).
- PHP File – automatically loaded (advanced mode only).
- PHP File (Header) – automatically loaded in wp_head; allows use of add_action, add_filter and add_shortcode (advanced mode only).
Shortcode usage is either [snippet id=1013] (where the supplied id value is a snippet post_id) or [snippet slug='hello-world'].

All snippets are loaded only on the site frontend; this protects the admin dashboard from white screen errors caused by badly formed PHP; only enable PHP if you really know what you’re doing.

Installation
- Download the latest release of the plugin from GitHub.
- Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
- Activate the plugin.
- Configure relevant settings via the settings page in the admin control panel (azurecurve menu).
Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugins languages folder; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

Changelog

Version 2.2.2
- Update plugin header for compatibility with ClasssicPress v2.
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
Version 2.2.0
- Add script type of PHP Header.
Version 2.1.5
- Update readme file for compatibility with ClassicPress Directory.
Version 2.1.4
- Fix bug with instructions on settings page not displaying correctly.
Version 2.1.3
- Fix bug to prevent error if snippet selected in shortcode does not exist.
Version 2.1.2
- Update readme files.
- Update language template.
- Fix bug with azurecurve menu.
Version 2.1.1
- Update azurecurve menu.
- Update readme files.
Version 2.1.0
- Remove debug code.
- Change priority of loading css/php to 10.
Version 2.0.2
- Fix bug with load of PHP files.
Version 2.0.1
- Fix bug with load of snippet folder option.
Version 2.0.0
- Add missing snippet url setting; this is a breaking change requiring settings to be updated.
- Add uninstall.
- Update translations to escape strings.
- Update azurecurve menu and logo.
Version 1.4.0
- Set priority on enqueue of CSS and JavaScript.
Version 1.3.0
- Replace admin menu icon with svg.
Version 1.2.0
- Add advanced mode toggle; until enabled PHP/JavaScript snippets and files are unavailable for creation, but existing ones will continue to function.
Version 1.1.1
- Fix bug when deleting post.
Version 1.1.0
- Amend to ensure snippets are not visible or accessible from the front end.
- Update azurecurve menu.
- Fix bug in azurecurve menu.
Version 1.0.1
- Fix bug with internal CSS and JavaScript not loading correctly.
Version 1.0.0
- Initial release.
Other Notes

azurecurve was one of the first plugin developers to start developing for ClassicPress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The other plugins available from azurecurve are:
- Add Open Graph Tags – details / download
- Add Twitter Cards – details / download
- Avatars – details / download
- BBCode – details / download
- Breadcrumbs – details / download
- Call-out Boxes – details / download
- Check Plugin Status – details / download
- Code – details / download
- Comment Validator – details / download
- Conditional Links – details / download
- Contact Forms – details / download
- Disable FLoC – details / download
- Display After Post Content – details / [download](https://github.com/azurecurve/azrcrv-displa
Maintenance Mode

azurecurve

Description Enable maintenance mode to disable the front-end of your ClassicPress site for non-administrators. Users will only see the configured mess ...

Download

More Info
Enable maintenance mode to disable the front-end of your ClassicPress site for non-administrators.

Users will only see the configured message; administrators will have full access to the site, but a prominent configurable warning that maintenance mode is enabled will be displayed at the top of every page.

This plugin is multisite compatible with each site having its own settings.

Installation
- Download the latest release of the plugin from GitHub.
- Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
- Activate the plugin.
- Configure relevant settings via the configuration page in the admin control panel (azurecurve menu).
Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugins languages folder; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

Changelog

Version 2.0.3
- Update plugin header for compatibility with ClasssicPress v2.
Version 2.0.2
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
Version 2.0.1
- Fix version issue.
Version 2.0.0
- Refactor code to use namespace, improve security and improve maintainability.
- Update language file.
- Update readme txt and md files.
- Update Update Manager to version 2.4.3.
- Update to only enqueue frontend styes if maintenance mode enabled.
Version 1.4.0
- Add option to disable admin banner.
- Change so empty title or detail of banner isn’t displayed.
- Update language template.
Version 1.3.1
- Update readme files.
- Update language template.
- Fix bug with azurecurve menu.
Version 1.3.0
- Fix bug with save of settings.
- Change language domain to avoid possible conflicts.
- Restructure settings page.
- Improve handling of output.
Version 1.2.1
- Update azurecurve menu.
- Update readme files.
Version 1.2.0
- Add uninstall.
- Update translations to escape strings.
Version 1.1.0
- Change Enabled default to off.
- Update azurecurve menu.
Version 1.0.1
- Update plugin images.
- Fix bug with Download link.
Version 1.0.0
- Initial release.
Other Notes

azurecurve was one of the first plugin developers to start developing for Classicpress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The other plugins available from azurecurve are:
- Add Open Graph Tags – details / download
- Add Twitter Cards – details / download
- Avatars – details / download
- BBCode – details / download
- Breadcrumbs – details / download
- Call-out Boxes – details / download
- Check Plugin Status – details / download
- Code – details / download
- Comment Validator – details / download
- Conditional Links – details / download
- Contact Forms – details / download
- Disable FLoC – details / download
- Display After Post Content – details / download
- Estimated Read Time – details / download
- Events – details / download
- Filtered Categories – details / download
- Flags – details / download
- Floating Featured Image – details / download
- Gallery From Folder – details / download
- Get GitHub File – details / download
- Icons – details / download
- Images – details / [download](https:
Unwrap Shortlinks

Kelson Vibber

Unwrap Shortlinks Stable tag: 0.3.4 Tags: urls, links, classicpress Tested up to: 6.6 Contributors: Kelson License: GPLv2 or later Follows shortened l ...

Download

More Info
Stable tag: 0.3.4
Tags: urls, links, classicpress
Tested up to: 6.6
Contributors: Kelson
License: GPLv2 or later

Follows shortened links (t.co, bit.ly, etc) and WordPress’ ?p=123-style links, and expands them so that your blog post will point directly to the destination.

Description

Automatically expands URLs at the following known link shorteners when you save a post:
- t.co
- bit.ly
- ow.ly
- j.mp
- is.gd
- trib.al
- buff.ly
- wp.me
- tmblr.co
- goo.gl
- dlvr.it
- fb.me
- qr.ae
- aka.ms
- tinyurl.com
Installation

Install the plugin and activate it. The next time you paste a supported short URL into a post, it will be updated when the post is saved.

Frequently Asked Questions

What if the destination redirects to another link?

If the destination is another known URL shortener (ex. t.co pointing to bit.ly pointing to wp.me pointing to a blog post), it’ll keep going up to 8 levels (to avoid infinite loops!) or until it gets a URL that isn’t on the list.

How do I add a shortener to the list?

It’s not supported yet, but I plan on adding an options page for it.

I’m running on a local server and this doesn’t do anything!

Most likely your system is configured to block your local webserver
from making outgoing connections. This is a sensible default for security!
Depending on your system, it may be blocked by a local or network firewall.
If you’re running Fedora Workstation with SELinux (like I am), this will enable it:
```
sudo setsebool -P httpd_can_network_connect true
```
Thanks to igienger’s post on the WordPress support forums!

What about compatibility?

It should work going back to the classic editor and forward to the block editor. It even works on ClassicPress.

Changelog

[0.3.4] – 2024-07-07
- Also follow WordPress’ ?p=123 links if they redirect to a permalink.
- tinyurl.com is accepting curl requests again, so I’ve added it back to the list.
[0.3.3] – 2023-07-22
- tinyurl.com is screening requests using Cloudflare, and a simple curl request is no longer allowed through. Removing it from the list.
[0.3.2] – 2022-10-29
- Tested up through 6.1, clean up headers, no functional changes.
[0.3.1] – 2022-09-01
- Update headers for new ClassicPress plugin directory. No changes affecting WordPress
[0.3.0] – 2022-06-23
- Follow link trails, add aka.ms.
[0.2.4] – 2022-06-13
- Fix bugs with plaintext URLs at the end of a block.
[0.2.3] – 2022-06-10
- Fix bugs with tinyurl.com and URLs inside HTML links. (Plaintext URLs were working fine.)
[0.2.2] – 2022-01-29
- Initial release based on the code I’ve been running locally for years, plus changes requested by the WordPress plugin review team.
Source on Codeberg.
Mirror on GitHub.
Plugin page at WordPress.
Plugin page at ClassicPress.

(c) 2016-2024 Kelson Vibber
Subscribe2 for ClassicPress

Matt Robinson

Subscribe2 provides a comprehensive subscription management and email notification system for WordPress blogs that sends email notificatio ...

Download

More Info
= Summary =

Subscribe2 provides a comprehensive subscription management and email notification system for WordPress blogs that sends email notifications to a list of subscribers when you publish new content to your blog.

= Email =

Email notifications can be sent on a per-post basis or periodically in a Digest email. Additionally, certain categories can be excluded from inclusion in the notification and posts can be excluded on an individual basis by setting a custom field.

= Subscriptions =

Subscription requests allows users to publicly subscribe (Public Subscribers) by submitting their email address in an easy to use form or to register with your blog (Registered Users) which enables greater flexibility over the email content for per-post notifications for the subscriber. Admins are given control over the presentation of the email notifications, can bulk manage subscriptions for users and manually send email notices to subscribers.

The format of the email can also be customised for per-post notifications, Subscribe2 can generate emails for each of the following formats:
- plaintext excerpt.
- plaintext full post (Registered Users only).
- HTML excerpt (Registered Users only).
- HTML full post (Registered Users only).
If you want to send full content HTML emails to Public Subscribers too then upgrade to Subscribe2 HTML.

Installation

= AUTOMATIC INSTALLATION =
1. Log in to your ClassicPress site and visit the Plugins page.
2. Click the Add New button and select the ‘Upload’ method.
3. Upload the Subscribe2-for-cp.zip file from your computer and click the ‘Install Now’ button. Then activate the plugin.
4. Visit the “Subscribe2 -> Settings” menu and configure the options to taste, including the email template.
5. Visit the “Subscribe2 -> Subscribers” menu and manually subscribe people as you see fit with due consideration to privacy.
6. Create a Page to display the subscription form. When creating the page, you may click the “S2” button on the QuickBar to automatically insert the Subscribe2 token. Or, if you prefer, you may manually insert the Subscribe2 shortcode or token: [subscribe2] or the HTML invisible  Ensure the token is on a line by itself and that it has a blank line above and below.
  This token will automatically be replaced by dynamic subscription information and will display all forms and messages as necessary.
7. In the WordPress “Settings” area for Subscribe2 select the page name in the “Appearance” section that of the WordPress page created in step 7.
= MANUAL INSTALLATION =
1. Using FTP software copy the entire /subscribe2-for-cp/ directory into your /wp-content/plugins/ directory.
2. Log in to your WordPress blog and visit the Plugins page.
3. Activate the Subscribe2 HTML plugin.
4. Complete step 4 and onwards in the instruction list above.
Frequently Asked Questions

Visit FAQ site

Changelog

See complete changelog installed in the same folder as this readme.
Nearby

azurecurve

Description Nearby creates a table of nearby locations (pages) based on GPS co-ordinates. Nearby integrates with the following azurecurve plugins: F ...

Download

More Info
Nearby creates a table of nearby locations (pages) based on GPS co-ordinates.

Nearby integrates with the following azurecurve plugins:
- Flags from azurecurve allows a location to be set for a page; this will display the location flag next to the location name in the table of nearby attractions.
- Icons from azurecurve allows an icon to be displayed next to a nearby location which has an entry on a timeline (requires integration with Timelines to be enabled).
- Timelines from azurecurve allows a character (such as *) to be displayed next to a nearby location which has an entry on a timeline.
- Toggle Show/Hide from azurecurve allows the table of nearby locations to be enclosed with a toggle.
Apply the [nearby] shortcode to a page with co-ordinates and nearby locations (pages with co-ordinates), based on the settings, will be displayed in a table.

The shortcode accepts two parameters:
- type to limit nearby attractions (multiple types can be provided in comma separated string).
- title to override the default toggle title.
Example shortcode usage:
```
[nearby type="Distilleries" title="Nearby Distilleries"]
```
Examples of this plugin in action:
- coppr|Distilleries To Visit
- DarkNexus|Tourist Attractions
This plugin is multisite compatible; each site will need settings to be configured in the admin dashboard.

Installation
- Download the latest release of the plugin from GitHub.
- Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
- Activate the plugin.
- Configure relevant settings via the configuration page in the admin control panel (azurecurve menu).
Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugins languages folder and can also be downloaded from the plugin page on https://development.azurecurve.co.uk; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

Changelog

Version 3.0.4
- Update plugin header for compatibility with ClasssicPress v2.
Version 3.0.3
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
Version 3.0.2
- Update readme file for compatibility with ClassicPress Directory.
Version 3.0.1
- Update readme files.
- Update language template.
- Fix bug with azurecurve menu.
Version 3.0.0
- Migrate type, country and co-ordinates data from cp_postmeta to custom table.
- Change text domain to ensure it is unique.
- Update to only load admin css when on plugin settings page.
- Update readme.txt and readme.md.
- Update azurecurve menu.
Version 2.5.0
- Add uninstall.
- Update azurecurve menu and logo.
Version 2.4.4
- Fix bug with version number.
Version 2.4.3
- Fix bug with call to undefined function on settings page.
- Update azurecurve menu.
Version 2.4.2
- Fix bug with timeline integration not returning correct result.
- Update azurecurve menu.
- Replace azurecurve menu icon with svg.
Version 2.4.1
- Fix bug with available icons not listing when Icons integration enabled.
Version 2.4.0
- Add types; allows attractions to have a type set.
- Add type parameter to shortcode allowing included attractions to be limited.
- Add title parameter to shortcode allowing toggle title to be amended.
- Add plugin links to Integrate settings tab.
- Fix bug with display of selected country in page meta box.
- Fix table display bug when no nearby attractions.
Version 2.3.0
- Amend call to get country flag.
- Add tabs to admin settings page.
- Integrate with Icons for icon to use as timeline signifier.
Version 2.2.0
- Fix plugin action link to use admin_url() function.
- Rewrite option handling so defaults not stored in database on plugin initialisation.
- Update azurecurve plugin menu.
- Amend to only load css when shortcode on page.
Version 2.1.0
- Fix bug in update manager namespace declaration.
- Add integration with Timelines from azurecurve.
- Add plugin icon and banner.
Version 2.0.0
- Correct typo in maximum-location option which was maximim-locations; settings will need to be updated and saved once update applied.
Version 1.2.0
- Add 16 point compass with option to toggle from 32 point compass.
Version 1.1.0
- Add direction for nearby locations using 32 compass points.
- Update CSS to provide more control.
Version 1.0.0
- Initial release.
Other Notes

azurecurve was one of the first plugin developers to start developing for ClassicPress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The other plugins available from azurecurve are:
- Add Open Graph Tags – details / download
- Add Twitter Cards – details / download
- Avatars – details / download
- BBCode – details / [download](https://github.com/azurecurve/azrcrv-bb
Remove Revisions

azurecurve

Description While revisions can be disabled or limited in number with settings in the wp-config file, there is no way to allow for the deletion of rev ...

Download

More Info
While revisions can be disabled or limited in number with settings in the wp-config file, there is no way to allow for the deletion of revisions over a certain ago. That is what this plugin allows you to do.

In the options you can set the number of months after which revisions are to be deleted. They can then be deleted at the click of a button or via a cron job running on a daily schedule.

The options also allow you to select the post types (both standard and custom) which can have revisions removed.

Removal of revisions is done using the ClassicPress function to ensure they are done correctly.

This plugin is multisite compatible, with options set on a per site basis.

Installation
- Download the latest release of the plugin from GitHub.
- Upload the entire zip file using the Plugins upload function in your ClassicPress admin panel.
- Activate the plugin.
- Configure relevant settings via the configuration page in the admin control panel (azurecurve menu).
Frequently Asked Questions

Can I translate this plugin?

Yes, the .pot file is in the plugins languages folder and can also be downloaded from the plugin page on https://development.azurecurve.co.uk; if you do translate this plugin, please sent the .po and .mo files to [email protected] for inclusion in the next version (full credit will be given).

Is this plugin compatible with both WordPress and ClassicPress?

This plugin is developed for ClassicPress, but will likely work on WordPress.

Changelog

Version 1.2.5
- Update plugin header for compatibility with ClasssicPress v2.
Version 1.2.4
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
Version 1.2.3
- Update readme file for compatibility with ClassicPress Directory.
Version 1.2.2
- Fix Update Manager View Details link (contributed by xxsimoxx).
- Fix bug with display of plugin action link.
Version 1.2.1
- Fix missing constants.
Version 1.2.0
- Update plugin list.
- Remove revisions from list of post types which are eligible for having revisions removed.
- Remove jQuery which should not have been included.
- Fix incorrect update server path; **plugin will need to be manually updated if 1.1.0 was installed.
Version 1.1.0
- Refactor code to improve maintainability.
- Update language file.
- Update Update Manager to version 2.4.3.
- Add option of selecting range of days/months (was previously only months).
Version 1.0.5
- Update readme files.
- Update language template.
- Fix bug with azurecurve menu.
Version 1.0.4
- Update azurecurve menu.
- Update readme files.
Version 1.0.3
- Fix bug with plugin icon and banner not displaying.
Version 1.0.2
- Fix version number issue.
Version 1.0.1
- Fix incorrect text domain.
Version 1.0.0
- Initial release.
Other Notes

azurecurve was one of the first plugin developers to start developing for ClassicPress; all plugins are available from azurecurve Development and are integrated with the Update Manager plugin for fully integrated, no hassle, updates.

The other plugins available from azurecurve are:
- Add Open Graph Tags – details / download
- Add Twitter Cards – details / download
- Avatars – details / download
- BBCode – details / download
- Breadcrumbs – details / download
- Call-out Boxes – details / download
- Check Plugin Status – details / download
- Code – details / download
- Comment Validator – details / download
- Conditional Links – details / download
- Contact Forms – details / download
- Disable FLoC – details / download
- Display After Post Content – details / download
- Estimated Read Time – details / download
- Events – details / download
- Filtered Categories – details / download
- Flags – details / download
- Floating Featured Image – details / download
- Gallery From Folder – details / [download](https://github.com/azurecurve/azrcrv-gallery-from-fol
Head Cleaner

Simone Fioravanti

Removing certain tags from the ClassicPress head section is a great way to enhance site performance. Why load assets for emoji if your site doesn't ...

Download

More Info