Post/Page Specific Custom Code

Plugin Banner

Post/Page Specific Custom Code

by Łukasz Nowicki

Download
Description

Post/Page/Product-specific custom code allows you to add custom CSS styles to individual posts, pages, or WooCommerce products. It provides a dedicated area in the editor screen where you can write your CSS code. You can also choose whether the CSS should apply only to the single view or also to archive-type views.

A new meta box will appear below the content editor on the edit screen for posts, pages, and products. You can enter any custom CSS there and decide whether it loads only on the single view or also on archive pages like category listings or product grids.

Requirements

This plugin requires at least WordPress 5.0 (remember always to keep your WordPress installation up to date!) and PHP 7.4 on your server.

Automatic installation

Automatic installation is the easiest way. Simply log in to your WordPress admin panel, go to the Plugins menu, and click “Add New”.

In the search field, type Post/Page Specific Custom Code and click Search Plugins. Then click the “Install Now” button.

Manual installation

  1. Upload the post-page-specific-custom-css folder to the /wp-content/plugins/ directory.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.
  3. That’s it – enjoy! 🙂
  1. If you don't see the CSS panel, open Screen Options and make sure "Custom CSS" is checked.

    If you don't see the CSS panel, open Screen Options and make sure "Custom CSS" is checked.

  2. Enter CSS code that will apply only to your post or page. You can force the plugin to apply it only on single post/page views.

    Enter CSS code that will apply only to your post or page. You can force the plugin to apply it only on single post/page views.

  3. Plugin settings panel.

    Plugin settings panel.

Is it free?

Yes, it’s licensed under GPLv2 (or later). However, if you’d like to support my work, you’re welcome to make a donation of a few dollars. I won’t stop you 🙂

Spam message asking for money

By brandoncollins on May 3, 2024

Be warned! This plugin is a sneaky scam. Out of nowhere, a giant info box shoves a payment message in your face on the WordPress admin page. It's clear the developer has no clue about user experience, and leaving their code on your site is a recipe for disaster.

Spammy plugin

By crissman on May 1, 2024

Uninstalled. Spams the WP Admin page with money begs.

A bit buggy

By revixi5 on February 4, 2024

The CSS metabox has a spinner that continuously spin, and the CSS is now inject inside the BODY content of the page instead of the HEAD... probably another bug. Had to switch to Simple CSS. It inject the code in the header and minify it.

A very useful plugin

By Victor Tyavbee (tsquare07) on May 3, 2023

The plugin is very useful

Such a handy plugin!

By jjminkle on May 2, 2023

I am surprised this plugin is not more popular. It is a great way to add a little CSS to a page. Sometimes I just find it handy when I want to test CSS before adding it to my main stylesheet. Especially if I want to show someone global page changes before actually doing them globally.

Gets the CSS displayed

By jmlord on January 6, 2023

Hi!

Great plugin, exactly what I was looking for.

On my version (6.1.1) the CSS validation fails due to line 679 (there is no data object in wp object).
const ppsccEditPost = wp.data.select('core/edit-post');

Otherwise the CSS saves and displays correctly.

It was very nice but today it crashed my site

By conman (normaldenker) on July 1, 2022

Hi there, I really loved your plugin but after installing WP 6.0 (PHP 7.4, WPML and TOTAL theme as Template) it crashed my site. Something caued a 500 error -> post-page-specific-custom-css.php on line 519 This is the debug information (XXXX for security reason):
[01-Jul-2022 11:48:39 UTC] PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Phylax\WPPlugin\PPCustomCSS\Plugin::the_content() must be of the type string, null given, called in /XXXXXXXXXXXXX/wordpress/wp-includes/class-wp-hook.php on line 307 and defined in /XXXXXXXXXXXXX/wordpress/wp-content/plugins/postpage-specific-custom-css/post-page-specific-custom-css.php:519
Stack trace:
#0 /XXXXXXXXXXXXX/wordpress/wp-includes/class-wp-hook.php(307): Phylax\WPPlugin\PPCustomCSS\Plugin->the_content(NULL)
#1 /XXXXXXXXXXXXX/wordpress/wp-includes/plugin.php(191): WP_Hook->apply_filters(NULL, Array)
#2 /XXXXXXXXXXXXX/wordpress/wp-includes/formatting.php(3877): apply_filters('the_content', '')
#3 /XXXXXXXXXXXXX/wordpress/wp-includes/class-wp-hook.php(307): wp_trim_excerpt('', Object(WP_Post))
#4 /XXXXXXXXXXXXX/wordpress/wp-includes/plugin.php(191): WP_Hook->apply_filters('', Array)
#5 /XXXXXXXXXXXXX/wordpress/wp-includes/post-templa in /XXXXXXXXXXXXX/wordpress/wp-content/plugins/postpage-specific-custom-css/post-page-specific-custom-css.php on line 519
Any ideas?

This plugin does not work for comments pages

By masoud1990 on June 6, 2022

While it is a useful plugin, it does not wok in comments pagination. For example, you can use it to have custom CSS in a single page address: domain.com/title/ (custom css different from the general CSS of the whole site are used), but it does not work for comments pages of the same address such as: domain.com/title/comment-page1 or domain.com/title/comment-page2 As you know, there is no separate editing environment for comments pages. As a result, there is no separate box to add custom css for comments pages. Suggestion for the next update: the plugin will be more useful if the custom CSS of each single page work for all of its comments pages (from first comments page to the last one). Regards

Great Plugin!

By Gwalter75 on May 3, 2022

Makes everything a lot easier 😉

One of my favorite plugins

By gustavovibe on May 2, 2022

Really useful in many cases, for those who want more freedom of the design and code of the page is one of the best plugins of the thousands we can add in wordpress.

0.3.0

  • Release date: 2025-07-21
  • Added support for WooCommerce products (custom CSS can now be assigned to individual products)
  • Plugin renamed from “Post/Page specific custom CSS” to “Post/Page Specific Custom Code”

0.2.5

  • Release date: 2025-07-17
  • Highlighting for CSS code is now enabled by default.
    7 years ago it was optional due to performance concerns on
    slower machines — nowadays that looks outdated; you can still
    disable it using:
    add_filter(‘postpage_sccss-highlight_code’, ‘__return_false’);
  • Fixed issue with incorrect validation of an empty CSS field
  • Replaced CSS validation with a linting mechanism
  • Minor code improvements and compatibility testing with newer PHP and WordPress versions
  • Removed birthday notice

0.2.4

  • Release date: 2022-01-20
  • Fixed default post/page values (it was in reverse, thank you, @olandir, for pointing that out!)

0.2.3

  • Release date: 2021-11-29
  • Fixed options saving issue
  • Fixed text formatting

0.2.2

  • Release date: 2020-05-10
  • Lot of fixes, to stay up to date with WordPress code rules
  • Birthday banner visible only for administrators
  • Birthday banner now can be hidden for the next year
  • Now it’s possible to let editors edit CSS

0.2.1

  • Release date: 2020-04-27
  • Custom JavaScript note
  • Birthday note

0.2.0

  • Release date: 2020-02-25
  • Compatibility: 5.3 and previous
  • Added options page for plugin
  • Added default CSS for post and page
  • Added CSS highlighting for posts, page and options (for default CSS)
  • Thou it’s a bit bigger by default, you may make input view even bigger

0.1.4

  • Release date: 2018-11-21
  • Status: Stable
  • Compatibility: 5.0 and previous
  • Minor code refactoring

0.1.3

  • Release date: 2018-05-18
  • Status: Stable
  • Compatibility: 4.9.6 and previous

0.1.2

  • Release date: 2018-05-05
  • Status: Stable
  • Compatibility: 4.9.5 and previous
  • Added screenshots, icons and header image for WordPress repository

0.1.1

  • Release date: 2017-08-03
  • Status: Stable
  • Compatibility: 4.8.1 and previous
  • Added screenshots, icons and header image for WordPress repository

0.1.0

  • Release date: 2016-12-16
  • Status: Stable
  • Initial release
Back to top