bluegeek9 → made their first commit to this issue’s fork.
Hi @armz23,
That block was removed in 8.x-2.20.
That was showing the total page views. We are now tracking each visitor uniquely and showing unique visits.
There is not an effective way to revert to old versions of Visitors.
📌 Remove the Visitor block Fixed
Changelog
Issues: 4 issues resolved.
Changes since 8.x-2.23 → :
Bug
- #3498839 → : UNK: config_browser_name too long
Task
- #3451813 → : Remove JavaScriptSnippet class
- #3496785 → : Browser language Null
- #3496400 → : Optional: Device Detect
I am not sure what you are requesting.
The visitor block was removed.
You can update the views to use total view instead of unique visitors.
bluegeek9 → created an issue.
bluegeek9 → made their first commit to this issue’s fork.
bluegeek9 → created an issue.
After reviewing your Drupal.org profile, we have to pass on your offer. You are not credited with enough fixes to be made a co-maintainer.
bluegeek9 → made their first commit to this issue’s fork.
Webforms are not nodes. This project only works with nodes.
bluegeek9 → made their first commit to this issue’s fork.
bluegeek9 → created an issue.
Can you show which issues you and your team have worked on?
bluegeek9 → made their first commit to this issue’s fork.
Hi @sourav_paul,
I addressed the bug in a different issue to clarify the change in the release notes.
📌 UNK: config_browser_name too long Active
8.x-2.24 will be released after 📌 Remove JavaScriptSnippet class Active is fixed.
bluegeek9 → created an issue.
bluegeek9 → made their first commit to this issue’s fork.
bluegeek9 → created an issue.
bluegeek9 → created an issue.
Visitors does allow for the statistics to be copied. It does not use the migrate sub-system.
The feature was added in a recent version of Vistiors, so that will not be of much help if you are on Drupal8.
The Statistics module has a migrate plugin. You could migrate the view count to Drupal11. Then use Visitors to copy the view count. That might be your best bet if you need a solution today.
Since there is an existing plugin, it would not be too hard to adopt it for Visitors.
bluegeek9 → created an issue.
bluegeek9 → created an issue.
bluegeek9 → created an issue.
The issue is already fixed in the dev release.
bluegeek9 → created an issue.
I am not able to reproduce the error. Which version of Vistitors are you using?
Maybe replace the active visitors view, with the one in config/optional ?
Hi Wes,
It looks like the browser language is not included/available.
With a resolution of 800x600, I think it is a wearable, or embedded device.
I created another issue to work on the error.
📌
Browser languare Null
Active
{
"7": ["route","entity.node.canonical"],
"8":["path","/node/1"],
"9":["viewed","node:1"],
"10":["server","a87f84d82bc8"]}
&_id=3b3e8f5e050b8447
&_idn=1
&_refts=0
&action_name=Custom software solutions | MyCompany Hosting LLC
&cookie=1
&h=14
&idsite=1
&m=12
&pf_dm1=908
&pf_dm2=0
&pf_net=0
&pf_onl=1
&pf_srv=2
&pf_tfr=0
&pv_id=2SPdOc
&r=679717
&rec=1
&res=800x600
&s=31
&send_image=0
&uadata={"fullVersionList":[],"mobile":false,"model":"","platform":"","platformVersion":""}
&uid=0
&url=https://myserverhost.com/
bluegeek9 → created an issue.
How often does the error occur?
Is this error on a local/development machine, or production?
bluegeek9 → created an issue.
I don't think the error is caused by visitor_localtime. It allows NULL.
Maybe it is the language?
@kongkx,
Which report has the bad link? I am having trouble reproducing the error.
@sourabhsisodia_,
I think you did not use composer to install visitors. You need to use composer.
bluegeek9 → made their first commit to this issue’s fork.
Thank you Wes!
I plan to make a new release. Would you verify the bug is resolved?
bluegeek9 → made their first commit to this issue’s fork.
Thank you Wes!
I made a MR for just the cache issue.
In Visitors 3.0.x, the geoip location service is/will be provided by MaxMind module.
bluegeek9 → created an issue.
bluegeek9 → created an issue.
bluegeek9 → changed the visibility of the branch 8.x-2.x to hidden.
bluegeek9 → changed the visibility of the branch 3484155-progress-bar to hidden.
I am confident it is the visitors_title. It is limited to 255 characters. I also recently stumbled upoun this error.
✨ Impression tracking Active
bluegeek9 → created an issue.
In 3.0.x, page views are stored in the visitors_log table. I want to track search metrics: keyword, page number, and search rank.
If the columns are added for search, maybe they could be used for entity type, bundle, entity id when viewing a canonical route.
Hi wes.congruityworks.com,
It sounds like you did not uninstall the module before going to and reverting from 3.0.x. That branch should not be used.
The change is in the Dev branch if you want to use it now.
A new release, 8.x-2.22, will be made before the end of the year if you want to wait.
Hi Wes,
Thank you for reporting the error.
Did you recently install Visitors, or did this happen after a recent update?
I left these four issues. All the changes in the pull request are whitespace changes.
FILE: /var/www/html/web/modules/custom/charts/modules/charts_chartjs/src/Settings/Chartjs/ChartjsScales.php
------------------------------------------------------------------------------------------------------------------------------------------------------
FOUND 4 ERRORS AFFECTING 4 LINES
------------------------------------------------------------------------------------------------------------------------------------------------------
32 | ERROR | Public method name "ChartjsScales::getXAxes" is not in lowerCamel format (Drupal.NamingConventions.ValidFunctionName.ScopeNotCamelCaps)
42 | ERROR | Public method name "ChartjsScales::setXAxes" is not in lowerCamel format (Drupal.NamingConventions.ValidFunctionName.ScopeNotCamelCaps)
52 | ERROR | Public method name "ChartjsScales::getYAxes" is not in lowerCamel format (Drupal.NamingConventions.ValidFunctionName.ScopeNotCamelCaps)
62 | ERROR | Public method name "ChartjsScales::setYAxes" is not in lowerCamel format (Drupal.NamingConventions.ValidFunctionName.ScopeNotCamelCaps)
------------------------------------------------------------------------------------------------------------------------------------------------------
bluegeek9 → made their first commit to this issue’s fork.
bluegeek9 → created an issue.