tgrblogger

Thanks for the post. I was wondering what happened to it. I had the paid version, $99 I believe, and like you, I doubt I’ll ever pay for one like that again. Which is a shame as there are surely other talented and committed theme authors out there that better deserve the money.

Which theme did you find to replace it?

FYI, the form error is the same one several others have listed on this forum:

Fatal error: Call to undefined function imagettftext() in /home/USER/public_html/wp-content/plugins/really-simple-captcha/really-simple-captcha.php on line 126

If the others would check the form editor area, perhaps they would find that this plugin also gives the message that the GD and Freetype libraries are missing.

I know that mine are not missing, however, I am wondering if it’s simply due to me having suhosin and the suphp mod enabled for my php installation, which may cause some scripts to fail. Can anyone verify this?

I’m having the same issue, only not using the icon (icon doesn’t appear, using default gallery), tried using the right click context menu. I’ve tried in 3 major browsers; IE 10.0.9200, Chrome 31.0.1650.63, and Firefox 25.0.1. WordPress version 3.8.

They may have rejected for other reasons, there are a whole list of things, including compliance with breaking changes, that have to be met when you submit. But for now this works, so I don’t bother to submit.

I was hoping that dlachapelle would post a url or step by step for the process they recommended in order that I could take a look at it and see if it’s more appropriate.

I logged into my account at https://developers.facebook.com/, selected Apps, then the app on the left that I wanted to work with. From there I selected Edit App button at the top right, then Open Graph on the right. I chose from the Action Type that I wanted to have shared, in this case Publish Article, and scrolled down to the checklist for optional capabilities and selected “Explicitly Shared: This action can specify the user explicitly shared an action.” Selected “Save Changes” button at the bottom and was done.

I’m not seeing the action you’ve described in my Facebook developers Open Graph Dashboard. Do you have an actual path you could post?

My apology, your solution is OK, had to go into Apps> THE APP NAME >Open Graph >Action Type: Publish and select the explicitly shared option.

dlachapelle, The fix you posted is not working for my app. With it I simply get a different error. It now gives me “Failed posting to your Facebook Timeline. Error: {“message”:”(#100) You haven’t enabled Explicitly Shared for this action type (331247406956072) yet. Please update your Open Graph settings in the App Dashboard”,”type”:”OAuthException”}”

I’ve gone into the App Dashboard and fail to see a way to update the settings to comply. Any further clues are appreciated.

Still seeing version 1.2.1 as only one available. I guess a weeks time must be longer where you are at peplamb… Just kidding ?? But really, are you still planning to update this plugin? WordPress itself is now up to version 3.5.

Simon,
Thanks for the info, however, we’ve tried that and more possible solutions. I can confirm that CSSHack was the most frequently used, but apparently someone has studied up on how AntiSpam Bee works and has found a way around their algorithms, at least for now. But that’s the way it is with all anti-spam / anti-virus battles, all that back and forth. Unfortunately I have to comply with others wishes as well and have disabled this solution for now and installed a different one. We’ll just have to see how long that one holds up.

I may be getting the same spammer. It’s listed as coming from a .uk domain, although I have not verified the IP addresses to see if that’s valid. Is this the case with the rest of the posters here?

Not sure what’s happening with version 1.0.2, but Publish to Fan Page is still being disabled when I first log into my WordPress blog. This seems to be an OAth connection issue, as once I check the box, it stays selected until I log out of my blog admin and posts publish to the fan page. If I forget to check the setting after logging in and put up a post, the post doesn’t publish to the Fan Page, and when I look at the settings afterwards, I can see that the Publish to Fan Page is deselected. Unfortunately, selecting it then doesn’t allow for me to report to the account and Fan Page.

I have multiple fan pages associated my Facebook account, not sure if that’s why it behaves this way. I do use the plugin on at least two other blogs, all experiencing the same behavior. It doesn’t matter whether I’m logged into Facebook or not.

I’m also experiencing where the first 50 characters are text with HTML markup showing. Then it repeats the same line below without the HTML markup.

One final thing… I notice a broken image just below the Save Changes button. It goes to https://www.facebook.com/impression.php?plugin=wordpress&payload= along with a long list of attributes, including the name of the fan page selected. Can anyone tell me what this is used for?

EDIT: Changed this comment to version 1.0.2, I’ve not tried 1.0.3 and won’t until I see consensus that these issues are resolved.

OK Jim, just to clarify this thread was not started about WordPress, it’s focused on informing people about WP-ecommerce. Thanks for sharing your opinions, but further comments about WordPress itself or themes would be more appropriate in a different thread elsewhere.

…Because I have had so many problems with WP themes and plugins, I will be checking out Joomla and Drupal after this site. I advise you to do the same

Jim, I can’t really agree with you on the WordPress ease of use, as I believe it’s gotten better. But I can imagine it’s made it tougher for plugin authors who don’t get paid or work off donations for their work to make time to stay up with the changes. WP-ecommerce has no such excuse though.

I will tell you that if your displease with WordPress, then you’re unlikely to like Drupal’s interface and update system. It’s as far from intuitive as sticking your hand up a dog’s ass to stop it from peeing on you. It works, but it’s nasty and can reach around and bite you!

I’d like to see Yahoo give this to the open source community to work on, they’d likely get a lot of credit for doing it and may even some further benefit, rather than what they have now.