Thomas
Forum Replies Created
-
Hi @saowp I’ll be happy to have a look into this. Any chance you could send us a system report (see https://matomo.org/faq/wordpress/how-do-i-find-and-copy-the-system-report-in-matomo-for-wordpress/) and a screenshot of the titles displayed in chinese or a description where this is happening? Eg do you mean the browser title or maybe a “page title” in the “page title report”? You can send it to us to wordpress at matomo.org
Generally Matomo isn’t translating anything but only recording / tracking the actual browser title that was used in a page. Is your site being used in China maybe?
@kirstenosa not sure to which text you refer to exactly. Maybe
CoreAdminHome_OptOutErrorNoCookies(“The tracking opt-out feature requires cookies to be enabled.”)? This would be only shown when cookies are disabled.“This website use Cookies.” this text is maybe not from us? At least I could not find this exact wording.
The settings are bit hard to find. Sorry about that, should have mentioned it.
* Log in to your WP Admin dashboard
* Click on Matomo Analytics -> Settings
* Click on the “Matomo Admin” tab
* You should now see the Matomo admin with a link on the left to “General settings”
* There you should find the settings under the “Customise translations” section.Does this work?
Hi @shawfactor
you can configure this in the Matomo Admin on the “Privacy -> Users Opt Out” page. To get there follow these steps:
* Log in to your WP Admin dashboard
* Go to Matomo Analytics -> Settings
* Click on “Matomo Admin” tab
* In the left menu click on “Privacy -> Users Opt-Out”There you should find the setting for do not track see screenshot: https://ibb.co/WBBNPT9
Does this work for you @shawfactor ?
Hi @kirstenosa you could install this plugin: https://plugins.matomo.org/CustomiseTranslations#description see how to install a Matomo Marketplace plugin in Matomo for WordPress
Then you can translate the wording for these translation keys:
*
CoreAdminHome_OptOutComplete
*CoreAdminHome_OptOutCompleteBis
*CoreAdminHome_YouMayOptOut2
*CoreAdminHome_YouMayOptOut3
*CoreAdminHome_YouAreNotOptedOut
*CoreAdminHome_UncheckToOptOut
*CoreAdminHome_YouAreOptedOut
*CoreAdminHome_CheckToOptInDoes this help @kirstenosa ?
In case you are a developer: We do not yet support WordPress filters for changing these translations but we started this in https://github.com/matomo-org/wp-matomo/pull/36 The code for this is in
wp-content/plugins/matomo/classes/WpMatomo/OptOut.phpand we could add filters if that helps.Hi @angiepunkt
could you check if the file
/home/wp/disk/wordpress/wp-content/plugins/matomo/app/bootstrap.phpexists? Did you install the plugin through the WordPress plugins directory? I wonder if the file was somehow not copied/written correctly.Forum: Plugins
In reply to: [Connect Matomo - Analytics Dashboard for WordPress] E_COMPILE_ERRORHi @angiepunkt Is there a chance this maybe refers to this plugin: https://wordpress.org/plugins/matomo/ ? Could you maybe create a support issue in our plugin for this? And then ideally also post the output of the system report there? https://matomo.org/faq/wordpress/how-do-i-find-and-copy-the-system-report-in-matomo-for-wordpress/
It seems to detect the Matomo directory wrong and I’ll be happy to look into it. Maybe some issue with symlinks or something.
I see. If you can’t change the initial
get_users()options then it won’t be possible to do anything. Changing the query parameter wouldn’t help because when the users uses your “approve membership” feature it would then also send theum_statusparameter and the issue be the same. I guess there’s nothing you can do in this case then. Thanks though for looking at it.Hi @champsupertramp yes it basically appends when approving a user/membership feature. Then the status variable is present from your plugin basically. We’re listening eg to the
profile_updatedhook and then callget_usersand it then only returns one user.@sebibiller as I haven’t heard from you in a while I’m assuming the issue is fixed and I’m marking it as resolved but happy to follow up should you still have this issue. Simply leave a comment any time.
Thanks for your valuable feedback @janaa . Very appreciated.
Problem 1:
I’ve documented this now in the app so it will be more clear in the future, thanks for this. It will be available in the next update.Problem 2:
The trigger conditions are definitely optional and it should not be needed. Maybe some cached container version was being tested or there was some other issue. Maybe you could try to remove that optional condition again and release a new version? This should work. If there’s still an issue, feel free to send us a link to the page where we can reproduce this to wordpress@matomo.org and we’ll be happy to investigate further.Problem 3:
Unfortunately we don’t support non-interactive events so far. We have an open issue for this here: https://github.com/matomo-org/matomo/issues/9199Problem 4:
Unfortunately, because we don’t have non-interactive events yet the average time on page might not be always correct when events are triggered on the page. It’s basically connected to problem 3. Additionally, the time spent on the last page view (if there is no event happening on that page) is currently always counted as 0s unfortunately. We have an issue for this in https://github.com/matomo-org/matomo/issues/9539We classified both these issues as major issues as they are quite important and I’m hoping that we can fix them in the next year.
I hope this helps @janaa ?
@tomasrisbergsilentse any chance you can send us the Matomo system report see https://matomo.org/faq/wordpress/how-do-i-find-and-copy-the-system-report-in-matomo-for-wordpress/ ? You may need to enable
define( 'MATOMO_SAFE_MODE', true );to avoid the maintenance error you are getting. You could send us the report by email to wordpress@matomo.org or paste it as a comment here (the report should be anonymised).Have you for now downgraded to 1.3.0 so it works again? I’ve looked through the changes and so far I can’t really explain it yet why this would happen. Did you maybe also update other plugins?
Hi @tomasrisbergsilentse sorry about that! Do you know from which version you updated? Do you see any more information or getting any email about any error?
Thanks for that @petermatthesius This will definitely help in the hope that they will eventually solve this for all WordPress installation as currently the next user might have to go through the same thing.
@petermatthesius I’ll close this issue for now as there is unfortunately nothing we can do for now. We have added a check to the system report under the browser section in the hope users will become aware of this issue more easily and will still look into further ways to improve the situation.