Comments on: WordPress 1.5 plug-in: view future posts

By: Mike B

Mike B — Thu, 20 Sep 2007 13:29:11 +0000

UPDATE:

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).

By: Mike B

Mike B — Wed, 19 Sep 2007 22:46:39 +0000

For those of you using WP 2.1.2 (maybe 2.1+) this solution fixed the plugin for the site I'm working on.

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);

By: zylstra

zylstra — Wed, 18 Apr 2007 07:06:04 +0000

I am using WP 2.1.2 and event calendar 3.1.0. Has anyone updated this plugin? I would love to use it.

By: lotech

lotech — Mon, 12 Feb 2007 02:31:09 +0000

There seems to be some compatibility issues with Wordpress 2.1 (Ella) - from what I can tell the command to list posts from today backwards has changed and no long gets modified by the plugin to include ALL dates (future and past).

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

By: Roy

Roy — Thu, 18 Jan 2007 20:33:34 +0000

I just can't get this to work. I've tried all the different code changes offered here, but I get an error at line 29 every time. I'd like to make the values 0 and false, so that all future-dated posts show up on my home page and are viewable by everyone. But I just keep getting an error.

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

By: Yoel Natan

Yoel Natan — Fri, 12 Jan 2007 22:20:43 +0000

Thanks for this plug-in!

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

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

$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.

By: Jim

Jim — Thu, 30 Nov 2006 18:58:52 +0000

sorry, the correct code should be

$content = pregreplace("/AND postdate_gmt <= '.+')/", "", $content);

note the escape "" before the newly added ")" in that expression

By: Jim

Jim — Thu, 30 Nov 2006 18:56:20 +0000

for wordpress 2.0.x a simple change to the regex worked for me. Using the regex as it is in the plugin was leaving and extra misplaced ")" in the sql query which breaks everything.

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?

By: Scott Gunsaullus

Scott Gunsaullus — Tue, 19 Sep 2006 20:16:24 +0000

I have roughly the same parameters as Marcel, wp 2.0.4 and ec 3.0.4, $futureminlevel=0;

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.

By: Michael Calabrese

Michael Calabrese — Thu, 06 Apr 2006 16:18:31 +0000

It is now posted.