<?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>Alex Mansfield</title>
	<atom:link href="https://alexmansfield.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://alexmansfield.com</link>
	<description>WordPress Developer</description>
	<lastBuildDate>Tue, 02 Sep 2025 21:13:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://alexmansfield.com/wp-content/uploads/2020/06/blank-favicon.png</url>
	<title>Alex Mansfield</title>
	<link>https://alexmansfield.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to keep the menu visible in the WordPress editor</title>
		<link>https://alexmansfield.com/hacks/prevent-fullscreen-gutenberg/</link>
					<comments>https://alexmansfield.com/hacks/prevent-fullscreen-gutenberg/#comments</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Tue, 02 Sep 2025 21:12:12 +0000</pubDate>
				<category><![CDATA[Hacks]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1695</guid>

					<description><![CDATA[For some reason, the default WordPress editing experience hides the dashboard menu. This can be confusing for beginners (&#8220;How do I exit the editor?&#8221;) and annoying for power users (&#8220;Why so many clicks to get to where I want to go?&#8221;). Yes, there is a user-configurable option for whether or not to show the dashboard [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>For some reason, the default WordPress editing experience hides the dashboard menu. This can be confusing for beginners (“How do I exit the editor?”) and annoying for power users (“Why so many clicks to get to where I want to go?”). Yes, there is a user-configurable option for whether or not to show the dashboard menu in the editor. However, I don’t expect a beginner to know about that setting…</p>
<p><a href="https://alexmansfield.com/hacks/prevent-fullscreen-gutenberg/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/hacks/prevent-fullscreen-gutenberg/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>How to hide WordPress content from search results</title>
		<link>https://alexmansfield.com/wordpress/hide-wordpress-content-from-search-results/</link>
					<comments>https://alexmansfield.com/wordpress/hide-wordpress-content-from-search-results/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Tue, 20 May 2025 20:31:11 +0000</pubDate>
				<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1676</guid>

					<description><![CDATA[While it is easy to drop in some code to hide content from search results, it can have some unintended consequences because WordPress uses the same search query loop for both frontend and backend searches. Hide content universally To hide content on both the front and backend, we can use the following code: function prefix_exclude_from_search( [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>While it is easy to drop in some code to hide content from search results, it can have some unintended consequences because WordPress uses the same search query loop for both frontend and backend searches. To hide content on both the front and backend, we can use the following code: Notice on line 3 there is an array. This array contains the IDs of content that will be hidden from search…</p>
<p><a href="https://alexmansfield.com/wordpress/hide-wordpress-content-from-search-results/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/wordpress/hide-wordpress-content-from-search-results/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Website Blueprint Settings</title>
		<link>https://alexmansfield.com/bricks-builder/website-blueprint-settings/</link>
					<comments>https://alexmansfield.com/bricks-builder/website-blueprint-settings/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Thu, 15 May 2025 16:05:53 +0000</pubDate>
				<category><![CDATA[AutomaticCSS]]></category>
		<category><![CDATA[Bricks Builder]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1671</guid>

					<description><![CDATA[While it is incredibly useful to use a blueprint site as a starting point for all new website development projects, it also makes it easy to forget what our default site settings are. This article is part checklist, part reminder what default settings I use for reference when create a new blueprint site. Body width [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>While it is incredibly useful to use a blueprint site as a starting point for all new website development projects, it also makes it easy to forget what our default site settings are. This article is part checklist, part reminder what default settings I use for reference when create a new blueprint site. Since there are a wide variety of monitor sizes, it is often useful to set a maximum width…</p>
<p><a href="https://alexmansfield.com/bricks-builder/website-blueprint-settings/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/bricks-builder/website-blueprint-settings/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>External Slide Navigation in Bricks Builder</title>
		<link>https://alexmansfield.com/bricks-builder/external-slide-navigation-in-bricks-builder/</link>
					<comments>https://alexmansfield.com/bricks-builder/external-slide-navigation-in-bricks-builder/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Sat, 22 Mar 2025 02:00:39 +0000</pubDate>
				<category><![CDATA[Bricks Builder]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1665</guid>

					<description><![CDATA[Bricks Builder has a flexible slider module called &#8220;Slides (Nestable)&#8221; which allows each slide to be built from scratch within the builder. In some cases, it may be necessary to create external tab-like navigation. In order for the following code to work properly, we need 3 things: The second half of the slider ID. By [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Bricks Builder has a flexible slider module called “Slides (Nestable)” which allows each slide to be built from scratch within the builder. In some cases, it may be necessary to create external tab-like navigation. In order for the following code to work properly, we need 3 things: You’ll notice the 3 variables at the top of the code correspond with the 3 items in the numbered list I just…</p>
<p><a href="https://alexmansfield.com/bricks-builder/external-slide-navigation-in-bricks-builder/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/bricks-builder/external-slide-navigation-in-bricks-builder/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Parallels Desktop (Solved): The password you use to log into your account no longer matches your login keyring</title>
		<link>https://alexmansfield.com/linux/parallels-desktop-solved-the-password-you-use-to-log-into-your-account-no-longer-matches-your-login-keyring/</link>
					<comments>https://alexmansfield.com/linux/parallels-desktop-solved-the-password-you-use-to-log-into-your-account-no-longer-matches-your-login-keyring/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Sun, 26 Jan 2025 06:39:49 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1655</guid>

					<description><![CDATA[When using a Linux guest OS on Parallels, I was occasionally getting the following error, along with a password input: The password you use to log into your account no longer matches your login keyring However, when entering the login password into the prompt, it fails. After going down this rabbit hole for a day [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>When using a Linux guest OS on Parallels, I was occasionally getting the following error, along with a password input: However, when entering the login password into the prompt, it fails. After going down this rabbit hole for a day or two, I cam across an old forum post with an answer that worked for me. Instead of typing your login password, just type “parallels” instead. It seems that by…</p>
<p><a href="https://alexmansfield.com/linux/parallels-desktop-solved-the-password-you-use-to-log-into-your-account-no-longer-matches-your-login-keyring/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/linux/parallels-desktop-solved-the-password-you-use-to-log-into-your-account-no-longer-matches-your-login-keyring/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Dealing with form spam</title>
		<link>https://alexmansfield.com/general/dealing-with-form-spam/</link>
					<comments>https://alexmansfield.com/general/dealing-with-form-spam/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Thu, 23 Jan 2025 02:49:49 +0000</pubDate>
				<category><![CDATA[General]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1652</guid>

					<description><![CDATA[Let&#8217;s start by looking at the timeline of a form submission, and then we can look at what can be done to combat spam at each section of the timeline. A user (or a bot) visits a page on our site. The user (or bot) fills out and submits the form. Our system processes the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Let’s start by looking at the timeline of a form submission, and then we can look at what can be done to combat spam at each section of the timeline. Now let’s look at our options: If the visitor is a human, this is probably not a good time to try to block them, because they will most likely be indistinguishable from a normal user. However, if the visitor is a bot, there are a number of…</p>
<p><a href="https://alexmansfield.com/general/dealing-with-form-spam/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/general/dealing-with-form-spam/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Remove formatting when pasting text by default</title>
		<link>https://alexmansfield.com/beaver-builder/remove-formatting-when-pasting-text-by-default/</link>
					<comments>https://alexmansfield.com/beaver-builder/remove-formatting-when-pasting-text-by-default/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Sat, 16 Mar 2024 11:37:58 +0000</pubDate>
				<category><![CDATA[Beaver Builder]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1643</guid>

					<description><![CDATA[When pasting text into the WordPress classic editor, the default behavior is to keep the formatting of the pasted content. The keeps things like links working, but it also keeps font colors, sizes, and other formatting that may be undesirable. To change the default behavior so that by default all formatting is removed, we can [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>When pasting text into the WordPress classic editor, the default behavior is to keep the formatting of the pasted content. The keeps things like links working, but it also keeps font colors, sizes, and other formatting that may be undesirable. To change the default behavior so that by default all formatting is removed, we can simply use the following lines of code: This works with the…</p>
<p><a href="https://alexmansfield.com/beaver-builder/remove-formatting-when-pasting-text-by-default/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/beaver-builder/remove-formatting-when-pasting-text-by-default/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Adding a menu item to the Beaver Builder admin menu</title>
		<link>https://alexmansfield.com/beaver-builder/adding-a-menu-item-to-the-beaver-builder-admin-menu/</link>
					<comments>https://alexmansfield.com/beaver-builder/adding-a-menu-item-to-the-beaver-builder-admin-menu/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Sun, 28 Jan 2024 11:31:34 +0000</pubDate>
				<category><![CDATA[Beaver Builder]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1639</guid>

					<description><![CDATA[Beaver Builder has a top level menu item in the WordPress admin menu. However, it doesn&#8217;t allow new menu items to be added using the standard WordPress methods. After reading a bunch of the Beaver Builder code base, I was able to find the filter that handles the submenu items in the /extensions/fl-builder-user-templates/classes/class-fl-builder-user-templates-admin-menu.php file. The [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Beaver Builder has a top level menu item in the WordPress admin menu. However, it doesn’t allow new menu items to be added using the standard WordPress methods. After reading a bunch of the Beaver Builder code base, I was able to find the filter that handles the submenu items in the /extensions/fl-builder-user-templates/classes/class-fl-builder-user-templates-admin-menu.php file.</p>
<p><a href="https://alexmansfield.com/beaver-builder/adding-a-menu-item-to-the-beaver-builder-admin-menu/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/beaver-builder/adding-a-menu-item-to-the-beaver-builder-admin-menu/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Improving Beaver Builder&#8217;s Video Lightbox</title>
		<link>https://alexmansfield.com/css/improving-beaver-builders-video-lightbox/</link>
					<comments>https://alexmansfield.com/css/improving-beaver-builders-video-lightbox/#comments</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Sat, 09 Dec 2023 06:18:28 +0000</pubDate>
				<category><![CDATA[Beaver Builder]]></category>
		<category><![CDATA[CSS]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1632</guid>

					<description><![CDATA[For some reason, Beaver Builder&#8217;s video lightbox opens quite small, even on large screens. I wanted the lightbox to take up most of the screen, so I used the following CSS to make that happen: .mfp-iframe-holder .mfp-content { max-width: 95%; aspect-ratio: 16/9; height: auto; } @media (min-aspect-ratio: 16/9) { .mfp-iframe-holder .mfp-content { height: 95%; aspect-ratio: [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>For some reason, Beaver Builder’s video lightbox opens quite small, even on large screens. I wanted the lightbox to take up most of the screen, so I used the following CSS to make that happen: …and while I was at it I thew in the following code to improve the look and placement of the lightbox close icon: Please note: this code is specific to videos with a 16/9 aspect ratio.</p>
<p><a href="https://alexmansfield.com/css/improving-beaver-builders-video-lightbox/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/css/improving-beaver-builders-video-lightbox/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
			</item>
		<item>
		<title>Disable WordPress Comments Programmatically</title>
		<link>https://alexmansfield.com/wordpress/disable-wordpress-comments-programmatically/</link>
					<comments>https://alexmansfield.com/wordpress/disable-wordpress-comments-programmatically/#respond</comments>
		
		<dc:creator><![CDATA[alexmansfield]]></dc:creator>
		<pubDate>Thu, 31 Aug 2023 06:12:23 +0000</pubDate>
				<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">https://alexmansfield.trustypress.dev/?p=1627</guid>

					<description><![CDATA[This post exists primarily for my own future reference. Sometimes I want to disable all comments without using a plugin. The code below borrows heavily (maybe even copies blatantly!) from a couple GitHub repositories I came across a while ago: &#8211; https://gist.github.com/mattclements/eab5ef656b2f946c4bfb &#8211; https://gist.github.com/alexwoollam/2f4bcd4eb4740eb49562131290248f26 Here&#8217;s the code: /** * Disable post type support for comments [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>This post exists primarily for my own future reference. Sometimes I want to disable all comments without using a plugin. The code below borrows heavily (maybe even copies blatantly!) from a couple GitHub repositories I came across a while ago: – https://gist.github.com/mattclements/eab5ef656b2f946c4bfb – https://gist.github.com/alexwoollam/2f4bcd4eb4740eb49562131290248f26 Here’s the code…</p>
<p><a href="https://alexmansfield.com/wordpress/disable-wordpress-comments-programmatically/" rel="nofollow">Source</a></p>]]></content:encoded>
					
					<wfw:commentRss>https://alexmansfield.com/wordpress/disable-wordpress-comments-programmatically/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
