glindr

Glindr is a fast growing repository of content in the fashion blogging space. Now, you can be a part of it 
with the Glindr plugin.
The Glindr plugin allows you to quickly and easily apply for syndication to Glindr. Once you submit your request, 
a Glindr administrator will review your information and Approve or Decline your site. You can keep track of your 
application status right from your blog.
After your request is approved, you’ll be able to easily submit your content to Glindr for syndication and reap 
all the benefits.

Glindr

Apply for access and start syndicating your posts to Glindr today!

vthierry

This plugins offers the following “ground” functionnalities:
<ul>
<li>
<ol>
<li>Display the content of a post or page without any header, sidebar and footer.</li>
</ol>
</li>
<li>
<ol>
<li>Importing the content from an external web site</li>
</ol>
</li>
<li>
<ol>
<li>Importing an internal content of the wordpress site</li>
</ol>
</li>
<li>
<ol>
<li>A few other deprecated functionalities</li>
</ol>
</li>
</ul>
<h4>1. Displaying a post or page without any header, sidebar and footer</h4>
In order to render the raw content of a post or page without any header, sidebar and footer use the link:
<pre><code>http://#mywordpressadress?httpsyndication&p=#post_or_page_id&title=#1_or_0
</code></pre>
where:
<ul>
<li><code>#mywordpressadress</code> is the wordpress web site adress.</li>
<li><code>#post_or_page_id</code> is the post or page id (you can read the post id in the http link when you edit the post).</li>
<li><code>#1_or_0</code> defines whether the post title (enclosed in a <code><h1></code> HTML tag) is displayed (default is <code>1</code>, i.e., true).</li>
</ul>
Remarks:
<ul>
<li>In this text all words prefixed by <code>#</code>, e.g., <code>#tag</code> or <code>#id</code> correspond to a variable, e.g., <code>#tag</code> means any tag name or <code>#id</code> means an ID label.</li>
<li>The post content is exported after filtering.</li>
</ul>
<h4>2. Importing the content from an external web site</h4>
In order to import an external a post or page contents in another post or page, use the following shortcode:
<pre><code>[import url="#external_resource_location" ]
</code></pre>
where:
<ul>
<li><code>#external_resource_location</code> is the external web site http location.</li>
</ul>
Inside the <code>[import ..]</code> shortcode, the following options allows to select and adjust the content to import:
<ul>
<li>Content selection:
<ul>
<li><code>body=1</code> : in order to only import the <code><body..>..</body></code> part of the <code><html><head>..</head><body..>..</body></html></code> page.</li>
<li><code>tag_id=#id</code> : only extract the content of the 1st tag of the given id, i.e. the <code><#tag id="#id">..</#tag></code> part, where <code>#tag</code> is any tag (e.g., <code>div</code>, <code>span</code>, ..). </li>
<li><code>tag_class=#class</code> : only extract the content of the 1st tag of the given class, i.e. the <code><#tag class="#class">..</#tag></code> part, where <code>#tag</code> is any tag (e.g., <code>div</code>, <code>span</code>, ..); the value <code>#class</code> can be a regex to deal with multiple defined classes. </li>
<li><code>tag_name=#name</code> : only extract the content of all tags of the given name, i.e. the <code><#name ..>..</#name></code> part (for code safety only 100 tags can be extracted). </li>
</ul>
</li>
<li>Content filtering:
<ul>
<li><code>noscript=1</code> : in order to delete all <code><script..>..</script></code> parts, avoiding any active JavaScript running from the imported HTML.</li>
<li><code>raw_href=1</code> : in order to provide raw href values, instead of properly relocating relative href in the source HTML code, as done by default.</li>
<li><code>mediawiki=1</code> : adds the <code>?printable=yes&action=render</code> query to the URL, in order to properly syndicate mediawiki sites.</li>
<li><code>style=#style</code> or <code>class=#class</code> allows to encapsulate the content in a <code><div .</code> with customized class and/or style attribute.</li>
</ul>
</li>
</ul>
Example :
<ul>
<li><code>[import url="http://localhost/wordpress/?cat=4687" tag_id="content" style="width:100%"]</code> allows to import a category rendering with another page.</li>
</ul>
How can i know with id, tag or class to select?
<ul>
<li>Display the page you want to import and consider the part of the page you want to select</li>
<li>Use the right-button to select Inspect or Inspect Element in the context menu, that will show the page source at the choosen position</li>
<li>Look around to find the <div or any other container with the proper id, tag or class (providing it is the first tag or class of this kind in the text) </li>
<li>Then report the attribute value in your import short-code</li>
</ul>
Remarks:
<ul>
<li>If the external content can not be read, an error message is produced in the page output.</li>
<li>The external content target page must be written in correct HTML (e.g., attributes value must be between quotes), otherwise the parsing may fail.</li>
<li>This functionality requires the <code>allow_url_fopen</code> option to be validated in the PHP configuration, otherwise an error message is produced in the page output.</li>
<li>By construction the import is “dynamic”, i.e., each time the page is loaded, the external content is queried and inserted in the page. Good news, to be sure to have an updated information. Bad news, if the external web site is down or slowed down. You may consider having a <a href="https://wordpress.org/plugins/wp-super-cache" rel="ugc">cache mechanism</a> to overcome related caveats.</li>
<li>The external HTML content is imported with its external CSS class styles. For another WordPress site, the match is expected to be good. If this is an exotic content management system, the situation is less obvious: Local CSS patch is likely required, or some additional content filter has to be hooked.</li>
<li>There is no way to prevent from infinite syndication loops between sites (e.g., a site with a page importing an external page that itself import the inquiring page).</li>
<li>Unless using <code>noscript=1</code>, the external JavaScript code is imported. Though security flaws are normally not to be expected considering usual JavaScript security rules, clearly malicious code can easily hugely perturb the page rendering.</li>
<li>The <a href="https://codex.wordpress.org/Embeds" rel="nofollow ugc">embed</a> shortcode is a core WordPress feature. It can embed content from many resources via direct link, and the <a href="http://www.w3schools.com/tags/tag_iframe.asp" rel="nofollow ugc">iframe</a> allows to safely and obviously include any external site page in “frame”. The <a href="https://wordpress.org/plugins/iframe" rel="ugc">iframe plugin</a> works well and properly make the job. The present import is a 3rd alternative, to be preferred when the former fail or mixing pages content is required.</li>
</ul>
<h4>3. Importing an internal content of the wordpress site</h4>
In order to import a post or page contents in another post or page, use the following shortcode:
<ul>
<li><code>[import id="#post_or_page_id"]</code> to include the filtered content of another post or page in the current content.</li>
<li><code>[import id="#post_or_page_id" content=1]</code> to include the raw (with shortcode expanded, but not content filter applied) of another post or page in the current content (to be used only if required).</li>
<li><code>[import id="#post_or_page_id" title=1]</code> to include the title of another post or page in the current content.</li>
</ul>
where:
<ul>
<li><code>#post_or_page_id</code> is the post or page id (you can read the post id in the http link when you edit the post).</li>
</ul>
Remarks:
<ul>
<li>This avoids spurious import, e.g. of social media buttons (contrary to usual <a href="https://wordpress.org/plugins/search.php?q=include" rel="ugc">include plugins</a>).</li>
<li>Shortcode recursion is managed (i.e. stopped when an infinite loop is detected).</li>
</ul>
<h4>4. A few other deprecated functionalities</h4>
These additonal functionalities are deprecated but still available for backward compatibility
<ul>
<li>
Using the <code>?w=#id</code> query allows to refer any page, post or archive by its numerical index.
</li>
<li>
Using the <code>[import wform=1 label="#theinputlabel"]</code> shortcode, allows to insert a small input field to switch to any page, post or archive given its numerical index.
</li>
<li>
Using the <code>[import banner="#page_id" url="#external_url"]#link-text[/import]</code> shortcode allows to display another site page in an iframe, with a banner from this site sitting on top of the external page. Inside the <code>[import ..]</code> shortcode, the following options allows to adjust the behavior.
<ul>
<li><code>header=false</code> : in order to include or not the usual site header().php on the top of the banner</li>
<li><code>height=1000</code> : in order to adjust the height of the frame for very long external pages.</li>
<li><code>newtab=1</code> : in order to open the page and banner in a new browser window.</li>
<li><code>style="border:none;"</code> : in order to adjust the height of the frame for very long external pages.</li>
</ul>
</li>
</ul>

http-syndication

This plugins offers the following "ground" functionnalities:

Glindr vs http-syndication