@yujiman85 so i have not yet done a clean install to test but i have eliminated a bunch of x-factors.
I can confirm that this is not happening with [site:base-url] but is definitely happening with [current-page:title] - please try using this specific token
im going to spend time trying to get more direct repro steps and work on doing a quick clean install to see if i can make it happen
Hi @thisisalistairsaccount is this still causing issues? If not, I will close. Thanks.
I am updating the tags according to the issue tag guidelines → and I am marking this in need of additional reproduction steps.
@sbrenner02 Have you been able to reproduce the bug on a clean Drupal installation?
It's possible there's other factors here ... we do have 'display if no results' enabled and a good number of modules on the site but most of which are not really relevant to views, tho Better exposed Filters is in use here. I'll try to nail down better repro but we are seeing this fairly consistently on our views with tokens
- 🇺🇸United States yujiman85
I followed the step-by-step directions for this issue and the only time the header disappeared was when there were no results after using an exposed filter. I was able to get the header to stay by enabling "Display even if view has no result" and it was permanently visible. Basically I couldn't reproduce this consistently, just my observation.
Drupal 10.3.10
View block with Ajax enabled
Global text area using token [site:base-url]
Exposed filters for title and published state - 🇬🇧United Kingdom steven jones
Sorry for the lack of attention to your issue, please accept my apologies.
Drupal 7 is going to be end-of-life'd by the community in approximately 1 month. →
As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on 📌 Close down Drupal 7 issues Active .
If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :) - 🇬🇧United Kingdom steven jones
Sorry for the lack of attention to your issue, please accept my apologies.
Drupal 7 is going to be end-of-life'd by the community in approximately 1 month. →
As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on 📌 Close down Drupal 7 issues Active .
If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :) - 🇬🇧United Kingdom steven jones
Sorry for the lack of attention to your issue, please accept my apologies.
Drupal 7 is going to be end-of-life'd by the community in approximately 1 month. →
As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on 📌 Close down Drupal 7 issues Active .
If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :) - 🇬🇧United Kingdom stevewilson
With version 1.0.0 of Statistics module, on Drupal 10.3.10 and PHP 8.1.30, I've run the following tests - first without and then with the changes in MR !7 applied:
Clear caches;
Load a page with number of views showing;
Note number of views;
Load a different page;
Reload the first page;
Note number of views.WITHOUT the MR !7 changes in place, on reloading the first page, the displayed number of views is unchanged from when the page was first loaded. Displayed number of views only increases after clearing caches.
WITH the MR !7 changes in place, on reloading the first page, the displayed number of views is incremented by 1 from when the page was first loaded. Further reloads result in further increments of the displayed number of views - no need to clear caches.
In other words, for me, the changes in MR !7 fix the failure to update issue.
- 🇮🇳India newswatch Delhi/Bangalore
I installed the module on a site where it had not been installed earlier.
I waited for 3 days to check. The ticker is not rolling. All stats remain 0 for all nodes.
