<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
		>
	<channel>
		<title>WordPress Ideas &#187; Topic: Idea: core, root file with version number ONLY for 3rd-party installers</title>
		<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers</link>
		<description>WordPress Ideas &#187; Topic: Idea: core, root file with version number ONLY for 3rd-party installers</description>
		<language>en-US</language>
		<pubDate>Sat, 25 May 2013 10:31:10 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1</generator>
				<atom:link href="http://wordpress.org/ideas/rss/topic/core-root-file-with-version-number-only-for-3rd-party-installers" rel="self" type="application/rss+xml" />

		<item>
			<title>Mark / t31os on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-17538</link>
			<pubDate>Tue, 20 Jul 2010 14:54:46 +0000</pubDate>
			<dc:creator>Mark / t31os</dc:creator>
			<guid isPermaLink="false">17538@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<blockquote><p>
Perhaps... but hosts that use something like Fantastico say that it cannot "know" when you've updated your WordPress application via the WordPress app itself (in the admin's auto-upgrade or otherwise)</p>
</blockquote>
<p>They should be able to detect that pretty easily, compare the version in <code>wp-includes/version.php</code> (or <code>get_option(&#039;version&#039;)</code>) to the version they have in their own file, if they don't match then the installation has been updated or modified.</p>
<p>That's a pretty simple thing to do, if your host can't manage a simple comparison check, i'd not trust them to install any application for me, let alone run upgrade routines.</p>
<p>So, my vote, not necessary, plugin territory.
</p>]]></description>
					</item>
		<item>
			<title>Partnersuche on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-17535</link>
			<pubDate>Tue, 20 Jul 2010 14:38:43 +0000</pubDate>
			<dc:creator>Partnersuche</dc:creator>
			<guid isPermaLink="false">17535@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>I also can't see any benefit in including a core, root level file with the current version of WordPress for 3rd-party installers.
</p>]]></description>
					</item>
		<item>
			<title>Mark on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-16706</link>
			<pubDate>Mon, 12 Apr 2010 21:15:36 +0000</pubDate>
			<dc:creator>Mark</dc:creator>
			<guid isPermaLink="false">16706@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Agree with the above posters: it is something that the 3rd party apps should support and there is no reason they couldn't do it as it is now.
</p>]]></description>
					</item>
		<item>
			<title>Ipstenu (Mika Epstein) on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-16448</link>
			<pubDate>Fri, 26 Mar 2010 15:38:06 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">16448@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>You could write a plugin that scraps the version and updates the fantversion.php file, but this is a flaw in the 3rd party, NOT in WP.  Also you hit the slippery slope with this. How many 3rd party installers should WP support?</p>
<p>IMO: None.
</p>]]></description>
					</item>
		<item>
			<title>syncbox on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-13406</link>
			<pubDate>Wed, 16 Sep 2009 00:45:43 +0000</pubDate>
			<dc:creator>syncbox</dc:creator>
			<guid isPermaLink="false">13406@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Perhaps... but hosts that use something like Fantastico say that it cannot "know" when you've updated your WordPress application via the WordPress app itself (in the admin's auto-upgrade or otherwise)</p>
<p>I've personally seen this 4 or 5 times since that ability was added to WordPress. Now normally, I'd go into a cpanel and use the Fantastico app itself to upgrade, but with the great new (and fairly reliable) function of doing this in the admin, why bother with Fantastico? (or whatever installer your host uses)?</p>
<p>All of them write their own file to keep track of the version of WordPress THEY install (eg. fantversion.php) They don't monitor YOUR WordPress application to determine if you need to upgrade... they simply look at their file and if they are now offering a later version, tell you need to upgrade... even if you don't!</p>
<p>Of course, you can manually modify THEIR file. Add another task to your list for every upgrade. I'd RATHER not. If a file IN the core of WP behaved like fantversion.php, I believe these companies would take advantage of that and read it.</p>
<p>It seems a logical companion to the internal auto upgrade functions. and by making it external to the admin and a core-level file that only does this one thing, it shouldn't be exploitable.
</p>]]></description>
					</item>
		<item>
			<title>Peter Westwood on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-13323</link>
			<pubDate>Mon, 07 Sep 2009 21:15:14 +0000</pubDate>
			<dc:creator>Peter Westwood</dc:creator>
			<guid isPermaLink="false">13323@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>Also - is there a clear definition of what the different 3rd party install/upgraders expect to find - if so I suspect a plugin could be written to achieve this.
</p>]]></description>
					</item>
		<item>
			<title>Julian Widya Perdana on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-13315</link>
			<pubDate>Mon, 07 Sep 2009 08:40:11 +0000</pubDate>
			<dc:creator>Julian Widya Perdana</dc:creator>
			<guid isPermaLink="false">13315@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>i have not faced this problem before
</p>]]></description>
					</item>
		<item>
			<title>Peter Westwood on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-13312</link>
			<pubDate>Mon, 07 Sep 2009 06:24:56 +0000</pubDate>
			<dc:creator>Peter Westwood</dc:creator>
			<guid isPermaLink="false">13312@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p>I really don't see the point of this.</p>
<p>The WordPress version number is already available in a well known file in an easy to parse format.</p>
<p>Why do they need another file?
</p>]]></description>
					</item>
		<item>
			<title>syncbox on "Idea: core, root file with version number ONLY for 3rd-party installers"</title>
			<link>http://wordpress.org/ideas/topic/core-root-file-with-version-number-only-for-3rd-party-installers#post-13280</link>
			<pubDate>Fri, 04 Sep 2009 15:37:12 +0000</pubDate>
			<dc:creator>syncbox</dc:creator>
			<guid isPermaLink="false">13280@http://wordpress.org/ideas/</guid>
			<description><![CDATA[<p><strong>I am proposing a core, root level file with the current version of WordPress listed in it that could be updated by any in-WP upgrade AND by any 3rd-party installer/upgrader. This would not be what WordPress reads to list the version AND would have NO other function, so would be no security risk. </strong></p>
<p>Per Midphase and other companies, third-party installers like Fantastico cannot determine the version of WordPress installed if you upgrade FROM WordPress rather than their application -- in their process, they update a (for example) a fantversion.php file (I am told this is how all 3rd-party installers do it).</p>
<p>This results in the scenario of a control panel saying you have an older version (whichever they last recorded) and that you need to upgrade even if you have the latest version.
</p>]]></description>
					</item>

	</channel>
</rss>
