Jump to content
adrian

Tracy Debugger

Recommended Posts

The new Console panel fullscreen mode now has keyboard shortcuts to collapse the code or results panes quickly.

Here you can see me toggling all code, all results, and the split of both.

Shortcuts are:

CTRL+SHFT+ 

Up arrow - collapses code pane
Down arrow - collapses results pane
Left arrow - to restore split to what it was before you initiated any pane collapses.

Hopefully you'll find this a really quick way to get to the view you need.

rlLAPv47u9.gif.0f3c122f4c276e2f3833fd9971ed6d46.gif

  • Like 4

Share this post


Link to post
Share on other sites

New version fixes a few bugs in the last release, especially regarding the keyboard shortcuts on Windows. Along these lines, I have also changed the shortcuts for the History Stack - they are now ALT+PageUp and ALT+PageDown. This means there is no longer the need to use the meta key (CMD or WIN key) for this which was conflicting on some systems. If you're on a Macbook without PU and PD keys, just use: fn + ALT + PageUp/Down

A big thanks to @Robin S for helping with all the Windows testing on this!

I think this is really starting to work really nicely now - I almost want to use it over my code editor 🙂

Anyway, please let me know if you find any issues.

  • Like 2

Share this post


Link to post
Share on other sites

Hi Adrian,

Does the "User dev template" feature do anything with _main.php if using the delayed output strategy?

If not, what do you think about adding a feature where _main.php is replaced with _main-dev.php if that file exists? Of course the relevant file names would depend on what is defined in $config->appendTemplateFile and the Tracy "User dev template suffix" setting. And to round things out I guess do the same for $config->prependTemplateFile (_init.php).

Share this post


Link to post
Share on other sites
13 hours ago, Robin S said:

Hi Adrian,

Does the "User dev template" feature do anything with _main.php if using the delayed output strategy?

If not, what do you think about adding a feature where _main.php is replaced with _main-dev.php if that file exists? Of course the relevant file names would depend on what is defined in $config->appendTemplateFile and the Tracy "User dev template suffix" setting. And to round things out I guess do the same for $config->prependTemplateFile (_init.php).

Hey @Robin S - it didn't, but now it does 🙂

I have also implemented this for the User Bar Page Versions feature and the Template Path panel. These three things do almost the same thing, but for different users in different scenarios.

I am going to PM you a copy of this new version to take a look at. I have some other things I am working on and I want to commit altogether.

  • Like 1

Share this post


Link to post
Share on other sites

Various significant updates today.

As per @Robin S's suggestion above, the User Bar Page Versions, User Dev Template and Template Path panel features now support automatic swapping out of the files included via `$config->prependTemplateFile` and `$config->appendTemplateFile` to use the same suffix at the replaced template, eg `_init-dev.php` or `_main-dev.php` if you are on the home page and using a home-dev.php template file replacement.

Robin also helped me track down a critical bug that was introduced to Page Versions and User Dev Templates some time ago - thanks for that!

If you haven't checked out any of these features in Tracy before, they can be very handy for testing changes (especially on a live site). In particular, giving your clients access to choose from a dropdown of template options can be a very easy way to get their feedback on various options.

I have also made several improvements to the new Console panel fullscreen editing experience and also updated the way the results pane scrolls when new items are added. Previously it always scrolled to the bottom of the pane. Now it scrolls to the top of the recently added section, so if you are using Clear & Run, then it will alway be at the top, but if you just Run to add new items, it will scroll down to the top of the new items. Hopefully you'll all find this a nice improvement and will help to reduce your scrolling.

I recently noticed some nasty issues with the Console panel in Safari, especially the new fullscreen editing mode, but also when trying to manually resize the panel. Everything looks/works great on Chrome, Firefox, and Opera. I'll take another look and see what I can do about getting Safari to play nicely, but sometimes I feel like Safari is the new IE 🙂

 

  • Like 3

Share this post


Link to post
Share on other sites

Ok, I officially hate Safari more than I already thought I did 🙂

I have fixed a whole range of issues I had never noticed previously (mainly because I rarely use it).

Detailing here in case they are useful for your development in general.

 

1) You can't resize panels smaller than their initial size on page load

I did however fix the internals of the Console not expanding to match a larger panel if you size larger.

The issue is that Webkit browsers will not let you use the CSS "resize" property to resize an element to make it smaller, only larger (in both dimensions): https://css-tricks.com/almanac/properties/r/resize/

Man it took me a long time to figure out why that wasn't working - I thought there was some min-height / min-width type thing going on that was only affecting Safari.

Thank goodness Chrome no longer uses the Webkit engine!

 

2) Safari doesn't play nicely with position: fixed when elements are outside document.body

The Tracy core adds its elements to document.documentElement so the only way I could figure around this was to move the Console panel to document.body when clicking the new fullscreen toggle and then back again when restoring to the panel size. This was also really difficult to track down and I never found any reference to this issue online anywhere - fun times 🙂 

Because the parent element is changed, I had to change the parent element of several css selectors. I can't find anything broken as a result, but please keep an eye out and let me know if you see anything amiss.

 

3) Fix missing inner scrollbar in code editor pane

This one looks to be a long standing Ace Editor bug, but someone else figured out a simple workaround: https://github.com/ajaxorg/ace/issues/2872

 

4) Fixed some keyboard shortcut bugs due to missing e.preventDefault()

Please let me know if you find any other issues like this

 

Anyway, I think I am done with Safari tweaks for now. I am not sure how many of you are even using it for regular development so I don't want to put too much more time into it, but please do let me know if you find anything I missed.

 

  • Like 3

Share this post


Link to post
Share on other sites
2 hours ago, adrian said:

using it for regular development

Are you kidding? 😉

Thanks a million, btw!

  • Like 1

Share this post


Link to post
Share on other sites

One more quick update. In addition to the existing shortcut keys for toggling the size of the code and results panes in the Console panel, I have added a new one:

CTRL + SHFT + → 

Which resizes the code pane to the height of all the lines of code:

EycZvBSDZG.gif.1fa6a8dac547b943637cf06a069a21fa.gif

  • Like 4

Share this post


Link to post
Share on other sites

One more shortcut 🙂

CTRL + SHFT + ENTER will toggle the Console in and out of fullscreen.

 

Totally random, but a little tip about the Console panel - not only is it great for testing the PW API and PHP in general, it's also pretty nice for testing JS code out. Take this example of:

  • calling an external API
  • populating an element in the Console results pane with a property from the returned JSON
  • logging the result to the browser dev console

ctN9oBrlFD.thumb.gif.598b9cab370b2ba85cdc2f10919f3669.gif

 

Why use this over the browser console, or CodePen, JSFiddle etc? Well, notice that the API call is grabbing a PW field from the current page:

'https://represent.opennorth.ca/postcodes/<?=$page->postcode?>/'

 

Also, if you are a fan of the output of the Browser dev console, don't forget about Tracy's fl() option to dump objects direct to this.

Anyway, hope there is something useful there if you hadn't thought about it before 🙂

  • Like 3

Share this post


Link to post
Share on other sites

Hi,

I have installed TracyDebugger on a live website, enabled it, set output mode to Development, and enabled File Editor

but I cannot find the FileEditor e.g. to edit the online template files. What do I have to do to find it ?

 

tracy.jpg

Share this post


Link to post
Share on other sites

My bad sorry. I found the File Editor.

But when I select a template file on the left, the editor window on the right does not update. The editor window on the right stays the same.

Double clicking on a template file on the left does not make a difference, the editor window on the right always shows the same.

tracy-2.jpg

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, pwired said:

But when I select a template file on the left, the editor window on the right does not update. The editor window on the right stays the same.

Double clicking on a template file on the left does not make a difference, the editor window on the right always shows the same.

Works for me. Can you please check for JS errors in the browser dev console.

Any difference in another browser?

  • Like 1

Share this post


Link to post
Share on other sites

Is it necessary to have debug = on for the file editor to work ?

I am using FireFox, will try Chrome

Share this post


Link to post
Share on other sites
Just now, pwired said:

Is it necessary to have debug = on for the file editor to work ?

Nope!

  • Like 1

Share this post


Link to post
Share on other sites

Ok the problem must be in my FireFox browser

Edit:
The File Editor is working perfectly in my Chrome browser,
and also in my Opera browser (45.0)

Thanks Adrian

 

Edited by pwired
Tried Opera Browser
  • Like 1

Share this post


Link to post
Share on other sites
Just now, pwired said:

Ok the problem must be in my FireFox browser

The File Editor is working perfectly in my Chrome browser

Good to hear - I'll take a look here with Firefox on Mac and see if I can reproduce and fix it.

Share this post


Link to post
Share on other sites

I am using FireFox Quantum ver 61.0.1 (64bit)

Maybe it has become messed up after so many weeks of heavy use. Will do a clean install and check again.

Share this post


Link to post
Share on other sites

@pwired - I could reproduce with Firefox on MacOS and I have pushed a fix in the latest version. Please let me know how it goes at your end.

New version also removes the keyboard shortcut text from the top of the Console panel and adds a new toggleable popup info table of all shortcuts:

cValA8pRkk.thumb.gif.961039bee582b637e21d26e082f5e677.gif

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

I uninstalled the previous version 4.11.32 and installed the latest version 4.11.34

I can confirm: now it is working in FireFox,

 

Record_2018_09_19_04_41_44_238.gif

 

Thanks, all good.

  • Like 1

Share this post


Link to post
Share on other sites

Another round of tweaks, bug fixes and new features.

1) File Editor revamp to improve layout and adds a new fullscreen editing mode (like the one added to the Console panel), also with the same CTRL + SHFT + Enter shortcut for toggling in and out of that fullscreen.

2) More tweaks and code cleanup for the Console panel.

3) Some nice enhancements and cleanup for the SnippetRunner panel.

4) New "Open" option for the "Goto Page ID" feature in the PW Info panel - this opens the page's branch in the page tree. I find this entire feature very useful when working on sites where the templates make heavy use of IDs instead of paths for querying pages. If you haven't tried, give it a go. 🙂

5) Various bug fixes in the module and also in the Tracy core.

There are quite a lot of changes in this version, so please let me know if you find any issues.

 

 

  • Like 4

Share this post


Link to post
Share on other sites

Another round 🙂

1) I have revamped the fullscreen / halfscreen buttons that are on many of the panels. They have been replaced by a single Maximize / Restore button which I think it much more useful. Hope you guys agree!

2) I have removed the "open in window" link from all panels - I never used this feature and it was painful to get the layout of some of the more complex panels to work in this mode. If others are finding they miss it, let me know and I'll see about reinstating it.

 

  • Like 4

Share this post


Link to post
Share on other sites
11 minutes ago, adrian said:

Hope you guys agree

I did agree a week ago or two too 🙂

Nice updates btw.

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, tpr said:

I did agree a week ago or two too 🙂

Nice updates btw.

I know, it was your suggestion that prompted me to make the change 🙂

Sometimes I am slow on coming around to a good idea 🙂

 

  • Haha 1

Share this post


Link to post
Share on other sites

Hey @tpr - sorry I just realized it was a bit rude of me to not acknowledge that change as your idea when I posted about it above.

Sorry about that!

  • Like 1

Share this post


Link to post
Share on other sites

No you haven't, don't take it too seriously 🙂

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By picarica
      so i am trying to put CustomHooksForVariations.module, a custom module, i am placing it into site/modules direcotry yet my modules page in admin panel gives me errors
      so this is the screen show when i refresh modules, i dont know why the shole hook is written on top of the page :||

      and this next image is when i try to install it, i saw that it is not defiuned modules.php but it shouldnt need to be ?, any ways i dont want to edit site's core just to make one moulde work there has to be a way

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
×
×
  • Create New...