Jump to content
ryan

Hanna Code

Recommended Posts

Okay, this getting very odd.

I have changed it so that I am getting the text from a field on the actual page, rather than from another page.

And it has exactly the same problem.

????????

Share this post


Link to post
Share on other sites

I'm not sure. Can you hand a copy? 

Cache?

Share this post


Link to post
Share on other sites

OKAY!!!
 

Ummmmm

If I change it to get the page name, rather than the page title, it works!!!

WHAT??

(Cache is very definitely off and this is just on a local box)

Share this post


Link to post
Share on other sites

APC php cache?

Is there anything on the title field? Textformatter?

It's hard without sitting in front.

Share this post


Link to post
Share on other sites

I know - sorry. Jump on a plane? :)

Share this post


Link to post
Share on other sites

BINGO!

Soma, well done. It was the HTML entity encoder textformatter on the title field (I have no memory of adding that, but then this project started a while ago)

Thanks mate, again.... :)

Now the question is why would that mess things up?

Share this post


Link to post
Share on other sites

Well the cool kids use remote control, Airplane bahh...

Glad you found it. I have no idea why.  ???

  • Like 1

Share this post


Link to post
Share on other sites

Neither do I. One for Ryan when he is wandering by at some point. 

Interesting to see if you can replicate it though.

Night!

Share this post


Link to post
Share on other sites

Correction - the problem seems to have been with the title field also having the hanna code textformatter added. Er, I think. 

I need to go through this tomorrow!

Share this post


Link to post
Share on other sites

Hi,

I've got a problem with trying to edit a hanna code. I can see the list of codes I've setup and I can create a new one but I'm not able to edit it after I've created it. I had this problem with the final 2.4 release but I thought an update to the most recent dev build (2.4.7) might fix it but, no. There's no browser errors at all. Reinstalled it, still no.

My server setup is: PHP 5.4.25 & MySQL 5.1.73-cll

Any thoughts?

Share this post


Link to post
Share on other sites

Some little new hannas from my playground with a question:

//BDay
//Use this with [[bday?d=1950-12-31]]
//You can add this to any place, even in the title of a link or alt text of an image. Also future day possible.

!HannaCode:BDay:eyJuYW1lIjoiQkRheSIsInR5cGUiOiIyIiwiY29kZSI6IlwvKmhjX2F0dHJcbmQ9XCIyMDAwLTEtMVwiXG5oY19hdHRyKlwvXG48P3BocFxyXG5cclxuXC9cL1VzZSB0aGlzIHdpdGggW1tiZGF5P2Q9MTk1MC0xMi0zMV1dXHJcblwvXC9Zb3UgY2FuIGFkZCB0aGlzIHRvIGFueSBwbGFjZSwgZXZlbiBpbiB0aGUgdGl0bGUgb2YgYSBsaW5rIG9yIGFsdCB0ZXh0IG9mIGFuIGltYWdlLiBBbHNvIGZ1dHVyZSBkYXkgcG9zc2libGUuXHJcblxyXG4kb3V0cHV0X3ZhbHVlID1cIlwiO1xyXG4kZD10cmltKCRkKTtcclxuJGRhdGVub3c9ZGF0ZShcIlktbS1kXCIpO1xyXG4kZGlmZj1zdHJ0b3RpbWUoJGRhdGVub3cpLXN0cnRvdGltZSgkZCk7XHJcbmlmKCRkaWZmIDwwKSRkaWZmPSRkaWZmICogLTE7IFwvXC9ubyBuZWdhdGl2ZSB2YWx1ZXNcclxuJGRheXM9Zmxvb3IoKCRkaWZmKVwvODY0MDApO1xyXG4keWVhcnM9cm91bmQoKCRkaWZmIFwvMzE1MzYwMDApLCAyKTtcclxuXHJcblwvXC9ERUJVR1xyXG5cL1wvJG91dHB1dF92YWx1ZT1cIiRkYXRlbm93ICRkIEFnZSBpcyAkeWVhcnMgeWVhcnMuIFRoYXQncyAkZGF5cyBkYXlzXCI7XHJcbiRvdXRwdXRfdmFsdWU9XCJBZ2UgaXMgJHllYXJzIHllYXJzLiBUaGF0J3MgJGRheXMgZGF5c1wiO1xyXG5cclxuZWNobyAkb3V0cHV0X3ZhbHVlOyJ9/!HannaCode

and

//countdown
//d_day=(day) d_month=(mont) d_year=(year) txt1=(text_before) txt2=(text_after)
//Use [[countdown?d_day=25&d_month=12&d_year=2009&txt1=Only&txt2=days until it is Christmas]]

!HannaCode:Countdown:eyJuYW1lIjoiQ291bnRkb3duIiwidHlwZSI6IjIiLCJjb2RlIjoiXC8qaGNfYXR0clxuZF9kYXk9XCIyNVwiXG5kX21vbnRoPVwiMTJcIlxuZF95ZWFyPVwiMjAxNFwiXG50eHQxPVwiT25seVwiXG50eHQyPVwiZGF5cyB1bnRpbCBpdCBpcyBDaHJpc3RtYXNcIlxuaGNfYXR0cipcL1xuPD9waHBcclxuXHJcblwvXC9kX2RheT0oZGF5KSBkX21vbnRoPShtb250KSBkX3llYXI9KHllYXIpIHR4dDE9KHRleHRfYmVmb3JlKSB0eHQyPSh0ZXh0X2FmdGVyKVxyXG5cL1wvVXNlIFtbY291bnRkb3duP2RfZGF5PTI1JmRfbW9udGg9MTImZF95ZWFyPTIwMDkmdHh0MT1Pbmx5JnR4dDI9ZGF5cyB1bnRpbCBpdCBpcyBDaHJpc3RtYXNdXVxyXG5cclxuJHRvZGF5ID0gdGltZSgpO1xyXG4kZGF5WCA9IG1rdGltZShkYXRlKCdHJyksIGRhdGUoJ2knKSwgMCwgJGRfbW9udGgsJGRfZGF5LCAkZF95ZWFyKTtcclxuZWNobyAkdHh0MS4nICcgLnJvdW5kKCgkZGF5WC0kdG9kYXkpXC8oMzYwMCoyNCksMCkuJyAnLiAkdHh0MjsifQ==/!HannaCode

so in my former cms (there was a similar addon called droplets) i could get the whole rendered page as a $var or the contentpart of it and could make a nice CreateToc droplet that search for Headingtags and build up the TOC:

preg_match_all( '#<h([1-6]).*>([^<].+)</h[1-6]>#i', $wb_page_data, $matches, PREG_PATTERN_ORDER );

the var $wb_page_data gets the actual pagecontent to analyse by the droplet (=HannaCode).

Is there a similar option or could i simply use the render() function on the parts of the page that i wanna get into the TOC?

Kind regards mr-fan

Share this post


Link to post
Share on other sites

I've double ask would it be nice to have a little hanna gallery with structured and sorted hanncode??

Could be a nic addition to the addons page? with some given parameters like name, desc, importcode, vars

Share this post


Link to post
Share on other sites

Just a note to all MODx'ers - I think this is a nice way to transfer some snippets/chunks to ProcessWire as well if people want to go down that route and have some they used to use in body text. Obviously it's not quite the same thing (potentially more powerful depending on your needs), but anything that helps make a transition easier is good in my book :)

Very useful, powerful module ryan!

Agree. I'm coming from that CMS and I really like the ability to not have to rely on includes so much.

Share this post


Link to post
Share on other sites

Hi guys

Thanks for looking at this!

A Hanna code question for you gents...

In WordPress, one of the things you can do inside the main text editor is that you can add a read more tag anywhere inside your blog posts. Usually you might insert it after say the end of the first paragraph.

And so if you set up WordPress such that it displays your blog posts as a list of excerpts or teasers, then should it come across a post that has a read more tag, it will display the contents of that post from the beginning as an excerpt right up to the point where you placed that read more tag. Finally WordPress turns that read more tag into a link such that if you click on it it takes you to the complete blog post.

So my question is gents, if we create a [[readmore]] hanna code, how do we go about replicating this WordPress functionality?

As my coding skills are not very good, I thought that there could be two approaches.

One would be to somehow break out of the body field once it reached our [[readmore]]. How to do this I do not know how. I tried getting my [[readmore]] to simply echo return; but it ignored that!

The other I guess would be to use our [[readmore]] as a "marker" of sorts and somehow extract the section between the beginning of the body field up until it sees our [[readmore]] marker. I'm thinking this might need an explode implode kind of approach but I have never ever done anything like that before and so I am really quite clueless on this one.

Or maybe there is a smarter way?

Any tips or suggestions or code chunks much appreciated!

Cheers guys!

Share this post


Link to post
Share on other sites

Hey Zahari,

In a bit of a rush, but PHP's strstr might be what you are looking for. Not sure that you really need a Hanna Code in this situation. Just parse the content of the field in your template.

$introtext = strstr($page->body, '[[readmore]]', true);

Then when you echo out the body on the full version, just:

echo str_replace("[[readmore]]", "", $page->body);

Hope that helps to get you started. I am sure there are lots of other ways to approach this. I usually go with automatic truncation because editors usually forget to add things like a [[readmore]] tag. 

  • Like 3

Share this post


Link to post
Share on other sites

Adrian!

That's such an awesome function!

Oh so elegant!

And here I was trying to bust my head with preg_split :wacko:

As always... thank you thank thank you!!

Share this post


Link to post
Share on other sites

Another little Hanna issue:

In CKEditor if you delete a space (like with backspace) and then press the space bar to put it back in, or anything similar, CKeditor inserts a

 

So, if on a hanna code you have something like this:

[[col class="medium-4 myclass"]]

When you first type it, it is fine, but if you edit it, the source becomes:

[[col class="medium-4 myclass"]]

And the code breaks.

Ryan, can you add a check in the hanna module so that it looks for   and replaces is with a blank " "?

Share this post


Link to post
Share on other sites

@Joss: unless you actually need non-breaking spaces somewhere (and assuming that you're running a new-ish version of PW), the "beautify markup toggles" section of CKEditor field are pretty neat. "Remove non-breaking spaces" has saved the day a lot of times for me. Just saying :)

Share this post


Link to post
Share on other sites

Arf'noon Teppo!

Yes, I know there is a way around it on CKEditor, but it struck me that having a catch-all on the Hanna Code is possibly not a bad idea. It's one of those things that could mess a client up if they don't know all the ins and outs.

Share this post


Link to post
Share on other sites

Ryan, next time you're are messing with the module, fancy putting in a drop down for font size on Ace? For us old blokes, you know......

  • Like 4

Share this post


Link to post
Share on other sites

Damn it is embarrassing that I felt the need to Like that suggestion of Joss'. I used to be fine on a 15" laptop running 1920x1200. Seems like 40 really is the beginning of the end when it comes to small things and low light :)

  • Like 2

Share this post


Link to post
Share on other sites

Hi, I just can't find my github login, so I'd like to report a minor bug here. (I did cost me some hours…)

In the description of the Hanna Code Name field is written, that hyphens are allowed in names:

post-426-0-43598900-1412005724_thumb.jpg

That's definitely not right. as you can read here:

https://processwire.com/talk/topic/7123-embedding-css-grid-markup-in-textareackeditor/

Hanna Code Module is not working with additional parameters if hyphens are in the Hanna Code Name.

This error was also reported on github in February here:

https://github.com/ryancramerdesign/ProcessHannaCode/issues/3

The module is great anyway. So thanks a lot in advance!  :rolleyes:

Share this post


Link to post
Share on other sites

Ryan,

I've got notified in the PW admin (2.5.3 master) that there was an update (0.1.9) available for Hanna Code. I checked GitHub and saw that you added support for hyphenated Hanna names, cool!

Unfortunately, updating via Setup->Upgrades did not go as planned. It timed out after 30 seconds and the mentions of TextformatterHannaCode and ProcessHannaCode had dissapeared from the modules list.

After that, a '.TextformatterHannaCode' directory was present in the site/modules and a 'ProcessHannaCode' directory with only partial files (the ace stuff)  in it. Clearing out these folder and installing from ClassName also did not seem to work anymore, as it also resulted in a timeout.

Grabbing the zip from GitHub, extracting it in site/modules and renaming it to 'ProcessHannaCode' and afterwards refreshing the modules section in PW admin seems to have restored everything, and i now have an up to date (0.1.9) Hanna Code Module, with all Hanna Codes i already had working correctly.

Maybe it was the initial time-out that got me screwed, but maybe there are some (re)naming issues when upgrading to the latest version of Hanna. Thought i'd mention it anyway.

  • Like 1

Share this post


Link to post
Share on other sites

next HannaCode to crosslink the topics

https://processwire.com/talk/topic/7930-screenshot-generator-url-to-img/#entry76654

!HannaCode:thumbnail:eyJuYW1lIjoidGh1bWJuYWlsIiwidHlwZSI6IjIiLCJjb2RlIjoiXC8qaGNfYXR0clxudz1cIjEyMFwiXG5oPVwiODBcIlxudXJsPVwicHJvY2Vzc3dpcmUuY29tXC9cIlxuaGNfYXR0cipcL1xuPD9waHBcclxuXHJcblwvXC9nZXQgc29tZSB0aHVtYm5haWxzIGZyb20gYSBzZXJ2aWNlIEFQSSBcclxuXC9cL2xpbmsgZXhhbXBsZTogaHR0cDpcL1wvYXBpLndlYnRodW1ibmFpbC5vcmdcLz93aWR0aD0xMjAmaGVpZ2h0PTgwJmZvcm1hdD1qcGcmdXJsPXByb2Nlc3N3aXJlLmNvbVwvXHJcblxyXG5lY2hvIFwiPGltZyBzcmM9J2h0dHA6XC9cL2FwaS53ZWJ0aHVtYm5haWwub3JnXC8/d2lkdGg9JHcmaGVpZ2h0PSRoJmZvcm1hdD1qcGcmdXJsPSR1cmwnPjxcL2ltZz5cIjsifQ==/!HannaCode

Some little thumbnailgenerator....;)

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