티스토리 수익 글 보기
This page will explain some aspects of the plugin directory, and explain of the more obvious aspects which a lot of people miss.<\/p>\n\n\n\n
To make your entry in the plugin browser most useful, each plugin should have a readme file named You can use the plugin readme generator<\/a> and put your completed result through the official readme validator<\/a> to check it. If you need more visual assistance you can use the tool wpreadme.com<\/a><\/p>\n\n\n\n Since WordPress 5.8 plugin readme files are not parsed for requirements<\/a>. This means that headers All plugins contain a main PHP file, and almost all plugins have a The Plugin readme header consists of this information:<\/p>\n\n\n\n At the end of the header section is a place for a short<\/em> description of a plugin. The example recommends no more than 150 characters and to not use markup. That line of text is the single line description of the plugin which shows up right under the plugin name. If it’s longer than 150 characters, it gets cut off, so keep it short.<\/p>\n\n\n\n If your plugin has no custom install settings, it’s okay to omit this section. If your plugin has custom configuration notes post install, this is a great place to put that information.<\/p>\n\n\n\n While custom sections are permitted and supported, please use them in moderation. People get used to seeing how every other plugin looks, and when yours is weird, they’ll miss important information.<\/p>\n\n\n\n While most of the readme details are self evident, there are a few sections that trip people up.<\/p>\n\n\n\n WordPress.org’s Plugin Directory works based on the information found in the field Stable Tag<\/strong> in the readme. When WordPress.org parses the When the Stable Tag is properly set, WordPress.org will go and look in If the Stable Tag is 1.2.3 and The WordPress.org Plugin Directory reads the main plugin PHP file to get things like the Name of the plugin, the Plugin URI, and most importantly, the version number. On the plugin page, you’ll see the download button which reads “Download Version 1.2.3” or similar. That version number comes from the plugin’s main PHP file, not<\/em> the readme!<\/p>\n\n\n\n The Stable Tag points to a subdirectory in the You can embed videos from YouTube, Vimeo, and anywhere else WordPress supports by default<\/a>. All you have to do is paste the video URL onto it’s own line in your readme.<\/p>\n\n\n\n We recommend you NOT have the video as the final line in a FAQ section, as sometimes formatting gets weird.<\/p>\n\n\n\nreadme.txt<\/code> that adheres to the WordPress plugin readme file standard<\/a>. This file controls the output on the front-facing part of the directory. Writing a description in the readme determines exactly what will be displayed on wordpress.org\/plugins\/Your-Plugin<\/code><\/p>\n\n\n\nRequires PHP<\/code> and Requires at least<\/code> are going to be parsed from plugin’s main PHP file. <\/p>\n\n\n\nSection Details<\/h2>\n\n\n\n
readme.txt<\/code> file as well. The readme.txt<\/code> file is intended to be written using a subset of markdown.<\/p>\n\n\n\nReadme Header Information<\/h3>\n\n\n\n
=== Plugin Name ===\nContributors: (this should be a list of wordpress.org userid's)\nDonate link: https:\/\/example.com\/\nTags: tag1, tag2\nRequires at least: 4.7\nTested up to: 5.4\nStable tag: 4.3\nRequires PHP: 7.0\nLicense: GPLv2 or later\nLicense URI: https:\/\/www.gnu.org\/licenses\/gpl-2.0.html\nHere is a short description of the plugin. This should be no more than 150 characters. No markup here.<\/pre><\/code><\/pre>\n\n\n\n
\n
https:\/\/wordpress.org\/support\/users\/YOURID\/edit\/<\/code> and change the display name.<\/li>\n\n\n\nInstallation<\/h3>\n\n\n\n
Custom Sections<\/h3>\n\n\n\n
Technical Details<\/h2>\n\n\n\n
How The Readme Is Parsed<\/h3>\n\n\n\n
readme.txt<\/code>, the very first thing it does is to look at the readme.txt<\/code> in the \/trunk<\/code> directory, where it reads the “Stable Tag” line. <\/p>\n\n\n\n\/tags\/<\/code> for the referenced version. So a Stable Tag of “1.2.3” will make it look for \/tags\/1.2.3\/<\/code>.<\/p>\n\n\n\n\/tags\/1.2.3\/<\/code> exists, then nothing in trunk will be read any further for parsing by any part of the system. If you try to change the description of the plugin in \/trunk\/readme.txt<\/code> then your changes won’t do anything on your plugin page. Everything comes from the readme.txt<\/code> in the file being pointed to by the Stable Tag. <\/p>\n\n\n\n\/tags<\/code> directory. But the version of the plugin is not actually set by that folder name. Instead, it’s the version that is listed in the plugin’s PHP file itself which determines the name. If you have changed Stable Tag to 1.4 and the plugin still says 1.3 in the PHP file, then the version listed will be 1.3.<\/p>\n\n\n\ntrunk<\/code> (rather than a version) still works in the Plugin Directory, it is neither supported nor recommended as a method of indicating new versions, and has been known to cause issues with automatic updates. We are currently actively discouraging the use of “Stable Tag: trunk” and prohibiting its use for new plugins.<\/div><\/div>\n\n\n\n\nVideos<\/h3>\n\n\n\n
Markdown<\/h3>\n\n\n\n