<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WordPress Craftsman &#187; admin</title>
	<atom:link href="https://www.wpcraftsman.com/tag/admin/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.wpcraftsman.com</link>
	<description>WordPress developer offering code snippets, tips and expert advice</description>
	<lastBuildDate>Sun, 01 Dec 2024 22:08:29 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.7.33</generator>
	<item>
		<title>Admin-triggered e-mail</title>
		<link>https://www.wpcraftsman.com/admin-triggered-e-mail/</link>
		<comments>https://www.wpcraftsman.com/admin-triggered-e-mail/#comments</comments>
		<pubDate>Fri, 09 Jan 2015 00:23:31 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[capability]]></category>
		<category><![CDATA[e-mail]]></category>
		<category><![CDATA[metaboxes]]></category>
		<category><![CDATA[PHPMailer]]></category>
		<category><![CDATA[ThickBox]]></category>
		<category><![CDATA[wp_editor]]></category>

		<guid isPermaLink="false">http://www.wpcraftsman.com/?p=117</guid>
		<description><![CDATA[Here&#8217;s something that touches on lots of topics. A &#8216;send e-mail&#8217; button within an admin panel, that opens up a ThickBox window with a standalone form and wp_editor. The metabox This requires two functions: one hooked into &#8216;add_meta_boxes&#8217; which calls the second, the metabox output function: Most of the second function builds the URL for [&#8230;]]]></description>
		<wfw:commentRss>https://www.wpcraftsman.com/admin-triggered-e-mail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disabling autosave</title>
		<link>https://www.wpcraftsman.com/disabling-autosave/</link>
		<comments>https://www.wpcraftsman.com/disabling-autosave/#comments</comments>
		<pubDate>Tue, 06 Jan 2015 00:29:13 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[Essentials]]></category>
		<category><![CDATA[Snippets]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[autosave]]></category>
		<category><![CDATA[custom post type]]></category>
		<category><![CDATA[post type]]></category>

		<guid isPermaLink="false">http://www.wpcraftsman.com/?p=97</guid>
		<description><![CDATA[You may already know, custom post types are the real workhorses of most customized WordPress themes. But often, they&#8217;re not meant to be read by the public; they&#8217;re functional things like &#8216;albums&#8217; or &#8216;reservations&#8217; or &#8216;index cards.&#8217; By default, WordPress tries to create auto-drafts of any post type when an author is adding / editing [&#8230;]]]></description>
		<wfw:commentRss>https://www.wpcraftsman.com/disabling-autosave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Draft status highlighting</title>
		<link>https://www.wpcraftsman.com/draft-status-highlighting/</link>
		<comments>https://www.wpcraftsman.com/draft-status-highlighting/#comments</comments>
		<pubDate>Mon, 05 Jan 2015 22:44:24 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[lists]]></category>
		<category><![CDATA[pagenow]]></category>
		<category><![CDATA[typenow]]></category>

		<guid isPermaLink="false">http://www.wpcraftsman.com/?p=78</guid>
		<description><![CDATA[A client wanted to display items with &#8216;Draft&#8217; status differently (gray color) in the admin list pages. Some might argue I&#8217;m a sloppy coder for using inline CSS, but there&#8217;s something I like about targeted post types, particularly in admin pages. Anyway, here&#8217;s a good example of using the &#8216;admin_footer&#8217; action and certain global variables, [&#8230;]]]></description>
		<wfw:commentRss>https://www.wpcraftsman.com/draft-status-highlighting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Members Only</title>
		<link>https://www.wpcraftsman.com/members-only/</link>
		<comments>https://www.wpcraftsman.com/members-only/#comments</comments>
		<pubDate>Thu, 24 Oct 2013 18:37:57 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[login]]></category>
		<category><![CDATA[members-only]]></category>
		<category><![CDATA[metaboxes]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[WooCommerce]]></category>

		<guid isPermaLink="false">http://www.wpcraftsman.com/?p=44</guid>
		<description><![CDATA[Recently, I was tasked with coding a &#8216;members only&#8217; site which required a login to view all but a few pages. This turned out to be a surprisingly simple task, so I thought I&#8217;d  share the code here. The job broke down into three tasks: Allow anyone who&#8217;s logged in or else redirect to the [&#8230;]]]></description>
		<wfw:commentRss>https://www.wpcraftsman.com/members-only/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
