Plugins

BBCode

azurecurve

Description Allows users to use standard bbcodes in posts and pages in place of HTML tags. The following bbcodes can be used: Bold: [b]bold[/b] It ...

Download

More Info
Allows users to use standard bbcodes in posts and pages in place of HTML tags.

The following bbcodes can be used:
```
	Bold:
		[b]bold[/b]
	Italic:
		[i]italics[/i]
	Underline:
		[u]underline[/u]
	Center Text:
		[center]centered text[/center]
	Strike:
		[strike]strike[/strike]
	Quote:
		[quote]quote[/quote]
	Color:
		[color=blue]color[/color]
	Font size:
		[size=12pt]12pt font size[/size]
		[size=1.2em]1.2em font size[/size]
		[size=12px]12px font size[/size]
	Image:
		[img]https://docs.classicpress.net/wp-content/classicpress/logos/icon-gradient-600.png[/img]
		[img=ClassicPress logo]https://docs.classicpress.net/wp-content/classicpress/logos/icon-gradient-600.png[/img]
	URL:
		[url]https://www.classicpress.net/[/url]
		[url=https://www.classicpress.net/]ClassicPress[/url]
		[link]https://www.classicpress.net/[/link]
		[link=https://www.classicpress.net/]ClassicPress[/link]
	Ordered lists:
		[ol]ordered list[/ol]
	Unordered lists:
		[ul]unordered list[/ul]
	List items:
		[li]list item[/li]
	Table:
		[table][/table]
	Table Row:
		[tr][/tr]
	Table Header:
		[th][/th]
	Table data (cell):
		[td][/td]
	Code:
		[code]function azc_bbcode_bold($atts, $content = null){ return "".do_shortcode($content).""; }[/code]
```
Allows users to use standard bbcodes in posts and pages; Shortcodes in Comments can be used to allow bbcodes in comments and Shortcodes in Widgets can allow them in widgets.

This plugin is multisite compatible.

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.
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.1.5
- Update plugin header for compatibility with ClasssicPress v2.
Version 2.1.4
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
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 missing constants.
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 bug in namespace of Update Client.
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.
Version 1.3.2
- Update azurecurve menu.
- Update readme files.
Version 1.3.1
- Update azurecurve menu and logo.
Version 1.3.0
- Fix problem with load of plugin icon and banner.
- Amend to only load css when shortcode on page.
Version 1.2.0
- Fix plugin action link to use admin_url() function.
- Add plugin icon and banner.
- Update azurecurve plugin menu.
Version 1.1.4
- Fix bug with plugin menu.
- Update plugin menu css.
Version 1.1.3
- 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.
- Localization fixes.
Version 1.0.0
- Initial release for ClassicPress forked from azurecurve BBCode 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
- 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](https://development.azurecurve.co.uk/classicpress-plugins/contact-form
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
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
PHP Error Log Viewer

Simone Fioravanti

The PHP Error Log Viewer plugin for ClassicPress brings your error log straight into your dashboard. Color-coding helps you to quickly scan even the l ...

Download

More Info
The PHP Error Log Viewer plugin for ClassicPress brings your error log straight into your dashboard. Color-coding helps you to quickly scan even the longest of error logs. Or, just filter out the errors you don’t want to see. No more wall-of-text error messages – this plugin turns your PHP error log into an incredibly useful display.

Fast, Lightweight, and User-Friendly

There are lots of debugging plugins out there – debugging suites, really. This plugin isn’t intended to become one of them. The PHP Error Log Viewer plugin handles a very specific task and that is to display the PHP error log in a user-friendly manner than can be easily filtered, styled, sorted, preserved, or purged.

More Debugging, Less Clicking

If you have grown tired of flipping back and forth between screens/browsers/apps/whatever to check and recheck your PHP error log as you’re writing code, this will be incredibly handy for you. There’s a link to the error log within reach at all times and it doesn’t require any special configuration.

Viewing the Error Log

Click the PHP Errors menu item in your admin bar. Hover the menu item momentarily and it will reveal your current PHP version. Alternatively, you can access the error log by navigating to Dashboard > Tools > PHP Error Log.

Filtering the Error Log

The checkboxes across the top of the display allow you to show and hide each of the various types of errors: Deprecated, Notice, Warning, Error, and Other. There are also checkboxes to show and hide the time/date, stack traces, and to sort the error log in reverse. Tick your preferred boxes and click the Apply Filters button to update the display.

Refreshing the Error Log

When viewing the error log, you will find a button to Refresh Error Log at the right side of the page. Clicking this button has the same effect as clicking your browser’s refresh button. The error log will be re-read and displayed fresh.

Purging the Error Log

When viewing the error log, you will find a button to Purge Error Log at the right side of the page. Clicking this button will purge all messages from the error log. A confirmation dialog prevents accidental deletion. If your error log is not writable by the PHP process, you will not see this button.

Purging the Error Log via AJAX

In the admin bar, you will find a link PHP Errors which, when hovered, will expose a link to Purge Error Log. Clicking this button will purge all messages from the error log without redirecting you away from the current page. A confirmation dialog prevents accidental deletion. If your error log is not writable by the PHP process, you will not see this link.

Manually Triggering Errors

As of version 2.2.0, there is a function that allows you to manually trigger user-level notices, warnings, or errors and have them neatly displayed in the error log. Here is an example of creating your own wrapper function for added convenience.
```
/**
     * Creating your own error logging wrapper function
     *
     * This example shows how you might integrate the logging function into your own
     * utility plugin.
     *
     * @param mixed $data   Pass in a string, integer, array, object, etc.
     * @param str $level    Must be notice, warning, or error.
     * @param int $file     Use __FILE__ constant to include filename.
     * @param bool $line    Use __LINE__ constant to include line number.
     */
    function log_data($data, $level='notice', $file=false, $line=false) {

    	// If error log plugin is active and the needed function exists...
    	if (function_exists('codepotent_php_error_log_viewer_log')) {
    		return codepotent_php_error_log_viewer_log($data, $level, $file, $line);
    	}

    	// Or, if error log plugin is inactive, you can include just the needed function...
    	if (file_exists($file = plugin_dir_path(__DIR__).'codepotent-php-error-log-viewer/includes/functions.php')) {
    		require_once($file);
    		return codepotent_php_error_log_viewer_log($data, $level, $file, $line);
    	}

    	// If the error log plugin just doesn't exist, there's a fallback.
    	trigger_error(print_r($data, true), E_USER_WARNING);

    }

    // Elsewhere, send data to the log like this:
    $data = 'whatever type of data';
    log_data($data, 'notice', __FILE__, __LINE__);
```
Display Options

The checkboxes at the top of the error log display allow you to choose which types of error messages you want to see. Check any of the boxes and click the Apply Filter button to update the display.
- Date/Time
  Check this box to show dates, times, and other meta data.
- Notice
  Check this box to show non-critical PHP notices.
- Warning
  Check this box to show non-critical PHP warnings.
- Error
  Check this box to show critical PHP errors.
- Other
  Check this box to show any other errors that didn’t meet the above criteria.
- Show Stack Traces
  Check this box to show stack traces for critical errors. Note that not all critical errors will generate a stack trace.
- Reverse Sort
  Check this box to display the error log with latest errors at the top.
Primary Alert Bubble This filter allows you to hide or redesign the primary (red) alert bubble in the admin bar. This filter accepts a single argument, the markup of the primary alert bubble.
```
function yourprefix_hide_primary_alert($alert) {
    return '';
}
add_filter('codepotent_php_errror_log_viewer_primary_alert', 'yourprefix_hide_primary_alert');
```
Secondary Alert Bubble This filter will allow you to hide or redesign the secondary (gray) alert bubble in the admin bar. This filter accepts a single argument, the markup of the secondary alert bubble.
```
function yourprefix_hide_secondary_alert($alert) {
    return '';
}
add_filter('codepotent_php_errror_log_viewer_primary_alert', 'yourprefix_hide_secondary_alert');
```
Add Content Before Legend

In cases where you need to insert some contextual information, either of the following filters can be used to place the content before or after the legend. These filters receive an empty string as an argument.
```
function yourprefix_before_error_log_legend($markup) {
    $markup = 'This content appears before the legend.';
    return $markup;
}
add_filter('codepotent_php_errror_log_viewer_before_legend', 'yourprefix_before_error_log_legend');
```
Add Content After Legend

Identical to the filter above, except this filter places your contextual content below the legend.
```
function yourprefix_after_error_log_legend($markup) {
    $markup = 'This content appears after the legend.';
    return $markup;
}
add_filter('codepotent_php_errror_log_viewer_after_legend', 'yourprefix_after_error_log_legend');
```
Using Custom Error Colors

To override the color-coding for the error messages and legend, copy the following styles into your theme’s style.css file and make your changes there.
```
/* Deprecated code. */
#codepotent-php-error-log-viewer .php-deprecated, 
.codepotent-php-error-log-viewer-legend-box.item-php-deprecated {
	border-left:10px solid #847545;
	}
/* Notices. */
#codepotent-php-error-log-viewer .php-notice,
.codepotent-php-error-log-viewer-legend-box.item-php-notice {
	border-left:10px solid #ccc;
	}
/* Warnings. */
#codepotent-php-error-log-viewer .php-warning,
.codepotent-php-error-log-viewer-legend-box.item-php-warning {
	border-left:10px solid #ffee58;
	}
/* Errors. */
#codepotent-php-error-log-viewer .php-error,
.codepotent-php-error-log-viewer-legend-box.item-php-error {
	border-left:10px solid #e53935;
	}
/* Stack traces. */
#codepotent-php-error-log-viewer .php-stack-trace-title,
#codepotent-php-error-log-viewer .php-stack-trace-step,
#codepotent-php-error-log-viewer .php-stack-trace-origin,
.codepotent-php-error-log-viewer-legend-box.item-php-stack-trace-title {
	border-left:10px solid #ef9a9a;
	}
/* Any other messages. */
#codepotent-php-error-log-viewer .php-other,
.codepotent-php-error-log-viewer-legend-box.item-php-other {
	border-left:10px solid #00bcd4;
	}
```
Enriched Editor

Simone Fioravanti

Enriched Editor The Enriched Editor plugin adds lots of additional options to the ClassicPress visual editor. This plugin is a fork of TinyMCE Advan ...

Download

More Info
The Enriched Editor plugin adds lots of additional options to the ClassicPress visual editor. This plugin is a fork of TinyMCE Advanced for WordPress and contains no Gutenberg code.

Pre-Installation

If you already have TinyMCE Advanced or WYWIWYG Advanced installed, you will need to deactivate and delete before installing Enriched Editor. If you want to preserve your current editor settings, you can export them to a text file before deleting the current plugin. You can then import those settings back into Enriched Editor after you get it installed.

Editor Options
- Enable Editor for Primary Screens
  Enable the Enriched Editor for primary editing screens, including those for posts, pages, and custom post types.
- Enable Editor for Secondary Areas
  Enable the Enriched Editor for secondary editing areas, including those for text widgets and other textarea inputs.
- Enable Editor for Public Use
  Enable the Enriched Editor for public use, such as in user comments and other textarea inputs.
- Advanced Menu
  Enable the advanced menu (File, Edit, Insert, View, Format, Table, and Tools) for the first row.
- Enhanced Lists
  Enable advanced list options, including upper-case, lower-case, disk, square, circle, etc.
- Right-Click
  Enable link insertion by right-clicking the editor.
- Simplified Links
  Use a simplified dialog for creating links.
- Font Sizing
  Use pixels (instead of points) for font sizes.
- Preserve Paragraphs
  Preserve <p> and <br> tags without replacing them.
- Custom Style Menu
  Pull custom styles from an editor-style.css file and add them to a drop-down menu.
CC Compat with WooCommerce

ClassicPress

CC Compat with WooCommerce Plugin to facilitate Classic Commerce compatibility with WooCommerce extension plugins. Some WooCommerce extensions check f ...

Download

More Info
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
Classic Commerce

ClassicPress

A simple but powerful e-commerce platform, forked from WooCommerce, built for ClassicPress. This plugin is not maintained.

Download

More Info
Disable Any Comment

Simone Fioravanti

Disable Any Comment Allows administrators to globally disable comments on their site. Activating this plugin disables every comment. Under the "Tools ...

Download

More Info
Allows administrators to globally disable comments on their site.
- Activating this plugin disables every comment.
- Under the “Tools” menu you can find “Delete Comments” that allows you to bulk delete already made comments.
This plugin is made specifically to use with ClassicPress.

Credits

This plugin is forked from Disable Comments v. 1.9.0 by Samir Shah.

Privacy

To help us know the number of active installations of this plugin, we collect and store anonymized data when the plugin check in for updates. The date and unique plugin identifier are stored as plain text and the requesting URL is stored as a non-reversible hashed value. This data is stored for up to 28 days.
Stats for Update Manager

Simone Fioravanti

Discover how many sites are using your plugins and themes! This is a companion plugin for Update Manager. With Stats for Update Manager you ...

Download

More Info
Discover how many sites are using your plugins and themes!

This is a companion plugin for Update Manager.

With Stats for Update Manager you can count active installations of your plugins and themes that serve updates with Update Manager.

You’ll find a new submenu, Statistics, under the Update Manager menu.

It’s compatible with Update Manager versions 1.x and 2.x.

It supports WP-CLI. See the help typing:
- wp help statistics show
- wp help statistics purge
- wp help statistics delete
When a plugin/theme is in that count

Plugins and themes that queried Update Manager at least once in the last week are considered active. When a plugin/theme have not queried Update Manager in the last 4 week it’s removed from the database table. See filters section to tweak.

It also add the number of active installations in the plugin details. See filters section to tweak.

You can reset the count using the Reset row action.

Disclaimers

This plugin is intended to be used by developers.

Filters

Change/hide the number of active installations in plugin info tab

sfum_active_installations let’s you change/hide the number displayed in the details of your plugins.

Examples:

add_filter('sfum_active_installations', 'example_filter');

Don’t show active installation for my nothing-to-see plugin and raise it to one million for boost!
function example_filter($ar){ unset ($ar['nothing-to-see/nothing-to-see.php']); $ar['boost/boost.php'] = 1000000; return $ar; }
Or simply disable it all
function example_filter($ar){ return []; }
Note: the real number is cached for 6 hours.

Add opt-in or opt-out for your plugin users

Supported by Update Manager Client since 2.3.0. Note: this filter is from Update Manager, not from Stats for Update Manager.
codepotent_update_manager_filter_{$slug}_client_request let’s you inject data in the request made by UpdateClient.class.php.

Example:
add_filter('codepotent_update_manager_filter_my-slug/my-slug.php_client_request', 'example_filter'); function example_filter($body){ if( 'no' === get_option( 'my-slug-usage-statistics' ) ) { $body['sfum'] = 'no-log'; } return $body; }
Recognize your own sites in debug

Note that debug information is displayed only if WP_DEBUG is set to true.

sfum_my_sites let’s you recognize your own sites. They will be marked with an * in the debug informations.
With this filter you can populate an array of sha512-hashed urls.
Example:
add_filter('sfum_my_sites', 'all_my_sites'); function all_my_sites($sha) { $mysites = [ 'https://my-first-site.dog', 'https://www.my-second-site.dog' ]; $myhashes = array_map(function($value){ return hash('sha512', $value); }, $mysites); return $myhashes; }
Configure the timing a plugin/theme is considered active or stale

sfum_inactive_after let’s you configure the number of days before a plugin/theme installation is considered inactive.

sfum_old_after let’s you configure the number of days before a plugin/theme installation is considered stale and will be removed from the database.

Example:
// An entry is old after 2 days and will be removed after 7 add_filter('sfum_inactive_after', 'return_two'); add_filter('sfum_old_after', 'return_seven'); function return_two($days) { return 2; } function return_seven($days) { return 7; }
Note that filtering sfum_old_after to 0 will erase your database when the daily maintenence cronjob is executed.

Prevent specific(s) plugin(s)/theme(s) to be logged

sfum_exclude let’s you configure an array of identifier that are excluded from logging.

Note: this don’t clean your database from already logged ones.

Example:
// Don't log those plugins add_filter('sfum_exclude', 'no_log_please'); function no_log_please($list) { $excluded = [ 'please-dont/log-me.php', 'excluded-plugin/excluded-plugin.php', 'my-theme-slug' ]; return $excluded; }
Shortcodes

[sfum-installs]

The above shortcode returns an integer depicting the total number of all installations (of all plugins and themes) across the web. Developers can use it in a sentence:

Our plugins have [n] active installations!

[sfum-installs id=”my-plugin-folder/my-plugin-file.php”]

Building on the previous example, you can also provide a plugin or theme id. This shortcode returns an integer depicting the total number of installs for the plugin or theme with the given identifier. Developers can use it in a sentence:

My Awesome Plugin has [n] active installations!

My Amazing Theme has [n] active installations!

[sfum-domains]

This shortcode returns an integer depicting the number of unique domains using all of the developer’s plugins. Developers can use it in a sentence:

Code Potent is running on [n] sites!

REST API

To get a list of endpoint identifier and active installations you can access wp-json/stats/v1/stats/.
To enable this, add to wp-config.php this line:
define( 'SFUM_ENABLE_REST', true );
Note that the value of active installation is affected by the filter sfum_active_installations.

GDPR / privacy

This plugin stores data about plugin/theme updates in a table.
You can configure how much time this data is kept using sfum_old_after filter (defaults to 4 weeks).
All the data is removed at plugin uninstall.
- URL of the site asking for updates, sha512 hashed
- plugin/theme checked
- timestamp of the last check
Is up to you to decide if and to inform your plugin/theme users that this data is kept.

To help us know the number of active installations of this (Stats for Update Manager) plugin, we collect and store anonymized data when the plugin check in for updates. The date and unique plugin identifier are stored as plain text and the requesting URL is stored as a non-reversible hashed value. This data is stored for up to 28 days.

To skip Stats for Update Manager from logging, the plugin/theme have to ask for updates defining, in the body of the request done by UpdateClient, $body['sfum']='no-log'.
Since version 2.3.0 of Update Manager client this can be done using a filter.

Screenshot
Vars

Simone Fioravanti

vars With vars you can define name-value associations from the admin. Then, in your content you can insert [vars]name[/vars] and get value display ...

Download

More Info
With vars you can define name-value associations from the admin.

Then, in your content you can insert
[vars]name[/vars]
and get value displayed.

Useful if you have a value (a phone number, number of employees) in several pages that can change, so you can change this once from the admin.

It integrates into TinyMCE by adding a menu (compatible also with TinyMCE v.5).

You can choose which users can manage vars.

Look at the screenshots.

Shortcodes everywhere

There is also an option (that affects every shortcode in your site) to display shortcodes in areas where normally they are not.
- single_post_title
- the_title
- widget_text
- widget_title
- bloginfo
- get_post_metadata
Integration

Security menu

If running ClassicPress 1.1.0 or newer those settings are moved to the Security menu: choose which users can manage vars, what to do with vars when uninstalling and apply shortcodes everywhere

Functions

If you would like to use in your theme/plugin
vars_do('name')
and get value displayed.

Filters

There is a filter called vars_output

An example to capitalize the output.
function vars_output_upper( $string ) { return strtoupper( $string ); } add_filter( 'vars_output', 'vars_output_upper' );
An example to use it to exec PHP code. Dangerous, don’t do it.
You have to open and close php tags in your string.
function vars_output_exec_php( $string ) { ob_start(); eval( "?>" . $string ." " ); $evalContent = ob_get_contents(); ob_end_clean(); return $evalContent; } add_filter( 'vars_output', 'vars_output_exec_php' );
Screenshots

Privacy

To help us know the number of active installations of this plugin, we collect and store anonymized data when the plugin check in for updates. The date and unique plugin identifier are stored as plain text and the requesting URL is stored as a non-reversible hashed value. This data is stored for up to 28 days.
Estimated Read Time

azurecurve

Description The Estimated Read Time plugin for ClassicPress allows you to display expected reading times on your articles and summaries. The average p ...

Download

More Info
The Estimated Read Time plugin for ClassicPress allows you to display expected reading times on your articles and summaries. The average person reads at 200 words per minute, so, that’s the default setting. You can change it with a simple filter to suit your own audience and content.

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.
To provide the most versatile placement options, the estimated read time display is implemented with a shortcode that is designed to be placed in your theme template files. It may require some experimenting to find just the right templates for your particular theme, but you can try the content.php, single.php, archive.php, and page.php templates as a starting point.

Note that the shortcode is designed to work in templates that are in the loop, so you won’t be able to place the shortcode in, say, your header.php or footer.php files. See the examples below and place one or the other into your theme’s template file(s) where you would like the estimated read time to be displayed.

Example 1: Minimal template shortcode

<?php echo do_shortcode('[estimated-read-time words="'.str_word_count(strip_tags($post->post_content)).'"]'); ?>

Example 2: Template shortcode with dashicon

<?php echo do_shortcode('[estimated-read-time words="'.str_word_count(strip_tags($post->post_content)).'"]'); ?>

There is only a single setting, you can use this filter in a functionality plugin or functions.php file:
`
<?php
```
// Define reading speed of your audience. 200 WPM is average; adjust to suit.
add_filter('codepotent_estimated_read_time_speed', 'codepotent_estimated_read_time_speed');
function codepotent_estimated_read_time_speed($reading_speed) {
	return 125;
}
```
`

If you are using a theme that is a parent theme (as opposed to a child theme) you will need to be cautious about updating your theme because the update will overwrite all the theme files. To avoid this, you have several options, as follows. Options are listed in the order of preference.
1. use a child theme and add your shortcodes to your child theme’s templates, or
2. use a theme that you built yourself to avoid surprise updates, or
3. carefully copy your shortcodes out of your theme files before updating, then replacing them afterward, or
4. continue using the parent theme, but don’t update it.
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.0.2
- Update plugin header for compatibility with ClasssicPress v2.
Version 1.0.1
- Update plugin header and readme for compatibility with ClassicPress Directory v2.
- Update Update Manager to version 2.5.0.
Version 1.0.0

2022-02-04
- Change plugin text domain.
- Add azurecurve menu.
- Add plugin action link.
- Add options page.
- Add option to set estimated read time (filter remains available for use ad will override the option).
- Update readme file for compatibility with ClassicPress Directory.
Version 0.2.1

JUN-04-2021
1. Fix missing constants
Version 0.2.0

JUN-03-2021
1. Update plugin directory and slug name
2. Update README.md
3. Update footer credits
4. Update plugin header details
5. Add UpdateClient.class.php v 2.1.0
6. Add constants.php file
7. Add adoption notice
8. Remove public-facing Code Potent links
9. Replace Code Potent graphics with new vendor graphics
Other Notes

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 –