Jump to content
ryan

Load RSS Feeds (MarkupLoadRSS)

Recommended Posts

ProcessWire RSS Feed Loader


Given an RSS feed URL, this module will pull it, and let you foreach() it or render it. This module will also cache feeds that you retrieve with it. The module is designed for ProcessWire 2.1+, but may also work with 2.0 (haven't tried yet).

This module is the opposite of the MarkupRSS module that comes with ProcessWire because that module creates RSS feeds. Whereas this module loads them and gives you easy access to the data to do whatever you want.

For a simple live example of this module in use, see the processwire.com homepage (and many of the inside pages) for the "Latest Forum Post" section in the sidebar.

Download at: https://github.com/r...n/MarkupLoadRSS

REQUIREMENTS


This module requires that your PHP installation have the 'allow_url_fopen' option enabled. By default, it is enabled in PHP. However, some hosts turn it off for security reasons. This module will prevent itself from being installed if your system doesn't have allow_url_fopen. If you run into this problem, let me know as we may be able to find some other way of making it work without too much trouble.

INSTALLATION


The MarkupLoadRSS module installs in the same way as all PW modules:

1. Copy the MarkupLoadRSS.module file to your /site/modules/ directory.

2. Login to ProcessWire admin, click 'Modules' and 'Check for New Modules'.

3. Click 'Install' next to the Markup Load RSS module.

USAGE


The MarkupLoadRSS module is used from your template files. Usage is described with these examples:

Example #1: Cycling through a feed

<?php

  $rss = $modules->get("MarkupLoadRSS");
  $rss->load("http://www.di.net/articles/rss/");

  foreach($rss as $item) {
      echo "<p>";
      echo "<a href='{$item->url}'>{$item->title}</a> ";
      echo $item->date . "<br /> ";
      echo $item->description;
      echo "</p>";
  }

Example #2: Using the built-in rendering

<?php

  $rss = $modules->get("MarkupLoadRSS");
  echo $rss->render("http://www.di.net/articles/rss/");

Example #3: Specifying options and using channel titles

<?php

  $rss = $modules->get("MarkupLoadRSS");

  $rss->limit = 5;
  $rss->cache = 0;
  $rss->maxLength = 255;
  $rss->dateFormat = 'm/d/Y H:i:s';

  $rss->load("http://www.di.net/articles/rss/");

  echo "<h2>{$rss->title}</h2>";
  echo "<p>{$rss->description}</p>";
  echo "<ul>";

  foreach($rss as $item) {
       echo "<li>" . $item->title . "</li>";
  }

  echo "</ul>";

OPTIONS


Options MUST be set before calling load() or render().

<?php

  // specify that you want to load up to 3 items (default = 10)
  $rss->limit = 3;

  // set the feed to cache for an hour (default = 120 seconds)
  // if you want to disable the cache, set it to 0.
  $rss->cache = 3600;

  // set the max length of any field, i.e. description (default = 2048)
  // field values longer than this will be truncated
  $rss->maxLength = 255;

  // tell it to strip out any HTML tags (default = true)
  $rss->stripTags = true;

  // tell it to encode any entities in the feed (default = true);
  $rss->encodeEntities = true;

  // set the date format used for output (use PHP date string)
  $rss->dateFormat = "Y-m-d g:i a";

See the $options array in the class for more options. You can also customize all output produced by the render() method, though it is probably easier just to foreach() the $rss yourself. But see the module class file and $options array near the top to see how to change the markup that render() produces.

MORE DETAILS


This module loads the given RSS feed and all data from it. It then populates that data into a WireArray of Page-like objects. All of the fields in the RSS <items> feed are accessible, so you use whatever the feed provides. The most common and expected field names in the RSS channel are:

  • $rss->title
  • $rss->pubDate (or $rss->date)
  • $rss->description (or $rss->body)
  • $rss->link (or $rss->url)
  • $rss->created (unix timestamp of pubDate)

The most common and expected field names for each RSS item are:

  • $item->title
  • $item->pubDate (or $item->date)
  • $item->description (or $item->body)
  • $item->link (or $item->url)
  • $item->created (unix timestamp of pubDate)

For convenience and consistency, ProcessWire translates some common RSS fields to the PW-equivalent naming style. You can choose to use either the ProcessWire-style name or the traditional RSS name, as shown above.

HANDLING ERRORS


If an error occurred when loading the feed, the $rss object will have 0 items in it:

<?php

  $rss->load("...");
  if(!count($rss)) { error }

In addition, the $rss->error property always contains a detailed description of what error occurred:

<?php

  if($rss->error) { echo "<p>{$rss->error}</p>"; }

I recommend only checking for or reporting errors when you are developing and testing. On production sites you should skip

error checking/testing, as blank output is a clear indication of an error. This module will not throw runtime exceptions so if an error occurs, it's not going to halt the site.

  • Like 1

Share this post


Link to post
Share on other sites

Great to have such a module, thanks Ryan!

Though can't install:

Warning: mkdir() [function.mkdir]: No such file or directory in /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/modules/MarkupLoadRSS.module on line 447

Share this post


Link to post
Share on other sites

Oops, looks like I messed up something last minute. Just committed the fix. Thanks for letting me know.

Share this post


Link to post
Share on other sites

Thanks, just installed and tested a run and works great so far!  8)

Share this post


Link to post
Share on other sites

Great work Ryan! Only thing I might add is support for multiple feeds. Though it might complicate this module too much?

Share this post


Link to post
Share on other sites

I want to display a RSS feed that contains items like below and it works well, except for the author field (dc:creator), which isn't parsed. Is there a way to parse this value as well?

		<item>
	<title>Taalkundigen Uppsala ontcijferen geheimschrift</title>
	<link>http://www.wereldwijzerzweden.net/2011/11/03/uppsala-geheimschrift-taalkundige-copiale/</link>
	<comments>http://www.wereldwijzerzweden.net/2011/11/03/uppsala-geheimschrift-taalkundige-copiale/#comments</comments>
	<pubDate>Thu, 03 Nov 2011 16:03:16 +0000</pubDate>
	<dc:creator>Marcel Burger</dc:creator>
	<category><![CDATA[Actueel]]></category>
	<category><![CDATA[berlijn]]></category>
	<category><![CDATA[Copiale]]></category>
	<category><![CDATA[geheimschrift]]></category>
	<category><![CDATA[universiteit]]></category>
	<category><![CDATA[uppsala]]></category>

	<guid isPermaLink="false">http://www.wereldwijzerzweden.net/?p=7227</guid>
	<description><![CDATA[<a href="http://www.wereldwijzerzweden.net/2011/11/03/uppsala-geheimschrift-taalkundige-copiale/"><img align="left" hspace="5" width="150" src="http://www.wereldwijzerzweden.net/images/copiale_280.jpg" class="alignleft wp-post-image tfe" alt="Deel uit vrijgegeven beeld van het Copialeschrift" title="copiale_280.jpg" /></a>3 november 2011 &#124; Twee Zweedse taalkundigen en een Amerikaanse wetenschapper zijn erin geslaagd een 280 jaar oud geheimschrift uit Duitsland met voorheen onbegrijpelijke tekens te vertalen.]]></description>
	<wfw:commentRss>http://www.wereldwijzerzweden.net/2011/11/03/uppsala-geheimschrift-taalkundige-copiale/feed/</wfw:commentRss>
	<slash:comments>0</slash:comments>
	</item>

I outputted the $rss array with print_r(); and it doesn't contain the dc:creator field (some others seem to be missing as well,  but I don't need these  ;))

/Jasper

Share this post


Link to post
Share on other sites

Just a guess, but do the other fields it's nor parsing contain a colon as well?

Share this post


Link to post
Share on other sites

No, for example comments didn't get parsed as well.

/Jasper

Share this post


Link to post
Share on other sites

If I recall correctly, SimpleXML doesn't work with the properties that have colons in them. But you can fix that by replacing the colon properties with underscore properties in the XML data. So in this case, you'd want to add this line in the load() function:

<?php
public function load($url) { 
    $this->items = new WireArray();
    $xmlData = $this->loadXmlData($url);
    $xmlData = str_replace('dc:creator', 'dc_creator', $xmlData); 

Or you may be able to cover all the colon properties at once using a regexp like this:

<?php
$xmlData = preg_replace('{(</?[_a-z0-9]+)[_a-z0-9]+>)}', '$1_$2', $xmlData); 

What that does is convert properties like <dc:creator> to <dc_creator> so that SimpleXML will understand them and likewise you can access them in the module. Let me know if this works for you. I'm not in a place where I can update the source on this module today, but will plan to add something like the above soon.

I don't know why the <comments> property wouldn't be getting parsed, as that appears to just be a string (URL). I need to test and experiment with that one to find out why.

Share this post


Link to post
Share on other sites

Thanks Ryan, replacing the colons work, both with the str_replace and the regexp..

I'm not in a place where I can update the source on this module today, but will plan to add something like the above soon.

I also submitted (via Github) a double encoding issue (I am good in finding these  :P) in this module. You might want to take a look at that one at the same time. :-)

I don't know why the <comments> property wouldn't be getting parsed, as that appears to just be a string (URL). I need to test and experiment with that one to find out why.

My fault  :-[, the comments property is parsed. One that didn't get parsed was the Category, but that may be because it appears multiple times. (guess).

The exact feed I am using is also in the Github issue, so you can test with it if you want/like.

/Jasper

Share this post


Link to post
Share on other sites

Thanks for submitting the issue, I will fix. Also I'd like to find a way to get Comments (and any multi-item properties) working as well, should be easy. The feeds I'd originally tested with were pretty basic and didn't have these extended properties.

Share this post


Link to post
Share on other sites

Great work Ryan! Only thing I might add is support for multiple feeds. Though it might complicate this module too much?

I had need for multiple feeds and it seemed to be pretty straightforward implementation. Only few modifications to load method:

public function load($url) {
 $this->items = new WireArray();
 if (is_array($url)) {
  $items = array();
  foreach ($url as $feed) {
   $xmlData = $this->loadXmlData($feed);
   $xml = simplexml_load_string($xmlData);
   $items = array_merge($items, $xml->xpath('/rss//item'));
  }
  $rss = simplexml_load_string($xmlData);
 } else {
  $xmlData = $this->loadXmlData($url);
  $rss = simplexml_load_string($xmlData);
 }

 if(!$rss) {
  $msg = "Unable to load RSS feed at " . htmlentities($url) . ": \n";
  foreach(libxml_get_errors() as $error) $msg .= $error . " \n";
  $this->error($msg);
  return $this;
 }
 $this->channel['title'] = $this->cleanText((string) $rss->channel->title);
 $this->channel['description'] = $this->cleanText((string) $rss->channel->description);
 $this->channel['link'] = $this->cleanText((string) $rss->channel->link);
 $this->channel['created'] = strtotime((string) $rss->channel->pubDate);
 $this->channel['pubDate'] = date($this->options['dateFormat'], $this->channel['created']);
 $n = 0;
 // If we already have $items set, it means we are dealing with multiple sources. Let's sort them
 if(isset($items)) {
  usort($items, function ($x, $y) {
 return strtotime($y->pubDate) - strtotime($x->pubDate);
  });
 } else {
  $items = $rss->channel->item;
 }
 foreach($items as $item) {
  $a = new MarkupLoadRSSItem();
  foreach($item as $key => $value) {
   $value = (string) $value;
   if($key == 'pubDate') {
 $value = strtotime($value);
 $a->set('created', $value);
 $value = date($this->options['dateFormat'], $value);
   } else {
 $value = $this->cleanText($value);
   }
   $a->set($key, $value);
  }
  $this->items->add($a);
  if(++$n >= $this->options['limit']) break;
 }
 return $this;
}

What it does it sniffs if $url is array, then loads/caches all those and merge their rss-items to $items array. Then later on that $items is sorted by pubDate. So this is fully backwards compatible => just give it an array instead of single url if you need to parse multiple feeds.

If you guys can test it works for you too then maybe Ryan you can put this on your version. I can do pull request if you want to (although it seems that new and fancy GitHub for windows does mess up line endings..).

  • Like 1

Share this post


Link to post
Share on other sites

I'm not sure that the W3 validator is picking it up right either? Seems like it is showing the whole thing as double entity encoded. Also tried loading in Safari, and it can't seem to read the feed correctly either. Firefox seems okay. Definitely something unusual going on with this feed, but I am not familiar enough with this particular format to know what's wrong. W3 validator isn't helping much since it's seeing the whole thing as double entity encoded.

Share this post


Link to post
Share on other sites

Yeah, there definitely was some strange going on with that feed. Now it seems to be working on my end too, so they must have been fixed that.

Ryan: have you thought about adding that multisource functionality to this module? I am already using it in couple of places, and it has been working great. Of course if you think the implementation should be different or alltogether different module then let me know (or if you prefer github pull request).

What I was thinking it might be more "pw" to have add->(source_url) etc and then load, instead of having all the urls in array load($array_of_urls) like it is currently.

Share this post


Link to post
Share on other sites

Sounds good! Lets go for a pull request if it's convenient for you. Or just post the .module file and I can go through the diff.

Share this post


Link to post
Share on other sites

Hi Ryan,

Thanks for this module.  Have been using it on our main site for awhile now.  Just wanted to let you know of an issue that I just discovered that others may run into, and see if there's a way to handle it.

I was trying to load a feed that for awhile was not responding.  The feed page wasn't throwing an error or even timing out, just loading for minutes on end.

This ended up causing a timeout on our site (the feed was loading on the main page) and producing this error in the PW log file:

Error Exception: MySQL server has gone away (in /mnt/stor7-wc2-dfw1/526843/www.agencypja.com/web/content/wire/core/Database.php line 118)

For now, we've just disabled that feed, but we are using the module to load other feeds.  Do you (or anyone else) know of a way to address this issue?  I don't see a timeout option in the module, but could certainly look into adding one if that determined to be the best option.

Thanks.

Share this post


Link to post
Share on other sites

Could you PM me the RSS feed you are working with? I can do some testing here. I believe we can get it working by switching MarkupLoadRSS to use the new WireHttp class in PW 2.3.10+, but I need an example to test with. 

Share this post


Link to post
Share on other sites

Hi Ryan,

Unfortunately, the feed that was causing problems is now back up and running normally.  I thought that I could recreate the issue by creating a php page on another server with a timeout set to at least 5 min, sleeping the script, and using that as the RSS feed, but that didn't work.

I'll be sure to let you know if I ever come across is again.

Thanks.

  • Like 1

Share this post


Link to post
Share on other sites

Is it possible to load image with this module?

Share this post


Link to post
Share on other sites

I get always empty RSS Feed output! On my Page i call the RSS module by url selector like blog/rss and for the output i need the same page array that i use for the /blog page. But in the RSS Feed i get no content!

$blogposts = $pages->find("template=post, publish_date<$today, sort=-publish_date, limit=10");

if($input->urlSegment1 === 'rss'){
  // retrieve the RSS module
  $rss = $modules->get("MarkupRSS");

  // configure the feed. see the actual module file for more optional config options.
  $rss->title = "Letzte Blogeinträge";

  $rss->render($blogposts);
  return;
} else {
  $content = renderPosts($blogposts, true);
}

Share this post


Link to post
Share on other sites

I just downloaded MarkupLoadRSS module from M.Cramer's Github repo.

Here is the demo code I used for test purpose in my template :

        $rss = $modules->get("MarkupLoadRSS");
        $rss->load("http://rss.cbc.ca/lineup/canada.xml");

        foreach($rss as $item) {
            echo "<p>";
            echo "<a href='{$item->url}'>{$item->title}</a> ";
            echo $item->date . "<br /> ";
            echo $item->description;
            echo "</p>";
        }

All I get is this error :

Error: Call to a member function load() on a non-object (line 65 of C:\wamp\www\mysite\site\templates\home.php)

As if the module wants an object, like a $page or $config or something...

I looked up the code and the function is load($url). Would it be conflicting with something ?

I'm running v2.7.2

Edited by kongondo
merged your topic here, the module's support forum

Share this post


Link to post
Share on other sites

The error says that $rss is not an object, so the call $modules->get doesn't return a module instance. Did you install the module after downloading it?

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