sonictail

Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Forum: Plugins
    In reply to: [Simple History – Track, Log, and Audit WordPress Changes] SH’s logs causing table bloat that negatively affects backups
    sonictail

    (@sonictail)

    3 months ago

    @eskapism all good, already sent to your support email. Just search for my username at gmail 🙂 Also no sweat in terms of reply time, I completely get having too many emails!

    I suspect a simple security plugin preventing multiple login attempts and perhaps even geofencing would go a long way in terms of just making your WP more secure and preventing the DB bloat in simple history.

    Keep up the good work!

    Forum: Plugins
    In reply to: [Simple History – Track, Log, and Audit WordPress Changes] SH’s logs causing table bloat that negatively affects backups
    sonictail

    (@sonictail)

    3 months ago

    Not a standard occurrence, but has occurred for me with multiple DBs on different websites. Have emailed @eskapism with the details.

    Forum: Networking WordPress
    In reply to: MU Cookies will not allow login and cause redirect loop
    Thread Starter sonictail

    (@sonictail)

    6 months, 2 weeks ago

    As I realise, the link from the dashboard to the other sites won’t work due to cookies. As they’re different domains.

    That’s a helluva showerthought.

    So I think this is done, the position of Cookie_Domain matters a lot!

    Forum: Networking WordPress
    In reply to: MU Cookies will not allow login and cause redirect loop
    Thread Starter sonictail

    (@sonictail)

    6 months, 2 weeks ago

    Talk about aggravating.

    1. they’re whole domain names for the sub sites. That does make sense, but you can cross login from the MU root menu.
    2. There’s usually a translation layer so at least some of .htaccess can be used. But depends on install, here I confirmed it is not installed.
    3. yep, disabled theme and plugins again. No dice.
    4. left it all disabled and turned off javascript, again no dice.

    So somehow I think I almost fixed it.

    1. Add ‘define(‘COOKIE_DOMAIN’, $_SERVER[‘HTTP_HOST’]);’ single directly below the rest of the multisite definition in wp-config.
    2. Clear the cache.

    That appears to allow multiple site dashboards at once.

    However, slight issue. now you cannot jump between sites using the My Sites > Site > Dashboard link, it boots you out to the login. BUt you can log straight back in.

    Forum: Networking WordPress
    In reply to: MU Cookies will not allow login and cause redirect loop
    Thread Starter sonictail

    (@sonictail)

    6 months, 2 weeks ago

    Huh, just got this which might be just AI garbage generated from the webhost.

    Thank you for testing that change. This behavior confirms a cookie domain mismatch—using define(‘'‘COOKIE_DOMAIN', $_SERVER[‘'‘HTTP_HOST‘'‘]); restricts sessions to the current subdomain, which is why you can only log in to subsites, not the main site.

    For WordPress Multisite with subdomains, the recommended approach is usually to omit the COOKIE_DOMAIN line entirely from wp-config.php. WordPress should then handle cookies across all subdomains automatically.

    And wants me to just add

    define('ADMIN_COOKIE_PATH', '/');
    define('COOKIEPATH', '/');
    define('SITECOOKIEPATH', '/');

    However, that did not fix the issue.

    Forum: Networking WordPress
    In reply to: MU Cookies will not allow login and cause redirect loop
    Thread Starter sonictail

    (@sonictail)

    6 months, 2 weeks ago

    Hi @bcworkz thanks for your reply, it’s appreciated.

    .htaccess

    Yep, we are using the WordPress >=3.5 Subdomain example as seen here Apache HTTPD / .htaccess – Advanced Administration Handbook | Developer.ww.wp.xz.cn

    In fact, dropped it all back just to that. No luck here. As we’re on is using NGINX and I believe Litespeed I’m not sure if it’s configured for it, but anyways. Have checked again 🙂

        Looking at wp-config again

        Here’s the config portion, if I have this it works fine with MainSite.com

        define( 'MULTISITE', true );
        define( 'SUBDOMAIN_INSTALL', true );
        define( 'DOMAIN_CURRENT_SITE', 'www.MainSite.com' );
        define( 'PATH_CURRENT_SITE', '/' );
        define( 'SITE_ID_CURRENT_SITE', 1 );
        define( 'BLOG_ID_CURRENT_SITE', 1 );
        define( 'NOBLOGREDIRECT', 'http://www.MainSite.com' );

        The noblogredirect is the only additional line, however it does not change anything disabling.

        I did play with the cookie settings as seen here.

        define('ADMIN_COOKIE_PATH', '/');
        define('COOKIE_DOMAIN', '');
        define('COOKIEPATH', '');
        define('COOKIE_DOMAIN', $_SERVER['HTTP_HOST'] );

        However when I enabled these lines in the wp-config, it entirely locked me out of the whole setup. I got the same symptom of endless redirect loop. The interesting part is that I got the redirect URL you mentioned.

        https://mainsite.com/wp-login.php?redirect_to=https%3A%2F%2Fmainsite.com%2Fwp-admin%2F&reauth=1

        However, removing it did nothing. Killing those define cookie path lines stops this issue entirely.

        Hoping for cookie to actually be active?

        This was one of the first things to try, yep I’ve seen it too. However in this case we have no luck. Just loops back to wp-admin.

        So I’m gonna explore two potential solutions.

        1. I think I might try turning off all plugins on both sites, see what happens.

        2. Install a clean subsite. See what happens.

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