WordPress.org

Ready to get started?Download WordPress

Forums

WP-Piwik
[resolved] Unknown site/blog in settings (4 posts)

  1. csigncsign
    Member
    Posted 2 years ago #

    Hi,

    I run WP 3.3.1 with newest wp-piwik plugin and newest Piwik software as a multisite installation (sub blogs in subdirectories), where these sub blogs are mapped to subdomains. I have deactivated all other plugins and tested it with WP standard theme.

    The plugin is NOT (!) activated as network, but only in - for the moment - in the main blog!

    When I try to change the settings there of wp-piwik I get an error "unknow site/blog".

    I tried your test script here:
    http://peepbo.de/board/viewtopic.php?f=4&t=13

    and it gives me the result:


    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <html><head>
    <title>403 Forbidden</title>
    </head><body>
    <h1>Forbidden</h1>
    <p>You don't have permission to access /statistik//
    on this server.</p>
    </body></html>

    Is it really right, that there is a double slash behind "/statistik"?
    Maybe this is causing the error?


    /statistik//

    Because in my test script I have added just this:


    $strPiwikURL = 'http://xxxxx.de/statistik';

    http://wordpress.org/extend/plugins/wp-piwik/

  2. braekling
    Member
    Plugin Author

    Posted 2 years ago #

    The double slash was caused by a test script bug. Please try again with the new test script and the same URL.

    This bug doesn't exist in WP-Piwik but in the test script only.

    (And please avoid double postings in different support forums.)

  3. braekling
    Member
    Plugin Author

    Posted 2 years ago #

    Maybe there is a fix regarding this "Unknown site/blog" (see http://peepbo.de/board/viewtopic.php?f=4&t=13&p=49#p47 - German). I'll have a look at this and will release a new WP-Piwik version as soon as possible.

    If you like to test this fix on your own, please let me know if it works for you.

  4. csigncsign
    Member
    Posted 2 years ago #

    Problem has been solved! Was my own fault with blocking in the htaccess, sorry!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags