이 플러그인은 최근 3개의 주요 워드프레스 출시와 시험 되지 않았습니다. 워드프레스의 좀 더 최근 버전으로 이용할 때 더 이상 관리되지 않고 지원되지 않고 호환성 문제가 있을 수 있습니다.

Disable WYSIWYG

설명

Disable WYSIWYG sets user_can_richedit to false that disable TinyMCE Visual Editor (WYSIWYG editor) totally completely permanently forever. This plugin also works fine with multisite enabled WordPress (aka. WordPress Mu).

More information please visit my site.

설치

WordPress:

  1. Upload the extracted files to the /wp-content/plugins/ directory
  2. In ‘Plugins’ page, choose ‘Activate’

Multisite enabled WordPress:

  1. Upload the extracted files to the /wp-content/plugins/ directory
  2. In ‘Site Admin’ mode (You need log in as site admin), go to ‘Plugins’ page, choose ‘Network Activate’
  3. Just FYI, you can also activate this plugin individually for different sites.

Old-styled WordPress Mu:

  1. Upload the extracted files to the /wp-content/mu-plugins/ directory
  2. That’s all.

후기

2017년 4월 15일
Handy Dandy! Simple and Functional Thanks to this, I avoided that ugly iframe injecting visual editor for the comments section
모든 5 평가 읽기

기여자 & 개발자

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

기여자

자국어로 “Disable WYSIWYG”(을)를 번역하세요.

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

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

변경이력

1.0.9

  • Compatibility check for 5.8, nothing new, just bump version to tell everyone this plugin still works.

1.0.8

  • Starting from WordPress 5.0, you need an additional plugin Classic Editor by Automattic to disable Gutenberg first.

1.0.7

  • Compatibility check for 4.6 and 4.7, nothing new, just bump version to tell everyone this plugin still works.

1.0.6

  • Compatibility check for 4.5, nothing new, just bump version to tell everyone this plugin still works.

1.0.5

  • Compatibility check for 4.4, nothing new, just bump version to tell everyone this plugin still works.

1.0.4

  • Compatibility check for 4.3, nothing new, just bump version to tell everyone this plugin still works.

1.0.3

  • Fix PHP warning, props deMediaWerker.

1.0.2

  • Compatibility check for 4.2.2, nothing new, just bump version to tell everyone this plugin still works.

1.0.1

  • Update readme

1.0.0

  • First release