• Hello,

    I have some confirmed issues with the plug in:

    1) In some magic way I have version 2.1.4 despite the last version shown on the WordPress repository is 2.1.3.

    2) There’s something going wrong creating the redirection:

    I should have:

    http://www.domain.tld/blog/wp-login.php?action=wordpress_social_authenticate&provider=Facebook&redirect_to=http%3A%2F%2Fwww.domain.tld%2Fblog%2Fwp-login.php%3Faction%3Dregister&redirect_to_provider=true

    and instead I get:

    http://www.domain.tld/blog/wp-login.php?action=wordpress_social_authenticate&provider=Facebook&redirect_to=http%3A%2F%2Fwww.domain.tld%3A8080%2Fblog%2Fwp-login.php%3Faction%3Dregister&redirect_to_provider=true

    That is it adds a spurious port 8080. The server runs a Varnish Cache front end responding to the regular port 80, the 8080 is an internal configuration.

    WordPress configuration is correctly set to:

    WordPress Address (URL)
    http://www.domain.tld/blog

    Site Address (URL)
    http://www.domain.tld/blog

    and no other WP plug in “digs” the 8080 out.

    3) The plug in always worked perfectly till this last update. Now even removing the 8080 I get this URL:

    http://www.domain.tld/blog/wp-content/plugins/wordpress-social-login/hybridauth/?hauth.start=Facebook&hauth.time=1379583187

    and it always results in a 404 page.

    Trying to use Google or Twitter social log in buttons gets the same error. All of 3 social networks worked since I installed the plug in some months ago and only now they exhibit this behavior.

    I have read about “whitelisting” pages, but this is a dedicated server running NGinx so what do I whitelist and how?

    I have found this Stack Overflow hauth related question and solution, am I meant to add it in the plug in code somewhere?

    4) Diagnostics report is OK:

    1. URL Rewrite

    OK!
    The rewrite rules on your server appear to be setup correctly for this plugin to work.
    What do I do if the Rewrite Diagnostics fail?

    If you get a 403 and 404 on the Rewrite Diagnostics test, request your hosting provider whitelist your domain on mod_security. This problem has been encountered with Host Gator* and **GoDaddy.
    2. PHP Version

    OK!
    PHP >= 5.2.0 installed.
    3. PHP Sessions

    OK!
    PHP Sessions are working correctly for WordPress Social Login 2.1.4 to work.
    4. cURL Extension

    OK!
    PHP cURL extension installed. [http://www.php.net/manual/en/intro.curl.php]
    4. cURL / SSL

    OK!
    PHP cURL/SSL Supported. [http://www.php.net/manual/en/intro.curl.php]
    5. JSON Extension

    OK!
    PHP JSON extension installed. [http://php.net/manual/en/book.json.php]
    6. PHP Register Globals

    OK!
    REGISTER_GLOBALS = OFF. [http://php.net/manual/en/security.globals.php]

    5) Website information: I only removed the domain name the rest is verbatim:

    SITE_URL: http://www.domain.tld/blog
    PLUGIN_URL: http://www.domain.tld/blog/wp-content/plugins

    HTTP_HOST: http://www.domain.tld
    SERVER_PORT: On (8080)
    HTTP_X_FORWARDED_PROTO: N/A

    MULTI-SITE: No

    WSL VERSION: 2.1.4
    WORDPRESS VERSION: 3.6.1

    PHP VERSION: 5.5.3-1+debphp.org~precise+2
    MYSQL VERSION: 5.6.13-1~precise+1
    WEB SERVER INFO: nginx/1.4.1

    SESSION: Enabled
    SESSION:WSL WordPress Social Login 2.1.4
    SESSION:NAME: PHPSESSID

    COOKIE PATH: /
    SAVE PATH: /var/lib/php5
    USE COOKIES: On
    USE ONLY COOKIES: On

    PHP/CURL: Supported
    PHP/CURL/VER: 7.22.0
    PHP/CURL/SSL: OpenSSL/1.0.1
    PHP/FSOCKOPEN: Supported
    PHP/JSON: Supported

    ACTIVE PLUGINS:

    akismet/akismet.php
    all-in-one-wp-security-and-firewall/wp-security.php
    better-delete-revision/better-delete-revision.php
    broken-link-checker/broken-link-checker.php
    contextual-related-posts/contextual-related-posts.php
    foliopress-wysiwyg/foliopress-wysiwyg.php
    inactive-user-deleter/inactive-user-deleter.php
    nextgen-gallery-optimizer/nextgen-gallery-optimizer.php
    nextgen-gallery/nggallery.php
    nginx-helper/nginx-helper.php
    nix-gravatar-cache/nf-gravatar-cache.php
    no-self-ping/no-self-pings.php
    page-links-to/page-links-to.php
    plugin-organizer/plugin-organizer.php
    really-simple-captcha/really-simple-captcha.php
    register-plus-redux/register-plus-redux.php
    remove-script-stylesheet-versions/remove-script-style-versions.php
    remove-wp-version-and-shortlink/version-shortlink.php
    responsive-image-widget/responsive_image_widget.php
    seo-image/seo-friendly-images.php
    si-captcha-for-wordpress/si-captcha.php
    sidebar-login/sidebar-login.php
    simple-google-sitemap-xml/simple-google-sitemap-xml.php
    simple-share-buttons-adder/simple-share-buttons-adder.php
    soliloquy-lite/soliloquy-lite.php
    stop-spammer-registrations-plugin/stop-spammer-registrations.php
    w3-total-cache/w3-total-cache.php
    widget-logic/widget_logic.php
    wordpress-seo/wp-seo.php
    wordpress-social-login/wp-social-login.php
    wp-hide-dashboard/wp-hide-dashboard.php
    wp-overview-lite/wp-overview-lite.php
    wp-slimbox2/index.php
    yith-maintenance-mode/init.php

    CURRENT THEME:

    Montezuma: 1.1.9

    # EOF

    http://ww.wp.xz.cn/plugins/wordpress-social-login/

Viewing 1 replies (of 1 total)
  • Thread Starter dfumagalli

    (@dfumagalli)

    Little update: I fixed the “port 8080” issue by tweaking the Nginx configuration:

    # Override the server port from 8080 => 80
    fastcgi_param SERVER_PORT 80;

    But the bad 404 error is still generated even with the correct URL.

Viewing 1 replies (of 1 total)

The topic ‘Some bugs’ is closed to new replies.