Thomas
Forum Replies Created
-
Hi @asahersh
sorry about that experience. As I haven’t heard before of anything similar I’m not really sure what you mean when you say “auto renew” and it crashed the entire site? There is no renewal as the plugin is completely free. If you give us some hint that would be greatly appreciated and we’d definitely look into it.
Thank you for the screenshot @manuel22 This helps. Could you add the following line to your wp-config.php?
define('PIWIK_PRINT_ERROR_BACKTRACE', true);I think then we should be able to see the trace that leads to this error and understand things better. The screen should basically change slightly and show a few file names and line numbers.
Does the entire page say that or is the page loading partially?
Any chance you could create another user in your WordPress (for example an administrator) and see if the same error happens there?
Sorry it’s taking a while. It’s one of those things that’s very likely very quick to find out when you have access to WordPress and the database but hard to know what it might be otherwise.
@p4r0dy have you had a chance to look at my previous comment or maybe any question around this?
@manuel22 when you click on the reporting link, can you let me know what URL it opens afterwards? Feel free to remove your domain but the path be useful. I’d just like to check if it mentions idSite 1 or idSite 2 there. I looked in the code and it should be using the idSite 1 ( as configured in
wp_optionstable).@thomasgoirand great to hear. Does this mean it’s the same issue on your production server and the issue is resolved?
Thanks for this @thomasgoirand
Seems the staging system is working and not having this error? I visited the staging site. It tracked my visit and the reports show it as well. You can see it when you click on
Matomo Analytics -> Summaryand then click onTodayorWeek.I noticed no data is shown when you click on
Matomo Analytics -> Reporting. Maybe the initial problem is resolved and this is now a different problem? This problem seems to be happening because the server doesn’t seem to serve HTML pages correctly. The server redirects requests from eg/files/plugins/matomo/app/plugins/CoreHome/angularjs/quick-access/quick-access.directive.html?cb=3e0e752ab672b35a60108a7fb65bdac1and redirects it to/files/plugins/matomo/app/plugins/CoreHome/angularjs/period-selector/period-selector.directive?cb=3e0e752ab672b35a60108a7fb65bdac1.I would assume there is either the web server configured to do these redirects or maybe a plugin is adding these redirects somehow. Any chance you know anything about it @thomasgoirand ?
I suppose to rule out the plugins we could maybe disable all the plugins except for Matomo and see if it works then (assuming the plugin would undo these redirect changes).
@manuel22 glad to hear it’s partially working. I wonder if the information is maybe still cached. Could you go to Matomo Analytics -> Diagnostics -> Troubleshooting tab and click there on “Clear cache”? If that’s the problem, it would eventually also resolve itself automatically.
Glad the data is still there @manuel22 Let me know how it goes and I’ll be happy to help.
Hi @p4r0dy
unfortunately we don’t yet have a feature to make this work out of the box.
You would first need to create a new Custom Dimension. You could call this new action dimension “Author” and then track the name of the author like this:
_paq.push(['setCustomDimension', 1, '$NameOfTheAuthor']);A new report will appear in the Visitor menu in Matomo afterwards.
To show the reports of their own pages for each author you would need to create a new custom widget. This could fetch the data from our WordPress API for example and then show the data.
Such a URL to fetch custom dimension data would look similar to this:
Does this help @p4r0dy ? I know it’s not trivial as it doesn’t come out of the box but depending on the resources you have re development this may not be too much work.
Hey @manuel22
sorry about the trouble. To find out whether the data for idSite 1 is still there you would need to execute below query. This requires access to your database and that you know how to execute a MySQL query. Would that work for you?
In below queries I assume your WordPress DB table prefix is
wp_. If that’s not the case you might have to adjust the queries to your WordPress table prefix. Let me know if you need help finding out that value (it would be shown in the Matomo System Report).select idvisit from wp_matomo_log_visit where idsite = 1 limit 1;If this query returns a result then the data is still there. In that case you could try if this makes the previously tracked data show up again:
update wp_options set option_value=1 where option_name = 'matomo-site-id-1';If this doesn’t work yet then you might need to execute the next query also:
update wp_matomo_site set idsite=1 where idsite = '2';Does this help @manuel22 ?
@thomasgoirand that’s wordpress@matomo.org . Sorry forgot to mention it.
@thomasgoirand staging be totally fine. Be great to send us also an email with the URL once you added this and also leave a comment here just in case the mail goes into spam. Thanks for this and thanks for your patience.
@dkrueger just checking if you had a chance to look at my previous comment yet? I haven’t seen an email yet. Just checking in case it was marked as spam or so.
I still have trouble reproducing this issue. Is there any chance you could upgrade to the new version which we released today (4.3.0)? There’s a small chance this might fix the issue in the next two days but it might not. We’ve continue to tried and find a way to reproduce it but weren’t successful. If this doesn’t help would it be in worst case possible to get access to your WordPress installation?