One visit is getting broken down into multiple visits (10+ in some cases).
I’m pretty sure that it’s the same session because all the visit data is identical. Most visits have single action/event.
There can’t be a visit with single Event.
Event is only triggered after the page is loaded. Hence, it would have at least 1 additional page action.
Did anyone face this issue before? Any idea about how to fix this?
Make sure you're using latest Matomo version. if you can reproduce the issue consistently, for example create a small HTML page with the code to reproduce, then create a bug report at: www.github.com/matomo-org/matomo/issues/ and the team will investigate.
Related
We recently upgraded one of our client sites to 09.01.01 to address a Telerik vulnerability, and then had to migrate the site from managed.com to Azure due to manage.com's outage. After the upgrade, a couple of pages on the site have been uneditable using the pencil icon in the persona bar, although the rest work fine. We're aware of the workaround of going into content > pages and clicking the pencil icon there, but even then not all of the areas on the page are editable. For example, there's one instance of the HTML module on the homepage where when you click on its pencil and then click "Edit Content," it just displays a pop-up with the text but no WYSIWYG or way to actually edit. Other instances of the HTML module work fine, on other pages and even other areas of the homepage.
What's more bizarre is that we just spun up another Azure VM and created a dev site from a clone of the live site so we could troubleshoot further, and this problem does NOT occur on that site even though it's an exact copy of the live site files and database and both sites are hosted in Azure.
Does anyone have advice on what might be causing this or how to troubleshoot? My original though was to clone the page and start removing modules one by one to see if anything made a difference, but it doesn't actually remove the module when I click delete. I've read about ways to do this directly in the database, but I'd prefer to avoid that if possible, especially since we're not seeing the same problem on the cloned site.
Thank you!
Could you please see if any error appearing on the logs folder? You can see the logs here. /Portals/_default/logs/2021.02.01.log.resources? The log file name may differ based on website's logging configuration.
A similar thing can be seen from the Personal bar as well using Admin Logs.
Google's webmaster tools is showing a large number of pages have mobile usability issues (see screenshot) yet once you click on the link and then click on "Check Live Version" (of the same page), it shows that everything is fine ("Page is mobile-friendly" in green). After resubmitting that page to the google indexer the page still appears to have issues a few weeks later.
It almost seems like a different algorithm is used to check mobile usability by the indexer and the Live tester.
Has anyone come across this issue? Any pointers as to how to reconcile these?
Thanks!
I just got this reply from another forum:
"If the page passes the live test, there is nothing more you can do.
The report is slow to update at times, so might just be delayed."
I have a site page with 3 external lists which display data through BCS connecting to an Azure SQL database as a web part.
They all display their data correctly when the page is in edit mode, but when saved, it just continually loads each web part and doesn't seem to finish.
Has anyone experienced the same issue?
[Edit]: Loading the lists on their own when not inserted to a page will work fine.
I seem to have solved my own issue.
Setting the web part miscellaneous properties to "Server Render" has all web parts loading their external data as expected.
My own inexperience seems to be the issue here, but I'm sure people familiar with web parts would know this.
This answer may helps others in the same situation.
I am importing products using Commerce Feeds. The products appear just fine on the front end and via Store > Products in the admin. However no products appear under Content in the admin area. I have tried clearing out the database, re-importing, re-indexing, flushing caches - nothing works.
Also this is bizarre and seemingly un-related, however I noticed it around the same time I realized my products were not appearing in the admin - there is a strange whitespace above my admin menu bar - which only appears on the Content page (also coincidently the page giving me trouble.)
Using Commerce Kickstart (commerce_kickstart-7.x-2.0-rc1) (Would love to upgrade to the latest release but I am unsure how to do this without losing a great deal of work. I have not found a good upgrade document - please chime in if you know something I don't!)
I feel kind of stupid now. I edited the admin/content view and saw there was a filter criteria which caused it to not display nodes of type "product_display." Evidently this is intentional behavior. I am guessing you are only supposed to manage products from within the store tab. Still wish I could figure out the cause of the phantom whitespace at the top though.
I'm playing with Salesforce's "Sites" functionality today for the first time, whereby I can expose Salesforce functionality to anonymous users via VisualForce. It's cool, but I'm seeing some weird timing behavior. I've been trying to figure it out, but it's a mystery, so I'll ask here?
When I save my changes to my VisualForce page, I would expect to see the changes right away. Or at least, when I do a "real" save (by hitting "Save"), versus a "Quick Save," which I assume is what happens when I'm using the developer toolbar to edit -- or actually hitting the "Quick Save" button in the main VisualForce section.
At any rate, I save it as much as I possibly can, and I'm able to see the right thing when I go to the VisualForce page itself (not using the force.com URL). But when I go to the force.com URL, I'm seeing an old version of a page. If it's just a matter of waiting long enough, that's one thing. But it's acting like I'm doing something wrong.
During development, it is very helpful to add a cache="false" parameter to the apex:page tag. This should solve the issue.
Reference page for apex:page has other optional parameters as well.