@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix sioct: <http://rdfs.org/sioc/types#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix content: <http://purl.org/rss/1.0/modules/content/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

<https://shawfactor.com/?p=153916>
  a sioc:Post, sioct:BlogPost ;
  dc:title "Introducing LH Archived Post Status" ;
  dcterms:identifier 153916 ;
  dc:modified "2024-03-12T17:48:16Z"^^xsd:dateTime ;
  dc:created "2015-02-13T14:51:29Z"^^xsd:dateTime ;
  sioc:link <https://shawfactor.com/2015/02/13/introducing-lh-archived-post-status/> ;
  sioc:has_creator <https://shawfactor.com/author/1/#account> ;
  sioc:has_container <https://shawfactor.com/#posts> ;
  content:encoded """
<p class="wp-block-paragraph">LH Archived Post status is a WordPress extension that creates an additional posts status available for content that may no longer be relevant to most visitors but should be available publicly (perhaps for historical purposes).</p>



<p class="wp-block-paragraph">I built this plugin as UI needed this flexibility whilst using WordPress as a CMS. The plugin adds a new post status that enables posts and pages (and custom post types) to be archived. Archiving in this context means that the content is still publicly available but is not published on the front page of the site  or the feed. I was not satisfied with other archiving solutions which hid the content for all non logged in visitors and was not configurable.</p>



<!--more-->



<div class="wp-block-image"><figure class="alignleft"><a href="https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-post-status-dropdown.png"><img data-dominant-color="f4f5f7" data-has-transparency="false" style="--dominant-color: #f4f5f7;" loading="lazy" decoding="async" width="600" height="400" sizes="auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px" src="https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-post-status-dropdown.png" alt="archived-post-status-dropdown" class="wp-image-153918 not-transparent"/></a></figure></div>



<p class="wp-block-paragraph">Posts are available directly for any visitor but can have a custom message added that flags that they may no longer be relevant.</p>



<p class="wp-block-paragraph">WordPress’ default <a href="https://wordpress.org/documentation/article/post-status/" target="_blank" rel="noreferrer noopener">post statuses</a> currently work very much like an on/off switch as far as a finished post is concerned. Of the eight default statuses, Published is the only one that is public, while all the rest remain behind the curtain in various states of unreadiness. None of the statuses, apart from Published, adequately indicate that a post is complete or finished or its relevancy.</p>



<p class="wp-block-paragraph">Fortunately, WordPress makes it possible for developers to register their own <a href="https://wordpress.org/documentation/article/post-status/#custom-status" target="_blank" rel="noreferrer noopener">custom post statuses</a>, which is what I&#8217;ve done with this plugin.  It allows you to archive posts in the same way that you might archive email.</p>



<p class="wp-block-paragraph">Archived Post Status is compatible with posts, pages, and custom post types, giving you a wide array of possible use cases:</p>



<ul class="wp-block-list"><li>Archive pages or posts from a conference or event for editing and re-use next year</li><li>Archive real estate listings for records</li><li>Cycle portfolio content in and out of the site as necessary</li><li>Temporarily remove listings from a site that indexes businesses or organizations</li><li>Archive products to bring back for future use</li></ul>



<p class="wp-block-paragraph">While custom post types seem to be one of the most likely uses for this plugin, you may not want to have the archived status available to all post types.  Thisd can be done by slecting the appropriate posts types in the settings area.</p>



<div class="wp-block-image"><figure class="aligncenter"><a class="img-hyperlink" href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/01/archived-posts-list-screen.png" rel="prettyPhoto[37591]"><img decoding="async" src="https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-posts-list-screen1.png" alt="archived-posts-list-screen" class="wp-image-37614"/></a></figure></div>



<p class="wp-block-paragraph">If you need  to public archive completed posts, but hide them from the front page, feeds, and flag their state this simple plugin will do the trick. Installation instructions etc are available here:<br>
<a title="Archived Posts Status" href="https://lhero.org/portfolio/lh-archived-post-status/">https://lhero.org/portfolio/lh-archived-post-status/</a></p>
"""^^rdf:XMLLiteral ;
  sioc:content """
LH Archived Post status is a WordPress extension that creates an additional posts status available for content that may no longer be relevant to most visitors but should be available publicly (perhaps for historical purposes).



I built this plugin as UI needed this flexibility whilst using WordPress as a CMS. The plugin adds a new post status that enables posts and pages (and custom post types) to be archived. Archiving in this context means that the content is still publicly available but is not published on the front page of the site  or the feed. I was not satisfied with other archiving solutions which hid the content for all non logged in visitors and was not configurable.











Posts are available directly for any visitor but can have a custom message added that flags that they may no longer be relevant.



WordPress’ default post statuses currently work very much like an on/off switch as far as a finished post is concerned. Of the eight default statuses, Published is the only one that is public, while all the rest remain behind the curtain in various states of unreadiness. None of the statuses, apart from Published, adequately indicate that a post is complete or finished or its relevancy.



Fortunately, WordPress makes it possible for developers to register their own custom post statuses, which is what I&#8217;ve done with this plugin.  It allows you to archive posts in the same way that you might archive email.



Archived Post Status is compatible with posts, pages, and custom post types, giving you a wide array of possible use cases:



Archive pages or posts from a conference or event for editing and re-use next yearArchive real estate listings for recordsCycle portfolio content in and out of the site as necessaryTemporarily remove listings from a site that indexes businesses or organizationsArchive products to bring back for future use



While custom post types seem to be one of the most likely uses for this plugin, you may not want to have the archived status available to all post types.  Thisd can be done by slecting the appropriate posts types in the settings area.







If you need  to public archive completed posts, but hide them from the front page, feeds, and flag their state this simple plugin will do the trick. Installation instructions etc are available here:
https://lhero.org/portfolio/lh-archived-post-status/
""" ;
  sioc:topic <https://shawfactor.com/category/programming/>, <https://shawfactor.com/backlink_count/has-0-backlinks/>, <https://shawfactor.com/?taxonomy=author&term=cap-pete> ;
  sioc:attachment <https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-posts-list-screen1.png>, <https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-posts-list-screen.png>, <https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-post-status-dropdown.png> .

<https://shawfactor.com/author/1/#account> rdfs:seeAlso <https://shawfactor.com/author/1/?feed=lhrdf&format=turtle> .
<https://shawfactor.com/category/programming/> rdfs:seeAlso <https://shawfactor.com/category/programming/?feed=lhrdf&format=turtle> .
<https://shawfactor.com/backlink_count/has-0-backlinks/> rdfs:seeAlso <https://shawfactor.com/backlink_count/has-0-backlinks/?feed=lhrdf&format=turtle> .
<https://shawfactor.com/?taxonomy=author&term=cap-pete> rdfs:seeAlso <https://shawfactor.com/?taxonomy=author&term=cap-pete&feed=lhrdf&format=turtle> .
<https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-posts-list-screen1.png> rdfs:seeAlso <https://shawfactor.com/2015/02/13/introducing-lh-archived-post-status/archived-posts-list-screen1/?feed=lhrdf&format=turtle> .
<https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-posts-list-screen.png> rdfs:seeAlso <https://shawfactor.com/2015/02/13/introducing-lh-archived-post-status/archived-posts-list-screen/?feed=lhrdf&format=turtle> .
<https://shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-post-status-dropdown.png> rdfs:seeAlso <https://shawfactor.com/2015/02/13/introducing-lh-archived-post-status/archived-post-status-dropdown/?feed=lhrdf&format=turtle> .
