<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.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>Gravity Support Forums Topic: Path errors on preview.php</title>
		<link>https://legacy.forums.gravityhelp.com/topic/path-errors-on-previewphp</link>
		<description>Gravity Support Forums Topic: Path errors on preview.php</description>
		<language>en-US</language>
		<pubDate>Sat, 04 Apr 2026 09:01:36 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/path-errors-on-previewphp" rel="self" type="application/rss+xml" />

		<item>
			<title>designodyssey on "Path errors on preview.php"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/path-errors-on-previewphp#post-2430</link>
			<pubDate>Thu, 31 Dec 2009 19:10:41 +0000</pubDate>
			<dc:creator>designodyssey</dc:creator>
			<guid isPermaLink="false">2430@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Yeah, after two fixes, I created a .xls file with plugin, path_to_file, line # and change description as fields.  I add the code for the patch as a comment.  Hopefully that will keep it organized if I need this for the upgrade.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Path errors on preview.php"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/path-errors-on-previewphp#post-2426</link>
			<pubDate>Thu, 31 Dec 2009 18:52:38 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">2426@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;We can also look into it on our end next week and see what we can do so that this fix is native to Gravity Forms.  &#60;/p&#62;
&#60;p&#62;If you find anything out, let us know.  In the mean time make the change, then what you can do is just keep track of your change so until we have a native fix... you can re-apply your patch when we release an update.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>designodyssey on "Path errors on preview.php"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/path-errors-on-previewphp#post-2425</link>
			<pubDate>Thu, 31 Dec 2009 18:38:15 +0000</pubDate>
			<dc:creator>designodyssey</dc:creator>
			<guid isPermaLink="false">2425@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;After some debugging, I found that ABSPATH wasn't defined at this point for some reason, so I solved the problem this way:&#60;/p&#62;
&#60;p&#62;&#60;code&#62;$local_path = $_SERVER[&#38;#39;DOCUMENT_ROOT&#38;#39;].&#38;#39;/wpmu/core/&#38;#39;;&#60;/code&#62;&#60;/p&#62;
&#60;p&#62;and then this&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;require_once ($local_path . &#38;quot;wp-blog-header.php&#38;quot;);
require_once ($local_path. &#38;quot;wp-admin/includes/admin.php&#38;quot;);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;This should work even after loaded to the production server (I hope)&#60;/p&#62;
&#60;p&#62;Now I have to figure out why your original file didn't work because this will get broken when I update GF.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Path errors on preview.php"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/path-errors-on-previewphp#post-2385</link>
			<pubDate>Tue, 29 Dec 2009 18:36:30 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">2385@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;wp-blog-header.php is a core WordPress file that is typically in the root.  In your case if you have moved the core files into a directory called /core then in order to get the wp-blog-header.php it's going to have to path to that folder.  &#60;/p&#62;
&#60;p&#62;Try adding core/ in front of wp-blog-header.php, and let me know what happens.&#60;/p&#62;
&#60;p&#62;While our pathing to files such as javascript calls, etc. rely on a WordPress function to get the correct path, this is an area that does not use that function.  We will look at what can be done about that as this isn't the typical install scenario so it's not something that has come up.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>designodyssey on "Path errors on preview.php"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/path-errors-on-previewphp#post-2381</link>
			<pubDate>Tue, 29 Dec 2009 17:41:17 +0000</pubDate>
			<dc:creator>designodyssey</dc:creator>
			<guid isPermaLink="false">2381@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;First, I'm loving this plugin.  Tried to view a preview and got&#60;br /&#62;
&#60;pre&#62;&#60;code&#62;Warning: require_once(C:\xampplite\htdocs\wpmu\wp-blog-header.php) [function.require-once]: failed to open stream: No such file or directory in C:\xampplite\htdocs\wpmu\wp-content\plugins\gravityforms\preview.php on line 7

Fatal error: require_once() [function.require]: Failed opening required &#38;#39;C:\xampplite\htdocs\wpmu\wp-blog-header.php&#38;#39; (include_path=&#38;#39;.;C:\xampplite\php\PEAR&#38;#39;) in C:\xampplite\htdocs\wpmu\wp-content\plugins\gravityforms\preview.php on line 7&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;As you can tell, I'm running MU on a XAMPP windows setup (XP)&#60;/p&#62;
&#60;p&#62;Your code is actually on line 2, but I tried a fix (see below) whiich is now commented out.&#60;br /&#62;
Anyway, I tried (ABSPATH . &#34;wp-blog-header.php&#34;), but it returned the same warning like ABSPATHwp-blog-header.php.  This warning made me think it's not reading the ABSPATH.  &#60;/p&#62;
&#60;p&#62;So much for my solution.  Any ideas?  This one should be simple.  Oh, my setup has wp-config and htaccess in root and a /core directory with everything except wp-content which is in root.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
