Tim
Forum Replies Created
-
The status you’re trying to post to Twitter is exceeding 140 characters, which will cause this problem.
Until the plugin has logic included to handle this, you’ll need to make sure your status updates are shorter.
The Pro version allows you to define status updates on a per-social media account, so you can have a short status for Twitter, and longer statuses for Facebook, G+ and LinkedIn.
Forum: Plugins
In reply to: [Image Lazy Load] Mobile not workingVague, works on our test suites. Once you are able to provide:
1. Web Site URL
2. iPhone make + model
3. iPhone OS version
4. iPhone browser app + version– I can then advise further.
Forum: Plugins
In reply to: [Image Lazy Load] Add a loading gif while image is loadingThis will be available in the Pro version, to be released in the next 2 weeks.
1. Install the latest version of WP to Buffer (2.3.2 at the time of writing)
2. Install http://wordpress.org/plugins/wp-to-buffer-usp, and activateUSP posts will then appear through your Buffer account, per WP to Buffer Plugin settings.
Forum: Plugins
In reply to: [Social Media Auto Poster - Schedule & Publish to Buffer] WP to Buffer ErrorsHi Frank,
You need to choose at least one social media account to send the updates to.
The error will then disappear.
Thanks,
Tim.
Fixed in 2.3
This was absolutely, 100% fixed in version 2.2.1. We spent around 8 hours thoroughly debugging the issue, finding the cause and resolving it to prevent this double post bug.
Your issue lies with WordPress:
I think I found what is causing this behavior. I have missed schedule plugin installed that goes through all posts regularly to see if anything is missed schedule. I have to use this because for some reason my WP doesn’t publish posts on scheduled time.
You shouldn’t need to rely on a third party plugin to publish your posts – WordPress is more than capable of handling scheduled posts itself.
We wouldn’t provide support for this third party configuration. Happy to support if you get scheduled posts working on WordPress without the use of a third party plugin and still get the double post bug behaviour.
I could support get_the_title(), so you’d need to check that your filter is applied to that.
Please confirm.
Please clarify what you require, I don’t understand the request/question.
Thank you.
If that’s your view, attitude and approach, then I can only suggest you find a more suitable free WordPress Plugin.
I’ve already said that you can go back through tagged versions and install an older version from prior to May 2013, which you believe works. That would resolve your issue.
Equally, I don’t have the time to chase for clarifications when it isn’t happening to everyone.
Best of luck.
I post images with commentary – you can go to bullandbearmash.com to see exactly what is posted. Nothing elaborate.
Please provide one specific example, including applicable social media link(s) showing the status update.
Logged in WP, I “post a chart” add my comments and click “publish”.
What is “post a chart”, please? Is this a Post, Page, what?
My first inquiry would be, what was changed between June 2013 and today’s version that – might – cause this to occur.
Then my first response would be to go through the tagged versions, find one that’s older than June 2013 (although you mention May 2013 in a previous paragraph – confusion), install that one, try it, see what happens.
Forum: Plugins
In reply to: [Social Media Auto Poster - Schedule & Publish to Buffer] FB post problemsPlease advise the precise steps you are taking to reproduce this issue, including:
1. Exactly which “extra characters and artifacts” are being displayed.
2. Facebook Page where extra characters can clearly be seen.Please provide precise steps you are taking so I can reproduce this issue. For example, what content you’re entering into the post, the order of buttons you’re pressing / fields you’re filling out etc.
Please email using the contact details in the plugin’s readme file.
Thanks.
The Javascript error (and missing admin.js script) won’t stop the plugin from working. The error itself will be removed in 2.0.3