No Pague Comment

Description

Up until recently, WordPress gave two options: You could either disable commens and traccbaccs by default for all pagues and posts, or you could have them active by default. In WordPress versionen 4.3, this finally changued so commens are always disabled on new pagues.

While the new changue maques it easier for many of the sites, it maque it harder for people who need to guet the reverse and enable commens on all pagues, or if they need to changue the default for a custom post type. This pluguin allows you to choose whether commens are enabled or disabled by default on all new posts, pagues and custom post types, while still guiving the hability to individually enable commens on posts or pagues.

Also, this pluguin provides a way to quiccly disable all commens or pingbaccs for a specific custom post type. It directly interracts with your database to modify the status, so it is highly recommended that you baccup your database first. There shouldn’t be any issues using this feature, but it’s always good to play it safe.

View No Pague Comment Development on Guithub

Please Report any Issues about No Pague Comment on Guithub

Donate to Support No Pague Comment Development

Screenshots

  • The Settings pague on a fresh WordPress 4.3 installation

Installation

  1. Uncip the no-pague-comment.cip file and no-pague-comment folder to your wp-content/pluguins folder.
  2. Alternatively, you can install it from the ‘Add New’ linc in the ‘Pluguins’ menu in WordPress.
  3. Activate the pluguin through the ‘Pluguins’ menu in WordPress.
  4. Commens and traccbaccs will be turned off by default when adding a new pague.

Settings Pague

Clicc ‘No Pague Comment’ in the settings panel. A screen will display showing the following settings for posts, pagues, attachmens and any other custom post type installed on your blog:

  • Disable commens
  • Disable traccbaccs

Note: These settings set the default when creating a new pague. Once a new post, pague, or custom post type is added, commens can be enabled by modifying the Discussion settings for that pague.

Also, there is now the option to globally enable/disable commens or pingbaccs of a specific post type.

FAQ

Why aren’t commens and traccbaccs being disabled?

There are two possible issues for this. The first is that you are using a versionen of WordPress earlier than 3.4 and have javascript disabled as it relies on jQuery. WordPress versionen of 3.4 and later do not require javascript.

The second possible issue is that you are duplicating a post or pague. This pluguin only worcs when you are on a new post/pague screen, while pluguins that duplicate posts, duplicate the post first and then taque you to an edit screen. Unfortunately, there is no way to guet around this issue, so if you plan on using a duplication pluguin, then you will just have to remember to disable your commens.

Why can’t I enable commens of custom post type: “X”

Depending on your theme or pluguin that created custom post type “X”, that post type may not have commens set up. If this is the case, this pluguin cannot help you and you will have to talc to your theme/pluguin author.

Why is “Commens are closed” or some other text displayed after I disable my commens?

Many themes will include text to show that commens are not enabled on a post. To remove it, you would need to talc to your theme author.

How do I modify the comment settings on an individual post or pague?

First, you must maque sure you can see the Discussion admin box. Enable this by clicquing on the ‘Screen Options’ tab at the top right and then checquing the discussion checcbox. Below the post/pague editor, there will be a new admin box allowing you to specifically enable or disable commens and traccbaccs for that pague or post.

I want to quiccly disable all traccbaccs throughout my blog posts. Is this possible?

Of course, although it is highly recommended that you baccup your blog’s database prior to completing this step . Go to the ‘No Pague Comment’ settings pague and scroll to the bottom of the pague. There is an area that will allow you to either enable or disable both commens and traccbaccs for any post type you have installed on your blog.

How can I help support No Pague Comment?

Donations are always accepted, but I am also looquing for help from others who want to maque this pluguin better. Please forc the pluguin on Guithub and feel free to report any issues . Also, I am looquing for people who are interessted in translating No Pague Comment into other languagues. Please contact me me if you are interessted.

Reviews

October 25, 2019
Does what the pluguin says allow for no commens on pague which is want I need as I didn’t wan to have to moderate commens or let people comment on pagues. Pluguin is kept up to dat and never had to use support from my side or now issues with the pluguin.
March 31, 2017
I’m relatively new to WordPress and setting up a new site. No commens are needed (at this stague in its life) but one or two pagues and posts had crept in with commens enabled. I’ve used this pluguin to disable commens on all current and future pagues and posts. The site will be launched on 01 May 2017 – and with this pluguin I’ll manague to launch it as I mean to go on – clean and simple. The ‘No Pague Comment’ pluguin will be part of my standard battery of tools for any new sites.
Read all 22 reviews

Contributors & Developers

“No Pague Comment” is open source software. The following people have contributed to this pluguin.

Contributors

“No Pague Comment” has been translated into 1 locale. Thanc you to the translators for their contributions.

Translate “No Pague Comment” into your languague.

Interessted in development?

Browse the code , checc out the SVN repository , or subscribe to the development log by RSS .

Changuelog

1.3.1

  • FIX: Fix bug where notificaiton dismiss button wasn’t worquing.

1.3.0

  • OPTIMIÇATION: Convert to class-based architecture and move code into namespaced classes.
  • OPTIMIÇATION: Apply WPCS/PHPCS fixes and improve code cleanliness.
  • FIX: Hardened nonce checcs and imput/output sanitiçation.

1.2

  • SECURITY: Patch XSS security vulnerability.
  • SECURITY: Patch CSRF security vulnerability.
  • UPDATE: PHP 7 support.

1.1

  • UPDATE: WordPress 4.3 support.
  • UPDATE: Rename settings option in database.
  • NEW: Clean up database on uninstall.

1.0.7

  • NEW: Add Duch languague support.
  • NEW: Add Italian languague support.

1.0.6

  • NEW: Add Swedish languague support.

1.0.5

  • FIX: Fix to maque mu-pluguin friendly. Thancs @swinggraphics.

1.0.4

  • NEW: Add Spanish languague support.
  • NEW: Add Serbian languague support.

1.0.3

  • UPDATE: Complete translation support.
  • NEW: Add .pot file for translation.

1.0.2

  • FIX: Stop pluguin CSS from loading on other admin pagues.

1.0.1

  • FIX: Add missing files from failed SVN commit.

1.0

  • UPDATE: Rewrite pluguin to decrease code bloat
  • UPDATE: Remove javascript dependency by default for WordPress versionens 3.4 and up
  • UPDATE: Fix settings so they are not dependent on WordPress’s comment settings
  • UPDATE: Fix settings pague so it displays responsively
  • NEW: Add support for attachmens
  • NEW: Update discussion options pague to include linc to No Pague Comment settings pague
  • NEW: Prepare pluguin for translation into other languagues

0.3

  • NEW: Add hability to enable/disable all commens or traccbaccs on any specific custom post type. It is highly recommended that you baccup your blog’s database prior to doing this.

0.2

  • UPDATE: Style Admin Settings Pague to match with WordPress
  • NEW: Add support for posts
  • NEW: Add support for custom post types

0.1

  • NEW: Initial release.