• Resolved kingfisher64

    (@kingfisher64)


    Hello,

    Upon install (tried several times) I get the following WP Die Admin/Includes/Menu.php 380 with Query Monitor.

Viewing 12 replies - 16 through 27 (of 27 total)
  • Thread Starter kingfisher64

    (@kingfisher64)

    Yes I’m the administrator with full permissions.

    I wonder why I don’t see get started sub-menu?

    I tried both /matomo/index.php and /matomo/app/index.php and both result in same issue so I’ll contact the hosting provider about nginx setup and get back.

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    That specific menu item (Get Started) only displays to users that have the superuser_matomo capability, which should be granted to all super admins upon installation. Perhaps the install didn’t run entirely… Are you able to check what capabilities your user has (you may need to install a plugin to be able to check this)?

    The menu item also won’t show if your install is multi site and you are not the network admin. Is your install multi site?

    Thread Starter kingfisher64

    (@kingfisher64)

    I think you are right regarding the install as the query monitor error shows up immediately after activation.

    I’m not on a multisite no ??

    I am administrator as I’m the only user on the site as it’s a dev site at present to try out different plugins/designs etc. This user role is the one I inherited when seting up the WordPress install.

    Thread Starter kingfisher64

    (@kingfisher64)

    Correction I assumed administrator “inherited” matomo super user. I’m not sure it does so will need to look into this further then report back ??

    Thanks for your time and advice so far.

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    Actually, if the Diagnostics page shows then your user must have the matomo superuser capability. There’s a button on the get started page that lets you hide the page forever, but I can’t see how that button would have been clicked if the page was never shown to you. Is this the first time you installed the plugin or have you installed it before?

    Thread Starter kingfisher64

    (@kingfisher64)

    Yes this is first time installed. Perhaps I should try an install on another blank site just as a test to see how this varies from this install and to see if these issues show up again.

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    You could try with the new version just released. It has one change related to this that *may* work better for you.

    If it doesn’t work, and you’re a developer (assuming you might be since you’re talking about a local instance), and you want to look into this further, this is where in the code for the plugin the Get Started submenu item is added: https://github.com/matomo-org/matomo-for-wordpress/blob/develop/classes/WpMatomo/Admin/Menu.php#L79-L93

    Thread Starter kingfisher64

    (@kingfisher64)

    Thanks @dizzyatinnocraft I see the getting started so have setup this. The plugin did not fail on install with no query monitor error page showing. So that will do nicely!

    Thank you for your support.

    I did try altering the .htaccess as described on the matomo.org support page. however what was in place is not the standard and it 500 errored out. This is what’s already in place:

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    How would the following be added/combined to this to allow the external matomo links to work? I assumed the first 3 lines and closing wouldn’t alter and tried in a completely separate ifmodule statement with no success so far.

    <IfModule mod_expires.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST URI} ^.*wp-content/.*\.php$
    RewriteCond %{REQUEST URI} !/matomo/app/
    RewriteRule ^(.*)$
    RewriteRule ^(.*)$ - [R=403,L]
    </IfModule>

    Many thanks

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    @kingfisher64 I think you would need to add:

    RewriteCond %{REQUEST_URI} ^.*wp-content/.*\.php$
    RewriteCond %{REQUEST_URI} !/matomo/app/
    RewriteRule ^(.*)$
    RewriteRule ^(.*)$ - [R=403,L]

    right before </IfModule>, without removing anything.

    Thread Starter kingfisher64

    (@kingfisher64)

    I tried that now and it 500 errors out. I dont’ know either as htaccess rules are not my thing. The full rule looked like (hoping I understood and actioned what you said exactly).

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    RewriteCond %{REQUEST_URI} ^.*wp-content/.*\.php$
    RewriteCond %{REQUEST_URI} !/matomo/app/
    RewriteRule ^(.*)$
    RewriteRule ^(.*)$ - [R=403,L]
    </IfModule>

    I’ll ask around regarding this ??

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    Yes, that’s what I suggested. I would’ve expected that to work… You may want to look in the apache error logs (the location is platform dependent, on Ubuntu based machines it should be at /var/log/apache2/error.log).

    EDIT: maybe remove this line RewriteRule ^(.*)$. Also if you’re still using nginx, the htaccess file won’t have an effect.

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    Marking this as resolved for now. Let us know if you need any more help or have any more questions.

Viewing 12 replies - 16 through 27 (of 27 total)
  • You must be logged in to reply to this topic.