Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter anonbob

    (@anonbob)

    The logs are purged but I can make an example:

    When your blog url would be http://www.example.com it was like:

    404 error log:
    example.com/null
    example.com/2015/blogpost1/null
    example.com/2015/blogpost2/null
    example.com/site1/null
    example.com/site1/null
    etc

    That */null thingy starts after your plugin was updated over the dashboard and for almost 6 hours every visitor was producing 404 errors in the background while every link on the frontend was working (weird). But now everything is normal, no */null anymore. Maybe it was temporary because I didn’t change anything.

    Thread Starter anonbob

    (@anonbob)

    Works fine now (everything which wasn’t working before), thanks a lot!

    Thread Starter anonbob

    (@anonbob)

    Version 1.3.1 seems to be fine 😀 “connected to https://wk3.org” 😀 I will publish a Post tomorrow. If everything is fine then, I will mark the thread as resolved 😉

    I can connect to every pod now, this looks good. Thanks for your work.

    Thread Starter anonbob

    (@anonbob)

    I gave it a try (1.3) and it’s not working “Couldn’t connect to <pod>, login failed” I really think it has somehting to do with your pwd encryption algorithm.

    Sorry to say that but I’m using the Plugin Diasposter atm for testing around and there are no problems with connections etc.

    More ppl need to laod your plugin to test it, it’s hard to find bugs like that, when only one person (me) is posting about that problem.

    Have a nice day

    Thread Starter anonbob

    (@anonbob)

    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 😛

    Thread Starter anonbob

    (@anonbob)

    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.

    Thread Starter anonbob

    (@anonbob)

    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. :/

    Thread Starter anonbob

    (@anonbob)

    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 😉

    Thread Starter anonbob

    (@anonbob)

    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

    Thread Starter anonbob

    (@anonbob)

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

    Thread Starter anonbob

    (@anonbob)

    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.

    Thread Starter anonbob

    (@anonbob)

    Works perfectly, the URL is okay now and the new tag feature is nice, all post tags were right, thanks for your work Sir. 🙂

    Thread Starter anonbob

    (@anonbob)

    Thank you very much 🙂 So I will deactivate the plugin until the new version 1.2.6 is ready.

    Thanks you anyways for this plugin, diaspora doesn’t get much love on wordpress etc.

Viewing 13 replies - 1 through 13 (of 13 total)