My previous comment didn’t work for users who weren’t logged in, because of the post_status = ‘private’ parts. So, here’s the new replacement line that works for everyone.

$content = preg-replace(”/post-status = ‘publish’/”, “post-status = ‘publish’ OR post-status=’future’”, $content);

(remember these comments are filtered, so replace the -’s with underscores).

REPLACE this line:
$content = preg_replace(…);

with this line:
$content = pregreplace(”/poststatus = ‘publish’ OR poststatus = ‘private’/”, “poststatus = ‘publish’ OR poststatus = ‘private’ OR poststatus=’future’”, $content);

Any one have a workaround, solution or update to the plugin? I’m stumped.

Would anyone be willing to look at my site and tell me what I need to do? I’d really love to use this plug-in, as it’s the only one I’ve found that does exactly what I want! Thanks

To those who have been getting the SQL error, the fix is to change the line

$content = pregreplace(”/AND postdate_gmt <= ‘.+’/”, “AND 1″, $content);

to

$content = pregreplace(”/AND postdate_gmt <= ‘.+?’/”, “AND 1″, $content);

Adding that question mark to the regular search expression prevents this plug-in from unintentionally removing large chunks of the SQL query conditionals generated by some versions of WordPress and/or other plug-ins.

$content = pregreplace(”/AND postdate_gmt <= ‘.+’)/”, “”, $content);

note the escape “” before the newly added “)” in that expression

Change (line 29 in my copy)
[code]
$content = pregreplace("/AND postdate_gmt <= '.+'/", "AND 1", $content);
[/code]

to
[code]
$content = pregreplace("/AND postdate_gmt <= '.+')/", "AND 1", $content);
[/code]

The replacement of the date string with “AND 1″ (an always matched condition) seems a bit pointless to me as well. Why replace the date condition with and always matched condition when you can just remove the date condition? So, like so
[code]
$content = pregreplace("/AND postdate_gmt <= '.+')/", "", $content);
[/code]

That also works for WP2.0.x, unless someone knows a good reason to have the “AND 1″ in the SQL query?

My goal is to allow future events to be viewed by anyone, with emphasis on anonymous viewers and viewers who are not logged in.

Something is missing. The permalinks for future posts ARE NOT visible, even to registered users whose access level is > X.