muskie

I was able to implement the fix above and when I published my next post it went to my Facebook Timeline without a fuss. I don’t think I’m running the absolute newest version of WordPress or possibly even the plugin…

Alright “GUllyv3r” I tried that. I’ll have to write another blog post to test it, I don’t write that many posts, but perhaps I can write a short one today.

This isn’t a Facebook issue, they can totally change their API / OpenGraph format whenever they damn well please. Unfortunately they have changed it so much and made developers jump through so many hoops, it has gotten annoying. Digg Digg (Buffer) have to upgrade their plugin to be compatible with the new Facebook standard, I and others have done quick fixes and I’ve had to fix other PHP code.

I have much bigger issues with the official Facebook for WordPress plugin and the instructions for installing that. Many, many, people are not starting with fresh clean installs and have blogs that are five or more years old with numerous other plugins, Facebook doesn’t seem to grasp that, making bloggers register their blog as a “Facebook App” seems a bit much…

After downloading the latest version to my desktop and guided by what Pinto did above my fix to the XBFML button is to comment out the first couple lines of the constructURL function in the dd-class.php file like so:

/*
 		if($this->isEncodeRequired){
 			$title = rawurlencode($title);
    		$url = rawurlencode($url);
 		}
 		*/

This is working on my blog, but I think an official fix would be better… It also appears there might be some means of turning off URL encoding from inside WordPress itself, or perhaps there should be…

I too am now getting this error. I didn’t upgrade anything, in 2012 things were working now in 2013 they aren’t.

Needless to say I too am getting this problem and I’m hoping for an official update soon. I blogged about it as the problem isn’t exclusive to Digg Digg and it seems the fix is to stop url encoding urls…

Do you have some other plugin that creates buttons, such as JetPack or Digg Digg? Also some plugins will put the buttons above and below the content, Facebook puts social mentions above and below the post by default for instance.

I too started using the Facebook for WordPress plugin and I created the sample Action but it did not go as smoothly as the plugin instructions implied. I turned on the Social Publishing feature along with the Recommendations Bar and a bunch of Actions and Objects were created automagically. I’ve tried submitting them but it just gives me a request for detailed instructions. I’ve typed various things into the box, I just get more errors/warnings.

I just want the plugin and the various features built into the plugin to work, but I’m not sure everything is functioning correctly. I’ve created support requests and Googled but to no avail.

When did the forum rules change and make posting code snippets a no no? Seems strange what with the big code button above the text entry box. I still have this problem and have had this problem since at least my upgrade to WordPress 2.7, could it be something in my database?

But why in one column on page load does is_tag return true and in another column during the same page rendering process, does a call to is_tag return false? This behavior is consistent across any of the tags regardless of when or how I added them.

I do use the Simple Tags plug in and bulk added some tags to old posts, but I also hand edited and tagged 100s of old posts and of course tag all my new posts using the standard tag entry box on the post edit/creation screen.

Cheers,

The spam is gone… This problem is solved but my sidebar is still not working as expected or more accurately the conditionals in my sidebar are not working as expected and documented.

Thanks for the help…

Thanks,

I checked discussion settings even tried toggling that setting. It allowed comments on new posts by default yet for some reason this first post had them disabled. I was using Opera with Turbo on which I think contributed to my problems, not sure if that is why Asian text input was causing issues.

My longtime loyalty to various pieces of software is being seriously questioned.

Any idea why my sidebar is behaving weird?

I’ll have to wait until I make another post to see if this behaviour repeats itself. I must have hid the discussion option or is it hidden by default?

I had a lot of trouble going to WordPress 2.0 especially in IE but that was years ago. Going from 2.7 to WordPress 2.9.1 was a real horror story. In fact I haven’t checked my old Asian text, the WordPress upgrade may have again borked it all, but I know the fix, it is one simple line in a config file.

I seem to have discovered a problem with Mac OS X Lion or the latest version of Disqus plugin, Asian character input.

わかりません

Couldn’t input that into Disqus on my blog just now, see why I strongly dislike upgrading my blogging software.

It was during the whole sad tale of going from WordPress 2.7 to WordPress 2.9.1 and making changes recommended by experts that broke my Asian text and led to my discovery of the weirdness with conditionals in my sidebar.php file and how it renders/runs.

I created a support thread then, never got any love or indeed any help at all.

Not that I know of obviously. My template/theme is as old as my blog, I’ve been updating it as necessary. Finding the template/tutorial it was originally based on might not be impossible.

I think my template is pretty logical in index.php for the theme is the following structure:

[Code moderated as per the Forum Rules. Please use the pastebin]

I’ve had to update it so many times…

page.php is basically unused in this blog but here it is:
[Code moderated as per the Forum Rules. Please use the pastebin]

archive.php is more relevant and here it is:
[Code moderated as per the Forum Rules. Please use the pastebin]

You’ll note in the link to the iTunes tag category archive that it says it is a tag archive meaning the call to is_tag() returns true in one column but in the column that contains the sidebar it does not return true.

There is one comment about some hack, I don’t remember when I did this, it sounds like something I would have read about rather than randomly tried, perhaps that is a contributing factor, but I don’t understand when the page is being rendered why is_tag returns true in one place on the page and returns false elsewhere on the same page. This used to work, I’d have to go look at old posts to figure out when it got busted but I’m pretty sure I’ve complained about it previously, I know I complained on my own blog…

This is an old problem. I wrote some code to diagnose it and prove I wasn’t insane.

This is at the bottom of my sidebar.php:

[Code moderated as per the Forum Rules. Please use the pastebin]

Pick any tag…

iTunes

It returns true for is_archive and is_date but not is_tag

That is not the only odd case I’ve noticed, for single posts such as

Upgraded to iOS 5 and iTunes 10.5

This time according to the code above returns:
is_home
is_front_page

Which clearly is not correct, only one page should return true for is_home and is_front_page and it shouldn’t be a random post from the 13th of October.

Cheers,

In the last four months or so www.ads-software.com reset my password. I cut and pasted it into the app. I’m using Version for Mac OS X if that matters. I tried several times. I can get a slightly different error sometimes…

I tried checking out then updating as well.

Well what do you know, it worked today. Maybe it took a while for my changed password to filter down to this system.

Let me know if all is well in plugin land? My sidebar still does behave correctly as is_tag among others does not return the expected value, but I’ve lived with this bug for many versions now…