pluc

You’re trying to re-do something that WordPress does out of the box. There is no correct way to force WordPress instanciations in places where WordPress has nothing to do. By that, I mean using stuff like wp_title() on pages that aren’t store in WordPress makes little sense.

The best (and correct) way to do what you want is to import your static pages into WordPress, and let WordPress handle your whole website – it’s made specifically for people who want to have /blog/ as an independent section. I’m sure your client will be happy to be able to modify its static files through WordPress.

You can always create a header-static.php file (and footer-static, and sidebar-static, and whatnot) and tell wordpress to get_header(‘static’) on those specific pages.

That’s how I would do it, anyway.

There was a mistake in the SVN tree (tags/1.0/trunk had no business there) – I’ve cleaned that up, let me know if it works.

Couldn’t replicate.. but I checked the headers of both files and re-commited just in case, so check back in 15 minutes.

PHP4 has been officially discontinued since August 8 2008.You should strongly consider upgrading.

Wanna say what’s wrong or should I just guess it?

WP-prettyPhoto uses jQuery in no conflict mode. It should work fine with other libraries providing they do the same.

Easy answer: Don’t use it.

Long answer: Read the manual, if there’s anything you don’t understand, post on WP-prettyPhoto’s support forums, we’ll either help you or we’ll tell you not to use our plugin because you have no idea how to even do step 1 correctly.

Thanks!

That’ll be fixed in the next version, thanks for the head’s up.

This is rather irrelevant to WP-prettyPhoto and to some extent, NextGen. WP-prettyPhoto will replace all the image links’ REL attribute, but they have to be displayed on the page for WP-prettyPhoto to perform this operation. It can’t loop through what it can’t see. Loading the gallery in AJAX affects the content of the post, and therefore prevents WP-prettyPhoto from being notified of a post output (which WordPress does). Short answer is you basically can’t, unless you modify the code of NextGen and/or WP-prettyphoto.

I would assume it’s an Events Manager issue as WP-prettyPhoto tries its best to be as friendly as possible to other plugins. There hasn’t been reports of conflicts since version 1.0. The only thing I can suggest to try is to disable jQuery substitution in the WP-prettyPhoto options. If that doesn’t work, well it’ll be up to the Events Manager author to improve its compatibility.

There’s been a brief bug with method scope, it was fixed pretty much 2-3 hours after. Everything should be fine now.