noplanman

Ok, see you again when your site is running PHP 5.3+ ??

Ok, I think your PHP version is the problem.

As a quick way to find out your PHP version, please add the following at the top of the autoload_real.php file:
die( phpinfo() );

Reloading your WordPress page, you should now see the PHP version at the top.

If you’re working on your live server and don’t have a development environment, please create a new file with a random name in the root directory of your WordPress installation and add this to it:
<?php die( phpinfo() ); ?>

Then point your browser to this new file: e.g. example.com/random-file-name.php

If you have access to the server error logs and feel comfortable debugging them, that would really help narrow it down too!

Hi @rodlinux

Please try to re-enter your pod and login infos on the “Setup” tab of the settings and save them.

If that doesn’t help, try adding &debugging to the URL on the setup tab and post the debug info here.

(the URL will be like “…example.com/wp-admin/options-general.php?page=wp_to_diaspora&tab=setup&debugging”)

Please try changing __DIR__ to dirname( __FILE__ ) manually in autoload.php
Does that fix it?

Does the file /vendor/autoload.php exist?
If not, try reinstalling the plugin please.

Closing thread as it is solved.

Great to hear that the normal posting works.

Please do let me know about the scheduled ones, so that we can dig deeper if need be.

I will look into it anyway to see how it could happen in the first place.

Did you update the plugin before or after the schedule was set?

Correct, the green tick means the connection to your pod is successful.

When you try to post to diaspora, do you get an error message at the top of the post page? If yes, what does it say?

On a successful post, there should be a green bar (similar to the one from WordPress) containing the link to the post on diaspora*.

Hi Bert!

What exactly isn’t working?

If you go to the “Setup” tab, does the connection to your pod work?
Or does it connect but not post?

We’re working on a better debug functionality to make it easier to find out what exactly isn’t playing right ??

Armando

Hi Patribus

Sorry for the late reply…

What version of the plugin are you using?

When you’re on the WP to diaspora* page in your WordPress admin panel, could you please add &debugging to the URL and post the debug results. As some pods handle logins a little bit different, it’s difficult to solve the problem without more info.

Also, what is your hosting company? Some hosts don’t fully support the SSL certificates which are necessary for the plugin to work. I’m mentioning this because I can connect and post to diasp.eu with no problems.

Thanks for your feedback ??

Hi saintblue

Maybe you missed the “NOTE” part in the plugin description:
“NOTE: This plugin serves as a mini-plugin until Tsu releases an official public API.”

This plugin was started to serve as a placeholder until Tsu releases an official API to add more Tsu-related functionality.

But since they are not likely to ever do that and the fact that I’m not using Tsu any more, this plugin is (as you say) a bit pointless at the moment.

Instead of a 1-star review, why don’t you just not use it and do it your way?

Thanks for letting us know about this, we’ll check it out and see how we can handle it.

As soon as we have a solution for it, you will be the first to know ??

Wonderful! Very glad to hear that everything is ok.

Thanks so much for helping us improve ??

Readme has been updated and will be published with the next update, thanks again!

Sure!

The cookie jar method we had been using with cURL has been removed, so the cookie is never written to the temporary folder on the server.

We will add it to the changelog to make it more detailed, thanks for pointing it out!