Category: Tools

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 in list view 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;
}

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.

If it’s not working in your theme

Under Tools → AI Transarency you can toggle those hooks without writing code.

Those three hooks let you enable stronger images detection.

If you prefer using the hooks directly, remember to use a priority greater that 10.

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 Shortcodes

Ciprian Popescu

Block-style layout shortcodes (cover, group, columns, details, media-text, button, card) for ClassicPress. One shortcode, many types, fully nestable.

Download

More Info

Block-style page layouts for ClassicPress, delivered as shortcodes.

Plugin page: https://getbutterfly.com/classicpress-plugins/fx-shortcodes/
Demo: https://studio.getbutterfly.com/fx-shortcodes/

Why this exists

ClassicPress dropped the Gutenberg block editor in favour of the Classic editor. That’s a deliberate choice — but it leaves a gap: the layout primitives that came with blocks (cover, columns, media + text, buttons, accordions, etc.) disappear with them. Themes still know how to style alignfull / alignwide, but there’s no easy way to author those layouts in a Classic post.

FX Shortcodes fills that gap. Every layout block you’d reach for in Gutenberg is available as a shortcode, with the same visual result and the same alignment classes — but authored as plain [element] tags inside the Classic editor.

No JavaScript, no block editor, no React. Just one shortcode and a stylesheet.

How it works

Everything goes through a single shortcode: [element]. The type attribute picks the layout:

[element type="cover" background="/hero.jpg" overlay="#000" overlay-opacity="0.4"]
  <h1>Welcome</h1>
[/element]

Self-closing void blocks use a trailing slash:

[element type="spacer" height="3rem" /]

Because the plugin parses [element] itself (innermost-first, before WordPress’ shortcode regex runs), same-name nesting works — you can drop an [element type="group"] inside another [element type="group"] without WordPress closing on the first [/element].

Available types

Type	Role
`cover`	Full-bleed hero with background image (`<img>`), overlay
`group` (alias `section`)	Generic container with optional flex / grid layout
`columns` + `column`	Equal or asymmetric column rows
`details` (alias `accordion`)	Native `<details>` element
`media-text` (alias `mediatext`)	Image on one side, text on the other; supports “crop image to fill”
`button`	`<a>` or `<button>` with fill / outline / text variants and OKLCH hover
`card`	Image + title + body, optionally a whole-card link
`spacer`	Invisible vertical or horizontal gap (void)
`separator` (alias `hr`)	Thematic break with style variants (void)
`line` (alias `colored-line`)	Decorative striped / dotted / shaded line (void)

All types accept a shared set of common attributes — width (full / wide / CSS length), align, vertical-align, background-color, padding, margin, gap, border-radius, shadow, etc. — plus a few type-specific ones.

Install

Drop the fx-shortcodes folder into wp-content/plugins/.
Activate it from the Plugins screen.
Open Settings → FX Shortcodes for the full reference with code samples for every shortcode.

Requirements

ClassicPress 2.0+
PHP 8.1+

Tradesw Visit Counter

tradesouthwest

Adds Admin column to edit page of posts to show number of visits to post.

Download

More Info
- Requires PHP: 7.4
- Requires CP: 1.4
- Version: 1.0.1
- Author: Tradesouthwest
- Tags: counter, posts, visits, translation-ready
- License: GPL 3 (see LICENSE)
- Text domain: tradesw-visit-counter
- Plugin URL: https://github.com/tradesouthwest/post-visit-tally
Overview

Adds Admin column to edit page of posts to show number of visits to post.

Support

Use https://github.com/tradesouthwest/tradesw-visit-counter/issues to post your issues with this plugin.

Change Log

See file CHANGELOG.md

Implementation Details

Hook Selection: We use wp_head for tracking to ensure the visit is only counted when the page begins to render for a user.

Metadata Naming: The meta key is prefixed with an underscore (_warsww_post_views), which keeps it hidden from the standard “Custom Fields” metabox in the editor, preventing accidental manual edits.

Performance: For high-traffic sites, consider offloading this to a REST API endpoint or using an external database to prevent heavy update_post_meta calls on the wp_postmeta table.

Citations: This implementation follows the standard WordPress Plugin Handbook guidelines for hooks and class-based architecture.
```
warsww-visit-counter/
├── warsww-visit-counter.php   # Main Loader & Logic
└── inc/
    └── class-admin-columns.php # Admin Display Logic
```

ClassicPack

Ciprian Popescu

A modular toolkit for ClassicPress and WordPress. Enable modules from the ClassicPack admin screen.

Download

More Info

A modular admin toolkit: one plugin, many optional features. You turn only what you need on from a single place so unused code is never loaded.

Official plugin page: getbutterfly.com — ClassicPack
More plugins from the same author: ClassicPress plugins at getbutterfly.com

What this plugin is for

ClassicPack does not run any optional feature until you enable it. After installation, you open the ClassicPack item in the admin menu, choose the modules you want (grouped by category), and save. Disabled modules are not loaded, which keeps the site lean.

Use ClassicPack if you want several small admin utilities in one place instead of many separate small plugins, with a clear on/off switch for each one.

Quick start (first-time setup)

Install the classicpack folder under wp-content/plugins/ (or install the release zip from your Plugins screen) and activate ClassicPack.
In the admin sidebar, open ClassicPack (top-level menu). You will see checkboxes for each module, grouped (for example: Performance and SEO, Media, Content, Users).
Enable the modules you need and click Save Changes. Only enabled modules are loaded on the next request.
Some modules add their own subpage under ClassicPack (for example User Manager) or a link from the modules list. Others appear only in context (for example a row action on a post list, or a block on a user profile).

If something does not show up, confirm the module is enabled and that you meet the module’s context (for example the post type switcher is for the classic post editor, not the block editor).

Where things appear in the admin

You are looking for…	Where to go
Turn features on or off	ClassicPack (main screen, module toggles)
Module-only settings (when available)	ClassicPack → submenu for that module, or the Settings / Details action on the module row, if shown
Core redirects, email commenters, auto-save images, users online, user manager, etc.	As documented per module in the table below
This README as project documentation	On GitHub or in the plugin folder as `README.md`

Help in the dashboard: ClassicPress and WordPress do not add a “Help” dropdown for third-party plugin screens by default. For ClassicPack, use this README, the readme.txt Description and Frequently Asked Questions sections, and the short text under each module on the ClassicPack screen.

Modules (what each one does, at a glance)

Enable these on the ClassicPack screen. Nothing here runs when the module is off.

Module	What it does (short)	Where you use it
Core Redirects Manager	Lists automatic redirects the CMS stores when a post’s URL changes; you can remove unneeded ones.	Under ClassicPress-related redirects (see module link)
Email Commenters	Sends a single email to every address that commented on a chosen post or page.	ClassicPack submenu: Email Commenters
Auto Save Images	When you publish, can pull hotlinked images into the Media Library.	Settings on the Auto Save Images screen
Delete Post with Attachments	On permanent post delete, can remove media uploaded only to that post when safe.	Runs when you trash/delete content (see description on the modules screen)
Users Online	Shows who is browsing the site and a dashboard summary.	ClassicPack / dashboard widget as implemented
User Manager	Optional Users list columns (e.g. registration, last login) and options to keep posts or pages for logged-in users only.	ClassicPack → User Manager and Users list
User Content Overview	On a user’s profile, shows counts and links for content that user “owns” (by post type, media, optional Woo customer orders) for cleanup or reassignment.	Users → edit a user
Post type switcher	In the classic editor, switch an existing item to another public post type (with a warning).	Posts or Pages (or CPT) → edit, Publish box
Duplicate post	Row action to duplicate a public post type as a draft (content, meta, terms, featured image as applicable).	Post type list tables
User Avatar	Profile picture from the Media Library on the user profile screen; replaces Gravatar when set (legacy meta key unchanged).	Users → Profile / Users → Edit user
Admin Login	Custom login URL; redirects for wp-login.php and /wp-admin/ when not signed in.	Settings → Permalinks (Admin Login section)

Some modules are Classic-editor specific or list-table specific. If you use only the block editor, test before relying on a module.

Requirements

ClassicPress 2.5+ or WordPress 6.2+
PHP 8.0+

Changelog

Release notes match readme.txt (plugin directory listing).

0.3.7

Core Redirects Manager: add per-page and total redirect counts, pagination, and plain-language help for Delete and Delete All
Rename modules screen submit button from “Save modules” to “Save Changes”
Code style: use curly-brace control flow in PHP templates, short array syntax ([]), and single-line HTML opening tags (no behavior change)

0.3.6

Admin Login: fix PHP 8 undefined-variable warnings on the custom login screen ($user_login, $error) when loading wp-login.php

0.3.5

Admin Login: use classicpack_admin_login_* options and resolve CPCS violations

0.3.4

Add Admin Login module (custom login URL and redirects; configure under Settings → Permalinks)

0.3.3

Load the classicpack textdomain on init (no translation files required); avoid WP 6.7+ _load_textdomain_just_in_time() notices from early gettext
Bootstrap enabled modules on init instead of plugins_loaded so module registry strings run after translations are allowed

0.3.2

Remove the non-functional Details action for Delete Post with Attachments and User Avatar on the modules screen
Add the classicpack-ui-toggle class to plugin admin checkboxes (Auto Save Images, User Manager, and post editor or meta box hooks)

0.3.1

Align short descriptions with ClassicPress and WordPress
Add Plugins list link to the ClassicPack modules screen
Clarify Core Redirects Manager description for ClassicPress and WordPress

0.3.0

User Avatar module: rename profile form table class from easy-author-avatar-image-form-table to author-avatar-image-form-table

0.2.1

Add User Avatar module (profile picture from Media Library, legacy user meta key retained)
Remove standalone Easy Author Avatar-style enable option; uninstall clears the legacy easy_author_avatar_image_option row if present

0.2.0

Add User Content Overview module (profile content counts and admin links)
Fix post type switcher nested-form submit (use detached form and HTML5 form association and fall back when wp_set_post_type is unavailable)
Lower PHP requirement to 8.0
Update documentation and readme