<?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>Bugfixing Archives - this is how i code</title>
	<atom:link href="https://thisishowicode.com/category/bugfixing/feed/" rel="self" type="application/rss+xml" />
	<link>https://thisishowicode.com/category/bugfixing/</link>
	<description>my personal journey through creating with code</description>
	<lastBuildDate>Sat, 06 Jul 2024 17:03:22 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>Lint PHP version breaking changes with phpcs</title>
		<link>https://thisishowicode.com/lint-php-version-breaking-changes-with-phpcs/</link>
					<comments>https://thisishowicode.com/lint-php-version-breaking-changes-with-phpcs/#respond</comments>
		
		<dc:creator><![CDATA[Jason M]]></dc:creator>
		<pubDate>Sat, 06 Jul 2024 17:02:41 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Bugfixing]]></category>
		<category><![CDATA[How to]]></category>
		<guid isPermaLink="false">https://thisishowicode.com/?p=1266</guid>

					<description><![CDATA[<p>Upgrading the php version on your server doesn&#8217;t come without risks. With all coding languages, old features can become deprecated or even removed. Trawling through a codebase manually to check it&#8217;s still all going to work doesn&#8217;t sound fun. So this article shows how to lint php version breaking changes. Prerequisites You&#8217;ll need PHP&#8217;s equivalent [&#8230;]</p>
<p>The post <a href="https://thisishowicode.com/lint-php-version-breaking-changes-with-phpcs/">Lint PHP version breaking changes with phpcs</a> appeared first on <a href="https://thisishowicode.com">this is how i code</a>.</p>
]]></description>
		
					<wfw:commentRss>https://thisishowicode.com/lint-php-version-breaking-changes-with-phpcs/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Adblock and your stylesheet &#8211; they don&#8217;t play nice</title>
		<link>https://thisishowicode.com/adblock-and-your-stylesheet-they-dont-play-nice/</link>
					<comments>https://thisishowicode.com/adblock-and-your-stylesheet-they-dont-play-nice/#respond</comments>
		
		<dc:creator><![CDATA[Jason M]]></dc:creator>
		<pubDate>Sun, 05 Sep 2021 11:33:50 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Bugfixing]]></category>
		<category><![CDATA[Front End Development]]></category>
		<guid isPermaLink="false">http://thisishowicode.com/?p=701</guid>

					<description><![CDATA[<p>Have you ever had a situation where your css just doesn&#8217;t seem to be working. You know you added the styles, but they just refuse to show up in the inspector? Fun fact: It might just be your browser&#8217;s adblock stylesheet. What&#8217;s adblock doing to my stylesheet? Hopefully you use good namespacing when you create [&#8230;]</p>
<p>The post <a href="https://thisishowicode.com/adblock-and-your-stylesheet-they-dont-play-nice/">Adblock and your stylesheet &#8211; they don&#8217;t play nice</a> appeared first on <a href="https://thisishowicode.com">this is how i code</a>.</p>
]]></description>
		
					<wfw:commentRss>https://thisishowicode.com/adblock-and-your-stylesheet-they-dont-play-nice/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>WordPress HTTPS Redirect Problem? Destroy it Like a Boss</title>
		<link>https://thisishowicode.com/wordpress-https-redirect-problem-fix/</link>
					<comments>https://thisishowicode.com/wordpress-https-redirect-problem-fix/#respond</comments>
		
		<dc:creator><![CDATA[Jason M]]></dc:creator>
		<pubDate>Thu, 13 Aug 2020 15:55:23 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Bugfixing]]></category>
		<category><![CDATA[WordPress]]></category>
		<guid isPermaLink="false">http://thisishowicode.com/?p=339</guid>

					<description><![CDATA[<p>The last time I had to update a WordPress website for SSL delivery, I thought it would be quick and easy. But a couple of things tripped me up along the way. I&#8217;ve documented my particular WordPress https redirect problem here, in the hope that you don&#8217;t run into the same issues I did. Let&#8217;s [&#8230;]</p>
<p>The post <a href="https://thisishowicode.com/wordpress-https-redirect-problem-fix/">WordPress HTTPS Redirect Problem? Destroy it Like a Boss</a> appeared first on <a href="https://thisishowicode.com">this is how i code</a>.</p>
]]></description>
		
					<wfw:commentRss>https://thisishowicode.com/wordpress-https-redirect-problem-fix/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Developer QA Checklist : Make Less Work Come Back to You</title>
		<link>https://thisishowicode.com/developer-qa-checklist-make-less-work-come-back-to-you/</link>
					<comments>https://thisishowicode.com/developer-qa-checklist-make-less-work-come-back-to-you/#respond</comments>
		
		<dc:creator><![CDATA[Jason M]]></dc:creator>
		<pubDate>Mon, 06 Apr 2020 22:42:04 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Bugfixing]]></category>
		<category><![CDATA[Front End Development]]></category>
		<guid isPermaLink="false">http://thisishowicode.com/?p=42</guid>

					<description><![CDATA[<p>I&#8217;ve always used a developer QA checklist, when I&#8217;ve worked on web projects. This article covers some basics like fixing markup errors and console errors. You also need to consider some other things before passing it onto a QA team. Markup Validation Optimisation Accessibility Testing Cross Browser Testing Check assets Form Testing Search Engine Optimisation [&#8230;]</p>
<p>The post <a href="https://thisishowicode.com/developer-qa-checklist-make-less-work-come-back-to-you/">Developer QA Checklist : Make Less Work Come Back to You</a> appeared first on <a href="https://thisishowicode.com">this is how i code</a>.</p>
]]></description>
		
					<wfw:commentRss>https://thisishowicode.com/developer-qa-checklist-make-less-work-come-back-to-you/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>WordPress Beginner tips: Gotchas when Starting out in WordPress Development</title>
		<link>https://thisishowicode.com/wordpress-beginner-tips-starting-out-in-wordpress-development/</link>
					<comments>https://thisishowicode.com/wordpress-beginner-tips-starting-out-in-wordpress-development/#respond</comments>
		
		<dc:creator><![CDATA[Jason M]]></dc:creator>
		<pubDate>Sat, 04 Apr 2020 08:07:32 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Bugfixing]]></category>
		<category><![CDATA[WordPress]]></category>
		<guid isPermaLink="false">http://thisishowicode.com/?p=85</guid>

					<description><![CDATA[<p>I really enjoy working on WordPress projects. For every one I kick out of the gate, the more comfortable I am with using it. However, getting to where I am now meant learning a few things first to &#8216;git gud&#8217;. Here are some wordpress beginner tips. Permalinks are your friend Sometimes, when you create custom [&#8230;]</p>
<p>The post <a href="https://thisishowicode.com/wordpress-beginner-tips-starting-out-in-wordpress-development/">WordPress Beginner tips: Gotchas when Starting out in WordPress Development</a> appeared first on <a href="https://thisishowicode.com">this is how i code</a>.</p>
]]></description>
		
					<wfw:commentRss>https://thisishowicode.com/wordpress-beginner-tips-starting-out-in-wordpress-development/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Test for Bugs and Other Issues in a Team Environment</title>
		<link>https://thisishowicode.com/how-to-test-for-bugs-and-other-issues-in-a-team-environment/</link>
					<comments>https://thisishowicode.com/how-to-test-for-bugs-and-other-issues-in-a-team-environment/#respond</comments>
		
		<dc:creator><![CDATA[Jason M]]></dc:creator>
		<pubDate>Wed, 26 Feb 2020 10:07:45 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Bugfixing]]></category>
		<category><![CDATA[Workflow]]></category>
		<guid isPermaLink="false">http://thisishowicode.com/?p=128</guid>

					<description><![CDATA[<p>This article looks how to test for bugs during web development, and whilst testing a website for bugs during the build process. I look at some of the things I&#8217;ve done in the places I&#8217;ve worked. This is primarily aimed at front end development, but I guess it could also apply to some back end [&#8230;]</p>
<p>The post <a href="https://thisishowicode.com/how-to-test-for-bugs-and-other-issues-in-a-team-environment/">How to Test for Bugs and Other Issues in a Team Environment</a> appeared first on <a href="https://thisishowicode.com">this is how i code</a>.</p>
]]></description>
		
					<wfw:commentRss>https://thisishowicode.com/how-to-test-for-bugs-and-other-issues-in-a-team-environment/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
