Forum Replies Created

Viewing 15 replies - 1 through 15 (of 383 total)
  • I have exactly the same problem. Here’s an entry from my PHP error log:

    PHP Fatal error:  Uncaught Error: Call to undefined method GuzzleHttp\Utils::chooseHandler() in /home/xxx/xxx/wp-content/plugins/google-listings-and-ads/vendor/guzzlehttp/guzzle/src/functions.php:61
    Stack trace:
    #0 /home/xxx/xxx/wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/HandlerStack.php(42): GuzzleHttp\choose_handler()
    #1 /home/xxx/xxx/wp-content/plugins/google-listings-and-ads/src/Internal/DependencyManagement/GoogleServiceProvider.php(124): GuzzleHttp\HandlerStack::create()
    #2 [internal function]: Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\GoogleServiceProvider->Automattic\WooCommerce\GoogleListingsAndAds\Internal\DependencyManagement\{closure}()
    #3 /home/xxx/xxx/wp-content/plugins/google-listings-and-ads/vendor/league/container/src/Definition/Definition.php(239): call_user_func_array(Object(Closure), Array)
    #4 /home/xxx/xxx/wp-content/plugins/google-listings-and-ads/vendor/league/ in /home/xxx/xxx/wp-content/plugins/google-listings-and-ads/vendor/guzzlehttp/guzzle/src/functions.php on line 61
    Plugin Author Peter Hardy-vanDoorn

    (@petervandoorn)

    Hi @cjk2

    The redirection only runs when the server is asked to deliver the page – as far as I understand it, most servers redirect from domain.com to www.domain.com (or vice versa) prior to this via either your DNS server or your web server, so it shouldn’t make any difference.

    The only thing I can think of off the top of my head is that your hosting company is employing some form of server-side caching which is misconfigured – ie, it’s caching the non-www address but not the www address.

    In the first instance, I would suggest that you investigate that and, if possible, disable any server-side caching so that you can test this hypothesis.

    Also, you should ask your hosting company to check that the www to non-www redirection is working properly.

    Let me know how you get on.

    Peter

    Plugin Author Peter Hardy-vanDoorn

    (@petervandoorn)

    Hi @linseyja

    Thanks for the input, but could you perhaps be a little more specific? I can assure you it does work, so there must be something that isn’t working right with your particular setup, or perhaps you’re misunderstanding what it’s supposed to do.

    If you could possibly let me know what isn’t working for you then I might be able to track down the problem and make it work for you.

    Cheers

    Peter

    Thread Starter Peter Hardy-vanDoorn

    (@petervandoorn)

    Thanks @duongancol. I’ve just sent you login details via the support form on your site.

    Thread Starter Peter Hardy-vanDoorn

    (@petervandoorn)

    So does this mean that it should work?

    I will do that, but I’ll need to set it up on another testing site that can be accessed as the 2 other sites mentioned are local.

    Thanks

    Plugin Author Peter Hardy-vanDoorn

    (@petervandoorn)

    Hi @philgreen

    Most server-side caching works by storing a rendered version of the page in the server’s RAM, so that means that the WordPress database won’t be queried and thus the Maintenance Redirect code won’t be run.

    I’m not a Siteground customer, so can’t check this personally, but if you look at this page: https://www.siteground.co.uk/tutorials/supercacher/dynamic-cache/ you’ll see that’s confirmed how it works. There’s a link on that page on how to manage their cache: https://www.siteground.com/tutorials/wordpress/sg-optimizer/supercacher/ and I suggest you study that to see how you can turn off their caching while you’re developing your site.

    Hope that helps

    Peter

    Plugin Author Peter Hardy-vanDoorn

    (@petervandoorn)

    Hi @pkclubpaul – apologies for not replying sooner but for some reason I don’t always receive notifications from wordpress.org about new posts!!

    To get you what you want as you can use the wpjf3_matches filter to check the URL of the page and allow access that way, for example:

    function my_wpjf3_matches( $wpjf3_matches ) {
        $slug = 'logo-upload'; // <- add the page slug here
        if ( stristr( $_SERVER['REQUEST_URI'], $slug ) ) 
            $wpjf3_matches[] = "<!-- Logo upload page -->";
        return $wpjf3_matches;
    }
    add_filter( "wpjf3_matches", "my_wpjf3_matches" );

    So, with that in your theme’s (child theme or self-coded, of course) functions.php file your logo upload page will be accessible.

    Hope that helps

    Peter

    Plugin Author Peter Hardy-vanDoorn

    (@petervandoorn)

    Hi @najram & @robsnijdersletigrenl (and apologies to @najram for not replying sooner – for some reason I don’t always receive notifications from wordpress.org about new posts – I only saw this because of Rob’s comment!!)

    Unfortunately, what you’re asking for isn’t possible as the redirect checks happen too early in the WordPress activation sequence – it actually happens before WP sets up the post data, so it’s not possible to use the built-in conditionals to check what page or post we’re on.

    However, there is as workaround to give you what you want as you can use the wpjf3_matches filter to check the URL of the page and allow access that way, for example:

    function my_wpjf3_matches( $wpjf3_matches ) {
        $slug = 'contact-us'; // <- add the page slug here
        if ( stristr( $_SERVER['REQUEST_URI'], $slug ) ) 
            $wpjf3_matches[] = "<!-- Contact us page -->";
        return $wpjf3_matches;
    }
    add_filter( "wpjf3_matches", "my_wpjf3_matches" );

    So, with that in your theme’s (child theme or self-coded, of course) functions.php file you could then set the redirect type to “Redirect – a little harder” and add the complete URL of your Contact Us page.

    Hope that helps

    Peter

    Thread Starter Peter Hardy-vanDoorn

    (@petervandoorn)

    Hi.

    Yes, that works perfectly too (and is much neater that my solution!!)

    Thanks for quick response.

    Peter

    I have the exact same problem. I’ve removed the old plugin to no avail, and the “Welcome… migrate now” panel is still at the top of every admin page.

    Thread Starter Peter Hardy-vanDoorn

    (@petervandoorn)

    That’s not entirely accurate. Yes, on the editing site blocks work differently, but when the page is output to the end user it is built using PHP just like everything else.

    I therefore stand by my assertion that it is a strange omission to not use the regular templates and hooks!

    Thread Starter Peter Hardy-vanDoorn

    (@petervandoorn)

    Thanks for the reply. I thought that was the case, and I understand that it might not be easy to patch into the blocks if Woocommerce haven’t given us the right hooks.

    However, the Woo blocks have been around for quite a while now, and I would have thought that you would, by now, have added the classes to your CSS to at least harmonise the styling!

    Thanks

    It might be the jQuery change in WordPress 5.5. Installing this plugin cured it for me:

    https://wordpress.org/plugins/enable-jquery-migrate-helper/

    Plugin Author Peter Hardy-vanDoorn

    (@petervandoorn)

    Great, thanks for updating!

    Plugin Author Peter Hardy-vanDoorn

    (@petervandoorn)

    Hi.

    This means that Maintenance Redirect has not been able to send the email. There could be two reasons for this:

    1. Maintenance Redirect uses WordPress’ built-in wp_mail function. Some hosting companies block sites from sending emails – you’ll know if yours does if you try to do a password reset from WordPress’ log in screen. It you get the reset email then you know that’s not the problem.

    2. The database table that stores the access codes might not have been set up properly. Do you see the access codes on your screen?

    Could you please try the following to see where the error lies:

    1. Try doing a password reset to see if you get the email. If that doesn’t work then contact your hosting company.
    2. Go to Plugins and disable Maintenance Redirect and then reenable it. This will make check for the database tables and create them if necessary. If that doesn’t work then try this:
    3. Add define( 'WP_DEBUG_LOG', true ); to your config.php file. Then try again and look in the /wp-content/debug.log file to see if there are any relevant errors. Please report the error by replying on this forum

    Thanks

Viewing 15 replies - 1 through 15 (of 383 total)