Disable Blogging in WordPress

설명

Turn WordPress into a non-blogging CMS platform. Disable Blogging is a plugin that disables all blog related functionalities on the front-end and back-end. This includes posts, comments, feeds, and so much more. As a result, you will have a cleaner and simpler WordPress platform to be used for static websites.

Disable all posting & comments functions

At its core level, all posting and comment related functionalities are disabled – but that’s not all. Disable Blogging includes 20+ extra features to disable and hide cumbersome functions that run on WordPress including:

Notice

This plugin does not delete any data on WordPress. It hides and disables those features that are blog related. If you have any existing, posts, comments, categories, and tags on your website: they must be manually deleted. That’s if you do not want to keep any of the blog information. All plugin features are available in the plugin’s settings (Settings > Blogging).

Links to previous posts will still be accessible and previous comments will be hidden from view.

Contribute on GitHub

Want to help improve this plugin? Head over to our GitHub page. Please make all contributions to our dev branch.

Contributors

We’d like to thank those who’ve helped improve our plugin: Piet Bos, SECT, Christian Jongeneel, John A. Huebner II, Maël Conan, CotswoldPhoto

As well as those who’ve spotted bugs for us: Benjamin Danon, Saumya Majumder, youpain, Bart Kuijper Timothée Moulin, vee w, Niels Lange, Damian

스크린샷

  • General settings to toggle which blog functions to disable.
  • Extra features to disable. Not necessarily blog related.
  • Hide unused fields and options from the Profile page to reduce clutter.
  • Hide unused menu items created by plugins or themes, and redirect them elsewhere.

설치

  1. Upload the plugin to the ../wp-content/plugins/ directory.
  2. Activate the plugin through the Plugins menu in WordPress.
  3. Let it settle in a for a minute and be amazed.

Settings Page

By default all blogging functionality are disabled. However, these options can be toggled in the plugin’s Settings > Blogging.

FAQ

Are these changes permanent?

No, this plugin simply disables, hides, and redirects all of the blogging functions. You can easily revert WordPress back to a blogging platform by simply disabling the plugin.

How do I find the label IDs to hide additional profile fields?

  1. Navigate to the Users > Your Profile
  2. Open up your browser’s web inspector (ex: Chrome)
  3. Use the element selector and select the label on the left side of field that you want to hide, for example:
    • <label for="first_name">First Name</label>
  4. For each <label for= tag, you will find the ID’s of each field, for example:
    • first_name

후기

2020년 August 27일
I've used this plugin for years, even when it was outdated. Still, its time has come. It generates too many errors now. It spits out 2 errors on nearly every page load: Deprecated: update_option was called with an argument that is deprecated since version 5.5.0! The "comment_whitelist" option key has been renamed to "comment_previously_approved". And another deprecated warning about contextual_help, which the plugin author mentioned would be updated, but is yet to be updated. I recently had to turn off the Disable Posts feature because it was preventing other features from working. So sadly, too many issues to workaround now.
2020년 August 25일
Screw up my website, I mean totally.
2020년 March 22일
simple and essential tool that should be in every website by default
2018년 July 20일
Simple, working as intended to.
모든 16 평가 읽기

기여자 & 개발자

“Disable Blogging in WordPress”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

자국어로 “Disable Blogging in WordPress”(을)를 번역하십시오.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록RSS로 구독하십시오.

변경이력

2.1.0

2020-09-14

  • Added minimum required PHP version in readme
  • Updated Settings API wrapper
  • Fix: depreciation warning for Extra > Help Tabs (thanks to Timothée Moulin)
  • Fix: depreciation warning for “Comment must be manually approved” option (pull #18)
  • Fix: large plugin icon (issue #12)

2.0.4

2017-01-14

  • Screen Options tab can now be removed from the admin header
  • Both post and comments are removed from the REST API
  • Hiding additional admin menu items is no longer available
  • Removed depreciated plugin option from v1.3.0
  • Fix: fatal error with WooCommerce setup (issue #12)

2.0.3

2016-11-26

  • Fix: fatal error given on some websites (thanks to CotswoldPhoto)

2.0.2

2016-11-25

  • i18n support: available in Japanese
  • Disable alternative “Howdy” greetings in different languages (thanks to Maël Conan)
  • Menu Feature: option to disable reordering of Pages menu
  • Fix: empty array error given for some websites
  • Fix: invalid argument supplied for foreach() warning (issue #10)

2.0.1

2016-10-23

  • Fix: website would load a blank page when disabling feeds

2.0.0

2016-10-23

  • Rebuilt plugin with new Settings API, everything is now 100% customizable
  • Reordered “Pages” menu further up underneath the “Dashboard” (thanks to Piet Bos)
  • The “Activity” meta box will show custom post types instead (thanks to SECT)
  • Extra Features
    • Remove code in header used to add support for emojis
    • Change or remove the admin footer
  • Profile Features
    • Hide additional profile fields created by plugins/theme by their label ID
  • Menu Features
    • Option to hide dashicons
    • Option to remove separators
  • Blog related options are hidden from the Settings
  • Set the following blog options in the Settings:
    • Reading: Set default the reading settings to a static page
    • Discussion: Unchecked “attempt to notify any blogs linked to from the article
    • Discussion: Unchecked “allow link notifications from other blogs (pingbacks and trackbacks) on new articles
  • More extensive features added to disable blog related features
  • Various code improvements
  • Fix: comments column showing up in Pages
  • Fix: custom Taxonomy redirecting to Pages upon update (issue #3)

The rest of the changelog can be viewed on GitHub.