Jump to content
adrian

Redirect Id Based Urls

Recommended Posts

This module redirects ID based URLs to the full SEO friendly URL
 
 
Very simple module that alllows you to link to pages with their page ID in the URL. The ID can be in any location in the URL.
 
There is a config option to simply load the content to the ID based URL, rather than redirecting to the original PW url if you prefer. If you use this option, the module adds a canonical link to the page to help identify the ID based URL as a duplicate of the proper PW url so Google won't penalize you for duplicate content.
 
For example you could do any of the following, where 1058 is the ID of the page you want to load:
 
At the moment for this to work, the page ID segment of the URL must be the only segment that is all numerical, otherwise, anything goes.
 
The reason for this module is mostly as a way to have a very simple shortlink to any page on the site, but it also allows for structuring URLs however you want with any content you want. I guess this could be abused and potentially bad for SEO!
 
I am not sure if this is a good way to do this, so I would definitely appreciate any feedback.
  • Like 5

Share this post


Link to post
Share on other sites

I thought of this already, but gave up on the idea because it allows anyone to start trying random numbers and get pages that you don't want accessible to everyone. One way of avoiding this would vbe to have a global checkbox field that you would have to check to activate the shortlink to that page.

Share this post


Link to post
Share on other sites

Hey diogo - I agree that could be an issue, but surely if pages are viewable then they will be indexed by search engines anyway. The module does check to make sure the page is not an admin page and that it is viewable for the user. Maybe that's not enough?

I'd be happy to add the checkbox idea though if you think that would help. Perhaps a "disable if checked" approach, or maybe a module config setting to change the behavior of the page specific checkbox - either check to enable, or check to disable, so there is the option to go either way.

Another option might be to require it to be enabled on a per template basis - an ASM field in the module config would allow you to specify templates that would work.

Edited by adrian

Share this post


Link to post
Share on other sites

The page is not indexed if there's nothing linking to it. I would have the links disabled by default at least and the checkbox to enabled them, and maybe the possibility of enabling by template (as you said) or by parent because it makes all the sense to enable all descendants of a page (articles page for instance). Like this, you could enable the links to all the site just by enabling the descendants of home. Or am I complicating? :)

Share this post


Link to post
Share on other sites

Hey Adrian, thanks for the Module, if I read that right, it looks like functionality I remember from Textpattern? If so then it was something I was trying to do (very poorly) in this thread, linked just in case it's any help (can't believe it will be tho ;))—actually that thread title is misleading, the post I was referring to was this one on that thread.

Edited by alanfluff

Share this post


Link to post
Share on other sites

IF this module ends up being is a goer (security implications sorted n'all) would it be possible to have some way in the admin of letting the user copy the short url to that page. I can see where this would come in handy for a site or two.

Share this post


Link to post
Share on other sites

@diogo - I have added support for limiting this functionality to only those selected templates (in the module config settings). I was also trying to add support for by page, but have come across a very strange thing - I can't seem to get an array of pages using wire('pages'). I get:

Trying to get property of non-object in /share/www/usaus-h2o-dev/site/modules/ProcessRedirectIds/ProcessRedirectIds.module on line 179

I have commented out this section of the code for the moment, but if you have any ideas why this isn't working, I'd love to hear them :)

@alanfluff - thanks for that link - I think this module will take care of what you are looking to do.

@Marty Walker - I have added a new tab to page edit screen in the admin called ShortLinks that lists a few key links for that page that the user might be interested in. The last example I give on that tab makes me wonder whether this module should actually be renamed to something that mentions permalinks.

I am not sure where to go with this now - I will definitely be using this for an upcoming site, but I would really like some feedback from some other PW gurus, especially Ryan, as to whether this should be a released module and whether you guys think this idea of a permalink like:

http://www.mysite.com/1234/articles/my-article-title/

is a good idea to be promoting or not. I know that Page Path History does an amazing job already of handling changes to page names and parents. So would the idea of using this module to create this style of permalink be redundant, or just bad practice?

Thanks for any feedback.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian This module is exactly what I was looking at doing before, but done better, so thanks again.

I've not read up on Page Path History but I see your question re that or this module. I like the idea of this module, my only comment would be that perhaps the approach the BBC take might be better, it's the same as yours but instead of

http://www.mysite.com/1234/articles/my-article-title/ 

they use

http://www.mysite.com/articles/my-article-title-1234

I assume as the result may be slightly better SEO-wise.

Edited by alanfluff

Share this post


Link to post
Share on other sites
I can't seem to get an array of pages using wire('pages'). I get:

What's the idea on these lines?

foreach(wire('pages') as $p) {
            $fieldEnabledPages->addOption($p->name);
        }

Grab all the pages?

funny, wire("pages") or even wire("pages")->find() also don't return anything to me (the same happens with $pages on templates, by the way), but wire("pages")->find("sort=sort") does. Maybe you can try that.

try:

foreach(wire("pages")->find("sort=sort") as $p) {
            $fieldEnabledPages->addOption($p->name);
        }

Anyway, I'm not sure if it is a good idea to iterate all the pages of the site in a module because it might cause problem on bigger sites.

  • Like 1

Share this post


Link to post
Share on other sites

@alan - I have added support for your suggested URL structure. Please test when you get a chance and let me know how it goes for you.

@diogo - thank you for the testing. The ->find("sort=sort") works for me too - any ideas why it doesn't work as normal?

Good point about iterating all those pages on a large site - that definitely won't work well at all. I have changed config setting to a InputfieldPageListSelectMultiple and it seems to work well now.

So now it is possible to limit the redirection of these links by template and or page/page parent.

Any other thoughts/ideas? 

Share this post


Link to post
Share on other sites

I asked Ryan about this module and he is happy with it going in the modules directory, so I have submitted it:

http://modules.processwire.com/modules/process-redirect-ids/ 

It is fine to have it run on all your pages/templates (the default), but don't forget to check out the module config settings where you can limit this. Remember it is only called by pages that return a 404 so I don't believe there should be any overhead on normal page loads.

So please feel free to start using it and let me know if you have any improvements you'd like to see.

  • Like 1

Share this post


Link to post
Share on other sites

Sorry I didn't get to test it Adrian, I'm sure it would have been a redundant test and I'll be trying this out next site I build, congrats on the Module and thanks!

Share this post


Link to post
Share on other sites

This module accomplishes exactly what I was looking for today. Thank you very much Adrian for making this available.

  • Like 1

Share this post


Link to post
Share on other sites

IF this module ends up being is a goer (security implications sorted n'all) would it be possible to have some way in the admin of letting the user copy the short url to that page. I can see where this would come in handy for a site or two.

Is this really such a security risk..? ...that people could guess IDs? It's not about whether those pages are indexed by Google; the same risk definitely applies to the default slug-based permalinks -- like Adrian said, he'd assume they would already be publicly inaccessible from the server-side, me too; it's no more secure than not doing so and leaving the regular slugs (unless you have yours or your titles randomly generated as complex strings). Or am I missing something?

Anyway I can't wait to try this out, thanks much.

Share this post


Link to post
Share on other sites

@hellomoto,

I don't really think there is a security risk, especially given that you can limit this module's actions to specific templates and pages if you wish.

Anyway, hope it works as you expect!

Share this post


Link to post
Share on other sites

Hey! Ok so it doesn't quite work as I expected, though it does work great... but what I'm looking to do is actually use the IDs for pages of one of my templates. 

I have it set up to Redirect (default), Rewrite Links checked, Rewrite Format = /sales/listings/{$page->make->name}/{$page->model->name}/{$page->id}/

/sales/listings/ is the path preceding each listing anyway, which is the template I have the rewrite enabled for.

So it works in my listings index on the frontend, but then those links redirect to their default URLs. I thought this might be accomplished with Load selected for Redirect Type instead of Redirect, but that gives me this error:

Compile Error: Cannot redeclare browserTitle() (previously declared in /.../site/templates/includes/functions.php:5) (line 10 of /.../site/templates/includes/functions.php)

Lines 5 and 10 are the beginning and ending of that function... So I don't know why that would be happening...

Update: I changed my header to include_once the functions. This is fixed :)

But what I really want is to redirect the default URL for each listing to the one I design. Like from the backend, the links still go to /sales/listings/{$page->name}/ when I want them to be what I set too, or at least redirect to what I set. I want the URL I set to be the absolute one. Anyone know how? Thanks.

Share this post


Link to post
Share on other sites

The Load option should do exactly what you are looking for. 

You shouldn't have the /sales/listings at the beginning of the rewrite format - just use:

/{$page->make->name}/{$page->model->name}/{$page->id}/

I haven't tested thoroughly with adding extra path segments like you are doing, but it seems to be working fine here. Typically I just put dashes between the components.

Glad you sorted out the include_once issue :)

To get the View links when editing a page to also be rewritten, make this change to line 115:

     if($page->id!=1 && $page->template != 'admin') {

to:

     if($page->id!=1) {

I did a quick test and I don't think there are any issues with this, but would appreciate you testing it before I make it live.

Share this post


Link to post
Share on other sites

I just tried out the module and I can confirm that it works just like it says.
 
I'm new to Processwire, so forgive me if what I'm suggesting is to much.  I come from the Drupal land.  In Drupal, all pages have a id called an nid(node id).  With core Drupal you can visit any page with /node/10003 and it will redirect you to that page.  When links from the editor are inserted into a textarea, they look like /node/10003.  When the page is viewed, the https://www.drupal.org/project/pathologic module converts those types of links into their aliased name(like /my-cool-page).

I believe Concrete5 does the same thing with it's core page link abstractor.
 
Couple of things/possible suggestions:
Is there a way to rewrite links that are inserted via the wysiwyg editor into a textarea?  For instance, clicking on the link icon in ckeditor opens a modal dialog where you can select a page, but when you select a page it inserts something like /parent/child-page instead of /1002.  If it just inserted /1002 then the editors wouldn't need to look at the short links tab because this module would automatically handle everything.
 
Maybe there can be a way to use a text formatter module to convert links like /1002 to /parent/child-page when outputting the page like https://www.drupal.org/project/pathologic?
 
Drupal also adds the following to the page to assist with SEO:
<link rel="canonical" href="https://www.mywebsite.com/my-cool-page" />
<link rel="shortlink" href="https://www.mywebsite.com/node/4796" />

Processwire looks really good, but I can't imagine not having some kind of way to handle links breaking when the site tree changes.  For big departmental or documentation websites, this happens all the time.  P.S. I have seen the other two modules page-link-abstractor and page-path-history.

Hope that helps, thanks for sharing your module I think it is definitely moving in the right direction!

Share this post


Link to post
Share on other sites

Maybe it would be possible to add another option to the ProcessPageEditLink module? something like "Absolute page id"? that would insert links like /1002

VHn4uyk6EykY7Eyx0YuTB5KlgMRPBn.png

Share this post


Link to post
Share on other sites

Hi @gmclelland - to be honest I don't really use this module for replacement of the main links - I only use it as a means of providing a shorter URL if required.

I actually think that the Page Path History module does an excellent job of preventing broken links. I have never actually been a fan of Drupal's /node/nnnn/ links, but in previous custom systems I have built, I have included the page ID as part of the URL, like: mydomain.com/nnnn-title-of-my-page/ which this module allows.

As for changing the insert link - this should already work - at least it does for me:

post-985-0-07407300-1449739560_thumb.png

Sorry if I am missing your point - in a bit of a hurry!

PS Did you select the "Rewrite Links" in the module settings?

Share this post


Link to post
Share on other sites

Oh... That's what that setting does.   :)  Yes, it works for me.  Thanks for pointing me in the right direction.  The only thing missing now is maybe some kind of text formatter module that would convert /1002 type links to /my-cool-page?

I've only used Page Path History once a while back, but it seems like Page Path History module is just covering up the problem by creating a ton of redirects without fixing the source of the problem which is the content is linking to the wrong page?  In Drupal, your not supposed to see the node/1002 links on the frontend.  Instead, you see the node's alias which would be something like /my-cool-page.

Their is a https://www.drupal.org/project/redirect module that is used to store changes of the node's alias.  For example, changing /my-cool-page to /my-cooler-page, but that is really only useful for when other websites link to the node's alias.  Internal links in text areas are always like node/1002 and then transformed on output into /my-cool-page.

As far as I know the systems that do this are modx, concrete5, Drupal.

Anyways, thanks again for responding.  I appreciate your help.

Share this post


Link to post
Share on other sites

As far as I'm concerned, redirects are pretty quick, and so using normal page links in CKEditor along with PagePathHistory should be more than sufficient for managing this. A Textformatter module would also indeed solve the problem, but there isn't one as yet.

Also not a fan of ID-based URIs - I just don't see the purpose...

Share this post


Link to post
Share on other sites

I have seen several drupal sites where the link in the html is still the /node/nnnn - does that mean they don't have it configured correctly or is this just something that is unavoidable in some cases, in which case that seems worse from an SEO point of view to me than just redirecting outdated links with PagePathHistory keeping in mind that there won't likely be that many changes - seems better than redirecting every /node/ link if it isn't being rewritten properly before the HTML is generated.

However, a textformatter to rewrite ID links made by this module wouldn't be hard to put together - in fact I bet you could steal some code from the Link Abstractor module - which btw is now deprecated.

If go to tackle this and need some help, please let us know and we'll help you get it working.

Share this post


Link to post
Share on other sites

Thanks adrian for the help.

I have seen several drupal sites where the link in the html is still the /node/nnnn - does that mean they don't have it configured correctly 

Yes, that can happen if you don't set any page aliases with the https://www.drupal.org/project/pathauto module.  The Pathauto module is used on pretty much every Drupal site.

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...