Kic00

Thanks! It would be nice if the plugin made it selectable by the end user, but we can use the example code for our purposes.

Thanks, I’ll let you know if that fixes it. This is a multisite install with subdirectories.

I’m happy to test a code snippet but it seems you already fixed it!

Sure. We have no other plugins outputting open graph tags, or any conflicting plugins.

You can put our URL into the Facebook debugger:
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fww2.kqed.org%2Fnews%2F

And you’ll see that it complains that the og:url field has a redirect that is circular.

Thanks! I will try to use the conditional syntax and let you know how it goes.

That’s not the solution I want, thanks. I would like the permalink to be permanent!

We’ve been using the custom permalinks plugin, but it’s buggy and I don’t really want custom permalinks, I just want the original permalink not to change if the publish date changes.

It’s possible that the varnish server we put in front of our live servers is the culprit.

It works in our development server but not in our production server, even with all of the same plugins activated in both places.

Weird – I tried to assign a variable then change the value but it always returns “Post”, as in:
$foo = $post_type->labels->singular_name ;
if ($foo = “Post”) { $foo = “Bar”; } else { echo $foo; }
echo $foo <- always returns Bar, no matter if there’s another singular label.

Any clues?

Client pull == meta refresh.

In any case, I guess I’ll have to live with whatever the change was..

Yes, I know I can do the ‘allow from my IPs’ thing, but I liked having it accessible from a not-linked-to URL. It wasn’t a state secret or anything, but users going there would see test stuff..

Why not?
Again, it all worked in 3.0.4.
We didn’t do a convoluted rewrite at all — had nothing to do with .htaccess in fact. User were redirected with a client-pull .HTML file.

I don’t want outside users to know about or see our test blog, which now lives at / instead of /wpmu/

Argh. Now I’ll have to do something annoying like redirect users outside of our IP range to www.

It was a feature, not a bug!

I changed the path for the first blog from /wpmu/ to / and that fixed it. But why can’t the first blog be in a subdirectory anymore?