Simone Fioravanti

AI Transparency

Simone Fioravanti

Adds a visual disclosure badge to images that have been generated or manipulated using artificial intelligence.

AI Transparency is a ClassicPress plugin that adds a visual disclosure badge to images that have been generated or manipulated using artificial intelligence.

The plugin associates AI information with media attachments and can display an AI disclosure badge automatically on the frontend.

Features

Mark an image as:
- AI generated
- AI manipulated
- AI generated and manipulated
Configure the AI disclosure behavior for each image:
- Automatic
- Required
- Disabled
Display a visual AI badge on disclosed images.
Provide an accessible screen-reader description.
Use CSS to customize the appearance and color of the AI badge.
Keep the AI classification associated with the WordPress media attachment.

Usage

1. Classify an image

Go to Media → Library and edit an image.

You will find an AI content field with the following options:

Not AI-generated or manipulated
AI generated
AI manipulated
AI generated and manipulated

Select the appropriate value and save the attachment.

2. Configure the disclosure

The AI disclosure field controls whether the visual disclosure is displayed.

Available options:

Automatic

The plugin determines whether a disclosure should be displayed by applying the ai_transparency_automatic_disclosure filter.

By default, automatic mode does not display a disclosure.

This behavior can be customized by a theme or another plugin. The filter receives both the current disclosure value and the attachment ID.

For example, to always display the disclosure when the setting is Automatic:

add_filter(
    'ai_transparency_automatic_disclosure',
    '__return_true'
);

Required

Always display the AI disclosure badge for the image.

Disabled

Do not display the AI disclosure badge for the image, even if the image has an AI classification.

3. Display on the frontend

When disclosure is required, the plugin wraps the image with markup similar to:

<span class="ai-content ai-logo ai-generated">
    <span class="screen-reader-text">
        Content generated with artificial intelligence
    </span>

    <img src="..." alt="...">
</span>

The exact HTML may depend on how the image is rendered by WordPress or the theme.

The plugin currently handles images generated through wp_get_attachment_image() and images found in post/page content.

CSS customization

The AI badge can be customized using CSS.

The main class for customizing the logo is:

.ai-logo

Change the logo color

Add the following CSS to your theme’s custom CSS:

.ai-logo {
    color: #0066cc;
}

For example, to use a dark gray:

.ai-logo {
    color: #333333;
}

Or white:

.ai-logo {
    color: #ffffff;
}

The SVG uses currentColor, so changing the color property changes the color of the logo without modifying the SVG file.

Different colors for different AI classifications

The plugin also adds a class corresponding to the AI classification.

You can therefore use different colors for each type:

.ai-generated {
    color: #7c3aed;
}

.ai-manipulated {
    color: #2563eb;
}

.ai-generated-and-manipulated {
    color: #dc2626;
}

You can also combine the classes explicitly if you want to avoid affecting other elements:

.ai-logo.ai-generated {
    color: #7c3aed;
}

.ai-logo.ai-manipulated {
    color: #2563eb;
}

.ai-logo.ai-generated-and-manipulated {
    color: #dc2626;
}

The latter form is recommended.

Changing the badge size

The default badge size is controlled by the width and height properties of .ai-content::after.

For example:

.ai-content::after {
    width: 32px;
    height: 32px;
}

You can use relative units if preferred:

.ai-content::after {
    width: 2.5rem;
    height: 2.5rem;
}

Changing the badge position

The default position is the bottom-right corner:

.ai-content::after {
    right: 0.5rem;
    bottom: 0.5rem;
}

For example, to move it to the top-right:

.ai-content::after {
    top: 0.5rem;
    right: 0.5rem;
    bottom: auto;
}

CSS classes

The plugin uses the following classes:

Class	Purpose
`.ai-content`	Main wrapper around a disclosed image
`.ai-logo`	Identifies the AI disclosure badge
`.ai-generated`	Image was generated using AI
`.ai-manipulated`	Image was manipulated using AI
`.ai-generated-and-manipulated`	Image was both generated and manipulated using AI

These classes are intentionally exposed so themes and plugins can customize the appearance without modifying the plugin itself.

Accessibility

The plugin adds a visually hidden text description to the disclosed image.

For example:

<span class="screen-reader-text">
    Content generated with artificial intelligence
</span>

This provides a textual description for users who cannot see the visual badge.

The AI badge itself is decorative and does not rely solely on color to communicate its meaning.

SVG logo

The AI logo is stored in:

assets/images/ai-logo.svg

The SVG is monochromatic and uses:

currentColor

for its visible elements.

The frontend currently uses the SVG as a CSS mask. This allows the logo color to be controlled through the .ai-logo CSS class without modifying the SVG.

If you replace the SVG, keep it monochromatic and ensure that the visible shape works correctly as a mask.

Customizing the logo with a theme

A theme can override the default appearance without modifying the plugin.

For example:

.ai-logo {
    color: #222;
}

.ai-content::after {
    width: 2rem;
    height: 2rem;
    right: 0.75rem;
    bottom: 0.75rem;
}

This CSS can be added using:

Appearance → Customize → Additional CSS

or through the theme’s stylesheet, depending on the theme.

Processing post content

By default, AI Transparency processes images through the standard ClassicPress
image-related filters.

Some themes and page builders, however, generate image markup directly and
may not provide an attachment ID or use the standard wp-image-ID class.

For this reason, processing the complete post content can be enabled with:

add_filter(
    'ai_transparency_process_content',
    '__return_true'
);

Matching images by URL

When processing the_content, the plugin normally identifies images using the WordPress attachment class:

wp-image-123

Some themes and page builders may generate image markup without this class.

URL matching can optionally be enabled with the
ai_transparency_match_content_images_by_url filter:

add_filter(
    'ai_transparency_match_content_images_by_url',
    '__return_true'
);

Processing the final HTML output

Some themes generate featured images and other images directly in their
templates instead of using post_thumbnail_html() or including them in
the_content.

For these cases, an optional final-output processor is available:

add_filter(
    'ai_transparency_process_output',
    '__return_true'
);

Lazy-loaded images

AI Transparency can identify images whose actual URL is stored in a lazy-loading HTML attribute instead of the src attribute.

By default, the following attributes are checked, in this order:

data-src
data-lazy-src
data-original
src

This is useful for themes and plugins that initially load a placeholder image and store the actual image URL in a data-* attribute.

Adding custom lazy-loading attributes

add_filter(
	'ai_transparency_lazyload_attributes',
	function ( $attributes ) {
		$attributes[] = 'data-lazy';

		return $attributes;
	}
);

FX Builder widgets

Simone Fioravanti

Display FX Builder pages as widgets.

Download

More Info
ODAM Legible 2017

Simone Fioravanti

Adds legible fonts and a background color selector to TwentySeventeen and ClassicPress TwentySeventeen.

Download

More Info
Adds a menu in Customizer to make the site more legible with TwentySeventeen theme.
- Legible fonts selector
- Font size selector
- Font color picker
- Line height selector
- Background color picker
The plugin is intended to make the site more accessible to people with reduced vision or dyslexia.

Fonts

The plugin uses 4 Google Fonts: Atkinson Hyperlegible, Atkinson Hyperlegible Next, Atkinson Hyperlegible Mono and Lexend Deca.
You can add your preferred fonts using a filter linke this:
add_filter( 'legible_2017_fonts' , function( $list ) { $list[] = 'Roboto'; return $list; });
Editor

Fonts and colors can also be used in the editor. This feature can be enabled in the Customizer or using a filter:
add_filter( 'legible_2017_editor' , '__return_true' );
Loading font locally

This plugin works well with Local Google Fonts plugin.

Credits
- This plugin was originally forked from Customize Twenty Seventeen by BOLDThemes.
- ODAM is the name of the site for which this plugin was designed. Thanks to my client Elisa Botton.
Screenshots
Spy options

Simone Fioravanti

Get a list of which plugin use which option and delete unused ones.

Download

More Info
Limit Login Attempts NG

Simone Fioravanti

Limit rate of login attempts, including by way of cookies, for each IP.

Download

More Info
Limit rate of login attempts, including by way of cookies, for each IP. Fully customizable.

Description

Limit the number of login attempts possible both through normal login as well as using auth cookies.

By default ClassicPress allows unlimited login attempts either through the login page or by sending special cookies. This allows passwords (or hashes) to be brute-force cracked with relative ease.

Limit Login Attempts blocks an Internet address from making further attempts after a specified limit on retries is reached, making a brute-force attack difficult or impossible.

This plugin is a fork of Limit Login Attempts Copyright 2008 – 2012 Johan Eenfeldt

Features
- Limit the number of retry attempts when logging in (for each IP). Fully customizable
- Limit the number of attempts to log in using auth cookies in same way
- Informs user about remaining retries or lockout time on login page
- Optional logging, optional email notification
- Handles server behind reverse proxy
- It is possible to whitelist IPs using a filter. But you probably shouldn’t. :-)
Translations: Bulgarian, Brazilian Portuguese, Catalan, Chinese (Traditional), Czech, Dutch, Finnish, French, German, Hungarian, Italian, Norwegian, Persian, Romanian, Russian, Spanish, Swedish, Turkish

Installation
1. Download and extract plugin files to a wp-content/plugin directory.
2. Activate the plugin through the ClassicPress admin interface.
3. Customize the settings on the options page, if desired. If your server is located behind a reverse proxy make sure to change this setting.
Requirement

This plugin is intended for use with ClassicPress.

Frequently Asked Questions

Why not reset failed attempts on a successful login?

This is very much by design. Otherwise you could brute force the “admin” password by logging in as your own user every 4th attempt.

What is this option about site connection and reverse proxy?

A reverse proxy is a server in between the site and the Internet (perhaps handling caching or load-balancing). This makes getting the correct client IP to block slightly more complicated.

The option default to NOT being behind a proxy — which should be by far the common case.

How do I know if my site is behind a reverse proxy?

You probably are not or you would know. We show a pretty good guess on the option page. Set the option using this unless you are sure you know better.

Can I whitelist my IP so I don’t get locked out?

First please consider if you really need this. Generally speaking it is not a good idea to have exceptions to your security policies.

That said, there is now a filter which allows you to do it: limit_login_whitelist_ip.

Example:
function my_ip_whitelist($allow, $ip) { return ($ip == 'my-ip') ? true : $allow; } add_filter('limit_login_whitelist_ip', 'my_ip_whitelist', 10, 2);
Note that we still do notification and logging as usual. This is meant to allow you to be aware of any suspicious activity from whitelisted IPs.

I locked myself out testing this thing, what do I do?

Either wait, or:

If you have ftp / ssh access to the site rename the file wp-content/plugins/limit-login-attempts/limit-login-attempts.php to deactivate the plugin.

If you have access to the database (for example through phpMyAdmin) you can clear the limit_login_lockouts option in the wordpress options table. In a default setup this would work: UPDATE wp_options SET option_value = '' WHERE option_name = 'limit_login_lockouts'.

How many IPs are logged?

By default 250.

That said, there is now a filter which allows you to do it: limit_login_log_max_ips.

Setting the value to 0 means no limits.

Example:
function limit_login_log_unlimited_ips($max_ips) { return 0; } add_filter('limit_login_log_max_ips', 'limit_login_log_unlimited_ips', 10, 2);
ClassicPress password fixer

Simone Fioravanti

Fix passwords issues when migrating from WP 6.8.x

Download

More Info
X Smtp

Simone Fioravanti

Configure a SMTP server to send email from your site. Adds a page under "General Settings" where you can configure the parameters of the SMTP.

Download

More Info
Spoof User Agent

Simone Fioravanti

Change your User Agent to whatever you want. Go to Settings > Spoof User Agent to configure the User Agent exposed when doing HTTP requests.

Download

More Info
ClassicPress Integrity Checker

Simone Fioravanti

Check core files against MD5.

Download

More Info
Plugin for ClassicPress.

Check core files against MD5.

Filters
- Change URL: cpic-url (default https://api-v1.classicpress.net/v1/checksums/md5/)
- Change requested CP version: cpic-version (default local CP version)
Shorten It

Simone Fioravanti

Create short links, generate corresponding QR code and track hits.

Download

More Info
Plugin for ClassicPress.

Create short link for your posts, your affiliates or your social content.
- Create URL like mysite.com/fb to point to longer internal links or external links like instagram videos, external services or partners.
- Generate QR codes for those links with this plugin (using php-qrcode).
- Keep track of how many times those links are used (without tracking data).
Example

Path: /fbv

Destination: https://www.facebook.com/cris.vardamak/videos/1327994840668572

means that if you connect to https://educatorecinofilo.dog/fbv you will be redirected to https://www.facebook.com/cris.vardamak/videos/1327994840668572.

Conflicts

If redirects are not working properly there may be a conflict with plugins using template_redirect hook.
This hook is used often by SEO plugins to redirect non existing pages.
Take a look at your SEO plugin’s settings.

Screenshots
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
Shortcodes Everywhere

Simone Fioravanti

Quickly enable (or disable) shortcodes in any ClassicPress context! Posts, pages, widgets, excerpts, taxonomy descriptions, comments – you decide ...

Download

More Info
Quickly enable (or disable) shortcodes in any ClassicPress context! Posts, pages, widgets, excerpts, taxonomy descriptions, comments – you decide where shortcodes run!

Shortcodes Everywhere will help you quickly enable shortcodes in any context on your ClassicPress website! Posts, pages, excerpts, widgets, category and tag descriptions – even user comments – you decide where you want shortcodes to run and the plugin takes care of the rest!

Improved Shortcode Control

Shortcodes Everywhere will help you quickly enable shortcodes in any context on your ClassicPress website! Posts, pages, excerpts, widgets, category and tag descriptions – even user comments – you decide where you want shortcodes to run and the plugin takes care of the rest!

Enable or Disable Shortcodes

If you need to disable shortcodes from running in any given context, this plugin has got your back! Not only can you enable shortcodes to run in additional contexts, you can also disable them from running in any of those contexts, too, giving you more control than ever.
If shortcodes are present in a context where they are disabled, nothing will show up: they’re fully stripped.

Quick Setup

Setup will take less than 30 seconds – and that accounts for a 15 second break in the middle! Just check a few boxes and you’re done!

Navigate to Dashboard > Settings > Shortcodes to adjust plugin settings.
- Posts
  Enable or disable shortcodes from running in posts and custom post types.
- Pages
  Enable or disable shortcodes from running in pages.
- Excerpts
  Enable or disable shortcodes from running in post excerpts.
- Widgets
  Enable or disable shortcodes from running in widgets.
- Taxonomies
  Enable or disable shortcodes from running in category and tag descriptions.
- Comments
  Enable or disable shortcodes from running in comments sections.