Double Posts on "sheduled Publish"

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!

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 ??

When I’m saving the shedule (plan post) for a later publish, it happens (not all the time, randomly). I’ve recognized it’s happening most of the time, when I’m using “Purge site from Cache” after the official publish (It’s a direct button on the edit post page from w3 total cache) and the page is reloading after the cache purge and “share on diaspora” is checked.

I have a second question, is your Plugin working with the xmlrpc.php? Since I’ve disabled the xmlrpc.php for security reasons, wp to diaspora isn’t working anymore (I cant save my pod account details and it’s not sharing).

Hi, sorry to butt in but, anonbob, you are clearly doing some wonderful testing. I wanted to let you know that another plugin called Diasposter that does a little more than WP to Diaspora currently does is also available but isn’t well-tested and would be happy to have you try it out and test if you’re interested.

Thanks and keep up the great work.

@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*?

The Problem is, when I’m trying to open the general settings for wp to diaspora (/wp-admin/options-general.php?page=wp_to_diaspora – doesn’t matter if i do it from the left menu or over plugins) it takes like 2 minutes to load the page. Then I’m trying to put my account login details into username and pwd form, press save and it loads like 2 minutes again and then it says “Couldn’t connect to <pod>”. I’ve tried different pods but I can’t get any connection to pods since I’ve disabled xmlrpc.php (before it wsa working fine).

all other plugins are working fine, I’m using only plugins which arre not using xmlrpc

Update:
Okay it has nothing to do with xmlrpc, i’ve tried it with xmlrpc.php enabled, didn’t work.

The problem begun since plugin version 1.2.6.2 (before it was working fine, no connection problems). Are you using any new features since 1.2.6.2 to get connection to pods or retrieve the connection tokens?

For example I’m blocking some curl functions over my php.ini for security reasons and I’m not sure about to allow those functions just for using one plugin? I don’t have a clue atm what the problem is because your plugin is the only one which is not working to shre on other networks like Diaspora and it was working fine with 1.2.6

Edit://

I just can guess, the changelog says “Password encryption” is new to 1.2.7. So I ve tried 7 different pods now and I got only connections to 2 of 7 pods but then it says “Login failed, username oder password wrong” but I’ve typed it right + I tried copy and paste and it’s not working, maybe something is wrong with your pwd encryption or token session.

I’ve installed version 1.2.6.1 now and it’s working fine, with any pod ??

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?

Right, since 1.2.6.2 – 1.2.7 it’s not working for me.

Our main Profile is on the wk3.org Pod, that pod is working up to 1.2.6 but all versions after 1.2.6 are not working for wk3. I’ve tried diasp.net, diasp.org, diasp.eu, pod.geraspora.de, londor.be and some more.

With 1.2.6.1 all pods are working (which i’ve tried) except wk3.org (could not establish connection to pod). wk3 works only with 1.2.6. For example diasp.org and pod.geraspora.de and wk3 are the biggest pods for German users and I’m from Germany, so it’s kinda annoying atm to use old plugin versions to make it work. :/

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.

I’m blocking
exec,passthru,shell_exec,system,proc_open,popen,parse_ini_file,show_source,curl_multi_exec
and it’s running in an open-basedir. (php 5.6.6)

I really don’t know where the problem is, 1.2.6 / 1.2.6.1 was runnig fine for me, after the update to 1.2.6.2 and 1.2.7 it isn’t working anymore. With 1.2.7 when I get a connection to a pod, I can’t login, because pwd/username is wrong, but I chose the right ones.

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!

Sorry I had a busy weekend. Yeah, I will hang with older versions for the next days. When is the new 1.3.0 update coming? can’t wait for it ??

@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.