Graham Stoney

I’ve just hit this myself for the first time, with WordPress 3.2.1. All my previous scheduled posts have gone out fine. What is going wrong here?

Thanks,
Graham

I’ve noticed this problem too. It’s particularly annoying for those of us without a plethora of mobile devices to test on, and it’s way too complex for novices to get right first go. It would be great if this could be made to work correctly out of the box when W3 Total Cache and WP Touch are used together.

Cheers,
Graham

Hmmm… my best guess is that WP_Query treats URLs like the original one I posted:
https://confidentman.net/confident-man-ebook/?p=112

… as 404’s internally in order to redirect them to honor the ?p=112 bit. When Smart 404 overrides WordPress’s built-in redirection it breaks with either a loop or a real 404.

Thanks Daedalon,

Hmmm… something about Smart404 seems to be making wp_query think it’s dealing with a 404 and calling set_404. Here’s a weird thing: the redirect loop has gone, but I’m now getting a 404 error on my live site for this URL:
https://confidentman.net/confident-man-ebook/?p=112

With Smart404 disabled, I get the post I expect (number 112).

On my local XAMPP test site (which has slightly different content but most of the same settings), I still get the redirect loop.

Fascinating captain…

Well it sure is confusing to change default behavior given there’s no 404 involved.

I’m not sure if the redirection loop is coming from the template_redirect action, or the redirect_canonical filter; or some interaction between the two. I can’t see an obvious bug in the Smart404 code, but I don’t claim to understand it. It’s almost as if is_404 is returning true for these requests and kicking Smart404 into action, when it should just be left to WordPress’s builtin redirect_canonical. The developer says he hasn’t got time to support this plugin any more; anyone interested in diving into this?

Cheers,
Graham

I understand your reasoning; I don’t like having zillions of options either. I just want things to work. But sometimes it helps users to be able to disable certain functionality when there is a plugin conflict or duplicated functionality. I have two other plugins installed that also generate OpenGraph tags.

Thanks for the tip. I’m not a fan of plugin-hacking, since the hack gets deleted in the next upgrade. I may have to resort to that; I’ve been playing with FacePress II for my wall updates, but it’s just not as clean as SFC Publish. ??

Cheers,
Graham

After a little more testing, I’ve discovered that WordPress already does exactly what I want by default. The request above doesn’t confuse WordPress at all. However a problem with the Smart404 plugin is causing a redirection loop.

The workaround is to disable Smart404; but I’m hoping the author can help fix the problem.

You can in fact retarget ClickBank affiliate hoplinks just by adding ?p=xxx to the hoplink.

Cheers,
Graham

Thanks for getting back to me. I worked around it at the time with Andy’s (author of CommentLuv) suggestion of selecting “Prevent Script Loads” for “Google scripts for +1” in the CommentLuv Premium Technical Settings. I just noticed that I’ve since reverted back to the default setting but it does seem to be working fine now. Weird!

Cheers,
Graham

Hey Otto,

Thanks for the quick reply. I can see what you’re saying, but it also seems inefficient to generate the content and run all the filters twice. Seems like a chick-and-egg problem. I was surprised when I first dove into the SFC code and saw all the content processing it was duplicating.

Would it be possible to add an option to en/disable Open Graph tag generation to work around problems like this? The only feature I use in SFC is Publish and I have little control over other plugin authors. ??

Thanks,
Graham

When I tweet a post with Tweet Old Post without link shortening, it uses the full permalink path like this:
https://buildyourblog.net/email/mailpress/mailpress-enhancement-bug-fix-wishlist

I’d like an option to use the shortlink that looks like this instead:
https://buildyourblog.net/?p=841

Have a look at the most recent two tweets here to see the difference; the most recent is from Simple Twitter Connect, and the next is from Tweet Old Post.

It’s just aesthetics as Twitter shortens the link with t.co anyway…

Cheers,
Graham

Thanks for the tip-off of the work-around Ajay. I found that Simple Twitter Connect – Base plugin was causing the conflict for me. I had to temporarily disable this and Google Analytics to get authorisation to work. That got around the problem for me.

Cheers,
Graham

I’m looking for it too. I’m wondering exactly what The Google+ Plugin‘s “integrate with Google+ page” feature does, if not this?

Cheers,
Graham

I’m interested in this too; it doesn’t seem to be supported yet. Anyone know of any other alternatives for automatically publishing to Google+?

Thanks,
Graham

There is a bug in the implementation of wp-cron which has been fixed for WordPress 3.3; which hasn’t been released yet. If you want wp-cron tasks to work reliably, you need to disable wp-cron and create a real cron job to do the work. Even once WordPress 3.3 is released, wp-cron is a hack I recommend you avoid. Read this article to learn how to work around wp-cron’s problems.

Cheers,
Graham

Thanks dude, that’s it all right. The fix is to turn off “Track Performance” in the SexyBookmarks options.