Simone Fioravanti

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 w ...

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.
Switch Post Status

Simone Fioravanti

Switch Post Status from draft to publish and back. This plugin allows to switch post status from draft to publish and back using a link in row actions ...

Download

More Info
This plugin allows to switch post status from draft to publish and back using a link in row actions.

Configuring other actions

Use the xsxswitch_lookup filter.

Example:
add_filter ('xsxswitch_lookup', 'myprefix_custom_sps_actions'); function myprefix_custom_sps_actions($lookup) { // Let it handle private posts and convert them to published. $lookup['private'] = [ 'dst' => 'publish', 'msg' => 'Switch to a great public post', ]; // Change the text to a custom one for draft posts. $lookup['draft'] = [ 'dst' => 'publish', 'msg' => 'My custom lovely message', ]; return $l; }
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.
Icons for CP

Simone Fioravanti

This plugin allows to use SVG icons in post and pages. Add new icons Just use the "Icons" menu in "Appearance" menu. Add your own icons ...

Download

More Info
This plugin allows to use SVG icons in post and pages.

Add new icons

Just use the “Icons” menu in “Appearance” menu.
Add your own icons or any from FontAwesome to the theme.

Put the name of the icon as the title (use something like my-brand-icon) and the SVG as the post.

Note: if you uninstall the plugin your icons get lost.
To keep them add define('KEEP_ICONS_FOR_CP', true); to wp-config.php.

Shortcode and MCE menu
```
[ifcp-icon icon='paw' size='16' color='#FF0000' class='my-wonderful-class']
```
Size (width, default 16px), color and class are optional.

It also adds a menu to TinyMCE (v. 4 and v.5) to choose the icon and insert the shortcode for you.

Integrations

This plugin integrates with Canuck CP theme, that is no more available.
Your icons are added to those present in the theme, and those present in the theme are available.

WP CLI

It is supported.
Use wp help icons or wp help icons add to see usage instructions.
You can bulk import a folder with a simple script like
for icon in *.svg; do wp icons add "$icon"; done
Post to Telegram

Simone Fioravanti

When editing a post, just check a checkbox and when you hit "publish" a link to the post will be sent to your Telegram channel. If there is one, post ...

Download

More Info
When editing a post, just check a checkbox and when you hit “publish” a link to the post will be sent to your Telegram channel.
If there is one, post the featured image.

This plugin is written for ClassicPress.

Usage
- Create your channel.
- Create a bot.
- Create a token for the bot
- Go to Settings -> Post to Telegram
- Fill your bot token.
- Fill your channel ID
Having troubles finding your channel ID?
Try revoking admin rights to your boot, give it admin rights again, and save the changes leaving Channel field empty.
Maybe some hints will be shown!

Filters

ptt_query_params

Change request made to Telegram Bot API.
Example: adding text to the message
add_filter( 'ptt_query_params' , 'myprefix_telegram_before_text' , 10 , 3 ); public function myprefix_telegram_before_text( $params, $post_id, $method ) { if ( $method === 'sendMessage' ) { $params[ 'text' ] = 'Nuovo articolo! ' . $params[ 'text' ]; } else { $params[ 'caption' ] = 'Nuovo articolo! ' . $params[ 'caption' ]; } return $params; }
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.
Block plugin updates

Simone Fioravanti

Block Plugin Updates One-click blocks updates from a specific plugin Easily click on the unlocked lock in the plugin page. The lock gets closed and ...

Download

More Info
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 e ...

Download

More Info
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 and tags without replacing them.
- Custom Style Menu
 Pull custom styles from an editor-style.css file and add them to a drop-down menu.
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;
	}
```