Matteo Enna

horshipsrectors

Fetches the content of another webpage or URL to display inside the current post or page.
Please note that this plugin previously used <code>file_get_contents()</code>, but it’s no longer recommended.
Starting now, this plugin utilizes the <code>wp_remote_get()</code> and <code>wp_remote_retrieve_body()</code> functions to retrieve content from URLs.
This plugin contains code adapted from the original work by horshipsrectors

Website Content in Page or Post – Embed website content in posts and pages

Fetches the content of another webpage or URL to display inside the current post or page.

David Artiss

WordPress README files are formatted using a version of the Markdown language. This plugin can be used to convert these to XHTML and display on a post or page of your site.
It’s ideal for plugin developers who wish to add instructions to their own site without having to duplicate effort.
Key features include…
<ul>
<li>Convert your markdown README to XHTML and display in any post or page</li>
<li>Use shortcodes or a direct PHP function call</li>
<li>Responsive output of screenshots</li>
<li>Output is cached for maximum performance</li>
<li>Links automatically added to author and tag information</li>
<li>Download links added</li>
<li>Ability to specify which sections of the readme to exclude</li>
<li>Can also omit specific lines of text</li>
<li>Extra shortcodes available to display plugin banners and to return specific plugin data (download link, version number, etc)</li>
<li>Google Translation suppressed on code output</li>
<li>And much, much more!</li>
</ul>
Iconography is courtesy of <a href="https://www.freepik.com/flatart" rel="nofollow ugc">Flatart</a> ♥️
👉 Please visit the <a href="https://github.com/morehawes/plugin-readme-parser" title="Github" rel="nofollow ugc">Github page</a> for the latest code development, planned enhancements and known issues 👈
<h3>Getting Started</h3>
To use, simply add the <code>[readme]</code> shortcode to any post or page. An example of use would be…
<pre><code>[readme]WP README Parser[/readme]
</code></pre>
This would fetch and display the README for this plugin. You can also specify a filename instead.
The first heading, which is the name of the plugin, will be automatically suppressed as it is assumed that you have already added this to your post/page or are using it as the title.
<h3>Additional Shortcode Parameters</h3>
exclude
Each README is divided into a number of sections. If you wish to exclude any from the output then use this parameter to list them.
Before the first section (usually “Description”) is a number of pieces of “meta data” about the plugin, including tags, etc. Links are automatically added to these. If, however, you wish to just exclude this data then you should use the section name of “meta”. Underneath this data is a short description which will remain in this case. If you want to remove this description and the meta data then use the section name of “head”. If you wish to just remove a particular bit of meta data then specify <code>contributors</code>, <code>donate</code>, <code>tags</code>, <code>requires</code>, <code>license</code>, <code>license uri</code>, <code>tested</code> or <code>stable</code>.
For example…
<pre><code>[readme exclude="Meta,Changelog"]WP README Parser[/readme]
</code></pre>
This will display the entire README with the exception of the Changelog and the Plugin meta.
include
The opposite of <code>exclude</code> this allows you to specify ONLY the section that you wish to appear. So, using the example from above…
<pre><code>[readme include="Meta,Changelog"]WP README Parser[/readme]
</code></pre>
This will ONLY show the Meta and Changelog sections of the README file.
The only difference to the exclude command is that you can’t include just specific sections of the meta. If you believe that this option is required then please get in touch via the forum.
ignore
Different from <code>exclude</code> this allows to ignore specific lines of the README. Multiple lines should be separated by double commas (to allow single commas to be be used in the actual line to be ignored). For example…
<pre><code>[readme ignore="this line,,and this line"]WP README Parser[/readme]
</code></pre>
target
Any links will have a target of <code>_blank</code>. If you wish this to be anything else then change it with this parameter. For example…
<pre><code>[readme target="_self"]WP README Parser[/readme]
</code></pre>
nofollow
If you wish a link to have a nofollow option (i.e. the tag of <code>rel="nofollow"</code>) then specify this as “Yes”. By default it won’t. For example…
<pre><code>[readme nofollow="Yes"]WP README Parser[/readme]
</code></pre>
cache
This allows you to specify how long output should be cached for, in minutes. By default caching is set to 60 minutes. For example, to cache for 24 hours…
<pre><code>[readme cache=1440]WP README Parser[/readme]
</code></pre>
version
If you wish to display a specific version of the README, use this parameter to request it. For example…
<pre><code>[readme version=1.0]WP README Parser[/readme]
</code></pre>
mirror
If your plugin is hosted at a number of other locations then you can use this to specify alternative download URLs other than the WordPress repository. Simply seperate multiple URLs with double commas (i.e. ,,). For example…
<pre><code>[readme mirror="http://www.example1.com,,http://www.example2.com"]WP README Parser[/readme]
</code></pre>
links
By default download and other links will be added to the bottom of the README output. By specifying a section name via this parameter, however, then the links will appear before that section. For example, to appear before the description you’d put…
<pre><code>[readme links="description"]WP README Parser[/readme]
</code></pre>
name
If you specify a README filename instead a name then it will be assumed that the plugin name at the top of the README is the correct one. This may not be the case, however, if you’ve renamed your plugin (as is the case for this plugin). You can therefore use the <code>name</code> parameter to override this.
<pre><code>[readme name="WP README Parser"]https://plugins.svn.wordpress.org/wp-readme-parser/trunk/readme.txt[/readme]
</code></pre>
ext
The extension that your screenshots are stored as – i.e. PNG or JPG.
assets
Storing your screenshots in your assets folder? Then set this to ‘yes’ for them to be read from there. For example…
<pre><code>[readme assets="yes"]WP README Parser[/readme]<h3>Using Content Reveal</h3>
</code></pre>
If you also have the plugin <a href="https://wordpress.org/plugins/simple-content-reveal/" title="Content Reveal" rel="ugc">Content Reveal</a> installed, then each section of the README will be collapsable – that is, you can click on the section heading to hide the section content.
By default, all sections of the output will be revealed.
You may now use 3 further parameters when using the <code>[readme]</code> shortcode…
hide
Use this parameter to hide sections automatically – simply click on them to reveal them again.
For example…
<pre><code>[readme hide="Changelog"]WP README Parser[/readme]
</code></pre>
scr_url
If you wish to supply your own hide/reveal images then you can specify your own folder here.
The two images (one for when the content is hidden, another for when it’s shown) must be named image1 and image2. They can either by GIF or PNG images (see the next parameter).
For example…
<pre><code>[readme scr_url="https://artiss.blog”]WP README Parser[/readme]
</code></pre>
scr_ext
Use this specify whether you wish to use PNG or GIF images for your own hide/reveal images. If you do not specify it, GIF will be used.
For example…
<pre><code>[readme scr_url="https://artiss.blog" scr_ext="png"]WP README Parser[/readme]<h3>Using a Function Call</h3>
</code></pre>
If you wish to code a direct PHP call to the plugin, you can do. The function is named <code>readme_parser</code> and accepts 2 parameters. The first is an array of all the options, the same as the shortcode. The second parameter is the README name or filename.
For example…
<pre><code>echo readme_parser( array( 'exclude' => 'meta,upgrade notice,screenshots,support,changelog,links,installation,licence', 'ignore' => 'For help with this plugin,,for more information and advanced options ' ), 'YouTube Embed' );
</code></pre>
This may be of particular use to plugin developers as they can then display the README for their plugins within their administration screens.
<h3>Displaying the plugin banner</h3>
Some plugins have banners assigned to them. The shortcode <code>[readme_banner]</code> can be used to output them (responsively too). Between the opening and closing shortcode you must specify a plugin name (a URL can’t be used) and that’s it. For example…
<pre><code>[readme_banner]YouTube Embed[/readme_banner]
</code></pre>
If no banner image exists then nothing will be output.
<h3>Display specific README information</h3>
You may wish to add your own section to the output to provide download links, etc. In which case you can suppress this section and then use an additional shortcode to retrieve the information that you need.
Use the shortcode <code>[readme_info]</code> to return one of a number of different pieces of information. Use the required parameter <code>data</code> to specify what you need – this can b…
<ul>
<li>download – Display a download link</li>
<li>version – Output the current version number</li>
<li>forum – Display a link to the forum</li>
<li>wordpress – Display a link to the plugin in the WordPress.org repository</li>
</ul>
In the cases of the links you must specify text between the opening and closing shortcodes to link to.
There are 4 additional parameters…
<ul>
<li>name – Use this to specify the plugin name. This is a require parameter</li>
<li>target – If outputting a link this will assign a target to the output (default is _blank)</li>
<li>nofollow – If <code>Yes</code> then this will be a <code>nofollow</code> link. By default it won’t be</li>
<li>cache – By default any output will be cached for 50 minutes so that if you use this shortcode multiple times on a page the data will only be fetched once. Specify a different number (in minutes) to adjust this. Set to <code>No</code> to switch off caching entirely</li>
</ul>
An example of usage may be…
`[readme_info name=”YouTube Embed” data=”download”]Download YouTube Embed[/readme_info]’
<h3>Reviews & Mentions</h3>
<a href="http://wpcandy.com/reports/wp-readme-parser-plugin-converts-plugins-readme-into-blog-ready-xhtml?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+wpcandy+%28WPCandy+-+The+Best+of+WordPress%29" title="WPCandy" rel="nofollow ugc">WPCandy</a> – WP README Parser Plugin converts Plugin’s readme into blog-ready XHTML
<h3>Acknowledgements</h3>
Plugin README Parser uses <a href="http://michelf.com/projects/php-markdown/extra/" title="PHP Markdown Extra" rel="nofollow ugc">PHP Markdown Extra</a> by Michel Fortin.

Plugin README Parser

Sooner or later, if you develop WordPress plugins that are being offered here at the Plugin Library, you will need this plugin — simply because it makes it so easy to include those Markdown-based READMEs as part of your own website.

Sooner or later, someone will contact you with lots of questions about your own plugins, and you'll want to let them know, on your own website, what you have developed so far.

Sure, you can always do a copy & paste; sure, recent versions of WordPress are sort-of-able to parse Markdown, so, strictly speaking, you could do everything manually.

But with the Plugin README Parser, everything happens automagically. No need to set a reminder to yourself to update your own pages on your site — this plugin will automatically contact the Plugin Library and regenerate those pages based on the latest and greatest version of the README.

And, as a bonus, it even retrieves most of the assets — such as images etc. — that are used by the README to illustrate, for example, how your plugin installation works. This is not 100% trivial to do manually. It's good to have a fully automated tool that does all the homework on your behalf!

A must for WordPress plugin developers, amateurs or pros!


I use the plugin to display a the changelog from my plugin readme on my site's changes page very handy to only have one changelog to update!



Thanks,



Joe


Very Handy!


Works fine again!Thanks for keeping it up-to-date


Website Content in Page or Post – Embed website content in posts and pages vs Plugin README Parser