Jump to content
adrian

Tracy Debugger

Recommended Posts

Everyone else coming from 3.0152 to 3.0153 seeing this? Looks correct to me based on what Ryan just committed to the core.

image.png.b0bf7af11ce1f08ce6b4f7bf59eb8a90.png

Share this post


Link to post
Share on other sites

Thanks @bernhard - those Breadcrumb and $process methods have been persistent for a while. I think you'll actually need one more update for them to disappear. I "reset" my cache when I was updating Tracy yesterday by going from 152 back to 151, then to 152 and today to 153. Can you remember to check on upgrade to 154 and let me know if the problem still persists please? Thanks.

Share this post


Link to post
Share on other sites

Not sure if that helps, but I have this site under git, so I reverted to 1.0.152, did a modules refresh, then went back to master branch (1.0.153) and this is what I get: 

Sdc9fBG.png

Share this post


Link to post
Share on other sites

Thanks @bernhard - is that just the start of things - is it listing virtually everything as new? It is kinda looking like the old cached version was removed somehow in the downgrade / upgrade process. Let's see what others report their experience to be.

Share this post


Link to post
Share on other sites

Now it shows this, so I guess it was somehow messing up with some cached values 🙂 

KTJZGCR.png

Wow, this even works for my own $theme API variable 😮 

  • Like 1

Share this post


Link to post
Share on other sites

@adrian Hi. 

I'm facing a small issue and I'm not sure that this one is relative to Tracy, but I feel that it's better to ask anyway.
I have quite a simple template that outputs page views based on the GET parameters.

Spoiler

<?php namespace ProcessWire;

	bp('template before');
	if (!config('ajax') || !input()->get('post_ids')) {
		wire404();
	}

	$layout->preventOutput(true);
	$dirty_post_ids = input()->get('post_ids');
	$post_ids = implode('|', sanitizer('intArray', $dirty_post_ids));



	header('Content-Type: application/json; charset=utf-8;');
	$data = cache()->getFor('PostViews', $post_ids, 300, function () use ($post_ids) {
		return pages()->getById($post_ids, [
			'getNumChildren' => false,
			'joinFields'     => [
				'phits'
			]
		])->explode(function ($p) {
			return [
				'id'    => $p->id,
				'views' => (int) $p->getViewsCount(3.3)
			];
		});
	});

	echo wireEncodeJSON($data, 0);
	bp('template after');
	$this->halt();

URL of this page is /ua/views/.

The issue is that I have significant and unreasonable leap in memory usage

image.png.b53bb594a76de53db13001323e8dc983.png

The strange thing is that if I change URL ( page name) to something else like v or view I get (if not contains 'views')

image.png.9bb5fdd73198780eb605dd1e6438b52e.png

I have reviewed all the code and did not find anything where occurs 'views'.

I don’t have any idea what can cause it, it's just some kind of mysticism, so I thought maybe it could be an issue with Tracy or Performance Panel. 

Thanks. 

Share this post


Link to post
Share on other sites

Hey @adrian

I've just started using live.js because I'm doing some work in the backend where I need JS/LESS a lot. After getting tired of reloading the browser I thought I'd try browsersync that I recently discovered but it did not work. Then I found live.js and added this to my module:

if(!$this->user->isSuperuser()) return;
if(!$this->config->debug) return;
$this->config->scripts->add('http://livejs.com/live.js');

And this just works!!

The great thing about it is that it even recognizes when my style.less file changed. The great thing here is that it does not reload the browser but only replaces the CSS file (which is crazy because the CSS is parsed via RockLESS on demand, so the server must somehow be involved. Anyway... the style gets updated without reloading the page as soon as I change my LESS file 😎

I thought this would be very easy to include in Tracy. For the frontend it would need to add the whole script tag instead of doing $config->styles->add(), but that would also be simple.

What do you think?

Edit: I understand now how the less-part works. On every poll of live.js the server is involved, so live.js results in lots of requests to your server! I don't think that's a very good option...

Share this post


Link to post
Share on other sites

@Zeka - sorry, I am not sure - that Performance panel is not my own work - it comes from https://github.com/Zarganwar/PerformancePanel although it hasn't seen any updates in a long time. It would be great if you could figure out where the problem is coming from though if you have the time.

@bernhard - thanks for the idea - but sounds like it's a no go afterall.

Share this post


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

but sounds like it's a no go afterall.

Unfortunately yes 🙂 

Share this post


Link to post
Share on other sites

Hi @adrian,

Is it possible to switch into a user with the guest role only using the User Switcher panel? I didn't see the default guest user available there so I created a new user with only the guest role but it doesn't appear either.

Or do you know of another way to get the debug bar to appear on a remote site when not logged in? (of course you would never to this on a live site - my site isn't publicly accessible)

Share this post


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

Is it possible to switch into a user with the guest role only using the User Switcher panel?

Use the logout button on the user switcher panel and it should do what you want.

  • Like 1

Share this post


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

Use the logout button on the user switcher panel and it should do what you want.

Thanks! I just had to start a User Switcher session and then the logout button did the trick.

  • Like 1

Share this post


Link to post
Share on other sites

Major new release, thanks in big part to @Robin S for ideas, testing, and feedback.

1. The Console panel now stores it's snippets on disk so they can be backed up, be under version control, and also editable via your external code editor (with direct link from the entry in the Console snippet sidebar). They are stored in either /site/templates/TracyDebugger/snippets/ or /site/assets/TracyDebugger/snippets/

Note that all your pre-existing snippets that were previously stored along with Tracy's module settings will be automatically written to disk when you upgrade to the new version of Tracy.

2. You can define a block of code to be prepended to the snippet when it is saved to disk. For example, Robin is using:

<?php namespace ProcessWire;
//<editor-fold desc="API variables">
/**
 * @var Config $config
 * @var Fieldgroups $fieldgroups
 * @var Fields $fields
 * @var Languages $languages
 * @var Modules $modules
 * @var Page $page
 * @var Pages $pages
 * @var Paths $urls
 * @var Permissions $permissions
 * @var ProcessWire $wire
 * @var Roles $roles
 * @var Sanitizer $sanitizer
 * @var Session $session
 * @var Templates $templates
 * @var User $user
 * @var Users $users
 * @var WireCache $cache
 * @var WireDatabasePDO $database
 * @var WireDateTime $datetime
 * @var WireFileTools $files
 * @var WireInput $input
 * @var WireLog $log
 * @var WireMail $mail
 * @var \ProCache $procache
 * @var FormBuilder $forms
 **/
//</editor-fold>

 

3. The SnippetRunner panel has been removed because it's no longer necessary with the new behavior of the Console panel.

4. The Console panel has a new inbuilt DB backup feature. If checked, it will backup your complete DB. The backups are stored under /site/assets/backups/database/ which is where Ryan's Database Backups module (http://modules.processwire.com/modules/process-database-backups/) stores its backups. It is recommended to install this module to make managing and restoring backups much easier. Backups can be automatically named: tracy-console-2020-04-14-18-23-38.sql or you can specify a custom name in the Console panel if you'd like to set something more meaningful before a major change. Automatically named backups are automatically pruned when there are a set number of backups (default is 25, but is configurable in module settings).

5. The user switcher panel now has the option to use a PW API selector string as a way to determine which users will be listed.

6. There is a new Quicklinks section at the top of the module settings to more quickly get to what you're looking for (code thanks to Robin).

7. Lots of other tweaks, fixes and improvements.

8. New core versions of Tracy and ACE editor.

Please let me know what you think and if you have any problems.

PS - please do a hard reload in your browser to ensure you get the new css and js files.

 

 

 

  • Like 4

Share this post


Link to post
Share on other sites

Big, big thanks @adrian for all your ongoing work on Tracy Debugger - it just gets better and better!

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites

Hello There @adrian

I am having a strange problem with the wonderfull tracy that started a long time ago but i havent notice until now because i have not used it in a while.

But i am getting errors about:
- The Console Panel
- The ProcesswireInfoPanel
- The ApiExplorerPanel

I will attach screenshots of the errors with some sensitive parts blured out for security.

I hope we can resolve this because i love to use the Console.

I am running:
- Processwire 3.0.153
- Tracy Debugger 4.21.1
- PHP 7.3.16
 

tracy_Debugger_console_error.thumb.png.5fc535d15ae1feb26b85c28b40119a80.pngtracy_Debugger_ProcesswireInfoPanel_error.thumb.png.68fcc9f997633760545e452dc1e47436.pngtracy_Debugger_ApiExplorerPanel.thumb.png.9337c6b027918efc50e3726976f6d1f9.pngtracy_Debugger_toolbar.thumb.png.22430b96c90b196200dd142ae2582a9d.pngtracy_Debugger_toolbar.thumb.png.22430b96c90b196200dd142ae2582a9d.png

Share this post


Link to post
Share on other sites

Hi @EyeDentify - what host are you using? Any chance it's nextcloud or one.com ? https://github.com/nextcloud/server/issues/16752

I can see why you might be getting the error in the PW Info panel, but am confused about the other two. Can you please try disabling the PW Info panel and see if that fixes the other two as well. If it does, then I think we might be able to do a try / catch for the PW Info panel that will fix it.

Finally, do you know why there are two copies of the main Tracy bar - that looks strange to me.

  • Like 1

Share this post


Link to post
Share on other sites

@EyeDentify - could you also check whether set_time_limit is actually in the php.ini disable_functions list?

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

Hi @EyeDentify - what host are you using? Any chance it's nextcloud or one.com ? https://github.com/nextcloud/server/issues/16752

I can see why you might be getting the error in the PW Info panel, but am confused about the other two. Can you please try disabling the PW Info panel and see if that fixes the other two as well. If it does, then I think we might be able to do a try / catch for the PW Info panel that will fix it.

Finally, do you know why there are two copies of the main Tracy bar - that looks strange to me.

Hi @adrian

Thanks for getting back to me.

I have one.com as host.

I am baffled by the double bar as well, but it says AJAX on the other one.

I tried to disable Info panel but that did not do any difference to the Console error.

Where do i check for the disable_functions list?

Share this post


Link to post
Share on other sites

If the other bar says AJAX, then that is expected, but your screenshot didn't show that at all, hence my question.

Looking at the error messages for the Console and API Explorer panels more closely, it shows it's actually coming from PW's core FileCompiler.php file on line 384. The PW core uses set_time_limit in many places: https://github.com/processwire/processwire/search?q="set_time_limit"&unscoped_q="set_time_limit" so I think your only decent option is a different host because from what I can tell, one.com doesn't let you enable set_time_limit.

  • Like 1

Share this post


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

If the other bar says AJAX, then that is expected, but your screenshot didn't show that at all, hence my question.

Looking at the error messages for the Console and API Explorer panels more closely, it shows it's actually coming from PW's core FileCompiler.php file on line 384. The PW core uses set_time_limit in many places: https://github.com/processwire/processwire/search?q="set_time_limit"&unscoped_q="set_time_limit" so I think your only decent option is a different host because from what I can tell, one.com doesn't let you enable set_time_limit.

Oki.

Thats unfortunate, because i just changed to one.com 🙂

But everything else seem to work with PW other then the Tracy Debugger.

I get this string:
"disk_total_space, diskfreespace, exec, system, popen, proc_open, proc_nice, shell_exec, passthru, dl"

When i run:
 

<?PHP print_r(ini_get('disable_functions')); ?>

 

Share this post


Link to post
Share on other sites
31 minutes ago, EyeDentify said:

But everything else seem to work with PW other then the Tracy Debugger.

Can you try a few different things for me:

1) Empty the PW trash

2) Do a field export (from the main fields list page)

3) Install the core ProcessPageClone module and click the new "COPY" page list action button

If those all succeed without error, I'll revisit, but otherwise I'll need to update Tracy to be PW 3.x only so that it avoids the FileCompiler completely. That would solve the Console and APIExplorer panel error. The PW Info panel error is due to the Versions List feature trying to check if the system allows runtime modification of max_execution_time so I could conditionally remove or deal with that, but I'd like to make sure those other core PW things work on that host first.

It's also weird how one.com seems to disable set_time_limit / max_execution_time some other way - ie not in disable_functions - make it much harder to detect. 

 

  • Like 1

Share this post


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

Can you try a few different things for me:

1) Empty the PW trash

2) Do a field export (from the main fields list page)

3) Install the core ProcessPageClone module and click the new "COPY" page list action button

If those all succeed without error, I'll revisit, but otherwise I'll need to update Tracy to be PW 3.x only so that it avoids the FileCompiler completely. That would solve the Console and APIExplorer panel error. The PW Info panel error is due to the Versions List feature trying to check if the system allows runtime modification of max_execution_time so I could conditionally remove or deal with that, but I'd like to make sure those other core PW things work on that host first.

It's also weird how one.com seems to disable set_time_limit / max_execution_time some other way - ie not in disable_functions - make it much harder to detect. 

 

 

I did the following:
1. Empty trash
2. Did a sucessfull field export

Did not install the ProcessPageClone because it had no install button, it seems to be manual only.
i am not sure how to install it manually.

And PW says i have an newer version of the ProcessPageClone in the system "1.0.4?"

install_ProcessPageClone.thumb.png.977fc6227b45228b24ab76363f7cf688.png

Share this post


Link to post
Share on other sites

It looks like you already have ProcessPageClone installed - do you have the "copy" button in the Page list action buttons?

Not sure where to go from here - I feel like one.com should be failing on those PW core calls to set_time_limit() as well. Any chance you can give me access to the server - either this one, or another test one at one.com?

 

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

It looks like you already have ProcessPageClone installed - do you have the "copy" button in the Page list action buttons?

Not sure where to go from here - I feel like one.com should be failing on those PW core calls to set_time_limit() as well. Any chance you can give me access to the server - either this one, or another test one at one.com?

 

Hello Again.

I Get a "Copy" option on any pages under the Root in pagelist.

I am going to uninstall Tracy Debugger and install it again and see what happens.
Cause some things have been acting strange like the image upload issue i postet about a short while ago then went away.

I will think about the server access thing.
 

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 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 (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...