Jump to content
ryan

Hanna Code

Recommended Posts

i tried using the shortcode module, and it is promising, and quite different than hanna codes; shortcodes allow you to have an opening and closing tag so you can enclose things within, which allows you to use them for things like tabs and accordions;

hanna code is very usable/flexible, but it doesn't know about things between each instance of itself (no opening/closing)...

also the shortcodes module doesn't allow for using more than 1 shortcode on a page.. i think it needs more work;

but it would be good if we could have a shortcodes module that works as well as the wordpress shortcodes, since there are still some rare use cases where shortcodes can be useful...

custom fields replaces and is superior for the most part to the concept of shortcodes, which is probably why the need has not come up much on PW.

And end users always mess up with shortcodes, like putting them in the wrong place in the RTE (like inside a heading), or forgetting to use the closing tag, and consequently break the layout on pages too easily...

  • Like 1

Share this post


Link to post
Share on other sites

I have never even considered using anything like Hanna code or shortcodes for our clients. I think what would make them usable would be making them appear as a block in editor, instead of plain text.

  • Like 1

Share this post


Link to post
Share on other sites

I have never even considered using anything like Hanna code or shortcodes for our clients. I think what would make them usable would be making them appear as a block in editor, instead of plain text.

Actuall in my testing phase of PW - there are much less usecases for such little snippets because you could use simple a extra field or do prefered PHP direkt in the page template....but in other systems you only had some blocks or one Wysiwyg per pages and such snippets catch up some content or bring some logic to a wysiwyg the user doesn't have to think about it.

For example you could easy setup some Hanna codes and implement it fast via import on new different websites....reusable codesnippets are the usecase.

Iportant question if i wanna make them work in the template i have to call the process i think??

Next HannaCode from my testings is a simple sitemap:

//:Sitemap: creates a simple sitemap (Snippet find in the forum from soma)
//:Use: [[sitemap]]

Just import this one:

!HannaCode:sitemap:eyJuYW1lIjoic2l0ZW1hcCIsInR5cGUiOiIyIiwiY29kZSI6Ijw/cGhwXHJcblxyXG5cclxuZnVuY3Rpb24gc2l0ZU1hcCgkcGFnZSwgJG91dHB1dD0nJykge1xyXG4gICAgJG91dHB1dCAuPSBcIlxcblxcdDxsaT48YSBocmVmPSd7JHBhZ2UtPnVybH0nPnskcGFnZS0+dGl0bGV9PFwvYT5cIjtcclxuICAgIGlmKCRwYWdlLT5udW1DaGlsZHJlbikge1xyXG4gICAgICAgICRvdXRwdXQgLj0gXCJcXG5cXHRcXHQ8dWw+XCI7XHJcbiAgICAgICAgZm9yZWFjaCgkcGFnZS0+Y2hpbGRyZW4gYXMgJGNoaWxkKSAkb3V0cHV0IC49IHN0cl9yZXBsYWNlKFwiXFxuXCIsIFwiXFxuXFx0XFx0XCIsIHNpdGVNYXAoJGNoaWxkKSk7XHJcbiAgICAgICAgJG91dHB1dCAuPSBcIlxcblxcdFxcdDxcL3VsPlwiO1xyXG4gICAgfVxyXG4gICAgJG91dHB1dCAuPSBcIlxcblxcdDxcL2xpPlwiO1xyXG4gICAgcmV0dXJuICRvdXRwdXQ7XHJcbn1cclxuXHJcbiRob21lcGFnZSA9ICRwYWdlcy0+Z2V0KFwiXC9cIik7XHJcbiRzaXRlTWFwID0gc2l0ZU1hcCgkaG9tZXBhZ2UpO1xyXG5lY2hvIFwiPHVsPlwiLiRzaXRlTWFwLlwiPFwvdWw+XCI7In0=/!HannaCode

Have Fun - mr-fan

  • Like 2

Share this post


Link to post
Share on other sites
I have never even considered using anything like Hanna code or shortcodes for our clients. I think what would make them usable would be making them appear as a block in editor, instead of plain text.

 Exactly my thought. And loaded/configurable per template, so that only hanna codes are shown that makes sence in that template. 

  • Like 1

Share this post


Link to post
Share on other sites

Hi all

I hope there's someone here that can help me.. I've set up this site (www.sejero-festival.dk) on my localhost and Hanna Code works excellent.

However, and I've tried two different hosts now, when I deploy the site, the Hanna Code module fails miserably when I try to go to the setup part :

Screenshot%202014-06-16%2014.08.42.png

One of the hosts has the following specs:

PHP: 5.3.28

MySQL: 5.5.37

Does anyone have a clue what might cause this error?

Share this post


Link to post
Share on other sites

For some reason I cannot get hanna code to work with php. I can get html to work just pine but php will not.

Here is my code

<?php
 
foreach($page->children as $product) {
 
    if($product->image) {
       // $image = $product->image->width(150);
        $img = "<img src='{$image->url}' alt='{$product->title}' class='flt-left-img' />";
    } 
    
    else {
     
        $img = "<span class='image_placeholder'>Image not available</span>";
    } 
 
    echo "
        $img
        <h3>{$product->title}</h3>
        <p>{$product->product_description}</p>
        <hr />
        ";
}
?>
 
 
 
The only thing that will output on the page is the product description but all other content from the body disappears.
 
Driving me nuts so any help would be great.

Share this post


Link to post
Share on other sites

I hope there's someone here that can help me.. I've set up this site (www.sejero-festival.dk) on my localhost and Hanna Code works excellent.

However, and I've tried two different hosts now, when I deploy the site, the Hanna Code module fails miserably when I try to go to the setup part :

One of the hosts has the following specs:

PHP: 5.3.28

MySQL: 5.5.37

Does anyone have a clue what might cause this error?

Is this still a problem? Does anything else work, i.e. is this the only place that's broken on this site?

Sounds like your database wasn't reachable at this point, but I'd imagine that causing issues elsewhere too. Unless, perhaps, it's somehow related to PHP's mysqli extension on that server (just about all core features have already been migrated to PDO instead).

For some reason I cannot get hanna code to work with php. I can get html to work just pine but php will not.

Here is my code

<?php
 
foreach($page->children as $product) {
 
    if($product->image) {
       // $image = $product->image->width(150);
        $img = "<img src='{$image->url}' alt='{$product->title}' class='flt-left-img' />";
    } 
    
    else {
     
        $img = "<span class='image_placeholder'>Image not available</span>";
    } 
 
    echo "
        $img
        <h3>{$product->title}</h3>
        <p>{$product->product_description}</p>
        <hr />
        ";
}
?>
 
 
 
The only thing that will output on the page is the product description but all other content from the body disappears.

Only weird thing I can spot in your code right away is that you've got $image = ... commented out, yet on the next line you try to use $image->url, which obviously won't be available here. I'm assuming that this was just something you did for testing and forgot there.

When you're saying that only output is the product description, it's coming from this Hanna Code snippet, right? Are you seeing empty <h3></h3> tags and then <p></p> tags with product description inside them and nothing else, or..?

I'm not really sure what you're referring to when you say that all other content from the "body" disappears; <body> element of your page, $page->body, or something entirely different? If you view the source of the page, is there anything weird there -- or in your log files, either in site/assets/logs/errors.txt or Apache logs?

Share this post


Link to post
Share on other sites

oops I didn't mean to have that commented out. Its not in my code, but that was a copy that I forgot to uncomment. 

I am not seeing empty <h3> tags or <p> tags and yes the product description is coming from the hanna code. In fact the only thing that showing on the page is the product description from the hanna code. Everything else disappears including all paragraphs and everything else in the textarea $page->body. There is nothing weird in the source. It has to be the way this php is whitten I think because I am using other php for another hanna code and it works.  

this is the other code that works

<?php foreach ($page->children() as $c): ?>

<li><a href="<?=$c->url;?>"><img src="<?=$c->listImage->url;?>" alt="<?=$c->listImage->description;?>" width="100" height="100"> <?=$c->listImage->description;?> <span>View More</span></a></li>
<? endforeach; ?>

Share this post


Link to post
Share on other sites

Is this still a problem? Does anything else work, i.e. is this the only place that's broken on this site?

Sounds like your database wasn't reachable at this point, but I'd imagine that causing issues elsewhere too. Unless, perhaps, it's somehow related to PHP's mysqli extension on that server (just about all core features have already been migrated to PDO instead).

Yeah it's still a problem. :-(

And now I've tried it on another host with same result. The only two places I've succesfully gotten the Hanna Code module to work were on localhost (yay) and on my Digital Ocean Droplet...

I guess I'll let the owner of the site know, that he can't get that module on the two host masters he wished for. :-)

Share this post


Link to post
Share on other sites

First problem I noticed, two people are asking two separate questions at the same time.

For @kasperwf,

 Hi all

 

I hope there's someone here that can help me.. I've set up this site (www.sejero-festival.dk) on my localhost and Hanna Code works excellent.

However, and I've tried two different hosts now, when I deploy the site, the Hanna Code module fails miserably when I try to go to the setup part :

  One of the hosts has the following specs:

 

PHP: 5.3.28

MySQL: 5.5.37

 

Does anyone have a clue what might cause this error?

 

On your localhost (that is working), what are the following:

ProcessWire version

PHP version

MySQL version

Apache version

Then, what are the same information for both hosts that you have have tried?  Having that information, will allow someone to truly be of help to you.  Thanks.

Share this post


Link to post
Share on other sites

On your localhost (that is working), what are the following:

ProcessWire version

PHP version

MySQL version

Apache version

Then, what are the same information for both hosts that you have have tried?  Having that information, will allow someone to truly be of help to you.  Thanks.

My localhost:

PHP version: 5.4.22

MySQL version: 5.6.10

Apache: Apache/2.2.26 (Unix)

The information for the hosts that doesn't work is the one I wrote earlier. Seems like they both use the exact same setup (as the other, not like mine, the working server). :-I

The info for my VPS that also work is:

PHP: 5.5.9-1ubuntu4

MySQL: I really don't know, because I obviously secured it too well, and I can't even mysql -v it. But it was last month, and it was the newest version, so, yeah. :-)

Apache: Apache/2.4.7 (Ubuntu)

Share this post


Link to post
Share on other sites

This turned out to be an issue with the order of variables returned by core TemplateFile::getArray. It was doing an array_merge which gave preference to API variables, preventing them from being overwritten. Maybe that's a good thing in general, but I don't think we want that limitation. I went ahead and changed it in dev. Now it gives preference to local variables, which enables Hanna Code to provide the behavior it was supposed to. 

Hello,

I fail to make it work. I'm using PW version 2.4.4. TemplateFile.php lines 156-158 are correctly updated:

	public function getArray() {
		return array_merge($this->fuel->getArray(), parent::getArray()); 
	}

My Hanna code is as simple as:

[[page-title]] :

<?php
echo $page->title;

The structure is as follows:

Page texts, with title "Texts" -> Field "Text 1" (Textareas ProField)-> "Some text... " . [[page-title]]

Page product name, with title "Product name"-> API reference to Field "Text 1"

Outputs "Some text... Texts"

Should be "Some text... Product name"

I think it should work, but can´t see the problem. The textareas field has Hanna Code Text Formatter applied.

Thanks,  :rolleyes:

Share this post


Link to post
Share on other sites

I think I am getting caught out by scope - well, I know I am.

I have some text on a page other than the one I am looking at, and I am drawing it in with get()

That text has a hanna code in it that simply echos the page title.

The problem is that it is echoing the page title of the page the code originates from and not from the page I am looking at.

How do I do this so that it gets my current page title, not the page where the text originates from?

Share this post


Link to post
Share on other sites

ummm ... I am halfway there.

by using this for the php for my hanna code <?php echo wire("page")->title; ?> I now get the current page title.

However, I am not getting the rest of the text.

So:

This is my [[pagetitle]] you can see

Is just printing out the page title, not the rest of the words.

Share this post


Link to post
Share on other sites

You don't happend to replace sorounding p tags and the hanna code is inside the text paragraph?

Share this post


Link to post
Share on other sites

Hi Soma, no, I have the replace bit turned off.

I think it is because the textarea that supplies the text, complete with the hanna code reference, is originating on another page.

I am calling it into my template with:

<? echo $pages->get("/servicing/")->service_model_default_text; ?>

Now, if I use a different code, one that pulls the info from a specified field in a specified page, that works fine.

For instance, a code that is:

echo "<span class='phonenumber'>Call {$pages->get("/settings/")->site_phone}</span>";

But if I try and call something from the current page, it goes wrong.

So if I used the code:

echo $page->title;

Simply prints out title of the page where the text originated, but not the rest of the text. if I use wire() it prints out the current page title, but again no text. Debug is not showing errors.

Share this post


Link to post
Share on other sites

Sorry can't really follow what you're doing. Mostly confused why you'd need hanna code at all just for a page title?

Share this post


Link to post
Share on other sites

Basically I have a huge lump of default text in a separate page that is pulled into about 100 pages or so.

The default text needs to pick up values from those pages - product name, price and so on - that will be part of that long default text. The page title is just one of those values.

The easiest way I could see to do it (and easy for the client to understand) was to use bits of hanna code within the text.

Share this post


Link to post
Share on other sites

I have hard time following what code is where and what doesn't work.

Share this post


Link to post
Share on other sites

Sorry, Soma, I should have explained it better.

I have a page called services that has a CKEditor field called service_model_default_text

It contains, for instance, "we can service your [[model-name]]"

The code for the [[model-name]] hanna code is 

<?php echo wire("page")->title; ?>

I have the replace surrounding tag set to "no" and it is type PHP

I have another page called Audi. In the template for that page I get the field from the services page.

<?php echo $pages->get("/servicing/")->service_model_default_text; ?>

The idea is that the hanna code is replace with the page title from the audi page so that the final result is:

We can service your Audi.

Unfortunately, the hanna code system does not seem to be able to do that, it prints out the page title fine, but not the rest of the text from the field.

However, if I change the hanna code to another one I have, [[phonenumber]], which takes its input from a field on a completely separate page, it works fine.

Confused!

Share this post


Link to post
Share on other sites

I tested something like this in latest dev and 2.4 installation, works fine. I can't see any text not outputting.

Default site. Added hanna code formatter to body field. In /templates/ page in the body I place a hanna code inside text [[model-name]] and output that text on the About page. 

Hanna code 

<?php
echo wire("page")->title;

In template basic-page.php

echo $pages->get("/templates/")->body;

The hanna tag gets replaced with the page title and the surrounding text is still there.

Share this post


Link to post
Share on other sites

Damn!

I wonder what I have got that is messing it up?

I think I will strip the entire template out apart from the get line and see what happens

Share this post


Link to post
Share on other sites

Do those two pages, the one you have the body field and the about page, use the same template?

I just emptied the template file, but it still is not working properly.

I noticed that when I save and test the hanna code, inside the dotted box it just says Hanna Code

No idea why.

Share this post


Link to post
Share on other sites

Yes those two pages have same template. It doesn't matter what template. I've never used the save and test. But I think you would see the current admin page title if anything at all.

Share this post


Link to post
Share on other sites

hmm ... so something is not right. 

With the other hanna code, the one that points to a telephone number, in test it shows the telephone number.

I have tried deleting the hanna code instance, and adding a new one and it is the same problem.

The only other thing is that they are on different tree levels - the page that has the text in it is a child of home, the other page, the Audi page, is its grandchild. But I dont think that should be a problem.

I am a bit lost on this, to be honest, and it has brought the project to a shuddering halt

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