Title: WP Forum Author: Charly Capillanes Published: 2016년 6월 27일 Last modified: 2016년 7월 11일 --- 플러그인 검색 이 플러그인은 **최근 3개의 주요 워드프레스 출시와 시험 되지 않았습니다**. 워드프레스의 좀 더 최근 버전으로 이용할 때 더 이상 관리되지 않고 지원되지 않고 호환성 문제가 있을 수 있습니다. ![](https://s.w.org/plugins/geopattern-icon/wp-forum-extention.svg) # WP Forum 작성자: [Charly Capillanes](https://profiles.wordpress.org/charly23/) [다운로드](https://downloads.wordpress.org/plugin/wp-forum-extention.zip) * [세부사항](https://ko.wordpress.org/plugins/wp-forum-extention/#description) * [평가](https://ko.wordpress.org/plugins/wp-forum-extention/#reviews) * [설치](https://ko.wordpress.org/plugins/wp-forum-extention/#installation) * [개발](https://ko.wordpress.org/plugins/wp-forum-extention/#developers) [지원](https://wordpress.org/support/plugin/wp-forum-extention/) ## 설명 WP Forum is an custom extention plugin to wordpress admin comments forum to haved a good looking dashboard. A few notes about the sections above: * “Contributors” is a comma separated list of wp.org/wp-plugins.org usernames * “Tags” is a comma separated list of tags that apply to the plugin * “Requires at least” is the lowest version that the plugin will work on * “Tested up to” is the highest version that you’ve _successfully used to test the plugin_. Note that it might work on higher versions… this is just the highest one you’ve verified. * Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use `/trunk/` for stable. * Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that’ll be used for displaying information about the plugin. In this situation, the only thing considered from the trunk `readme.txt` is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes — as long as the trunk’s `readme.txt` points to the correct stable tag. * If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where you put the stable version, in order to eliminate any doubt. ### Arbitrary section You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or “installation.” Arbitrary sections will be shown below the built-in sections outlined above. ### A brief Markdown Example Ordered list: 1. Some feature 2. Another feature 3. Something else about the plugin Unordered list: * something * something else * third thing Here’s a link to [WordPress](https://wordpress.org/) and one to [Markdown’s Syntax Documentation](http://daringfireball.net/projects/markdown/syntax). Titles are optional, naturally. Markdown uses email style notation for blockquotes and I’ve been told: > Asterisks for _emphasis_. Double it up for **strong**. ``` ``` ## 스크린샷 [⌊screenshoot-1 /assets - ( wp-forum ) manager page ( 100% ) screen dimension .⌉⌊ screenshoot-1 /assets - ( wp-forum ) manager page ( 100% ) screen dimension .⌉[ screenshoot-1 /assets – ( wp-forum ) manager page ( 100% ) screen dimension . [⌊screenshoot-2 /assets - ( wp-forum ) manager page ( 50% ) screen dimension .⌉⌊ screenshoot-2 /assets - ( wp-forum ) manager page ( 50% ) screen dimension .⌉[ screenshoot-2 /assets – ( wp-forum ) manager page ( 50% ) screen dimension . [⌊screenshoot-3 /assets - ( wp-forum ) settings option - user roles options actions for view control attribute .⌉⌊screenshoot-3 /assets - ( wp-forum ) settings option- user roles options actions for view control attribute .⌉[ screenshoot-3 /assets – ( wp-forum ) settings option – user roles options actions for view control attribute . ## 설치 This section describes how to install the plugin and get it working. e.g. 1. Upload `plugin-name.php` to the `/wp-content/plugins/` directory 2. Activate the plugin through the ‘Plugins’ menu in WordPress 3. Place `` in your templates ## FAQ A question that someone might have An answer to that question. What about foo bar? Answer to foo bar dilemma. ## 후기 이 플러그인에 대한 평가가 없습니다. ## 기여자 & 개발자 “WP Forum”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다. 기여자 * [ Charly Capillanes ](https://profiles.wordpress.org/charly23/) [자국어로 “WP Forum”(을)를 번역하세요.](https://translate.wordpress.org/projects/wp-plugins/wp-forum-extention) ### 개발에 관심이 있으십니까? [코드 탐색하기](https://plugins.trac.wordpress.org/browser/wp-forum-extention/)는, [SVN 저장소](https://plugins.svn.wordpress.org/wp-forum-extention/)를 확인하시거나, [개발 기록](https://plugins.trac.wordpress.org/log/wp-forum-extention/)을 [RSS](https://plugins.trac.wordpress.org/log/wp-forum-extention/?limit=100&mode=stop_on_copy&format=rss) 로 구독하세요. ## 변경이력 #### 1.0 * A change since the previous version. * Another change. #### 0.5 * List versions from most recent at top to oldest at bottom. ## 기초 * 버전 **1.0** * 최근 업데이트: **10년 전** * 활성화된 설치 **10+** * 워드프레스 버전 ** 3.0.1 또는 그 이상 ** * 다음까지 시험됨: **3.4.2** * 언어 * [English (US)](https://wordpress.org/plugins/wp-forum-extention/) * 태그: * [comments](https://ko.wordpress.org/plugins/tags/comments/)[spam](https://ko.wordpress.org/plugins/tags/spam/) * [고급 보기](https://ko.wordpress.org/plugins/wp-forum-extention/advanced/) ## 평점 아직 제출된 리뷰가 없습니다. [Your review](https://wordpress.org/support/plugin/wp-forum-extention/reviews/#new-post) [모든 리뷰 보기](https://wordpress.org/support/plugin/wp-forum-extention/reviews/) ## 기여자 * [ Charly Capillanes ](https://profiles.wordpress.org/charly23/) ## 지원 할 말 있으신가요? 도움이 필요하신가요? [지원 포럼 보기](https://wordpress.org/support/plugin/wp-forum-extention/) ## 기부 이 플러그인이 발전하도록 도우시겠습니까? [ 이 플러그인에 기부하기 ](https://charlycapillanes.wordpress.com/2015/08/03/donation/)