<?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: Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard</title>
		<link>https://legacy.forums.gravityhelp.com/topic/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard</link>
		<description>Gravity Support Forums Topic: Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard</description>
		<language>en-US</language>
		<pubDate>Fri, 10 Apr 2026 13:39:25 +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/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard" rel="self" type="application/rss+xml" />

		<item>
			<title>noxbane on "Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard#post-38831</link>
			<pubDate>Mon, 24 Oct 2011 22:52:54 +0000</pubDate>
			<dc:creator>noxbane</dc:creator>
			<guid isPermaLink="false">38831@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks Chris.  I think that definitely gives me the logic of what I need, if not the exact code.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard#post-38816</link>
			<pubDate>Mon, 24 Oct 2011 21:22:11 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">38816@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I would use a page template, call it &#34;Logged In&#34; or something, then use that template on the pages for which you must be logged in to view.  Then, put this at the top of the page template:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;[php]
&#38;lt;?php
/*
Template Name: Must log in
*/
if(!is_user_logged_in()) {
    $siteurl = get_bloginfo(&#38;#39;url&#38;#39;);
    $request = $_SERVER[&#38;#39;REQUEST_URI&#38;#39;];
    $redirect = urlencode($request);
    header(&#38;quot;Location: $siteurl/wp-login.php?redirect_to=$redirect&#38;quot;);
    exit;
}
// continue with rest of page template
// maybe starting with get_header();&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;There's probably room in there for a 301 or 302 header, but this code has worked for me in the past.  If the user is not logged in, they will be redirected to the wp-login.php page, with the additional benefit of being redirected to the original page AFTER they log in.  &#60;/p&#62;
&#60;p&#62;Let me know if that works for you.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>noxbane on "Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard#post-38798</link>
			<pubDate>Mon, 24 Oct 2011 14:48:45 +0000</pubDate>
			<dc:creator>noxbane</dc:creator>
			<guid isPermaLink="false">38798@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Bumping this thread to see if there is an answer to my followup question.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>noxbane on "Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard#post-38219</link>
			<pubDate>Tue, 18 Oct 2011 14:50:36 +0000</pubDate>
			<dc:creator>noxbane</dc:creator>
			<guid isPermaLink="false">38219@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi David,&#60;/p&#62;
&#60;p&#62;Thanks for your reply. Do you have any advice on how to make the registration form appear for certain pages?  There's only a handful of pages that will be protected.  But where or how do I mark these specific pages as protected so that when a user goes to the URL, they are presented with the registration form?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>David Smith on "Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard#post-37593</link>
			<pubDate>Tue, 11 Oct 2011 16:03:11 +0000</pubDate>
			<dc:creator>David Smith</dc:creator>
			<guid isPermaLink="false">37593@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi Noxbane,&#60;/p&#62;
&#60;p&#62;It sounds like signing them up as users is still the most ideal way to tackle this. If you'd like to prevent them from ever visiting any admin screens, just set up some simple redirect logic along the lines of:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;[php]
if(!is_admin())
    wp_redirect(get_bloginfo(&#38;#39;home&#38;#39;));&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;This way you can still use standard WordPress functions to handle the user logging in to access content and you could use the User Registration Add-on to handle registering the new users.&#60;/p&#62;
&#60;p&#62;Does that help?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>noxbane on "Capture Lead Info, Allow to Bypass Next Time,  No Access to Dashboard"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/capture-lead-info-allow-to-bypass-next-time-no-access-to-dashboard#post-37563</link>
			<pubDate>Tue, 11 Oct 2011 12:24:20 +0000</pubDate>
			<dc:creator>noxbane</dc:creator>
			<guid isPermaLink="false">37563@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I have the skills necessary to work with PHP and hooks and such.  I just need a basic breakdown of the logic/implementation required to do this: &#60;/p&#62;
&#60;p&#62;So I make real estate websites and this is a common request.  Some useful information (buying tips, selling tips, etc) is available to the user only after they submit their contact info.  (Yes, I know its not good practice, but some people insist). &#60;/p&#62;
&#60;p&#62;I DON'T want people to actually register with Wordpress itself, or at least I dont want them to have access to a dashboard, nor do they have a profile to edit.   They simply enter their contact info, and then they can see the information they want.&#60;/p&#62;
&#60;p&#62;If they come back a few days later, they should be able to enter their email or password or both (it doesnt matter, whichever is easiest) and then view the content without submitting info again.  &#60;/p&#62;
&#60;p&#62;Also, if there are five protected articles, they only have to register for one, not all five. &#60;/p&#62;
&#60;p&#62;Whats the basic logic for this setup?    Thank you very much in advance for any assistance.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
