Plugins

Share Classicly

Kelson Vibber

Adds a link to ShareOpenly at the end of your posts so that readers can share to Mastodon, Bluesky, and similar open social media

Download

More Info
Stable tag: 0.4
Tags: sharing, fediverse, mastodon, classicpress
Contributors: Kelson
License: GPLv2 or later

Adds a link to the ShareOpenly service at the end of your posts for easy sharing to Mastodon, Bluesky, Threads and similar open social media sites.

Description

Adds a link to the ShareOpenly service at the end of you posts so that readers can easily share them to Mastodon, Bluesky, Threads and similar open social media sites. No remote scripts or data are loaded until the visitor clicks on the link.

The plugin is built for ClassicPress, but will probably work fine on WordPress too.

Notes

ShareOpenly is a service built and run by Ben Werdmuller. I just used the link format described at Add ShareOpenly links to your site.

There is a WordPress plugin that does something similar, but it detects when it’s running on ClassicPress and deactivates itself. I thought about forking it, but decided to just write my own, since I’d already done it myself with Eleventy. I did not read any of that plugin’s code except for the function that blocks running on forks — which I’m obviously not using here! — and did not reference any of it when writing this one.

Installation

Add share-classicly.zip from the latest release using your plugin dashboard, or unzip it yourself and upload the share-classicly folder to wp-content/plugins/, or (once it’s approved) install it from the ClassicPress Plugin Directory.

Then just activate it. Nothing else special is needed.

Changelog

[0.4] – 2024-11-23
- Change default link text and make it customizable.
[0.3] – 2024-11-14
- More code cleanup.
- Submit to plugin directory.
[0.2] – 2024-11-11
- Code cleanup.
- Use translatable text.
- Add option for whether to show on posts, pages or both.
[0.1pre] – 2024-10-31
- Initial prototype.
Source on Codeberg.
Mirror on GitHub.
Plugin page at ClassicPress.

(c) 2024 Kelson Vibber
ClassicPress Pepper for Passwords

ClassicPress

For enhanced security add a "pepper" to password hashing.

Download

More Info
Overview

The ClassicPress Pepper Password Plugin is designed to enhance the security of user passwords by implementing a unique “pepper” mechanism. This plugin allows administrators to generate and manage a pepper string that is used in conjunction with password hashing, adding an additional layer of protection against unauthorized access.

Features
- Pepper Generation: Easily generate (or refresh) a random pepper string to enhance password security by clicking a button.
- Settings Menu: Access the plugin settings through the ClassicPress admin menu at Settings > Pepper.
- Automatic Activation: The plugin creates a pepper file upon activation, if it doesn’t already exist, to store the random Pepper string.
- User-Friendly Interface: Simple navigation and clear messages for users.
Manual Installation
1. Download the plugin .zip file.
2. Upload the pepper-password folder to the /wp-content/plugins/ directory via FTP, or visiting Plugins > Upload.
3. Activate the plugin through the Plugins menu in ClassicPress.
Installation
- Install the ClassicPress Directory Integration plugin and activate it on your site
- Visit Plugins > Install CP Plugins and search for ClassicPress Pepper Password Plugin
- You can install and activate the plugin by clicking the respective buttons.
Usage

Accessing Settings
- Navigate to Settings > Pepper in the ClassicPress admin dashboard to manage your pepper settings.
Generating a Pepper
- Click on the Enable Pepper or Renew Pepper button within the settings page to generate or renew the pepper string.
Important Notes
- Changing or deactivating this plugin will invalidate all stored password hashes, requiring users to reset their passwords.
- Ensure you have filesystem permissions set correctly for the plugin to function properly.
Contributing

Contributions are welcome! Please fork the repository and submit a pull request for any enhancements or bug fixes.

License

This plugin is licensed under the GPL v2 or later. Please see the LICENSE file for more details.

Support

For support or inquiries, please open an issue in the repository or contact the plugin author directly.
W3P SEO

Ciprian Popescu

W3P SEO has options for local business JSON-LD data, Open Graph, optimized SEO defaults, native XML sitemaps and advanced topic clustering settings.

Download

More Info
W3P SEO has options for search engines, such as ownership verification, local business JSON-LD data, Open Graph, analytics, and optimized SEO defaults.

W3P SEO also features native XML sitemaps and advanced topic clustering settings.

For support, feature requests and bug reporting, please visit the official website.

Installation

Upload and activate the plugin.

Changelog

= 1.8.2 =
- Add the proper “WRP SEO” plugin name in a few places
- Remove several WordPress references
- Remove obsolete Web of Trust references
= 1.8.1 =
- FIX: Pass all CPCS guidelines
- UPDATE: Remove lots of obsolete features
= 1.8.0 =
- FIX: Fix Link Whisper feature to use word boundaries, excluding words already inside <a> tags
- FIX: Fix excerpt not working with ClassicPress
- UPDATE: Implement custom meta field for meta description as a fallback for excerpt
- UPDATE: Remove Web of Trust verification
- UPDATE: Remove Majestic verification
= 1.7.7 =
- UPDATE: Update WordPress compatibility
- UPDATE: Add FAQs to supported custom post types
- UPDATE: Add robots meta to complement the header
= 1.7.6 =
- FEATURE: Add option to noindex URLs with query strings
= 1.7.5 =
- FIX: Change meta meter functionality to respond to input instead of keyup events
- FIX: Only loop through content types if XML sitemaps are enabled
- FEATURE: Add Link Whisper functionality (not affiliated with the Link Whisper plugin)
- UPDATE: Update WordPress compatibility
= 1.7.4 =
- UPDATE: Add missing “image” field
- UPDATE: Improve LocalBusiness schema
- UPDATE: Improve image upload functionality
- UPDATE: Update Twitter to X (Twitter)
- UPDATE: Update WordPress compatibility
= 1.7.3 =
- UPDATE: Updated WordPress compatibility
= 1.7.2 =
- UPDATE: Updated WordPress compatibility
= 1.7.1 =
- FIX: Removed property CPT from the list of allowed metabox locations
= 1.7.0 =
- FIX: Fixed description being echoed instead of returned in the <head> element
- FIX: Fixed Open Graph tags property names
- FIX: Fixed WPCS (WordPress Coding Standards)
- UPDATE: Added extra Open Graph tags for Twitter Cards and Pinterest
- UPDATE: Removed old secure_url image Open Graph tag
- PERFORMANCE: Joined all wp_head actions into one
- PERFORMANCE: Changed several options into variables so they can be reused without having to query the database
= 1.6.1 =
- FIX: Fixed auto-adding image attributes from image filename
- FIX: Fixed Schema generating empty image dimensions
- FIX: Sanitized Schema excerpt for the description field
= 1.6.0 =
- UPDATE: Updated author banner
- UPDATE: Updated WordPress compatibility
- UPDATE: Removed unused option (readonly)
= 1.5.9 =
- UPDATE: Added Yoast migrator (temporary)
- UPDATE: Added Meta report for posts
= 1.5.8 =
- FIX: Fixed subpages container not being properly closed
= 1.5.7 =
- FIX: Fixed admin scripts not being enqueued due to broken dependencies
- UI: Improved layout of meta report
= 1.5.6 =
- FIX: Fixed excerpt generation (faster now)
- FIX: Merged two options
- FEATURE: Added Meta Report, similar to Screaming Frog, showing page titles and descriptions
= 1.5.5 =
- FIX: Fixed HTML tags in Schema description/excerpt
- FIX: Fixed duplicate meta description
- UPDATE: Added option to enable/disable SEO title
- UPDATE: Added option to enable/disable SEO meta description
- UPDATE: Improved the [subpages] shortcode
= 1.5.4 =
- UPDATE: Updated SEO title and meta description logic
- UPDATE: Added character counter/meter for SEO titles and meta descriptions
= 1.5.3 =
- FIX: Fixed Sitelinks schema for potentialAction
= 1.5.2 =
- FIX: Fixed several issues with breadcrumbs
- FEATURE: Added better breadcrumbs
= 1.5.1 =
- FIX: Fixed several typos
- FEATURE: Added topic clustering settings
- UPDATE: Started plugin rebranding to W3P
- UPDATE: Updated UI for more intuitive options
= 1.5.0 =
- FIX: Removed unused Facebook administrator ID option
- FEATURE: Added Knowledge Graph Schema details
- FEATURE: Added custom title
- FEATURE: Added excerpt as custom meta description
= 1.4.11 =
- FEATURE: Added native WordPress XML sitemaps
- FEATURE: Added option to automatically add image caption, description and ALT text from image title for all new uploads
- UPDATE: Updated WordPress compatibility
- UPDATE: Updated WPCS (WordPress Coding Standards)
= 1.4.10 =
- FIX: Removed broken custom sitemap functionality
- UPDATE: Updated WordPress compatibility
= 1.4.9.1 =
- UPDATE: Updated WordPress compatibility
= 1.4.9 =
- UPDATE: Updated WordPress compatibility
= 1.4.8 =
- UPDATE: Updated WordPress compatibility
= 1.4.7 =
- FIX: Removed all references to codor class
- UPDATE: Updated all non-secure Schema URL to HTTPS
= 1.4.6 =
- UPDATE: Updated WordPress compatibility
- UPDATE: Removed GIT2SVN integration as it’s not feasible
- UPDATE: Renamed stylesheet to avoid conflicts with other getButterfly plugins
- PERFORMANCE: Removed custom fonts for code blocks for WordPress Dashboard
= 1.4.5 =
- FEATURE: Added sitemap feature
= 1.4.4 =
- FIX: Fixed excerpt generation (strip shortcodes and remove tags)
= 1.4.3 =
- FIX: Fixed excerpt generation
- FIX: Fixed custom excerpt not being generated for homepage
- UPDATE: Admin UI tweaks
= 1.4.2 =
- UPDATE: Removed Facebook admin ID from Open Graph tags
- UPDATE: Added og:image:alt to Open Graph tags
= 1.4.1 =
- UPDATE: Added missing Open Graph tags
- UPDATE: Unified meta description and Open Graph tags
- UPDATE: Added excerpt to pages by default
= 1.4.0 =
- UPDATE: Changed styling of code elements
- UPDATE: Set up groundwork for improved breadcrumbs
- UPDATE: Set up groundwork for improved page descriptions
= 1.3.12 =
- UPDATE: Updated WordPress compatibility
- UPDATE: Incremental testing GIT2SVN
= 1.3.6 =
- UPDATE: Updated help text for custom homepage description
- DEVELOPMENT: Restarted development on GitHub
= 1.3.5 =
- UPDATE: Removed Google+ integration
- UPDATE: Updated PHP requirements
- UPDATE: Updated WordPress compatibility
= 1.3.4 =
- FIX: Removed unused shortcode parameter
- UPDATE: Updated WordPress compatibility
= 1.3.3 =
- UPDATE: Updated string/variable sanitisation
= 1.3.2 =
- UPDATE: Updated plugin name to avoid confusion
- FIX: Fixed readme.txt version
= 1.3.1 =
- UPDATE: Added Baidu verification tag
- UPDATE: Updated Google Tag Manager loading priority
- UPDATE: Removed Google Tag Manager (noscript)
= 1.3.0 =
- UPDATE: Updated WordPress compatibility
- FIX: Added missing Google Analytics and Google Tag Manager tags
- FIX: Added missing header and footer tags
- FIX: Added missing content
= 1.2.1 =
- UPDATE: Updated WordPress compatibility
- FIX: Removed unused files and functions
- FIX: Removed deprecated links
- FIX: Added missing styles (backend)
= 1.2 =
- FIX: Removed double variable declaration
- FIX: Removed unused (inherited) variable declaration
- UPDATE: Moved plugin to Settings area to unclutter menu
- UPDATE: Removed unused welcome mat feature
- UPDATE: UI tweaks
- PERFORMANCE: Removed unused code, fixed line endings and added PSR code changes
= 1.1.3 =
- FEATURE: Added microdata breadcrumbs (unstyled)
= 1.1.2 =
- FIX: Google Tag Manager script position
= 1.1.1 =
- FIX: Fixed excerpt not being generated from the post/page content
- FIX: Fixed settings page description
= 1.1.0 =
- FEATURE: Added welcome mat (scroll mat) feature
- FIX: Fixed performance
= 1.0.4 =
- FIX: Unified gbad.css styles (.codor)
- UPDATE: Removed Google Maps as it now requires a key and a developer account
= 1.0.3 =
- UI: UI and wording tweaks
- UI: Added sharing debugger link for Open Graph/Facebook
- FIX: Added OG schema to DOCTYPE only if Open Graph option is checked
- FIX: Fixed excerpts for SEO description
- FIX: Fixed DOCTYPE prefix for Open Graph
peendev-markdown

niels

Write your posts and pages in Markdown. Replaces TinyMCE with EasyMDE.

Download

More Info
This plug-in replaces the default ClassicPress editor with the EasyMDE Markdown editor.

Changelog

v1.0.5
- Remove Premium URL from ClassicPress directory headers.
v1.0.4
- Add headers required for ClassicPress plug-in directory.
v1.0.3
- Fix issue where EasyMDE did not show up on post-new.php.
- Add readme.txt with PHP 8.1 requirement.
v1.0.2
- Bundle EasyMDE and highlight.js, allowing for offline use.
- Various small fixes.
v1.0.1
- Use built-in Markdown renderer. (You should remove the azrcrv-markdown plug-in).
- Support Markdown in comments.
v1.0.0 Initial release.
- Support Markdown in Posts and Pages.
Requirements
- ClassicPress >= 1.5
- PHP >= 8.1.0
Installation

No special instructions. Install & activate nielspeen/peendev-markdown. There is no settings page.
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)
Nofollow Post Links

iljester

Nofollow Post Links is a plugin that allows you to manage the nofollow attribute of post links. You can manage them granularly,

Download

More Info
Description

Nofollow Post Links is a plugin that allows you to manage the nofollow attribute of post links. You can manage them granularly, within the single post, or you can assign nofollow attribute to all links, or again, you can remove the attribute for all links.

Compatibility and support

This plugin was designed specifically for ClassicPress. However, it may also be compatible with WordPress if the classic editor is used. In any case, support is limited to ClassicPress installations only.

Installation
1. Upload plugin in the wp-content > plugins directory.
2. Then, install it.
3. Activate.
Thirdy part assets

Nofollow Post Links uses:
- Update client class from plugin (Update Manager)[https://software.gieffeedizioni.it/plugin/update-manager/], released under GPLv2 license. Author Simone Fioravanti.
- github workflows by Simone Fioravanti https://github.com/xxsimoxx
Frequently Asked Questions

Can I choose the links to which I want to nofollow?

Yes, for each post you can establish which links should have nofollows.
You can also globally determine which domains will not be nofollowed.

Is the nofollow attribution definitive?

Here we must distinguish between attribution of nofollow on a “single content” and attribution of nofollow on “all contents” for every post type in your site:
- Attribution on single content. Here the attribution of nofollow or its removal occurs by modifying the content post unless you have set or left the “Same for the metabox action” option set. In this case, see the next point.
- Global attribution. Global attribution works in three ways: “Javascript”, “Content Filter” and “Content Edit”. If you use the “Javascript” or “Content Filter” mode, the original content of the post is not changed. With the “Content Edit” mode, the plugin will write the content of your post. If you choose the “Content Edit” option, remember to make a backup of your database before proceeding.
What is the purpose of Restore Post Settings?

“Restore post setting” is an action that allows the restoration of the configuration via metabox, before the global action is run. This action is particularly useful if you use the “Content Edit” mode. However, please note that if you save the content of your post after a global action in “content edit” mode, a new backup will be generated with the globally assigned settings.

Should I make a database backup before using Nofollow Post Links?

Generally, it is good practice to make a backup before installing and using a plugin on a live site. In the case of Nofollow Post Links, backup is highly recommended if you use the “Content Edit” mode for global actions. This mode is still experimental, and is highly invasive, because edit the post, and since the plugin has not been sufficiently tested on a sufficient number of installations, it becomes essential to create a backup (at least of the wp_posts and wp_postmeta tables.) before executing it, also because the “Restore post settings” action may not be useful in this case.

What is the best mode for global action?

Please note that the “Javascript” mode and the “Content Filter” mode work in the frontend, therefore, although minimal, they will have an impact on the loading of the page. But if you use a caching system, you won’t even notice.
The “Content Edit” mode has no impact on the frontend, because it only edits the post.
The choice is therefore subjective, without prejudice to what has been said in the previous FAQs.

Wait! When I started a global action the metabox disappeared!

Naturally. If you have activated a global dofollow or nofollow action you cannot edit links via the metabox.

What is nofollow mapping?

Nofollow mapping allows you to retrieve nofollows manually inserted into links and update metabox settings. Very useful especially after installing the plugin.

What is the function of harmonize?

Harmonize allows you to simultaneously assign the nofollow attribute to a specific domain or remove the nofollow attribute. It is a global assignment function which however only acts on a specific domain.

Can I create a domains whitelist?

Yes. Simply enter them in the appropriate field in the settings tab, and the global actions will ignore those domains. Additionally, you won’t be able to assign nofollow via the metabox. However, in content edit mode you can assign it manually (but why would you do that?).

Can I choose the post type for global actions?

Yes. From the settings, you can determine which post types you can perform global actions on. You can also decide in which post types to show the post link metabox.

What happens when the plugin is uninstalled?

Any data in the database referring to the plugin will be removed. If you used content edit mode to assign nofollows, they will remain after uninstallation unless you used “Restore Post Settings” or the “Global Dofollow” action before uninstalling the plugin.
MicroBlog

ElisabettaC77

adds front-end micro blog to ClassicPress

Download

More Info
FX Builder

Ciprian Popescu

FX Builder is an improved page builder plugin for ClassicPress that provides visual columns in the post editor without using shortcodes.

Download

More Info
FX Builder is a page builder plugin that provides visual columns in the post editor without using shortcodes. From the settings page, you can enable it for posts, pages, and custom post types.

Changelog

= 1.4.3 =
- Add section duplication feature
- Improve outer section inserter
- Remove rogue console.log
= 1.4.2 =
- Fix undefined array key “row_html_height_unit”
- Fix SCF/ACF outline overlapping the FX column wrapper
- Convert FX switcher to vanilla JavaScript (from jQuery)
= 1.4.1 =
- Fix bottom column selector being displayed as block instead of Flex
= 1.4.0 =
- Fix unescaped variable
- Fix typo in readme.txt
- Add new Settings and Typography options panel
- Add Google fonts and Bunny fonts functionality to TinyMCE’s fontformats array
- Add translatable strings to the Settings page
- Add admin stylesheet
- Update readme.md with helpful links and a short description
- Update ZIP release workflow
- Switch more elements from floats to Flex CSS
- Replace deprecated “resize” function with “resize” event
- Clean up old settings panel (alpha)
- Remove unused filter
- Remove tabbing capability in textarea element
= 1.3.1 =
- Add line height controls
- Add column vertical alignment
- Add 5-column layout
- Add section height controls to create spacers
- Various UI improvements
= 1.3.0 =
- Remove jQuery UI Sortable dependency and replace with SortableJS
- Remove old, unused files
- Update plugin branding to be consistent with “FX Builder”
= 1.2.3 =
- Fix author link
- Add system fonts to TinyMCE
= 1.2.2 =
- Fix undefined variable
- Add image styling to wraps to make sure images are not wider than content
- Remove “Wide” content width, as it’s not relevant, and can be added as a class
= 1.2.1 =
- Add font size presets, custom font size and font weigh to TinyMCE
- Clean up row and item templates
- Clean up front-end styles
- Clean up readme.txt
= 1.2.0 =
- First public release for ClassicPress
= 1.0.2 – 13 Ags 2017 =
- Fix bug: WP 4.8 compat (thanks to nick6352683)
= 1.0.1 – 06 Jan 2017 =
- Fix bug: wp preview remove FX Builder data
- Fix CSS Bug: Tools & CSS button position
- Store _fxb_active in revisions
- Hide “Preview Changes” button in “Publish” meta box when FX Builder is active
- Fix “save_post” hook to fix fatal error bug
= 1.0.0 – 09 Dec 2016 =
- First stable Release
= 1.0.0.beta – 12 Oct 2016 =
- Browser compatibility (Tested with: Firefox, Chrome, IE11, Edge, Android Phone, Tablet)
- Use Admin Color
- UI and UX Improvement
- RTL Support
- Use HTML Class for Front End Output + Update Front CSS
= 1.0.0.alpha3 – 29 Sep 2016 =
- Revision: Revert to Revision now also revert to FX Builder data
- Remove disable editor feature. Simpler Settings
- Change settings option name. You need to re-configure settings
- Page is enabled by default
- Introduce Tools: Export / Import FX Builder data
- Auto focus to editor when open editor modal
- Fix Custom CSS textarea line break
- Fix several small-screen accessibility issue in modal box
= 1.0.0.alpha2 – 23 Sep 2016 =
- Add row with thumbnail for each layoout
- Welcome notice with link to admin page
- Improve overall builder design
- Fix overflow in editor modal
- Add post class “fx-builder-entry” when active
- Reset undo in editor modal
- Custom CSS for each posts
- Other small fixes and improvements
= 1.0.0.alpha – 21 Sep 2016 =
- Initial alpha release
KTS Display Widgets

Tim Kaye

Simply show or hide widgets on specified pages. Adds checkboxes to each widget to either show or hide it on specific posts, pages, archives, etc.

Download

More Info
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
DebugPress: Debugger in a Popup

Dev4Press

DebugPress is an easy-to-use plugin that implements popups for debugging and profiling website pages with support for intercepting AJAX requests.

Download

More Info
DebugPress is an easy-to-use plugin implementing popup for debugging and profiling currently loaded WordPress powered website page with support for intercepting AJAX requests. The main debugger window is displayed as a popup, activated through the button with the Bug integrated into WordPress Toolbar, or floating on the page.

The plugin currently has a total of 22 tabs in the popup debugger window, showing all kinds of information relevant to the current page, WordPress setup, background AJAX calls, and much more.

The plugin doesn’t modify or replace any WordPress files or functions.

= Home and GitHub =
- Learn more about the plugin: DebugPress Website
- Contribute to plugin development: DebugPress on GitHub
= Quick Overview Video =
https://www.youtube.com/watch?v=-eFnBRLhy-s

= Pretty Print for objects =
To display the content of objects or arrays, plugin has pretty print functionality through use of simpler PrettyPrint library, or more robust third-party library Kint. You can choose one or the other from the plugin Settings, Advanced tab.

= Debugger Panels =
Currently, the plugin has the following panels:
- Basic
- Request (optional)
- Query (for frontend only)
- Content (optional)
- Roles (optional)
- Constants (optional)
- Hooks (optional)
- PHP (optional)
- Server (optional)
- Enqueue (optional)
- SQL Queries (if SQL queries logging is enabled)
- User (optional, if user is logged in only)
- HTTP (optional, if HTTP API calls are captured)
- bbPress (optional, on bbPress forum pages only)
- Plugins (optional, if plugins store data)
- Errors (for all captured PHP errors)
- Doing It Wrong (for captured WordPress Doing It Wrong warnings)
- Deprecated (for captured PHP deprecated warnings)
- AJAX (for captured AJAX calls while page is active)
- Store (for any user stored objects during the page loading)
- Tools (internal and external tools links)
- Debug Log (load content on demand from WordPress ‘debug.log’)
- Layout (control the size, position and activation of the popup)
= SQL Queries =
This panel lists all the queries WordPress has run. It allows you to order the queries by execution order or length of execution, and all queries can be filtered by the query type, database table it targets or the WordPress function that called it. Every query displays the execution time, order, caller functions stack and fully formatted SQL query that is easy to read. For some Dev4Press created plugins (and that list will grow), DebugPress can detect the source of the query and allow you to filter by the plugin calling the query.

= PHP and WordPress Errors =
Plugin has 3 panels dedicated to showing PHP and WordPress errors and warnings. The Plugin captures this information during the page load, and it shows full debug trace as returned by the PHP debug tracing function.

= AJAX =
The plugin tracks every AJAX call coming through WordPress admin-ajax.php handler, and with every response, it returns HTTP headers with AJAX request basic execution information. Right now, plugin is not returning a list of logged errors or SQL queries, because both can produce huge output that goes over the HTTP header limits. Plan is to introduce these in the future plugin versions.

= Info Panels =
In the administration Tools menu, plugin adds DebugPress Info page showing several panels
- PHP Info: full formatted results from phpinfo() function
- OPCache Info: full settings and statistics for the OPCache PHP extension
- MySQL Variables: full MySQL settings retrieved from the database
= Plugin Settings =
The plugin has various options controlling the plugin activation, button integration position, user roles that can see the debugger window, options to attempt overriding WordPress debug flags and options controlling the visibility of optional debugger panels.

= Log into Database =
Debugger popup is visible for the request running in the browser. But there are many requests that are happening in the background (AJAX calls, REST API calls…), and for them, you can’t see errors, call information and other stuff in the debugger. Because of that, DebugPress supports logging of various events into database with the use of ‘coreActivity’ plugin, and it is highly recommended to install and use coreActivity.

Log various debug events into a database with the free plugin: coreActivity Plugin, supporting over 120 events and 10 popular WordPress plugins. DebugPress related events will be logged and available for later analysis, and this includes errors, AJAX calls, and HTTP API calls.

= Documentation and Support =
To get help with the plugin, you can use WordPress.org support forums, or you can use Dev4Press.com support forums.
- Plugin Documentation: DebugPress Website
- Support Forum: Dev4Press Support
Installation

= General Requirements =
- PHP: 7.4 or newer
- Tested with the latest PHP, version 8.3
= WordPress Requirements =
- WordPress: 5.5 or newer
- Tested with the latest WordPress, version 6.5
= Basic Installation =
- Upload folder debugpress to the /wp-content/plugins/ directory
- Activate the plugin through the ‘Plugins’ menu in WordPress
- Plugin settings are available under WordPress ‘Settings’ panel
Frequently Asked Questions

= How I can install this plugin? =
If you are not sure about WordPress plugins installation, here is the quick information: Plugin Installation.

= How can I enable WordPress Debug Mode? =
To enable WordPress debug mode via wp-config.php, check out the article here: WordPress Setup.

= How can I open Debugger popup? =
If you have enabled debugger (for admin side and/or frontend), Debugger is activated via Bug button placed in the WordPress Toolbar or as a float button (depending on the settings). Since version 3.0, you can activate the button via keyboard shortcut, default combination is ctrl+shift+u, but it can be changed in the plugin settings.

= Can I change the size and position of the popup? =
Yes. Once the popup is open, you will find the Layout icon next to the button to close the popup. On the layout panel, you can change the location for the popup, size, modal status and auto activation on page load.

= Where can I configure the plugin? =
Open the WordPress ‘Settings’ menu, there you will find ‘DebugPress’ panel.

Changelog

= 4.0 (2024.11.02) =
- New: tested with WordPress 6.7
- New: tested and compatible with PHP 8.4 RC 3
- New: using composer to load Kint library
- New: various constants for KINT library control
= 3.9.2 (2024.08.23) =
- Fix: one more issue with the access to OPCache status information
= 3.9.1 (2024.08.19) =
- Fix: problem with the Tracker when closure makes a call #08
= 3.9 (2024.05.14) =
- Edit: few more updates and improvements
- Edit: replacement of some native with WordPress functions
- Edit: various small updates and tweaks
- Edit: Kint Pretty Print Library 5.1.1
- Fix: various PHP notices related to PHP 8.1 and newer
= 3.8 (2024.04.24) =
- Edit: few minor tweaks and changes
- Edit: updates to the plugin readme file
- Edit: small changes related to the PHP 8.3 compatibility
- Fix: various PHP notices related to PHP 8.1 and newer
= 3.7 (
WP Version Modifier for CP

DigTek

Allows Spoofing the WP Version to Install and Troubleshoot Plugins and Themes in ClassicPress.

Download

More Info
Allows Spoofing the WP Version to Install Plugins and Themes in ClassicPress.

ChangeLog

= 1.1.0 =
11/20/24
- Apply Blue Haze UI to Settings Page
- Add Code to Insure Save Success Message Displayed
- Code Cleanup
= 1.0.2 =
6/4/24
- Another Save Error Adjustment…
= 1.0.1 =
6/3/24
- Fix Error when Saving on Some Sites
= 1.0.0 =
5/12/24
- Add Multisite Compatibility
- Change Icon to WP Icon
= 0.9.2 =
4/13/24
- Fix Fatal Error if is_plugin_active() not loaded
= 0.9.1 =
4/9/24
- Code Cleaned
= 0.9.0 =
Initial Release Date – 4/4/24

Installation
1. Upload
2. Activate
Updates will be available in the dashboard like any other plugin
- WP Version has a Dashboard Menu to Access the Settings