noplanman

Sorry for the late message!

We released 1.3.1 earlier today which should resolve the connection problems.

Please give it a try and let us know if everything is working again.

You are absolutely right that it would be great to have more people use it to make the plugin more stable.

@anonbob Version 1.3.0 is out now, so you can give it a try and please do let us know if everything is working ok.

For the next version, we will be adding a more advanced debug feature to pin-point problems better, but I hope it works for you now.

We’re not using any of the functions you’re blocking, so it’s not that.

If you hang tight with 1.2.6.1 for the moment, I will do my best to get 1.3.0 out this weekend, which has a bunch of fixes in it.

I’m really sorry that this bug has somehow crept in, even though I still don’t know what it is exactly :-/

Thanks for your great and especially clear feedback!

Very strange indeed…

I’ve tested all the pods you listed with version 1.3.0 which I’m finishing off at the moment and had no problems with either of them.

Which cURL functions are you blocking? That might be a reason why it’s not working properly.

So you have updated to 1.2.7 with no luck either?

I have noticed that different pods handle the login slightly differently.

What pods are you trying?

@anonbob, thanks for the clarification on how the problem occurs when using W3 Total Cache.
I will have another look into it and make sure to find the culprit ??

About xmlrpc.php, as far as I know we don’t use that. Do any other plugins behave differently with xmlrpc.php disabled, or just WP to diaspora*?

As there has been a lot of changes in the new version, I couldn’t reproduce your problem. I’ve been trying different methods but they all worked.

The next release is coming soon ??

Does it first post the moment you save the schedule and then again when the scheduled publish happens? Or both at the same time?

Thanks for letting us know, we’ll get to it as soon as possible!

Ok, thanks so much for the thorough reply!

I’ve just released version 1.2.0.

Please update your plugin and see if it works.

Feel free to open another support issue if it isn’t resolved, I’ll close this one as it isn’t up to date anymore.

Are you in the position to activate a default WordPress theme to make sure it’s not your theme that’s causing the problem?

Is it the unmodified original Magazine Basic theme or have you modified it?

What version of PHP are you on?

Did you manage to resolve the problem?

Please let me know so we can get it sorted out ??

I have no problems with the widget on a clean WP 4.1 installation with the Magazine Basic theme (version 3.0.4).

Maybe it’s another plugin that’s interfering…

What plugins do you have activated?
Maybe you could disable them all and see if the widget is there.
If yes, activate one after the other to see which one causes it to disappear.

Give me a sec to install WP 4.1 in my dev environment.

Will get back to you in a few minutes…

Hi twostuds

Is the plugin activated? Please check just to make sure.

Then, there should be a widget called “Tsu Widget”.

Could you provide any more details? Version of WordPress?