Jump to content
MoritzLost

TrelloWire - Turn your pages into Trello cards

Recommended Posts

TrelloWire

This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.

Features

  • All the things the module can do for you without any custom code:
    • Create a new card on Trello whenever a page is added or published (you can select applicable templates).
    • Configure the target board, target list, name and description for new cards.
    • Add default labels and checklists to the card.
    • Update the card whenever the page is updated (optional).
    • When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable).
  • You can extend this through hooks in many ways:
    • Modifiy when and how cards are created.
    • Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello.
    • Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly.

Feedback & Future Plans

Let me know what you think! In particular:

  • If you find any bugs report them here or on Github, I'll try to fix them.
  • This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it!
  • The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular).
  • I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case!
  • Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂

Links

Module configuration

TrelloWireFullPage.thumb.png.000845648085ad2934da6f34074974e7.png

  • Like 13
  • Thanks 1

Share this post


Link to post
Share on other sites

This sounds great, even though I don't use trello 🙂 A short screencast would be great to get a quick impression 🙂 

  • Like 3

Share this post


Link to post
Share on other sites
28 minutes ago, bernhard said:

This sounds great, even though I don't use trello 🙂 A short screencast would be great to get a quick impression 🙂 

And some background on why you built this would be really interesting too! Looks great!

  • Like 3

Share this post


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

This sounds great, even though I don't use trello 🙂 A short screencast would be great to get a quick impression 🙂 

Thanks! I was hoping the screenshot would do that 😆 Maybe I can give the screencast a go this weekend ... though I'm just now realizing I don't even have a headset any more 😅

1 hour ago, elabx said:

And some background on why you built this would be really interesting too! Looks great!

Lockdown because of Covid-19 mostly 😅

No but really, the README on Github has two examples, and the first one is basically the client project that started this off. This project is a lead generation platform with multiple contact / data collection forms. Our client's team manages all requests on a Trello board. This works really well once everybody is used to it, they use many custom labels and lists to organize all requests / leads. Currently all the new leads are entered manually, but after the relaunch every request will create both a ProcessWire page and a Trello card for the lead. After additional data is entered through one of the forms, the cards are updates with more information and appropriate labels. This is what the status change handling options are for; if the ProcessWire page is trashed, the Trello card can be archived and so on ...

  • Like 3
  • Thanks 1

Share this post


Link to post
Share on other sites

Oh wow! I discovered Trello just last week (yes, more free time during lockdown...). We were planning to use it as a project management tool for my (non-tech) team to enriched the content of the website (yes, again, lockdown...). Basically, I created some lists : "to do", "done", "added to website". The module will allow me to create the page (unpublished) with an automated checklist (text, image, translations), so people will choose one card, assign to self and work on the subject. When everything will be checked, they will move to "done", until I added the new content to the website (I'm the only one having backend access and I want it stay like this).

So for now, it's working. And I like the fact I could add some automatic text without having to copy manually. Could I ask something? I'm not sure I understand what is wirePopulateStringTags
Do I can use this to pull out the creation date or the child pages?
Can it could be possible to add a trigger on "publishing" a page in status change handling?
And last question. I guess via a hook, I should be able to create a button to automating card creation for existing pages?

Thanks a lot!

Mel

  • Like 1

Share this post


Link to post
Share on other sites

Hi @mel47, I'm happy to hear that!

13 hours ago, mel47 said:

So for now, it's working. And I like the fact I could add some automatic text without having to copy manually. Could I ask something? I'm not sure I understand what is wirePopulateStringTags
Do I can use this to pull out the creation date or the child pages?

Yes, you can! You can use this to output fields from the page to the Trello card. For example, by default the card body contains a link to the page: {httpUrl}, this will be the page's url after parsing. You can use both custom fields as well as system fields. For example:

**Page title: {title}**

Page content:

{body}

Page was created at {created}

This approach is somewhat limited. For example, the {created} placeholder will output the raw timestamp, and as far as I'm aware there's no way to change that to a proper date format. But that's why all methods are hookable. For example, if you want to append the (properly formatted) creation date to the body of all cards (when they are created or updated), you can hook TrelloWireCard::setBody:

<?php
// site/ready.php
namespace ProcessWire;

wire()->addHookBefore('TrelloWireCard::setBody', function (HookEvent $e) {
    $body = $e->arguments(0);
    $card = $e->object;
    if ($card->page) {
        $body .= sprintf("\n\nCreated at: %s", date('Y-m-d', $card->page->created));
        $e->arguments(0, $body);
    }
});

You can hook different methods of TrelloWire or TrelloWireCard depending on when you want to modify the cards, there's a complete list of hookable methods in the README.

 

13 hours ago, mel47 said:

Can it could be possible to add a trigger on "publishing" a page in status change handling?

Currently the only things you can do through the module configuration when a page is published is (1) create a new card for this page or (b) restore the card associated with this page if it was previously archived. It's also possible to update the card whenever the page is saved, though that doesn't differentiate between status changes.

If you want to perform a specific action after a page is published (like, for example, tick one of the checklist items), you can do that through hooks and use the TrelloWireApi class to perform the action through the Trello API. If you need some help with that let me know what you want to do!

Quote

And last question. I guess via a hook, I should be able to create a button to automating card creation for existing pages?

Yes, you can create cards manually in your template files. In that case, I would first deactivate the automatic card creation through the configuration. Then you can create cards manually:

// replace with a check for your button
if ($buttonWasClicked) {
    $TrelloWire = $modules->get('TrelloWire');
    $page = wire('page');
    $card = $TrelloWire->buildCardData($page);
    // dont create cards for pages that are already associated with a card
    if (!$card->id) {
        $TrelloWire->createCardForPage($card, $page);
    }
}

Let me know if it's working for you! Something on my To-Do list for this module is to add some "recipes" for stuff like that 🙂

6 hours ago, bernhard said:

That's the old version of https://processwire.com/api/ref/wire-text-tools/populate-placeholders/ and it does what it says: Populate placeholders in a string with corresponding variables (thx for reminding me about that! 😄 ).

I think both methods are equivalent, wirePopulateStringTags just passes through to the populatePlaceholders method. Some of those methods are really well hidden in the documentation, those are super handy and should definitely be more visible!

  • Like 1

Share this post


Link to post
Share on other sites

Hi

Thanks for the answer. For now, I was able to create the button for existing pages. However I'm stuck with triggering after publishing a page. I want to move to a different list.

I'm there now, but I'm missing the part concerning retrieval of the lists. I tried different things but no success, I'm still learning hooks and API, I don't understand everything... 

$this->pages->addHookAfter('publishReady', function(HookEvent $event) {
    $processor = $event->object; 
    $page = $event->arguments('page');
    
    if($page->template != 'content') return;
    
    $TrelloWire = $processor->wire('modules')->get('TrelloWire');
    $card = $TrelloWire->buildCardData($page);
    
    $TrelloWire->moveCard($card->id, ?????);  
});

Thanks for any help

Mel

Share this post


Link to post
Share on other sites
17 hours ago, mel47 said:

I'm there now, but I'm missing the part concerning retrieval of the lists. I tried different things but no success, I'm still learning hooks and API, I don't understand everything... 

You need to know the ID of the list you want to move the card to. To get all lists of a board, you need to know the ID of that board first. In general, you can check the Trello API docs and perform the query you need using the TrelloWireApi class included in the module.

Take note that all the API methods are defined on the TrelloWireApi class, not TrelloWire itself. So you need to use $TrelloWire->api()->moveCard()!

For this particular case, the TrelloWireApi class has a helper method to retrieve both boards and lists associated with your account:

// get the module and the api helper class
$TrelloWire = wire('modules')->get('TrelloWire');
$TrelloWireApi = $TrelloWire->api();

// this will return an array of boards (with name and id)
$boards = $TrelloWireApi->boards();

// alternatively, you can use the target board defined through the module configuration
$boardId = $TrelloWire->TargetBoard;

// this returns an array of lists on the board
$lists = $TrelloWireApi->lists($boardId);

Once of you have the array of lists, take note of it's ID, this is what you need to move a card to it. You can do this dynamically by searching through the array and search for the correct name or whatever, but I'd just dump the array of lists, grab the ID you need and put it in a constant somewhere 🙂 This also saves an API call each time, and those actually have a noticable impact on performance because of network overhead.

$targetId = 'some-id'; // get this ID from the lists() method above!
$TrelloWireApi->moveCard($card->id, $targetId);

Let me know if something isn't working for you!

  • Thanks 1

Share this post


Link to post
Share on other sites

Thanks! Got it! Put it here if someone needed.

const ADDED_BOARD = '';  //put here the id as previously described by MoritzLost

$this->pages->addHookAfter('publishReady', function(HookEvent $event) {

    $processor = $event->object; 
    $page = $event->arguments('page');

    if($page->template != 'content') return;
    
    $TrelloWire = wire('modules')->get('TrelloWire');
	$TrelloWireApi = $TrelloWire->api();
    
    $card = $TrelloWire->buildCardData($page);
    	
	if ($card->id) {
   			 $TrelloWireApi->moveCard($card->id, ADDED_BOARD);
   			 $page->message($this->_('Moved Trello card to "Added" Board'));
	}
});

Mel

  • Like 1

Share this post


Link to post
Share on other sites

@mel47 Great 🤙 Though I think you have mixed up boards and lists; The method TrelloWireApi::moveCard only moves a card to a different list (within the same or a different board). So your constant ADDED_BOARD should probably be named ADDED_LIST instead to avoid confusion!

Share this post


Link to post
Share on other sites

Oups, too newbie with Trello... but it do what I wanted!

  • Like 1

Share this post


Link to post
Share on other sites

Hello @MoritzLost

Found a bug. If you let empty "body" in config, I get this error. Put any text and problem solved.
Except that, everything working fine so far!
Thanks.

image.thumb.png.3c771e518d12cd5275c35a1398764f42.png

Share this post


Link to post
Share on other sites

@mel47 Thanks for the report! I have just pushed a fix for the issue in release 1.0.1. The title and body arguments to TrelloWireApi::createCard() are now nullable, and the body defaults to an empty string if not set. This also means that the Hook for TrelloWireCard::setBody now gets called even if the body is empty, which it wouldn't previously. I have also added a Changelog.

Let me know if you find any more bugs!

Share this post


Link to post
Share on other sites

Looks like a great module. I have it installed (API also looks like connected successfully, but none of the pages are being sent over to Trello as cards. All the  Is there a log that shows API requests or does anyone have a suggestion?

  • Like 1

Share this post


Link to post
Share on other sites

@maddmac Unfortunately, I recently started having problems with the Trello API as well, and right now I'm not sure that the module will work correctly. I have asked the support if they have changed something in their API-backend, but nothing came of it. Anyway, I have discovered some minor problems with the way the module sends it's requests as well as some major problems with ProcessWire's WireHttp class which prevents the module from connecting to the Trello API using cURL. Unfortunately, I wasn't able to get it to work using sockets or fopen as well. Now, I have submitted a pull request to ProcessWire's core that fixes the issues with the WireHttp class, but as of now it hasn't been merged yet. I have also started work on fixing the issues with the module itself - the dev version is available as a separate branch on Github. The problem is that this branch won't work at all without the fixes to the WireHttp class included in the pull request.

So right now, I'm not sure how to put out a release that will work for everyone. The likely path it that I will have to wait until the pull request is merged, and then push out a new release that includes all the related fixes, updating the required ProcessWire version to whichever version the pull request is available in.

Unfortunately, the only surefire way to get the module working correctly at the moment is to (1) apply the changes from my pull request to your installation of ProcessWire and (2) manually download the dev version from this branch of the TrelloWire module.

Sorry I can't provide a better solution at the moment. I'll keep this thread updated as soon as I can solve those issues!

BTW I also plan to add more logging / error reporting, but I first want to get the module working properly again ...

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites

Thank you sir. I've patched my install with your updates and its working. I haven't seen any issues caused by your changes to the core yet but I'll keep my eyes open. This could be a game changer for our process. 

  • Like 1

Share this post


Link to post
Share on other sites

@maddmac That's great, good to know it's working in other environments as well ^^ Let me know if you run into any problems!

Share this post


Link to post
Share on other sites

Now that I have been playing around with this. I realized that I would like to utilize custom fields within the cards. Being able to send attached fields from the chosen PW template would make a great addition. Hoping this may be accomplished by a hook.

Fond this 

https://stackoverflow.com/questions/49458850/setting-custom-field-values-on-a-card-with-the-trello-api

Share this post


Link to post
Share on other sites

@maddmac Thanks for the suggestion! As far as I can tell from the documentation on creating cards, custom fields can't be send in the same POST request the card is created with. But you can utilize a hook to add custom fields whenever a card is created / updated (see the hook documentation for the module). Something like this:

wire()->addHookAfter('TrelloWire::createCardForPage', function (HookEvent $e) {
	$TrelloWire = $e->object;
	$page = $e->arguments(1);
	$TrelloWireCard = $TrelloWire->buildCardData($page);
	
	$api = $TrelloWire->api();
	$cardId = $TrelloWireCard->id;
	$customFieldId = 'id-of-the-custom-field'; // replace with actual custom field id
	$api->put(
		sprintf('cards/%1$s/customField/%2$s/item', $cardId, $customFieldId),
		['custom-field-data' => $page->my_custom_field]
	);
});

Quick and untested, might need some adjustments. I haven't worked with custom fields yet, so I'm not sure what data a custom fields needs (the documentation is also handwavy about it), but this should be a good starting point.

A the moment this will only work correctly with the dev version of the module (branch JSON-request-body on Github) and with a core that includes the pull request mentioned above.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

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

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...