• Resolved leo1951

    (@leo1951)


    Hello, I have raised this issue before since I have several websites. I hope that I can get a solution, The issue is present on two websites. Both sites are running on Ubuntu with Nginx. It is a frustration especially since Google is recommend Site Kit be used for placing ads on the site. I now have no adds runnning.

    I am running PHP8 and WordPress 5.7.1.

    Please give possible suggustions. what is the meaing of the error message? Error: Request parameter is empty: accountID. The problem is on the adsense section.

    Now there is no adds running.

    Send me that secure link I wl upload my Health Check
    I never had site kit installed on this site before.
    Thanks

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out. Based on the error message, which is slightly different to your other reported issue there may be something hosted related blocking Analytics setup. Another user who reported the same issue provided insights into their setup below:
    https://github.com/google/site-kit-wp/issues/2782

    Regardless if you want to share your Site Health information for this particular site please do so here or privately using this form, while including your current hosting provided.

    In relation to your ads not working I’ll also see what I can find on this, or whether it’s related.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing your Site Health information. I suspect what’s occurring is a particular nginx configuration, based on your details provided and the issue as reported by another user. If so this isn’t something we can solve on the plugin side however we can try and pinpoint the cause.

    Firstly can you share the following:

    1. Did Site Kit work as expected previously on both these impacted sites?
    2. As you have multiple websites can you share whether this occurs with other sites on the same hosting platform? You mentioned it occurs on 2 sites, I’m curious if the sites whereby this doesn’t occur are using the same hosting setup
    3. Have you tried resetting the plugin on one of the impacted sites before setting up once more? Note that resetting the plugin will result in you having to connect all modules once more. Other connected users will also have to setup the plugin once more.

    Let me know if you have anymore questions on the above.

    Thread Starter leo1951

    (@leo1951)

    Thanks for responding. You seem to be making an observation that could be causing the problem. All of my sites are using the same configuration of Nginx. The fresh installation of the plugin is having a problem, whereas the old installations are working. I want to run some tests if I can have an old version of Site Kit like 1.25.0. The upgrade of the plugin is fine where I installed it some time back. It is a new installation that I see the problem with.

    Where Site Kit was

    search_console_property: https://www.multimixradio.com/
    adsense_account_id: none
    adsense_client_id: none
    adsense_account_status: none
    adsense_use_snippet: yes
    adsense_web_stories_adunit_id: none
    analytics_account_id: 1472???
    analytics_property_id: UA-1472??????
    analytics_profile_id: 3614????
    analytics_use_snippet: yes
    tagmanager_account_id: none
    tagmanager_container_id: none
    tagmanager_amp_container_id: none
    tagmanager_use_snippet: yes
    Plugin Support James Osborne

    (@jamesosborne)

    You’ll find older versions of the plugin here, although I wouldn’t recommended downgrading. If you do wish to test older versions be sure to reset your currently installed Site Kit version in full and uninstall from your plugin repository.

    Rather than downgrading while you mentioned that you checked your Nginx configuration files and they all match are you using a WP Toolkit or Softaculous? Maybe you can spin up additional new testing WordPress sites before checking on these sites.

    I can also propose some troubleshooting steps to rule out the issue being with installed plugins or your current theme if you wish.

    Thread Starter leo1951

    (@leo1951)

    Hello James, if “plugin here” meant to be a link, then you missed pasting the link.

    I will first install the plugging on a fresh installation and on an old installing that never had the plugin.

    I will share the fix if I come up with one.

    Plugin Support James Osborne

    (@jamesosborne)

    Apologies, you are correct. Here is the link to where you’ll find previous versions of the plugin.

    And yes, please do share details on a fresh install. Hopefully we can gain some additional insights.

    Thread Starter leo1951

    (@leo1951)

    Thanks very.

    As I start to troubleshoot on two sites running WordPress 5-71 with PHP 7.4, never install the plugin before, I get the error, `Warning: include(/usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/vendor/composer/autoload_classmap.php): failed to open stream: No such file or directory in /usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/loader.php on line 26

    Warning: include(): Failed opening ‘/usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/vendor/composer/autoload_classmap.php’ for inclusion (include_path=’.:/usr/share/php’) in /usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/loader.php on line 26

    Warning: include(/usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/third-party/vendor/composer/autoload_classmap.php): failed to open stream: No such file or directory in /usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/loader.php on line 28

    Warning: include(): Failed opening ‘/usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/third-party/vendor/composer/autoload_classmap.php’ for inclusion (include_path=’.:/usr/share/php’) in /usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/loader.php on line 28

    Warning: array_merge(): Expected parameter 1 to be an array, bool given in /usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/loader.php on line 28

    Warning: require(/usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/third-party/vendor/autoload_files.php): failed to open stream: No such file or directory in /usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/loader.php on line 53

    Fatal error: require(): Failed opening required ‘/usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/third-party/vendor/autoload_files.php’ (include_path=’.:/usr/share/php’) in /usr/share/nginx/html/wp-content/plugins/site-kit-wp-1.25.0/includes/loader.php on line 53`.

    I started with version 1.21 and working my way up on the two sites. However, it’s late, and I must go to bed. I will continue tomorrow. I disable auto-update on WordPress.

    Please leave the ticket open. I will complete the progress and will not update on still I end the progress.

    Hello @leo1951 ,

    Thanks for your efforts in investigating this, which may be useful for other users with the same hosting setup.

    For Site Kit GitHub version it requires Composer to install that’s why you are seeing warnings & fatal errors.

    Please download the previous version from Site Kit plugin page & make a try again. I hope you’ll not see those errors on activation of the Site Kit.

    Best Regards,

    Thread Starter leo1951

    (@leo1951)

    The solution is with Nginx.

    In your Nginx open config # sudo nano /etc/nginx/conf.d/xxxxxxx.conf and change the line in location / {
    try_files $uri $uri/ /index.php; [to:] try_files $uri $uri/ /index.php$is_args$args;
    check for error >$sudo nginx -t
    If al OK reload Nginx: >$sudo systemctl reload Nginx.

    The issue is not with the plugin, but it an Nginx/WordPress problem. Other issues show up in some WordPress installation when editing a post, and this is also the fix.

    Plugin Support James Osborne

    (@jamesosborne)

    Many thanks for the update, really appreciate your efforts which we can keep in mind for other Nginx users who encounter the same.

    If you have any plugin related questions be sure to get in touch. Thanks again.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Error: Request parameter is empty: accountID.’ is closed to new replies.