<?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>404 errors &#8211; Blogvaria</title>
	<atom:link href="https://blog.evaria.com/key/404-errors/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.evaria.com</link>
	<description>The personal pages</description>
	<lastBuildDate>Wed, 15 Apr 2009 11:19:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>
<site xmlns="com-wordpress:feed-additions:1">1077093</site>	<item>
		<title>Custom WP forms and 404 errors</title>
		<link>https://blog.evaria.com/2009/custom-wp-forms-and-404-errors/</link>
		
		<dc:creator><![CDATA[Thomas]]></dc:creator>
		<pubDate>Wed, 15 Apr 2009 11:19:55 +0000</pubDate>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[404 errors]]></category>
		<category><![CDATA[custom WP forms]]></category>
		<guid isPermaLink="false">http://blog.evaria.com/?p=1093</guid>

					<description><![CDATA[Recently I&#8217;ve been building various custom form plugins for WordPress. And even if it all seemed to work properly I would get an &#8220;404 page not found&#8221; error instead of &#8230; ]]></description>
										<content:encoded><![CDATA[<p>Recently I&#8217;ve been building various custom form plugins for WordPress. And even if it all seemed to work properly I would get an &#8220;404 page not found&#8221; error instead of my &#8220;thank you page&#8221;. I know I&#8217;m not the only one as this <a href="http://wordpress.org/support/topic/209747" target="_blank">has been reported before</a>.</p>
<p>The reason this happens is basically due to the fact that some form values should NOT be used as they will cause a conflict with the variables passed by WordPress itself. Among them are values like: name, day, year etc.</p>
<p>So, if you are running in to this issue/bug yourself you can isolate the &#8220;forbidden&#8221; values by simply filling in one value on the form after another and performing a quick submit between each and every one. As soon as you get the 404 error you will know you&#8217;ve found one (of potentially several) values you will have to rename.</p>
<p>What you need to do then is give your form field (e.g. text input, textarea or select box) a new name. A field named &#8220;year&#8221; could then be passed on as &#8220;dyear&#8221; or similar. Nothing more to it actually.</p>
<p>Please feel free to comment should I&#8217;ve left something out, or leave a thank you if I saved you some headaches and time <img src="https://s.w.org/images/core/emoji/16.0.1/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p>Happy coding!</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1093</post-id>	</item>
	</channel>
</rss>
